hornblower793

Have you got the latest version of the AIRIO extension installed?

I haven't tried this, but now seem to have problems getting the FW-190 (either variant) recognised in VAICOM until I press the keyboard PTT button. It then shows as the module in the VAICOM config screen but does not respond without a delay (or not at all and the RLY light in VAICOM does not come on) EDIT: Having tried some more this seems to be an issue with Instant Action missions (I have only tried free flight). When trying from my own missions modules seem to pick up fine and select does not cause an issue.

Good call - I have tried both the P47D and the KA-50 now. I mapped the PTT options in both planes to single keys and pressing these cleared the delays. Commands then worked perfectly until the next Select commands when the delay re-appears. Pressing key again cleared this

Have just tested with the latest hotfix for VAICOM and still have the same issues. I did notice that once I had been in the KA-50 (which has delayed responses from the start) and switched straight to another of the modules I have issues with they would also be delayed response from the start. If I switched to the A10c quickly and then the P47D this cleared the problem until select was used again.

The plane should reappear when you have closed the wheel Sent from my SM-T835 using Tapatalk

Will be interesting to see how well the lists correlate - i have always found ATC to be temperamental at the best of times..... Sent from my SM-T835 using Tapatalk

I have now run quick tests on all the modules I own (excluding FC3 aircraft). The following modules seemed to work fine: A10c, AV8B, C101, F14, F16, F18, JF17, M2000c, MiG-21Bis, Mi-8, MiG-15, MiG-19P, P51D, Spitfire, UH-1H The following modules seemed to work fine until I used a Select command at which stage they all suddenly experienced delays: BF-109 (expected as it is down as a known issue module), F86, FW190-A8, FW190-D9, KA-50, P47D-30 The method of testing used for each airframe was to: select a free flight from the instant mission, active pause the module as soon as the mission started so I didn't have to worry about flying, call inbound and wait for text to appear top right, use options and work through the menu options, use Select command to pick an airbase, call inbound and wait for text to appear top right, use options and wait for the menu to appear I also tried removing the 2 Radio Control options from the VAICOM profile to see if this would make any difference and it didn't appear to. I have also tried resetting the LUA files, after running a DCS repair. All on latest standalone OB

Have now tried with the KA-50 and can confirm that I also have a delay. The delay is exactly 60 seconds between VAICOM beeping to say it has recognised the command and the text appearing on screen (either my command and the response in the top left corner or the menu top right if I use options). This is so regular it seems like it might be either a timeout value or an inbuilt delay. Will now try some other craft and see what happens

I tried this at lunchtime using the P-47 and initially had issues. Resetting the lua coda and importing a clean VAICOM profile / repeating Finish steps seems to have cleared it for me. A few things I noticed which may help as well: 1. Issuing a lot of commands quickly to select menu options seemed to cause an issue 2. Getting the steps out of order can confuse it (e.g. Take before options) 3. The menu sometimes stays up when the ATC responds to inbound. Saying Take 12 before releasing the PTT clears this. If you don't clear (you can use the F12 key as well) before saying the next command the system gets confused. The last point is interesting as the menu only appeared / stayed up in about 50% of my tries. Will test more extensively later to see how it works over an extended period Sent from my SM-T835 using Tapatalk

This is a symptom because I also used to get it. Sent from my SM-T835 using Tapatalk

As MAXSenna says, TX6 is there for possible use in the future according to the manual. TX5 is Intercom but also works for ground crew in some modules Sent from my SM-T835 using Tapatalk

Understood - will have a try later and see if I can give you any other pointers Sent from my SM-T835 using Tapatalk

I can also register zero fine but had the exact issue you describe until i changed to 'Oh' Sent from my SM-T835 using Tapatalk

Have you tried saying 'Oh' rather than zero as I had a similar problem but this fixed it for me. I am at work at the moment but will try and work out the cadence I use later Sent from my SM-T835 using Tapatalk

I have done it by changing tune to freak in the command and then using 'Oh' rather than zero. Now works very reliably and you can just say the phrase Sent from my SM-T835 using Tapatalk

I think the problem is different people would like different things. I certainly would not want the wheel appearing each time I talk to Jester Sent from my SM-T835 using Tapatalk

Have you tried resetting the database and / or using the export function to get a clean profile? Sent from my SM-T835 using Tapatalk

Is Jester recognised as a keyword in the VA log when you say it?

Have you tried RIO instead of Jester (and maybe added either or both of them to the Windows speech dictionary)? Also, is it in the VA list of commands as well as the VAICOM editor tab list?

I have just checked mine to confirm it still works and I have no problems What does your VA log show when you say Jester, options? My log shows as follows (note I have debug on to show more information). To make the test easy I said Jester, waited for the beep and then said Options 5:58:31.544 Joystick : 'Transmit TX5 release' 5:58:30.119 Done. 5:58:30.114 Constructing message... 5:58:30.111 TX5 | INT: [ F-14 AI RIO ] , [ Show Options ] 5:58:30.105 Getting selected unit failed. 5:58:30.102 Getting selected unit for category RIO 5:58:30.100 Generic recipient: using selected unit 5:58:30.097 Searching called unit RIO in category RIO 5:58:30.091 Have result, identified as command: Options 5:58:30.086 Captured sentence: options 5:58:30.081 Recognized : 'options' (Confidence 97) 5:58:28.474 (awaiting additional input) 5:58:28.470 Have result, identified as recipient: Jester 5:58:28.468 Captured sentence: jester 5:58:28.459 Recognized : 'jester' (Confidence 94) 5:58:26.793 Listening resumed 5:58:26.738 Joystick : 'Transmit TX5 press'

Have you installed the new AIRIO extension? Sent from my SM-T835 using Tapatalk

I have only tried it briefly and it seemed to work fine for me - how are you trying to use it (you need to do Jester, options and then take 1, take 2 etc) Sent from my SM-T835 using Tapatalk

UsIng TX5 should do this. Press and then say a command (e.g. Chief, Ground Power On) Sent from my SM-T835 using Tapatalk

Are you saying that you want the comms menu to appear at the same time as using VAICOM? If so, you shouldn't need to set the DCS comms menu. You can either say options and keep the PTT button pressed to show the menu or adjust the VAICOM options so that the menu shows (uncheck Disable menus on the Preferences tab) Sent from my SM-T835 using Tapatalk

Have you tried running a repair on the DCS installation? Sent from my SM-T835 using Tapatalk