Greyman

Maybe watch their video, see for yourself and then apologise https://forums.eagle.ru/showthread.php?t=273624&highlight=stingers

Nice one. Thanks @hornblower793

Maybe take a couple of weeks out and do something else? I'm not saying it will be much different when you come back, even if the 'bug of the day' might have changed, but it might help to recharge those batteries and to help retrieve the obvious enthusiasm/passion that has kept you in DCS for all these years.

Make sure that you have totally cleared the "when i say" field, before pasting in the new contents. Is the "multipart commands...." message a warning that you can ignore and continue anyway, by the way?

Maybe watch the video linked in https://forums.eagle.ru/showthread.php?t=270012 and listen to why ED use early access as a way to develop very complicated modules. Also, if you have a specific problem, maybe you should read the many posts on the performance issues with 2.5.6 and hopefully find a fix. Opening posts like this will achieve nothing but to drive your blood pressure up

check that you have the right mic selected. to be safe, maybe unplug any other mics/headsets check that the sliders on the EX tab are set to match your installation As DCS has also recently been updated, make sure that you have done the usual steps: delete export.lua, set custom path etc

You did check the SC box in the EX tab of the config window and go through the FINISH process to install the SC commands, i take it?

page 70 of the manual linked on the OP of the "big thread"

nice one \o/

On the Editor tab of the VAICOM config panel, you should see the FINISH button, highlighted in yellow. Press that and follow the instructions that appear in the pop-up dialogue. The Finish button basically copies the full list of Vaicom commands to the clipboard and you copy that over the top of what is currently in the "When I say" field of the Vaicom Pro profile.

..and you have deleted the export.lua file, in your ..../saved games/<DCS folder>/Scripts folder and restarted VA? Also, are you running VA in Administrator mode? Sorry if the answers to the above are an obvious "yes", but still safer to make sure.

I know it's a potentially silly question, but the mission you're in, Mark, does have a tanker in the air and you have tuned the appropriate radio to the correct frequency, including band?

Whether you switch carriers in the mission or not, it would appear that, if you have bought SC, you still get access to the advanced ATC radio comms, the "pop-up ball" and ED's LSO grading, so if that was all you were looking for, then just carry on using the existing mission, with the Stennis. Having said that and even though the deck crew don't yet do anything for recoveries, I still hope that someone produces an SC variant of the mission, just to see a more lively deck.

Good to hear that you are back up and running

Check out the "10%" issue in the FAQ page, linked at https://forums.eagle.ru/showpost.php?p=4311067&postcount=5.

Make sure that you clear the license key field before entering your licence key.

The flashing AoA indexer would suggest that you don't have your hook down Edit: Ah, having watched your subsequent attempts, i see that you did drop it.

If you buy the bundle (VAICOM, AIRIO and ATC), you will get the ATC functionality, but if you previously bought just the VAICOM Pro licence, you will need to buy the ATC addon, for an additional 3.50 Euros.

Did you do the Finish commands?

try "Texaco approaching to refuel" rather than "Texaco request refuelling"

Nice one and the previous pass wasn't too shoddy either.

By the way, that "full fat" instruction set, for the supercarrier is awesome and should really appeal to the hardcore simmers, a lot of whom have been complaining about the automatic nature of ED's early implementation. Nice one

Make sure that the prompt text has all been cleared from the licence key field, as some of that will be invisible after you have pasted the key in from your email.

probably because your throttles aren't at idle before you have touched down and have weight on wheels. if you retard the throttles after touchdown, you go straight to ground idle

there have been reports around the transition between night and day, where the start time, eg before dusk, appears to determine that Case 1s continue to be called after dark, yet the radio logic appears to switch to case 3. maybe steer clear of dawn and dusk for misions for the time being.