parent
da60d3cc4d
commit
98b5ae52ca
2 changed files with 32 additions and 7 deletions
|
@ -1,5 +1,14 @@
|
|||
# devel
|
||||
|
||||
Updated the “Updating” instructions in the README. Sadly it’s a bit more
|
||||
convoluted in practice than just “import the new profile package”.
|
||||
|
||||
I have submitted a feature request on the VA formus to make it less of a hassle
|
||||
in the future. Until there’s a better way I will include all profiles that have
|
||||
been updated on the release pages in addition to the profile package. That way
|
||||
you only have to go through the process of deleting the old profile, importing
|
||||
the new one and fixing the includes for profiles that have actually changed.
|
||||
|
||||
## EliteDangerous 6.0.2
|
||||
|
||||
### Fixed
|
||||
|
|
30
README.md
30
README.md
|
@ -132,14 +132,30 @@ likely just ignore them.
|
|||
|
||||
## Updating ##
|
||||
|
||||
If you have followed the steps outlined above closely, updating will be
|
||||
exceedingly simple: just download the new VoiceAttack package, import, done!
|
||||
Sadly VoiceAttack doesn’t let you overwrite an existing profile when you import
|
||||
a different (newer) version of it. So you’ll have to follow these steps:
|
||||
|
||||
Should VoiceAttack report any conflicts, either tell it to overwrite the
|
||||
commands or start from a clean slate by deleting the profiles manually and then
|
||||
re-importing. Again, if you have followed the recommended installation
|
||||
guidelines this will not cause you to lose any settings or changes you have
|
||||
made.
|
||||
1. Look at the release page and see which profiles have been updated (they’ll
|
||||
also be attached as single `.vap` files to the release)
|
||||
1. Delete these profiles from your VoiceAttack.
|
||||
1. Import the updated profiles.
|
||||
1. Fix all profiles that include the updated profiles. You are going to have to
|
||||
re-add the includes (“Edit Profile” → “Options” → “Include commands from
|
||||
other profiles”).
|
||||
|
||||
You could also delete _all_ the profiles, then re-import the entire release
|
||||
package (the `.vax` file). You will still have to fix the includes.
|
||||
|
||||
If you have followed the installation instructions above, you will not lose any
|
||||
of the changes you have made since they will be in a separate profile. **Do not
|
||||
delete** that profile!
|
||||
|
||||
If you delete anything by accident or something didn’t work out quite like you
|
||||
intended, you can find backups of VoiceAttacks data file in
|
||||
`%AppData%\VoiceAttack\Backup`. They get saved every time you change settings or
|
||||
profiles. To restore, close VoiceAttack, find the file with the right timestamp
|
||||
just before you made the changes, copy it to the parent directory, remove the
|
||||
old “VoiceAttack.dat” file and rename the backup to that.
|
||||
|
||||
### Major Version Changes ###
|
||||
|
||||
|
|
Loading…
Reference in a new issue