BuzzLine

A remote tropical island ? Just watch out if you hear about guerilla fighters in the jungles or you start seeing Hueys above your head. You don't want to be Lost in Paradise... (hahaha)

Hey @Reflected, apologies in advance for a trivial question but since in that video you mentioned your (much appreciated) neverending quest for realism, here goes nothing : what's with the spelling of "bale out" in your mission briefings ? I'm not a native english speaker and elsewhere I've *always* seen it written "bail out". Is there a difference in meaning or is it a UK/US spelling difference or something else ?

Ah, it could be my old friend the "End Mission" bug. Post your dcs.log if it happens. If (if !) it's the same issue, I've provided a fix in that thread. But it may also be a new issue, without the dcs.log it's hard to tell. Also plz post the debriefing.log file, it's next to the dcs.log file.

Additional tip : use TacView to debrief your flights. It's great to understand where to improve. I recommend looking at the "total mechanical energy" value (EM) which helps a lot understand why the opponent is flying circles around you. null

Maybe we should point this issue out to the devs ? They should either add a check that flag names are not a reserved Lua keyword or (better) properly escape the keys when they serialize data on disk ? Or move this thread to the Bugs section ? Let's ask @NineLine . For convenience, as this thread is getting long, below is my detailed investigation:

Yes but no. I tried. You can inject code through the flag name but at execution time it will have no access to any function, none at all, that's the whole point of the setfenv sandbox in Lua. ( see http://lua-users.org/wiki/SandBoxes ) I prefer of course when inputs are sanitized but here the problem is well contained and the solution is to avoid Lua-reserved keywords. No other vulnerability detected. Case closed.

I thought as much but I looked and the call is wrapped in a properly set up setfenv jailbox. That's as secure as it gets, at least for consumer-grade applications.

Assuming my hypothesis is correct and unless/until ED fixes the issue, avoid the following identifiers : https://www.lua.org/manual/5.1/manual.html The following keywords are reserved and cannot be used as names: and break do else elseif end false for function if in local nil not or repeat return then true until while (case sensitive so Break and BREAK would be fine but I'd still avoid this).

@baltic_dragon : expanding on my answer above, I believe the issue is caused by an orbit task given to Raven 22 (weed) that is stopped when a flag called "break" is set. Rename that flag to something else and that should fix the issue. (see screenshot below) My guess on the root cause : The debrief.log file is written on disk formatted as a lua file. It's not code, just objects, but it's convenient. It lists many things including all the events and the states of the flags and when they were set. The code that fills the debriefing window (when you end mission) is mostly written in lua and for convenience, it just gobbles up the debrief.log as if it were some lua code : -- load debriefing data function load(path) local f, err = base.loadfile(path) (taken from me_debriefing.lua somewhere in ED's code) But loading debrief.log as if it were lua code assumes that debrief.log is a properly formatted lua file. HOWEVER, in our case, the debrief.log contains the following in the flags section : (...) ['50'] = { time = 706.028, value = 1, }, -- end of ['50'] radio = { time = 157.855, value = 1, }, -- end of radio break = { time = 433.901, value = 1, }, -- end of break (...) (in this snippet I show the flag numbered 50, and the flags named "radio" and "break") The problem is that "break" is a reserved keyword in lua (and many other programming languages) so the above snippet is not valid lua and that confuses the parser when it tries to loadfile it. Anyhow. I don't work for ED, I don't have full access to their code, this is just guesswork, and maybe I'm all wrong. But to me it looks like a decent explanation for the issue. And it's a fairly benign fix that I'm sure someone would be willing to test, if you were to provide an updated mission file. HTH, Buzz.

Short answer : Don't name a flag "break" or any other lua-reserved keywords. debug_lua_parse.miz

Well, if you want to be precise, squadrons (like F18s but also E2 and other types required for the full complement) are bound to an air wing. That air wing is then deployed to a carrier, which can change for the next cruise.

Indeed. However, @Dieselmadness , do note that many USMC squadrons operate the F18 (check out all the VMF liveries !) so there were probably many transfers between those airframes, while remaining in the Marine Corps. And US Navy carriers often embark at least one USMC squadron (F18 now and in the past, slowly moving to F35 as it becomes available).

Is that the one in Le Bourget Air&Space Museum ?

I thought it had been fixed...

nullOur flight lead trying to steer 060. Either he's drunk or the zig-zag AI bug is back. null Anyone can duplicate the issue ? Reference :

Happy to contribute to fixing such a critical bug ! (And the FR Wikipedia entry was fixed too, awesome)

The writing style of combat manuals has not changed much over the centuries, it seems. "Then shalt thou count to three, no more, no less. Three shall be the number thou shalt count, and the number of the counting shall be three. Four shalt thou not count, neither count thou two, excepting that thou then proceed to three. "

Well, you do have to admit that there will be low cabin pressure after an ejection, so ... err ... I guess there is (some) method to the madness ?

nullHere's a fullsize screenshot of the modification to make. Simply add the missile type to the "missile in zone" condition. poke @baltic_dragon : bug+fix on "Crime and Punishment" M2.

Same. DCS hung (hanged ?) halfway through M08. Nothing special either, I was joining on the wing of someone on my way back. Love the campaign so far but I'll wait until next patch to try it again.

Gosh, between the TGP/waypoint bug and the AI F14/GBU bug, this is a pretty rough patch. I wish they'd hotfix the thing, it's a mess at the moment.

@JethroTundra My guess is you have a waypoint sequence active (seq1 usually). You can't access markpoints if a sequence is active, unbox seq1 and you should be good to access markpoints (as well as other non-sequence waypoints).

Campaigns that come for free with aircraft modules can be found in the mods/aircrafts/<module name>/missions/campaigns (or something like that). Not the mods/campaigns folder as for the payware ones.

+1 on all of those ! "Viper Pilot" by Dan Hampton is also a good read, if you're into F-16s.

Weird, I always seem to have time for one orbit, if not two. Sometimes more if there's many aircraft in the recovery ahead of me. CV NATOPS ( a.k.a navair 00-80t-105, can be found online easily ) makes no reference to airspeed limitations either within the Carrier Control Area (50nm) or the speed at which the holding pattern should be flown (although common sense and plane NATOPS recommend max conserve). There are probably airwing-specific procedures in place and of course CATCC has full control over their airspace. Also, if your fuel status is a concern for flying 450kts GS, then I don't think it's a super great idea to waste time orbiting in the marshall stack ??