Command "xxx" is currently disabled for this session and was not executed.[BUG]

[Jayhawk1971]

Hello everyone,

after updating to the community fix 2.8.0., I get this VoiceAttack message after any voice commands:

Command 'xxx' is currently disabled for this session and was not executed. For example: 6:58:27.499 Command 'navigate steerpoint 1' is currently disabled for this session and was not executed. 6:58:27.489 Recognized : 'navigate steerpoint 1'

This seems to be an older problem that apparently must have been introduced after VAICOM version 2.5.24, I personally never experienced it until now.

A "workaround" is to keep pressing the (any) TX button until the "confirmation beep" can be heard, after which the command is being executed.

So, press TX -> speak command -> wait for "beep" -> release TX -> command is being executed.

"Normal" behavior would be either press TX -> issue command -> release TX -> beep and execution. Or, with ICS set to "hot", VAICOM is "always listening".

Could the community please have a look at this so that it works as it used to, especially WRT the ICS hot mic function to interact with Jester without the need for PTT?

Thanks.

[Silverit0]

To add something more to what Jayhawk comments. The following happens to me: The first command fails and the second does not fail and the third fails again and the fourth does not fail and so on, one yes, one no. I have observed that this happens when the simulator is running, if, for example, I stop it by pressing ESC and I am in the DCS options menu, curiously, SENDING COMMANDS NEVER FAILS (it never appears: "currently disabled for this session and was not executed"). The simulator is interfering with the proper functioning of Vaicom for some reason that I do not know.

[rcflyinghokie]

Just curious how many official modules do you have installed? We are tracking this sort of behavior with X number installed.

[Silverit0]

Specifically I have two modules

[rcflyinghokie]

Sounds like a bad install as I still cannot replicate this issue

[Jayhawk1971]

Just curious how many official modules do you have installed? We are tracking this sort of behavior with X number installed.

Including FC3, I have 9 modules installed (or 10, if A-10C II counts as a standalone), excluding maps.

There's a thread over at the DCS forum, started in June 2021, by MAXSenna, if that helps shed more light to the problem: https://forum.dcs.world/topic/273962-command-disabled-for-this-session-and-was-not-executed/

[Silverit0]

Me, two aircraft and 3 theaters. The rest comes by default.

[rcflyinghokie]

Log files (dcs and vaicom,) vaicom settings, and the mission aircraft being used when you reproduce it would be useful in further diagnosis, I am unable to reproduce the issue.

[Silverit0]

