Florence201

There should be 2 tankers around. A KC-130 and a KC-135 The TACAN is set by the MOOSE script with Airboss. Are you running DCS 2.5.6?

Are you running DCS 2.5.6 and the MOD version of the campaign?

Yes indeed

This could be wind related and the jet is CCRP is allowing for that

Really am waiting with baited breath for this campaign......:D

Flight Comms are on 135Mhz. Do you have that set on the VHF radio? And are you selecting the correct radio to try and communicate with them?

Sometimes tgt can be at a WP that is not programmed to enough decimal places and therefore means searching the datum slightly. Tried to make this as real world as possible and not just "Hit the WP" spot on all the while.

This is an issue with DCS, not the campaign itself. I have double checked under 2.5.5 that as long as you wait for the "In Vader" call, then send them to bomb first, as if you hit tgts first, they leave them alone for some reason?!?!?

Depends how far you'd gotten

New upload on the the User files repository. Folder contains both MOD and No MOD versions!! please feedback any more issues.

New upload on the the User files repository. Folder contains both MOD and No MOD versions!! please feedback any more issues. Thanks to all

I have the fixes made, i just can't upload them to the DCS user files page for some reason. And the zip file limit on here is too small

Yeah i figured that might be the case. So 2.5.6 won't even let you open the missions with George Bush in the ME? I'm trying to get a new version updated, but the DCS server keeps stopping the upload.

Cheers Space Cadet

Hi, I've recently installed VA and Viacom Pro. I thought i had things set up correctly, but when i try to VA radio commands, VA is telling that the commands aren't recognised?? Is there a specific file i need to add? I have added Bailey's excellent F-16 and F-14,, along with the standard for DCS.vap. Here a lot about the added immersion with these apps and it's frustrating me that they won't work...

Hi, I've recently installed VA and Viacom Pro. I thought i had things set up correctly, but when i try to VA radio commands, VA is telling that the commands aren't recognised?? Is there a specific file i need to add? I have added Bailey's excellent F-16 and F-14,, along with the standard for DCS.vap. Here a lot about the added immersion with these apps and it's frustrating me that they won't work... :helpsmilie:

So this appears to be a DCS 2.5.6 related issue. May i suggest to all (until i can get an update released) that you go into all missions in teh ME and change anything that is a MOD. ie, change P-3 to S-3, C-5 to C-17 and maybe change the CVN George Bush to USS Stennis. This should remove all mods to see if that is the problem.

Hi Sydy So you should be able to open all missions in the ME and select the aircraft/planes tab on the assets page. Look down the right hand columns for "MOD" and change anything with Military Aircraft Mod to a normal jet (P-3 to S-3 etc) As for the error, i think this is 2.5.6 related. Getting a lot of feedback on this from both F/A-18C and F-16C versions. They all worked prior to the "upgrade" DCS rolled out.

Not 100% what you're asking here mate. Can you provide a little more info?

It seems to be a common theme across most jets. Certainly seems that BINGO fuel is set unrealistically low

As long as you don't engage until SEAD flight calls "Target# down" then you'll be good. Glad you're enjoying it :thumbup:

Tried that buddy, but no joy. I'll see if replacing the original .lua works better rather than JSGME

Added this to my JSGME folder and it works great for my AI wingmen, but not for me. In fact i have no strobe at all. Any guidance??

You do have enough of a loadout to personally destroy all 8 units (4 at each site). You will have to use A-G gun to complete, but it's doable

No idea why you can't R&R at Kish. Kish is definitely a BLUE airfield and therefore you should be good. Are you using 2.5.1? These missions haven't been tested after the update, as i only have 2.5 The hornets will radio when they have destroyed the associated SAMs at both WP3 then WP4. Allow them to "clear" your path before proceeding to target.