Discovered bugs with the start of chapter 4

[Arty-1975]

I confirm the issue from post #17 and #45. Despite having changed any bind using L/R ALT/CTRL (4 combo's) into a combination of something else (simpler), the problem remains of processing Toggle Commands (Lights on/off) which leads to "That's already done" after requesting the first toggle ("on") and then followed with the second request ("off).

Meanwhile, ED has been updated, so we're talking here 2 updates (variables) to see what's going on: ED update and Singularity update.
I re-installed the previous HCS (part of Voice Packs dated Dec 2018), which worked fine back then, yet I got the same problem ("That's already done" on Toggle Commands). Back to the latest.

My conclusion is that ED has changed something internally that conflicts with VA and/or Singularity. Am sure HCS will work it out.

Edit:
I found a website that might be related (cause?) to this issue:
https://forums.frontier.co.uk/showth...ctrl-modifiers
Has ED changed the way it reads certain inputs?
Has Singularity gotten a bug regarding reading ED's (new?) I/O method?
Is Singularity (now) sending and/or reading invalid/outdated codes with the last ED update?

Unfortunately, and understandably, Singularity code is signed against debugging.

[Gangrel]

I confirm the issue from post #17 and #45. Despite having changed any bind using L/R ALT/CTRL (4 combo's) into a combination of something else (simpler), the problem remains of processing Toggle Commands (Lights on/off) which leads to "That's already done" after requesting the first toggle ("on") and then followed with the second request ("off).

Meanwhile, ED has been updated, so we're talking here 2 updates (variables) to see what's going on: ED update and Singularity update.
I re-installed the previous HCS (part of Voice Packs dated Dec 2018), which worked fine back then, yet I got the same problem ("That's already done" on Toggle Commands). Back to the latest.

My conclusion is that ED has changed something internally that conflicts with VA and/or Singularity. Am sure HCS will work it out.

Edit:
I found a website that might be related (cause?) to this issue:
https://forums.frontier.co.uk/showth...ctrl-modifiers
Has ED changed the way it reads certain inputs?
Has Singularity gotten a bug regarding reading ED's (new?) I/O method?
Is Singularity (now) sending and/or reading invalid/outdated codes with the last ED update?

Unfortunately, and understandably, Singularity code is signed against debugging.

Try running VA as admin, ED did something to change how the file is meant to be read (it appears)

[Arty-1975]

Done that. Ran quite a few tests today (4, actually 8) to attempt to isolate the issue of "Toggle" based (ie. gear, light, cargo-scoop, etc) errors.

Test
Run VA first as non-admin user and then as admin user to see if that makes any difference. Use Notepad as target window to catch VA's output meant for ED for Toggle based commands. In all tests there are no messages of any missing keybinds: the Missing Keybinds check comes back clean.

Installed HCS Tools v1.01 and imported Singularity in VA, restarted VA as per installation instructions.
VA starts with version indicators Plugin v3.01 and Singularity v2.02
Both tests show the same outcome (described below).
Uninstalled HCS Tools v1.01

Installed HCS Tools v1.02 and imported Singularity in VA, restarted VA as per installation instructions.
VA starts with version indicators Plugin v3.02 and Singularity v2.03
Both tests show the same outcome (described below).
Kept HCS Tools v1.02

So far, these 4 testing combo's (v1.0x in admin and non-admin modes) were expanded to see if either the Plugin or Singularity might be an issue:

• ran the old version (v1.01, with Singularity v2.02) and used the newer Plugin v3.02 too (pasted into place and used in VA)
• ran the new version (v1.02 with Singularity v2.03) and used the older older Plugin v3.01 too (pasted into place and was used in VA)

In each of the 8 test scenario's, Notepad was used to catch the output (keyboard entries) as set in ED (Toggle):

• L - Landing Light On/Off
• G - Gear Down/Up
• C - Cargo Scoop (Deploy/Retract)

Outcome
Running the test in all 8 (eight) scenarios led to the same output:
ANY initial commands (L/G/C ) was caught in notepad properly (and shown in ED to work!), but ANY subsequent counter command (Gear Down now Gear Up), did NOT lead to catching the same character again, but for each new L/G/C request VA only kept saying "That's already been done." No output caught in Notepad, as if the command wasn't sent out. Does Singularity think that it's the same (repeat) request as before and hence defaults to "That's already been done"?

Other checks:

• I verified my KeyboardLayout and system settings from the binds in "HCS Voice Pack Plugins\ControlSchemes" and they match. This was based on: http://forum.hcsvoicepacks.com/forum...eyboard-layout
• I checked my system settings in Windows10 to see if there's anything that could interfere with keyboard entries (auto-correct, text suggestions, you name it) and turned them all OFF.

In any possible combination (admin/non-admin/versions/System Settings) it seems that Singularity is not "moving on" after a request for a Toggle, ie Gear Down, because the next request for Gear Up is only answered with "That's already been done" without any further key sent to Notepad (meant for ED). Is she out of sequence, stuck?

I remember it all used to work end of last year (Nov-Dec 2018), perhaps on an earlier version, or is it just my rig?