With each minor patch to Elite Dangerous after 3.3, the Singularity Profile and VA are becoming less and less reliable.
I have three packs installed: Eli, Orion, and Verity. I primarily use a mix of the first two, usually Eli manning all stations except for Science and Tactical, which are assigned to Orion.
Since 3.3.02, if I have Orion in charge of all stations, he can not execute a Discovery Scan successfully. It will toggle the HUD mode to Combat mode (where the DS won't work) and then either remain in Combat Mode or switch back to Analysis Mode when it's done, depending on what mode it was in first. So no matter what mode I start in, he'll always switch to the wrong one and fail to scan. Once I switched back to Eli in all stations save for Science and Tactical, this problem went away... sort of. If in Combat HUD, it will switch to Analysis and do the scan, and then switch back to Combat HUD as it should. However, if in Analysis HUD when command is issued, it will switch to Combat HUD, fail to scan, and then switch back to Analysis.
And it just gets worse from there. If I tell it to switch to Analysis HUD, it will toggle the HUD to the other mode - it doesn't even check to see what mode it is in. Further, the command to switch to "Combat Mode" always ends in a reply "That's already done" and does nothing. So I have to use "Analysis Mode" command to switch modes like a toggle and Eli is completely unaware of the mode he's in.
Now the problem has spread to the landing gear. The deploy command works. The retract command sometimes works and other times doesn't with the response "That's already done" when it isn't. The Departure Handover command will successfully retract the gear as part of its routine. The landing gear issue is hit or miss, with no apparent pattern.
Retracting Weapons never works anymore. I'm always told "That's already done" when it isn't.
I had to turn off "Invoke actions" because any time I dropped out of Super Cruise, he asked if I wanted to deploy the landing gear! I'm in deep space! No!
The weird thing about all this is everything was working perfectly when 3.3 was first released. With each successive micropatch, the Singularity profile responds in an increasing erratic manner. Is there someway to reset the state it is reading in from the game (or failing to read in)? "Run Diagnostics" doesn't fix this issue.
The worst bug of all hits when I try to target a subsystem. It's only happened once, when I tried target the NPC's Frameshift drive. The command macro cycled through the subsystems and then kept going back and forth between two choices (couldn't tell whether either was the Frameshift Drive). When I tried to alt-tab out to kill VoiceAttack and restart it, my computer became unresponsive. I couldn't even bring up task manager to kill the process. Only choice I had was to do ctrl-alt-del and then choose sign out to close everything. Not fun.
And before you ask: VA was installed as admin. HCS voicepacks were installed as admin; registry keys for each pack that was installed under admin (during installation) were exported to my user account so they work fine. Game was installed as admin. However, all have been run under my user account for as long as I've had them (3+ years for Elite, 2.5 years for VA+HCS).
I have three packs installed: Eli, Orion, and Verity. I primarily use a mix of the first two, usually Eli manning all stations except for Science and Tactical, which are assigned to Orion.
Since 3.3.02, if I have Orion in charge of all stations, he can not execute a Discovery Scan successfully. It will toggle the HUD mode to Combat mode (where the DS won't work) and then either remain in Combat Mode or switch back to Analysis Mode when it's done, depending on what mode it was in first. So no matter what mode I start in, he'll always switch to the wrong one and fail to scan. Once I switched back to Eli in all stations save for Science and Tactical, this problem went away... sort of. If in Combat HUD, it will switch to Analysis and do the scan, and then switch back to Combat HUD as it should. However, if in Analysis HUD when command is issued, it will switch to Combat HUD, fail to scan, and then switch back to Analysis.
And it just gets worse from there. If I tell it to switch to Analysis HUD, it will toggle the HUD to the other mode - it doesn't even check to see what mode it is in. Further, the command to switch to "Combat Mode" always ends in a reply "That's already done" and does nothing. So I have to use "Analysis Mode" command to switch modes like a toggle and Eli is completely unaware of the mode he's in.
Now the problem has spread to the landing gear. The deploy command works. The retract command sometimes works and other times doesn't with the response "That's already done" when it isn't. The Departure Handover command will successfully retract the gear as part of its routine. The landing gear issue is hit or miss, with no apparent pattern.
Retracting Weapons never works anymore. I'm always told "That's already done" when it isn't.
I had to turn off "Invoke actions" because any time I dropped out of Super Cruise, he asked if I wanted to deploy the landing gear! I'm in deep space! No!
The weird thing about all this is everything was working perfectly when 3.3 was first released. With each successive micropatch, the Singularity profile responds in an increasing erratic manner. Is there someway to reset the state it is reading in from the game (or failing to read in)? "Run Diagnostics" doesn't fix this issue.
The worst bug of all hits when I try to target a subsystem. It's only happened once, when I tried target the NPC's Frameshift drive. The command macro cycled through the subsystems and then kept going back and forth between two choices (couldn't tell whether either was the Frameshift Drive). When I tried to alt-tab out to kill VoiceAttack and restart it, my computer became unresponsive. I couldn't even bring up task manager to kill the process. Only choice I had was to do ctrl-alt-del and then choose sign out to close everything. Not fun.
And before you ask: VA was installed as admin. HCS voicepacks were installed as admin; registry keys for each pack that was installed under admin (during installation) were exported to my user account so they work fine. Game was installed as admin. However, all have been run under my user account for as long as I've had them (3+ years for Elite, 2.5 years for VA+HCS).
Comment