A mess in the middle of the flight with the F86 Sabre

[Japo32]

Hi!

 

A new issue. This happens in this version and previous one also

When I am on ground no problem. In fact after landing all comes back to normal.

On flight that is another history. No recognition of menus... appear and disappear of menus even I don't say the options to appear. F10 menu disappears options (in the Yalu Campaign)

 

I think I read other user that had problems on air...but not on ground. This happens with the Sabre (don't know other aircrafts). The F18 has been right all the time I have tested.

[MAXsenna]

Did you update yesterday?
If yes.
Did you close VoiceAttack before you updated, and did you start VoiceAttack again, before you started DCS after the update? That's an old issue if you didn't do this.
You might try this.
1. Close DCS and VoiceAttack. Start VoiceAttack and wait until VAICOM plugin has initialized, start DCS. If that doesn't solve it...
2. Close DCS and VA. Repair DCS. Start VA, then DCS. Still have issues.
3. Close DCS and VA. Rename your export.lua. If you're using TacView, SRS, SSA etc. It's always handy to have a working copy anyway. Repair DCS, start VA, start DCS. If it's now working, close down DCS and VA. Delete the export.lua and copy the copy to export.lua, start VA and DCS.

If none above works, post VAICOM log and name any mods you use.
Hope this helps!
Cheers!

Sent from my MAR-LX1A using Tapatalk

[Japo32]

Thanks for the reply. Will try that.

[Japo32]

HI!

while I did the vaicom before DCS and seems that the Sabre was ok this time, I discovered that with the Mi-24, everytime I was airborne, all became a mess and I could not give any orders with vaicom.

Trying to investigate more, and because I almost have all the modules of DCS, I saw that with this aircrafts Vaicom don't work at all when airborne (on ground, no problem, the first time. Once landed still issues even on ground).

 

Mi-24, Yak52 and I-16

 

Those three the same behaviour. Of course I did a repair and all the steps in this post. 

With the rest of the planes all are correct on ground and once airborne. 

Cannot publish the log, because it seems to be february the last month log file. (???)

[MAXsenna]

Hmmm, interesting. The Hind is in early access. Maybe ED changed something in the radios. I haven't really tried it in a comms perspective yet, as it only uses presets for the 863, unlike the Mi-8.
Does this happen in any of the provided missions, so I can try to reproduce?
The XE, Yak and I-16 are the only modules I don't have, so cannot check them out.

Sent from my MAR-LX1A using Tapatalk

[hornblower793]

Will try my Yak at some point

Sent from my SM-T835 using Tapatalk

[Japo32]

@MAXsennafor testing the mi-24 it is easy. Just go to the mission editor and put one Mi24 with engines running from runway or platform. Check if the menu call in vaicom is ok on ground (it should be ok) and then just take off. Once you have been a little un in the air, call again the "menu" (options) with vaicom. Now it is when it won't respond. At least to me.

[MAXsenna]

@MAXsennafor testing the mi-24 it is easy. Just go to the mission editor and put one Mi24 with engines running from runway or platform. Check if the menu call in vaicom is ok on ground (it should be ok) and then just take off. Once you have been a little un in the air, call again the "menu" (options) with vaicom. Now it is when it won't respond. At least to me.

Sorry, I don't understand. I only use the "options... Take..." for cargo.
Don't use menu for anything else, for me that's sort of the point with VAICOM.
I do have issues though. 50% I get "Commmand disabled...", and I hace to restart VA, if revert back to 2.5.24, everything works, except the kneeboard..

Sent from my MAR-LX1A using Tapatalk

[Japo32]

well. I modified all to spanish. It is the Special commands (undefined) show options the one that I use to make appear the menu, and then Menu commands menu items to choose between options.

In any case, no other vaicom order is working once the mi24 is airborne.