Hollywood_315

++ openbeta resolution ++ @all Preliminary results with Franky suggest that the problem indeed originates in the Saved Games folder. Current DCS openbeta can seemingly corrupt data in some cases. If you have issues, removing DCS.openbeta folder (DCS folder for STEAM) (make a backup first) will clear data and bring things back to normal. Grtz Sent from my SM-G960F using Tapatalk

Thanks people OK Just to repeat: none of this has been reproducible, on the reference test system things are working perfectly atm. Plugin version 2.5.13, VA 1.8.2, smooth sailing on all DCS versions with all tested missions and modules. So, I will need more specifics on the specific settings/configs which make this effect apparently occur on some systems. Voice Chat settings seem to make no difference here, but feel free to confirm and look for your magic setting - any further clues are appreciated especially links to dcs.log. Also reports of having no issues are helpful btw. Prerequisites: If you run third party stuff make sure they're all up-to-date i.e. SRS 1.7.1.2, SSA 1.3.8.0 / Sound Module 2.12, TacView 1.8.1. To test disable all mods and you might try removing your DCS.openbeta folder from Saved Games to clear any cached DCS settings (make a backup first). If you're on STEAM do NOT select the ob flag with the Custom Path because whereas regular DCS ob uses the DCS.openbeta folder in Saved Games, the STEAM openbeta version - wait for it..- does not. Long live consistency hey..*sighs* Obviously all the usual (VA runs as admin etc., adequate folder R/W access etc.) applies. Looking forward to your inputs! Let's see if we can Sherlock this down.

@Tundra for Steam can you try with unchecking the ob flag per @Theseus' suggestion some 5 posts back.

@Jason @Theseus @FF Thanks for the updates. Indeed some unexplained Mission Start entries in @FF's logfile. I get that this occurs only on ob. Since I for the life of me can't reproduce it myself, looking for specifics. Just to check: does that mean this effect occur only with a specific mission / module? If so, can you share a link to the misison file to test with. To get a lead, can you see if changing config/preference settings makes any difference. Did you disable mods and other entries in export.lua. Anything to see in DCS.log?

Everything will function as normal. The 000.000 is just a display glitch in SRS PTT mode, fixed for next update. Grtz

@FF Thanks can't reproduce, all working fine on the test rig. There have been no changes to the plugin. If it's an ob snag it may resolve itself in next update. SRS made some changes recently, perhaps try with updating to latest version or disabling. @D3adCy11nd3r Should work ok, we'll have a look to see if it can be reproduced. @soupyc Yeah that MP server came up before recently. BFPG server appears to run some kind of special custom script, rendering it incompatible. Perhaps contact the server admins. Caucasus a.o. working fine.

@hreich Thanks for updating.

@hreigh Thanks moving to x: is not an issue and the plugin seems to recognise the path just fine. I would be interested in dcs.log particularly. Confirm your VA is latest 1.8.2 and check in Options / Special / F14 that Radio menu behaviour is set to Default.

@FF Thanks, can't reproduce any issues so far on ob, all working smoothly here (double mission start data log entries are themselves benign and do no necessarly point to a problem btw). Can you confirm the easy comms on is not enforced by the mission, and more importantly if enabling/disabling voice chat makes a difference for behavior. If so any leads from DCS.log you can provide may help. -- UPDATE -- After trying many times randomly hitting the keyboard PTT keys I could reproduce one or two forced PTT 'hangs' with VA 1.8.2. Something that has been impossible to achieve with VA 1.7.8 (attached, remove your current VA program folder first): can you test with VA 1.7.8 version and report back please thanks. VA_178.zip

Since it worked for you before, you'll need to think about which changes you made to your system. If you followed the the FAQ steps https://www.vaicompro.com/faq.html, the problem is not the plugin but something specific to your rig. The basics again: - Run a FULL DCS Cleanup and Repair https://www.digitalcombatsimulator.com/en/support/faq/709/. - Confirm in DCS settings are according to manual and correct F14 settings are applied for AIRIO (see manual) - For testing disable all background apps and mods, disconnect hardware - Confirm your Windows account has UAC admin rights with R/W access to all folders - For testing disable antivirus and firewall - Disable all plugin options, switch off audio redir - Confirm correct VA installation and VA settings (see manual), VA MUST run as admin - If no joy enable debug mode and look in the log window for error messages - Look for results across various mission, modules, settings (easy comms). - Apply the registry fix (bottom page) https://www.vaicompro.com/support.html - Look in DCS.log for additional hints. Grtz

@Theseus Your log shows a clear install error: Auto-install could not complete for DCS version 2.5 Almost certainly to do with Windows AUC admin rights i.e. folder R/W access. Elevate your Windows account rights for your Steam DCS program folder and/or check user manual page 35 for manual lua files install. Obviously this assumes your VA runs as admin in the first place. Grtz