My log file: 1:59:43.003 Scanning for new theater. 1:59:43.003 No new ATCs were found. 1:59:43.021 Adding themepack collections 1:59:43.021 Chatter theme set to NATO 1:59:43.021 Adding chatter resources.. NATO 1:59:43.055 Resources added. 1:59:43.055 Chatter initialized. 1:59:43.177 ------------------------------------------ 1:59:43.178 DCS mission | F-16C - Caucasus - Ready on the Ramp 1:59:43.178 Resetting selected units. 1:59:43.178 Player Silver entered module F-16C Viper, unit callsign Colt11 1:59:43.178 Nearest ATC: Gudauta. 1:59:43.178 Scanning for new theater. 1:59:43.178 No new ATCs were found. 1:59:43.179 Adding themepack collections 1:59:43.179 Chatter theme set to NATO 1:59:43.179 Adding chatter resources.. NATO 1:59:43.179 Resources added. 1:59:43.180 Chatter initialized. 1:59:51.831 Joystick : 'Transmit TX1 press' 1:59:52.083 ------------------------------------------ 1:59:52.083 DCS mission | F-16C - Caucasus - Ready on the Ramp 1:59:52.084 Resetting selected units. 1:59:52.084 Player Silver entered module F-16C Viper, unit callsign Colt11 1:59:52.084 Nearest ATC: Gudauta. 1:59:52.084 Scanning for new theater. 1:59:52.084 No new ATCs were found. 1:59:52.085 Adding themepack collections 1:59:52.085 Chatter theme set to NATO 1:59:52.085 Adding chatter resources.. NATO 1:59:52.085 Resources added. 1:59:52.086 Chatter initialized. 1:59:52.088 TX1 | AN/ARC-164 AM 305.000 MHz: no tuned units. 1:59:52.726 Joystick : 'Transmit TX1 release' 1:59:56.938 Joystick : 'Transmit TX1 press' 1:59:57.032 TX1 | AN/ARC-164 AM 305.000 MHz: no tuned units. 1:59:59.531 Recognized : 'recues rearmin' %%% (* GOES WELL***) 1:59:59.547 Captured sentence: recues rearmin 1:59:59.549 Have result, identified as command: Recues rearmin 1:59:59.562 Recipient for Crew set by call contents. 1:59:59.564 TX1 | AN/ARC-164: [ Ground Crew ] , [ Request Rearming ]
1:59:59.566 Constructing message... 1:59:59.569 Done. 2:00:00.213 Joystick : 'Transmit TX1 release' 2:00:04.381 Joystick : 'Transmit TX1 press' 2:00:04.485 ------------------------------------------ 2:00:04.485 DCS mission | F-16C - Caucasus - Ready on the Ramp 2:00:04.485 Resetting selected units. 2:00:04.485 Player Silver entered module F-16C Viper, unit callsign Colt11 2:00:04.486 Nearest ATC: Gudauta. 2:00:04.486 Scanning for new theater. 2:00:04.486 No new ATCs were found. 2:00:04.487 Adding themepack collections 2:00:04.487 Chatter theme set to NATO 2:00:04.487 Adding chatter resources.. NATO 2:00:04.487 Resources added. 2:00:04.488 Chatter initialized. 2:00:04.488 TX1 | AN/ARC-164 AM 305.000 MHz: no tuned units. 2:00:06.464 Recognized : 'recues rearmin' 2:00:06.468 Command 'recues rearmin' is currently disabled for this session and was not executed. % ( DOESN´T GO **) 2:00:07.439 Joystick : 'Transmit TX1 release' 2:00:08.599 Joystick : 'Transmit TX1 press' 2:00:08.708 TX1 | AN/ARC-164 AM 305.000 MHz: no tuned units. 2:00:10.720 Recognized : 'recues rearmin' %%% (*** GOES WELL**) 2:00:10.728 Captured sentence: recues rearmin 2:00:10.728 Have result, identified as command: Recues rearmin 2:00:10.729 Recipient for Crew set by call contents. 2:00:10.729 TX1 | AN/ARC-164: [ Ground Crew ] , [ Request Rearming ]
2:00:10.729 Constructing message... 2:00:10.729 Done. 2:00:11.254 Joystick : 'Transmit TX1 release' 2:00:13.106 Joystick : 'Transmit TX1 press' 2:00:13.238 ------------------------------------------ 2:00:13.238 DCS mission | F-16C - Caucasus - Ready on the Ramp 2:00:13.239 Resetting selected units. 2:00:13.239 Player Silver entered module F-16C Viper, unit callsign Colt11 2:00:13.239 Nearest ATC: Gudauta. 2:00:13.239 Scanning for new theater. 2:00:13.239 No new ATCs were found. 2:00:13.240 Adding themepack collections 2:00:13.240 Chatter theme set to NATO 2:00:13.240 Adding chatter resources.. NATO 2:00:13.240 Resources added. 2:00:13.240 Chatter initialized. 2:00:13.241 TX1 | AN/ARC-164 AM 305.000 MHz: no tuned units. 2:00:15.305 Recognized : 'recues rearmin' 2:00:15.322 Command 'recues rearmin' is currently disabled for this session and was not executed. %(DOESN´T GO**) 2:00:15.937 Joystick : 'Transmit TX1 release' 2:00:17.466 Joystick : 'Transmit TX1 press' 2:00:17.571 TX1 | AN/ARC-164 AM 305.000 MHz: no tuned units. 2:00:19.578 Recognized : 'recues rearmin' 2:00:19.582 Captured sentence: recues rearmin 2:00:19.583 Have result, identified as command: Recues rearmin 2:00:19.583 Recipient for Crew set by call contents. 2:00:19.583 TX1 | AN/ARC-164: [ Ground Crew ] , [ Request Rearming ]
2:00:19.583 Constructing message... 2:00:19.584 Done. 2:00:20.030 Joystick : 'Transmit TX1 release' 2:00:22.849 Recognized : 'shell' 2:00:22.854 Command 'shell' is currently disabled for this session and was not executed.

