Unable to save crew assignments

[Masaq]

I have been running HCS - Singularity (Elite Odyssey) with just the ASTRA voice pack without any issues. I decided to add another pack (HELIX) and assign stations for my two crew members. The assignments last as long as I have VoiceAttack open, but as soon as I close it the assignments are lost and all deafault to Astra.
On startup VoiceAttack tells me I have 2 crew members aboard, but Astra has all stations covered.
I have uninstalled everything related to HCS, uninstalled VoiceAttack, reinstalled everything again but have exactly the same issue.
The first time I did this I installed Helix before Astra, and Helix became the default.
I haven't been able to find an answer to this. Does anyone have any ideas?
Thanks in advance.

[Gangrel]

In the voice attack settings -> First tab, do you have voice attack set to load a specific profile on startup?

In the voice attack settings -> First tab, do you have a global profile assigned?

Also: How are you assigning the crew members? By voice or by using the HCS Customiser (The Stations buttons) ?

[Masaq]

Firstly, thanks for the reply.

VoiceAttack is set to load HCS - Singularity (Elite Odyssey) on startup.
Global profiles is set to None.
I have been assigning the crew using the buttons in the customiser.

[Gangrel]

The "Load profile on start up" should be set to NONE.

VA will always automatically load the last active profile on start up in the first place anyway. If you had assigned the profile to load on start up from a while back, then this could explain as to why the settings are "not sticking".

[Masaq]

Thanks.
I set "Load profile on start up" to None, but the same issue is ocurring.
I am running Windows 11, so I tried running in compatability mode in case that might be the cause, but it hasn't helped. I am running Voiceattack as Administrator.

[Gangrel]

Thanks.
I set "Load profile on start up" to None, but the same issue is ocurring.
I am running Windows 11, so I tried running in compatability mode in case that might be the cause, but it hasn't helped. I am running Voiceattack as Administrator.

OK, if you are doing it under "The Stations" setting, we have noted an issue where it will not be applying them if the number 1 role is *unchanged*

This is fixed internally and will be pushed out soonish.

[Masaq]

Thanks for the update.
Just so I'm clear; are you saying that if I change the number 1 role then the changes should stick? This isn't the behaviour that I'm seeing. Whichever voice I set to number 1, it always reverts back to one voice for all roles.

[Gangrel]

What follows comes from internal discord discussion about the issue (or similar to what you have experienced)

The settings for Operations role was duplicated (and didn't have an engineering role to be saved). The Operations role was also assigned to the Engineering dropdown.

There was also a bug in that it was only setting them if the change was different to the Number1 role.

This has been fixed internally and will be in the next update.