hornblower793

Mig-21 is great fun to fly Sent from my SM-T835 using Tapatalk

As BN says, I have set up a symbolic link and download quite happily to another disk. Sent from my SM-T835 using Tapatalk

I permanently fly with a WarBRD base and Thrustmaster grips (plus the Virpil VFX for the F14). I also have a short extension (5cm) so I don't wear out the base connector with lots of swapping. It works well for me with all functionality exactly as it was (you just need to use the Virpil config software to ensure you have the right grip / base combination set). I wouldn't go back to the Thrustmaster base (although I do have it still as an emergency backup in case of failure).

Attach the mission file to a post and I will then try it and see if I get the issue / can figure out what is going on Sent from my SM-T835 using Tapatalk

What other software are you now running? Does it work until you use PTT to talk to ATC, another plane etc., or does it just stop regardless? If the latter, it might be a VA problem and their Discord might be a good place to ask

Do you get a beep from Vaicom and any text in the top left corner (unless you have disabled this) Sent from my SM-T835 using Tapatalk

if you still have your licence key information then I think you just need to reset the licence data on the Reset tab and re-enter the licences for what you want to use

Which issues - mine seems OK on OB which should be the same as stable at the moment

The first one (export.lua)

Is ICS Hot Mic enabled on the EX tab in Vaicom config?

Is it appearing in the Windos controllers list and does it behave properly there? Is it working OK in Synapse (I have a Tartarus Pro and use it for the same reason in DCS)? Sent from my SM-T835 using Tapatalk

Which modules are people trying in and are they ED supplied missions (if not, what missions are they)? Just trying to spot if there is any common pattern Sent from my SM-T835 using Tapatalk

Don't worry - we have all been there at some point or another. Glad it is working:thumbup:

FIXED BY CHANGING CALL SIGN TLDR - I have now conducted some further testing and my issue seems to be related to the call sign in use for the player aircraft. Hawg, Boar, Pig and Tusk cause issues I loaded the takeoff from Kobuleti mission and, as previously, got the beep but no message appearing top right. Without changing anything else in the mission I deleted the player A10c II and replaced with a new one. On starting the mission I got a message top right and an instant response from ATC when I tuned the radio. Having compared my dropped in plane to the original one, the only differences I could see were the tail number and the call sign - the ED provided one was Tusk and mine was Colt. I therefore changed the call sign on my dropped in plane to Tusk, started the mission and got no response. I then swapped back to the ED mission, changed the call sign of the player aircraft to Colt and Vaicom worked. Based on this, I tried every available call sign with the ED plane and found that the firearms series (Enfield, Springfield, Uzi, Colt) and car make series (Dodge, Ford, Chevy, Pontiac) worked, but the porcine series (Hawg, Boar, Pig, Tusk) didn't. I have sampled missions from the Gulf map as well and the same thing is true there. Would be interested to see if others can replicate

After lots of testing this morning, my issue with the A10C II seems to be related to the instant action missions - I was using the takeoff from Kobuleti mission and getting no response at all. I then created my own mission to takeoff from Kobuleti and Vaicom worked fine. I will carry on with further testing later and see if I can pinpoint the cause in the mission (I know there are lots of hidden units)

He did, because so am I :-) Sent from my SM-T835 using Tapatalk

I wonder what order the SRS and Vaicom entries are in Export.lua (starting to clutch at straws here, especially as I do not have SRS)

Glad to be of service:thumbup:

Do you have the Supercarrier comms extension installed? It is the only thing I can think of Sent from my SM-T835 using Tapatalk

At which stage I think the issue is to do with a left over entry in your registry (I am assuming you used to fly stable). You need to delete this key from the registry. If you don't know how to do this the steps are as follows (do while VA is closed) To clear this out go to windows search and type regedit and then click on Yes if a Windows message box appears Once regedit is open there should be a folder structure on the left hand side. Find the top level entry called HKEY_CURRENT_USER and expand this (if it is not already) by clicking on the > arrow next to it. In the list that appears there should be a SOFTWARE entry, again expand this and then find the Eagle Dynamics entry and expand it. In here there should be key titled DCS World (there may also be a DCS World OpenBeta - if so ignore this). Right click the DCS World entry and select Delete from the context menu. You can then close the Registry Editor. See if VA then works when you open it back up. If the DCS World OpenBeta key was not in the registry then open the VAICOM config and select the fix registry option next to the custom path (making sure that the sliders are set for OpenBeta and standalone / steam as appropriate) If this works then great, if not drop me a private message and we can try other things:)

This is because A10C II is not currently supported in Vaicom - it will probably come with the next update

The obvious difference I can see between my set up and yours is that you have SRS installed - it might be worth seeing if temporarily disabling the SRS options on the MP tab has any effect (remembering to restart VA after you have made changes). Also, you are running VA as administrator? I will have a play and see if I can replicate the issue but it might be worth PMing @Hollywood_315 or dropping him an email at Vaicom support to see if he has any idea Sent from my SM-T835 using Tapatalk

Is the exe for the OB or stable version of DCS? The steps to be taken depend on this information Sent from my SM-T835 using Tapatalk

I don't use this, but have just run a test and it is working for me so we will try and work out what the differences are. I also tried having disabled my TX4 and it still worked (as it does with TX5 and TX6 for which I removed the mappings a long time ago) When I change the dial to SNGL, all the TX options become --- lines apart from the 1 TX node I have selected (at the start I think they were all --- and I had to press the down arrow to get them working). I do get a small sound when the up and down buttons are pressed so I think this is a clue that the problem is that the buttons are just not being recognised. Could you post some screenshots of your PTT (with NORM selected and with SNGL selected) and Preferences pages so I can see if there are any differences with my setup Also, do you have any other VAICOM extensions (e.g. AIRIO) and are they installed?

Or if you have OK internet but not enough disk space you can just switch from OB to stable and back using the updater. A10c II definitely worth it