---

The mission is Instant Action , Ready on Ramp aircraft=F16 Please dont put "Unable to Reproduce" without try all this. I put labels in the VoiceAttack's log like "Goes" and "Doesn´t go" to see the moment of the fail. We are several people who have this same problem. Sometimes it goes, and other times it doesn't. So always. This happens with any message you send it. It doesn't have to be exactly the one in the example ("Request Rearming")

dcs.log

[rcflyinghokie]

I will keep unable to reproduce as I am unable to reproduce this issue with the information given. Looks to me though you have either the wrong TX node or wrong frequency selected.

Again what are your vaicom settings?

[Silverit0]

[rcflyinghokie]

You have the wrong DCS folder selected for your path. Rehook DCS to just the DCS World OpenBeta folder, not the bin, by clicking fix reg, verifying your sliders, and hitting the SET button and navigation to that folder instead of the bin folder within. Then reset the lua.

[Jayhawk1971]

Here's my VA log:

6:58:50.849 Command 'ready for takeoff' is currently disabled for this session and was not executed. 6:58:50.837 Recognized : 'ready for takeoff' 6:58:50.413 Joystick : 'Transmit TX1 release' 6:58:49.153 TX1 | UHF ARC-159 AM 225.000 MHz tuned for AAR unit Texaco1-1 [AI] 6:58:48.262 Joystick : 'Transmit TX1 press' 6:58:27.499 Command 'navigate steerpoint 1' is currently disabled for this session and was not executed. 6:58:27.489 Recognized : 'navigate steerpoint 1' 6:58:21.459 Joystick : 'Transmit TX6 release' 6:58:19.336 Joystick : 'Transmit TX6 press' 6:58:19.154 Listening resumed 6:58:18.731 Joystick : 'Transmit TX6 release' 6:58:17.892 Joystick : 'Transmit TX6 press' 6:57:57.853 Allied Flight (Texaco1-1): Texaco1-1, on station at bulls 359 for 70 at 15000 6:57:49.623 Allied Flight (Texaco1-1): Texaco1-1, passing waypoint 1 at 15000 6:57:20.189 Listening resumed 6:57:19.691 Chatter initialized. 6:57:19.690 Resources added. 6:57:19.690 Adding chatter resources.. NATO 6:57:19.689 Chatter theme set to NATO 6:57:19.689 Adding themepack collections 6:57:19.664 No new ATCs were found. 6:57:19.663 Scanning for new theater. 6:57:19.662 Nearest ATC: Nellis. 6:57:19.662 Player Ghost entered module F-14AB Tomcat, unit callsign Colt11 6:57:19.661 Resetting selected units. 6:57:19.657 DCS mission | F-14B_IA_NTTR_take_off 6:57:19.656 ------------------------------------------

My VAICOM settings:

VAICOM diag:

[Silverit0]

You have the wrong DCS folder selected for your path. Rehook DCS to just the DCS World OpenBeta folder, not the bin, by clicking fix reg, verifying your sliders, and hitting the SET button and navigation to that folder instead of the bin folder within. Then reset the lua.

In the multiple attempts I have made, I have left this incorrectly configured, I have set it correctly but I continue with the same problem. That was not the solution, thanks anyway.

[rcflyinghokie]