@jason No such issue here, all working just fine with latest SRS, SSA, TacView. Perhaps try with disabling LotATC then inspect your SRS config settings and re-check TX press/release bindings. @Musicman Cargo is managed via "Cargo, options" and Take commands. @Mojo What @MAXsSenna says, also check audio redirect setting. @Phantomflyer @hreich suggestions here https://www.vaicompro.com/faq.html @lxsapper Potentially in a next AIRIO update @hreich Select TALD is part of the keywords set, apply FINISH steps if needed.

Hi all To confirm: VA 1.8.2 is OK to use. @lxsapper Disable AIRIO in the EX tab and restart DCS. @Ares With easy comms off the call is directed to the unit for which your radio is tuned. If you use the wrong callsign for the selected frequency, this is auto-corrected. If not properly tuned, the call will go to the currently selected unit as set by Select command or nearest by default. @FreightDog The correct alias to use is "approaching for refuel", see ref. tables.

@nessuno Sure that's the plan, let's see how this will be implemented by ED.

Hm I believe you said all regular commands were functioning fine. I'm starting to wonder if your AIRIO dll is up to date, PM inbound.

@Tundra :thumbup: @Snacks EDIT The updater knows VA folder locations and runs where the dll's are stored. You may want to doublecheck folder admin R/W access in your case but you can always replace the dll's manually. @flankerrider Good tip! @TWC_Alamo PM inbound @williehayesjr Perhaps have a look at the Audio tab and try with REDIR set to (default). @Ferciful You'll need to be in a running F-14 mission for AIRIO to be available, PM me if you need more help with that one. Grtz

To readout the module name, just have VA write the token value to the log. SRS button can be toggled with the API. SRS button state value is not exposed at this time: could be useful though, we'll consider it for addition. The log shows nearest coalition airfield with radio capabilities. Grtz

@Viper Well it's a bit of an advanced case but there are certainly ways to make it work. First of all let your joystick software send an emulated keyboard key instead of a DX button so that modifiers like shift, alt etc can be used to bind the button to different TX nodes in VA. For swapping radios you can use SRS mode in this case but more generally use the plugins exposed variables. On TX1 make a condition block in the VA press/release commands that tests for fhe F14. If true invoke plugin call ptt.tx2.press / release, else normal ie invoke ptt.tx1. press / release. Do the same for TX2 and you will have swapped the TX mapping. EDIT as a sidenote speaking to both radios at the same time doesn't not make sense, e.g. when having two airbases selected you may want to test with this using SNGL mode, as addressing the airfield name in your calls should automatically use the correct corresponding radio. So I expect this actually wouldn't be an issue. Sent from my SM-G960F using Tapatalk

@Dehuman Cool, thanks for updating. @DERacing Perhaps have a look at this thread here to get started: https://forums.eagle.ru/showthread.php?t=226019&highlight=vaicom+srs+teamspeak @Swordfish Not reported by other users, appears specific to your setup. Problem likely originates outside the plugin. Changing LUA stuff will be counterproductive: run a DCS repair. For testing disable all mods and 3rd party apps. I'll need logfiles and info on firewall/router/antivirus settings etc. to make further assessments, PM inbound. @STGChamby Cheers mate :thumbup:

Not reproducible here, test with other MP servers. Allow Player Export must be enabled. Sent from my SM-G960F using Tapatalk

Thanks @Greyman, good to hear it works for you. @Viper You may want to consider using SNGL for PTT mode, this will allow you to use just one button. Grtz

+++ Release 2.5.13 +++ Plugin 2.5.13 with AIRIO 2.5.5 is out! New features added e.g. forcing speech language across all modules, blocking of on-screen text for max. immersion and TALD support for AIRIO. Existing users update automatically. Enjoy! :pilotfly:

@tribundf You may want to check that your AIRIO is propely installed. Manual page 36. @flankerrider Not reproducible, all working fine here. Make sure to use Connect Air Supply before Apply Air. @jv44bubi Enable the Import F10 option and fly the mission, the menu items will be added with 'Action' keyword. Next tailor the aliases at will with the editor and go through the FINISH steps to use. @nessuno0505 You're in luck, upcoming plugin release update (2.5.13) has a new option to force English spoken language across all modules.

Carrier comms is WIP.

@Boomer Couldn't reproduce with that MP server but in any case there's been no change to the plugin. Perhaps check again with the wheel instead of AIRIO to compare. Also make sure to use the correct command phrase/alias i.e. 'Track Single Bogey Ahead'. @Monty Cant't reproduce, sounds like your flight may be actually on UHF (which is more typical), or that you need to apply "Colt, Select" on VHF first if that is your flight callsign (or more basic 'Flight, Select') to tune the radio. In any case make sure you run latest plugin build i.e. 2.5.12.2.