Roller83

Lol. Sighting other aircraft in DCS is much harder than in real life I find. The dot labels do make it easier than real life, but only by a comparatively smaller margin. It's a little bit easier with dot labels, as opposed to a LOT harder without. I flew IRL and you won't get any judgement from me for using labels!

My orbit must have been too wide after Sweepstake called in. It worked this time as I tracked a tighter orbit on the kneeboard. Thanks Reflected, love your work!

Thanks for the quick reply Reflected. I'll fly mission 8 again to check. I do always fly with the ^ labels in DCS (I find it unrealistically difficult to spot aircraft without them). I'm not terrible with my dead reckoning of locations, but that doesn't mean I don't make mistakes! I was off course to the west of Cherbourg, so tracked east while north of the coast until I heard the scripted call to Sweepstake. I started my orbit shortly after that radio call. I'll let you know if it was just my poor navigation.

Hey Reflected, I really enjoy your campaigns. As a former military pilot in training, your dedication to accuracy is very much appreciated and does add to the immersion. I have a problem in two consecutive missions now where important actions within the missions aren't triggering. I flew mission 7 and it all worked well, then after engaging the Luftwaffe fighters I was RTB and hit by flak right on the French coast, so had to bail out over the channel. No worries - I'll just go re-do that mission. The next time I flew it, Jerry didn't show up at all. I landed back at Chailey and the mission showed as successful, so I didn't think anything of it. I flew mission 8 a few days later and this time the bombers didn't show up at the rendezvous near Cherbourg. The weird thing is that the scripted radio call to Sweepstake (advising at rendezvous) did trigger, and Sweepstake responded (that heavies were on their way). I orbited on location for about 10 minutes and the B-17s never showed. I flew the rest of the mission plan, landed at Chailey, but this time the mission shows as a draw. I've only ever played this campaign with the multithread .exe. The only mod I have is DCS Input Command Injector Quaggles. I don't think there was even a version update between the triggers working and then not working, though I'm pretty sure there was a version update early in my playthrough of this campaign, perhaps somewhere around mission 4 or 5. Any advice appreciated.

Ah, that explains how I got through that bit. Perhaps dumb luck I didn’t eat a Fox 2. I’m having a problem where I can’t lock air targets. I could see these Migs via DataLink (red diamonds), both on the SA page and A/A radar, but I could not for the life of me get a radar lock. I searched all up and down and could never get a radar ‘brick’ on which to depress the TDC. I’ve tried RWS, TWS, AAMRAM selected and not*. I have A/A master mode on, Master Arm selected and ECM in Receive (not Xmit). If I can see a brick on the radar, I can select it (tested this on some friendlies), but I can never get bogeys/bandits to show a brick. *I think. Would being in boresight mode prevent getting a lock via the radar? Actually, it’s been happening all campaign. I can’t figure it out. I am absolutely loving this campaign, by the way. My second campaign ever and first in the Hornet, with about 50-ish hours in the bug. The learning curve is about perfect - I try a mission first, then if I fail at something find a tutorial (either mission tutorial or even just a particular weapon tutorial) and then I’m usually good to go. It’s forcing me to learn weapons I would otherwise avoid, which is excellent). Scored 100 for one mission and got super excited (previously scoring typically in the 80s), so told my wife who then gave me a very diplomatic “well done, dear”.

I confuse a lot of people. You're a legend, it is working now (mostly). I could call ground crew and get them to connect power, etc. but it still won't talk to ATC. As a test, I left pilot voice on; the ground crew commands are repeated, but not the ATC calls. When I say 'Nellis' is get the beep, then when I "request taxi to runway" I get the thud.

@MAXsennaStill nada. I had to use the command prompt repair method, but I didn't do a cleanup first as I wanted to see if I could avoid having to re-do all the other .lua mods for iUFC, WinWing and DDI viewports. Is it worth running a cleanup then repeating the process? I don't know if it's relevant, but there are two DCS folders in my user/saved games - DCS and DCS.openbeta. The VAICOMPRO folder does appear in both, though iUFCExport.lua and TacviewGameExport.lua only appear in the DCS/Scripts.

Ripper, thanks heaps. I'll repair DCS tomorrow and report back.

Thanks for taking the time and replying. By full repair, do you mean all the tickboxes in the Reset tab in Vaicom PTT?

Auto install VA log below. I think I have a several export.lua backups at the moment! All from different versions depending on the peripherals I had at the time...

Thank you, sir. I hope these are what you need. Do you want to see the .lua files?

Hi all. Long time lurker, first time poster. A couple of nights ago I installed VA Pro and Vaicom Pro, but I can't get it to operate anything in DCS. VA is recognising my inputs, but I'm getting "No ATC available" in the log and otherwise absolutely no response from DCS (can't tune a radio, contact ground crew, etc.). The PTT panel doesn't display the name of the aircraft either, so I figured I had a .lua problem. I've gone through the manual install of .lua files in the instructions, but I just can't get it to work and it's driving me mental because I really like how it is supposed to operate! It may be worth noting that my setup does use export.lua for a few things, being WinWing Take Off and Combat Ready panels and DDI viewports to second and third 600x600 screens. I've checked the release/open beta and standalone/steam sliders and set the custom DCS path (tried a few folders for this as I wasn't sure which to use). I was initially using the stable release, but switched it over to open beta when the AH-64D dropped. Please help! I'm losing my mind!