Instead of troubleshooting here, pop on discord and we can see if we can further diagnose. I still cannot reproduce the issue with your settings and the mission you describe.

[Jayhawk1971]

I believe I've found a solution to the problem.

In VAICOM, go to the PTT page and ensure that the RELEASE HOT feature is disabled (light is off - the light is a clickspot, so just click on it to turn on/off).

Turning RELEASE HOT off returned VAICOM Pro to work as it was supposed to for me. ICS HOT is also working.

I suppose the 2.8.0 patch (or the patching process) turned the function on, and since I never had to mess with this before I did not even consider this. I wasn't even aware that once could click on the light.

Anyway, Silverit0, I recommend you try that and let us know if it helped.

[Silverit0]

I read this solution on another forum but it didn't help me, anyway thank you very much for your effort. When I hit ESC and the DCS menu appears all commands are recognized without exception. Inside the plane one yes and one no. Another thing is that I installed the .msi version, I don't know if this will influence. thx VAICOMPRO.log

[rcflyinghokie]

I read this solution on another forum but it didn't help me, anyway thank you very much for your effort. When I hit ESC and the DCS menu appears all commands are recognized without exception. Inside the plane one yes and one no. Another thing is that I installed the .msi version, I don't know if this will influence. thx VAICOMPRO.log

It working with the ESC menu up tells me you might not be running DCS or VA as an admin. Also if you used the recent MSI version, check and see that your dll files are in the correct place.

[rcflyinghokie]

I believe I've found a solution to the problem.

In VAICOM, go to the PTT page and ensure that the RELEASE HOT feature is disabled (light is off - the light is a clickspot, so just click on it to turn on/off).

Turning RELEASE HOT off returned VAICOM Pro to work as it was supposed to for me. ICS HOT is also working.

I suppose the 2.8.0 patch (or the patching process) turned the function on, and since I never had to mess with this before I did not even consider this. I wasn't even aware that once could click on the light.

Anyway, Silverit0, I recommend you try that and let us know if it helped.

Nothing in the new update forced that on, at least on mine it certainly isn't forced on, but good catch regardless as it being triggered on is a good datapoint!

[Silverit0]

I read this solution on another forum but it didn't help me, anyway thank you very much for your effort. When I hit ESC and the DCS menu appears all commands are recognized without exception. Inside the plane one yes and one no. Another thing is that I installed the .msi version, I don't know if this will influence. thx VAICOMPRO.log

It working with the ESC menu up tells me you might not be running DCS or VA as an admin. Also if you used the recent MSI version, check and see that your dll files are in the correct place.

DCS is running but not into the sim but with the general menu open. Of course VA with admin rights.

[rcflyinghokie]

I read this solution on another forum but it didn't help me, anyway thank you very much for your effort. When I hit ESC and the DCS menu appears all commands are recognized without exception. Inside the plane one yes and one no. Another thing is that I installed the .msi version, I don't know if this will influence. thx VAICOMPRO.log

It working with the ESC menu up tells me you might not be running DCS or VA as an admin. Also if you used the recent MSI version, check and see that your dll files are in the correct place.

DCS is running but not into the sim but with the general menu open. Of course VA with admin rights.

Can you clarify this sentence, I would hope DCS is running...

[Silverit0]

In this menu al goes like a champ. In flight no goes well. I hope that is clear.

[rcflyinghokie]

Still sounds like a bad DCS hook, I cannot replicate this with any dat you all have provided

[Silverit0]

Sorry but If it was that I would never go.

[rcflyinghokie]

Sorry but If it was that I would never go.

Please come to the discord to further troubleshoot this, I think the back and forth is getting nowhere with this issue and we can get more brains and testers on it there...if we find something out we can post it in here but this is not meant to be a troubleshooting venue to this extent.

[Silverit0]

Problem solved 😎😎. Thanks you anyway. I switch to Dynamic Switching and all the problems solved. 🤣🤣🤣 Simple but I don't understand why this happens.

[Penecruz]

Closing as individual install issue.