mikeguy

Minor bug for the kneeboard for mission 4. the start up time is listed at 1802 and sc is at 1816. The ETAs for the waypoint are quite a bit off showing 2030/2045 since it doesn't take 2 hours to hit those.

Ahh ok, maybe they are just holding on to their tanks then. Thanks for the reply!

Great campaign so far! Question for you. Do you set the power settings for the AI? Or does the AI choose its own. If so can you share them? In every mission I'm way behind on fuel consumption compared to the AI. I'm flying with all the published RPM and manifold pressure for cruise and climb. Or even slightly below if I can get away with it and stay in formation. I'm flying perfectly in trim. No matter what, I have to drop my external tank well before the AI does. I've also drained aux first, but no matter what my external fuel doesn't last anywhere near as long as the AI. I do make it back to base with a little bit of fuel to spare, so if this is just one of those AI DCS things where they magically consume less fuel, that's fine. But figured I would ask.

Thanks for replying. Just kneeboard VR. But I wasn't using it. I'll do a clean / update of DCS open beta and see where that gets me. I assume we should be running open beta? I doubt this will help very much, but here is the crash event. Looks like a generic hang, maybe VR specific if the "top level window is idle". I tested quitting out of a few other missions, no problem. After cleaning DCS I'll skip one and see what mission 2 does. The program DCS.exe version 2.7.15.26783 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Security and Maintenance control panel. Process ID: 1adb8 Start Time: 01d8c1631fd712ff Termination Time: 4294967295 Application Path: C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin\DCS.exe Report Id: 8b81e93b-eafe-4551-a489-3064063a3590 Faulting package full name: Faulting package-relative application ID: Hang type: Top level window is idle

Has anyone experienced crashing / bugs when exiting the mission? I get the you may exit the mission when ready and quit. I've completed the first one twice and the first time it went straight to the hangar screen and didn't give the briefing and no progress was saved. On the second play through, it crashed to desktop. I haven't had any other mission end crashes. I just played through all of persian freedom (great job btw) for example, and no issues. Thanks for any trouble shooting tips!

I'm not sure if it's the altitude AGL or the way they spawn in, but I'll confirm that the manpads on this mission are way trickier to defeat than any other setting I've come across in DCS. Even with the proper break, flaring, engine to idle, I had to repeat this mission quite a few times from getting sniped by manpads. It's especially tricky since they just spawn in after you do the second attack tasking and are ready to fire. if you follow the given attack heading on that task, you will die 100% of the time. But on a replay you know it is coming, so you can break off and get some distance. I don't know if this helps track down the problem, but I have a hunch it might be with the call out davy does of sam launch break. Without the mws even going off Davy will do the call out and then instant explosion. No MWS warning. I'm not sure if there is a scripting issue there, but thought I'd bring it up as it seems unique to this mission. You can defeat them by just eventually memorizing where they all are and then sniping them with laser rockets from way far out, so it's not a big deal. Manpads should be pretty lethal to a low flying a10 that only has 2000 feet AGL to work with, so this mission is probably more realistic than others where a simple break and flare defeats them 90% of the time. Really cool mission though!