Nix Mills

Hi there @Kurnass1977. Thanks for reporting the fratricide for M15. This is caused by the increased blast effect that was introduced with one of the recent DCS updates. Not complaining, though, because it is much more realistic now. However, it has lead to several missions having to be tweaked. I'll make sure to update this one also with the next update release. As for altitude, all of the above is correct. What you see on your instruments is not 'true' altitude. This is why you'll sometimes see both altitudes and fuel states being called out a little bit off from what you see on your instruments - and not only in Rampagers, but also in DCS' own comms with the carrier.

You start up the engines to run all your checks. When all that is done, you shut down the engines again so as not to sit and burn fuel in the parking area. All your instruments will stay powered on by the external power.

Thanks for following up. I'll have a go at this myself in a little while when I get back. Unfortunately, I believe this relates to a general wingman bug and not the mission, but I'll be curious to see if I can replicate the bug also.

Thanks @paloncho. Yes, unfortunately, this would be a bug relating to DCS wingman behaviours and is not something we can control in the missions. This may have been a one off, but if you often have odd issues with the wingman, common causes may be unlicensed third-party mods installed (not including SRS or Open Kneeboard) - see Common Issues and Bugs section. Common mods like Viacom and even Tacview (sorry) are known to cause some issues in campaigns. If the problem persists, you would still be able to complete the mission for example by letting wingman engage with Mavericks and then order it to rejoin. Hope you're otherwise enjoying your deployment. Ram On!

Thanks @KENNY1988. Unfortunately, there's nothing we can do about these DCS wingman AI behaviour bugs. There's nothing in the mission or scripting that tells it to do this. However, looking at your Tacview, I suspect the problem is that your wingman took off almost a minute ahead you. It can confuse it making it decide to prepare for recovery (jettison full tanks and hook down). Other common causes to odd wingman behaviours can be unlicensed third-party mods installed (not including SRS or Open Kneeboard) - see Common Issues and Bugs section. Common mods like Viacom and even Tacview (sorry) are known to cause some issues in campaigns. If the problem persists, and it is only dropping its tanks, then I suggest you just continue the mission and let wingman be wingman. Hope you're otherwise enjoying your deployment. Ram on.

Thanks @KENNY1988. Yes, @RLTick normal DCS wingman commands are given on AUX. Have a look in your campaign guide also, which explains this. It can be found in your mods/campaigns/rampagers/doc folder.

I've noticed that the other Nimitz class carriers technically had been provided for and that Marshal can already say they respective callsigns. Provided its only a matter of updating liveries (with CVN numbers), unit type name and radio ATC options, could we please also add CVN-68 Nimitz (Old Salt), CVN-69 Eisenhower (Ike), CVN-70 Vinson (Gold Eagle), CVN-76 Reagan (Freedom) and CVN-77 Bush (Avenger)? Please

Thanks @-=Bagel=-. We literally just submitted updates to ED, but will make sure to address these ones with the next one. As for the KC-135, yes, it is operating elsewhere as it should be possible to complete this mission without refueling - and have the carrier's recovery tanker as backup. Enjoy and Ram On!

Thanks @BIGNEWY F/A-18C The Rampagers campaign by Baltic Dragon and Whipbird is now working normally again. In the meantime, we have updated scripts using net.dostring_in to call the start_listen_command so that it will simply be bypassed in the future if/when settings don't permit calling mission or server functions.

Yes, as well as to missions 9 and 12 where the new and more realistic blast effects from bombs have changed the outcome. We are testing the fixes now then will submit to ED.

Looks like something else. You need to go to the folder Saved Games\DCS\Config and put the file there or edit the existing one. An update to all Rampagers missions is on its way, which won't crash if you haven't changed your autoexec.cfg and just let you continue with using F10 options.

You can download the file I attached and place it in your folder then.

UPDATE: The issue was resolved with update 2.9.18.12899. Hi all - Update 2.9.18.12722 has introduced additional scripting functionality and therefore also new security features. Unfortunately, this means that in every Rampagers missions, whenever getting the option to use the windshield switch to make a radio call, you will get a scripting error. We're working on a permanent solution. In the meantime, to overcome this problem, you will need to give your DCS permission to call functions in lua scripts. You do this by copy/pasting the following lines into the file Saved Games\DCS\Config\autoexec.cfg if not net then net = {} end net.allow_unsafe_api = { -- this defines the secure zones where net.dostring_in() should be called from "userhooks", "scripting" } net.allow_dostring_in = { -- and this defines the scopes that you want to use from net.dostring_in() "server", "mission" } You can do this with any text editor. You can also use the attached file. For more details, and to verify the authenticity, please refer to this link: And sorry for the inconvenience. autoexec.cfg

This made my day, thanks 2circle. A bit of behind-the-scene stuff in response to your comments. The voice actors were full of enthusiasm. No way we wanted to take that away from them - it's contagious. And of course there's way too much chatter on AUX altogether, but that's to tell the story. Actually, hadn't thought of a penalty on the recovery weight. Loving the idea. We did actually try to create time slots for departures and recoveries, but it got really messy. AI groups got stuck on the catapults if you, as the player, didn't comply. The long missions with AAR were also a worry -- we weren't sure whether it would be well received in the community -- so didn't want to add extra wait time at the end of a 2-3 hour mission. But, perhaps we need to revisit the idea next time. We're here for carrier stuff, after all.