Nix Mills

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.

Hey Kenny. Thanks for reporting this. The issue you have follows on from today's update that has added security controls to the scripting environment. We will have this in every mission. BIGNEWY has provided a fix in the link above which involves editing your autoexec.cfg file and pasting a few lines into it.

Ouch. I wonder if there's been an update to the weapons effect. We'll check and update. Thanks for reporting it.

Thanks, I hope you had better luck the second time. I'm not sure how it got to that point - it was waiting for the wingman to detect the MANPAD, however all that should've been over by the time you did show of force. We'll make sure to build in a safeguard to prevent it from happening again.

The external power is a bit tricky the first couple of times. If the kneeboard checklist is not enough, I suggest finding a YouTube video that shows you how. That might be a bit easier than trying to walk you through it here.

That is unfortunately a Core DCS bug. If it persists, .

Yes, I made those updates just after the cutover. Enjoy.

Here you go... image.jpgnullnullimage.jpg

Noted

Thanks. This is really helpful. I can see that it is missing also giving you 5 points for being on station when the operation commences. I'll make sure to fix this.

Scoring system seems right to me, but you’d need to get all the targets for a 100 result. As for your loadout, you’ll need to push that one up the chain to CAOC who issued the ATO.

I can take a look. Do you have a screenshot or message log of the debriefing you can select at the end when you’ve landed?

Hi guys I'd really like to ask for the lua task "refueling" to be made so that it can be used for a Unit also, like many of the other tasks do. The task works for a Group, but if you give it to a Unit (such as your wingman), the Unit will "RTB". Examples: Refueling = { id = 'Refueling', params = {} Group.getByName('Ram-2'):getController():setTask(Refueling) <-- this works fine for an AI group Unit.getByName('Ram-2-2'):getController():setTask(Refueling) <-- if used on player's wingman, wingman will RTB Keep up the good work - love it.

Hmmm... that sounds a bit frustrating. I haven't heard of or experienced that problem before. It might not be caused by the mission. However, I have updated the failsafe now so that at least the bunker will be destroyed. I'll request for it to get pushed out with the next general update.

Read this first

I'd have thought that was an impossible bug to create. The error you got was because it was trying to calculate the bearing to the Gecko the moment it fires at the decoys, so that Shadow can call it out. It appears that you'd have somehow managed to destroy the Gecko at the same time it fired its first missile. Anyway, the script error you got should not have had any impact on your ability to complete the mission. I have however created a failsafe for this now.

Thanks - I wasn't aware of this until you mentioned it. Nevertheless, someone else had already reported it to ED, so hopefully it'll be resolved soon.

Thanks for reporting this. I was a bit surprised to see this as the Guard frequency was not actually controlled by the missions but a native DCS setting. It would seem that one of the recent DTC updates might have broken the Guard setting. For now, I suggest you simply put 243.000 into channel M (manual).

Thanks for letting me know. Apparently it has not been updated although mentioned in the patch notes. I'll resubmit for next patch then.

Yeah, the thing is, that message doesn't exist in any of the missions. Your standard message is: F-10 OPTION (I) TO CHECK IN WITH STRIKE (265AM)