Reflected

I don’t think there’s anything wromg with the Vaicom code. I mean if you run Spotify in the background that also puts more stress on the cpu, but that doesn’t mean Spotify needs to work on anything I may be wrong though, I never used vaicom.

I’m sorry but what could Baltic do about it? ED needs to rewrite the MT code to make sure it’s never allowed to miss any flags or tasks. Baltic, Vaicom, you and I have the same access to that code: none. Probably the vaicom code itself doesn’t interfere with dcs the same way unofficial mods do, but it’s an extra load on the cpu which makes the MT engine more likely to be too busy to notice flags and tasks. e.g. i see that bug more often when I play in VR than in 2D.

Baltic found out that with VAICOM DCS is more likely to miss flags and tasks, so it exacerbates the MT stop flag bug.

Yes absolutely. The MT engine needs fundamental fixes…it’s a real disaster that missions are a roll of the dice whether they’re gonna work or be completely broken because the game goes “oops sorry I missed this flag/trigger” I’ve been whining about this to ED on a daily basis for the past 1 year. Apparently it’s really hard to fix but it’s a complete showstopper nonetheless next time it happens please send me the track so I can send to ED.

I hope you find these helpful:

https://en.wikipedia.org/wiki/Organization_of_United_States_Air_Force_Units_in_the_Gulf_War

In order to be able to make any meaningful Desert Storm missions, it needs to have at least Prince Sultan Airbase in Saudi Arabia. Many squadrons flew from the UAE, but that's on our PG map. I guess they can't be connected so that would mean a "load new mission when crossing from one map to another" kind of campaign, which is not ideal.

@Fester thanks a lot, that's awesome. If you survived, that's the biggest victory. Any ground and air to air kills are just the cherry on top.

The DCS AI has been taxiing through statics since the release of the Supercarrier. And I'm glad because otherwise you couldn't make missions with populated decks and the current AI pathfinding capabilities.

Interesting, in my copy of the briefing it says 13. Maybe the file hasn't been updated by ED? I'll submit again.

It's weird that the shift+U solves the problem because PAco's trigger has nothing to do with how you salute. I'm suspecting VAICOM itself is the issue, which is known to make DCS miss triggers sometimes.

Thanks for the feedback and the beautiful screenshots!

Who said he would move to cat 3?

See 2 posts above. I hope Ugra will finish the map soon.

Dude you're way out of line. How the heck can you make a mission NOT crash from within the editor?! Are you kidding me? How many times do I have to tell you that I have the same access to DCS as you? I could repeat what I wrote a 100 times before but you're either not reading them or don't care. The only thing the lighting bug affects is that you cannot cheat in case the mission is too dark for you. Period. I'm not defensive because I wrote it. I didn't write it. It's what happened 80 years ago. Hey why don't I move D-Day H-hour to 12 noon on a sunny cloudless day? Or next time the P-51 is bugged I'll just change it into a Spitfire campaign. So easy, yeah? Please send me your paypal address, I'll give you your money back. I'm out of this conversation.

In the meantime here’s an enlightening (no pun intended) reading for everyone: “In a break with normal operations, a red flare spluttered from the control tower high into the dark and wet. At once, the 486th’s P-51s huffed and barked and spun themselves to life in a gratifying staccato growl that soon steadied to a comforting thrum. A few minutes later the squadron’s aircraft began their awkward, waddling taxi to the takeoff funnel. All pretense of order came apart in the dark and some flights failed to assemble while tagalongs joined others; few of them made it to their proper place in line. Fahrenwald found himself at the head of the entire mess as part of a three-ship. According to the brief, they were supposed to take off in four-ship formations: By the darting flames of their engine exhausts I could make out the dim identifying letters painted on the fuselage of each ship. So Pappy Gignac and McKibben and I were together, and we three were hogging the slot reserved for the Colonel’s flight. That, however, was tough titty, because it was too late now to monkey around trying to get organized. We ran up our engines and it was time to go, and I didn’t want to push that throttle at all. My instruments glowered greenly at me like the winking, blinking, luminous eyes of a whole pack of pussycats racked up in a blacked-out bookcase. But they did go. With their throttles pushed up, the pilots of the first three Mustangs felt their aircraft bump along the muddy grass on a northeasterly heading as they picked up speed. Gignac’s mount hit something slippery that spit him off to the side. Fahrenwald, on McKibben’s wing, jockeyed his throttle to stay in position until the two of them finally lifted off. They both drew a collective breath as they raised their landing gear and put precious altitude between themselves and the ground. Behind them Martin Corcoran swung his four-ship into takeoff position.4 A string of lights intended as a takeoff aid had been torn away, presumably by Gignac, Fahrenwald or McKibben. Without the lights, and failing to check his compass, Corcoran aligned the flight too far to the right. Not noting the mistake, he advanced his throttle and started his takeoff roll. To his right, Donald “Red” Whinnem rolled with him as did Robert Frascotti who was next in line to the right. Carleton “Bud” Fuhrman was on Frascotti’s right wing. Unknown to any of them, Charles Griffiths had mistakenly tacked onto Fuhrman’s right wing and was also taking off. Corcoran’s four-ship was actually a five-ship. Meanwhile, Fahrenwald tucked himself tightly to McKibben’s wing, anxious not to get separated in the murk. “We banked into an easy turn to port,” Fahrenwald recalled, “and I glanced back to the field and all of a damned sudden a horrible, billowing explosion half-blinded me, and I knew automatically what it was: a Mustang, a maximum load of high-octane and one of the boys, all gone to glory in a puff of flame.” Below Fahrenwald and McKibben, every man on the ground gaped horror-stricken into the brilliant pyre. Robert Frascotti was dead. On the errant heading, Corcoran’s flight hurtled at high speed to the edge of the airfield where a new control tower was under construction. Corcoran and Whinnem passed to the left of it as they lifted airborne. Fuhrman passed it to the right. Further right, one of Griffith’s wheels struck a pole on a nearby volleyball court but he was unhurt. Frascotti, in the center of the flight, smashed into the tower with a blinding yellow-white blast.“ no gamma slider, no refly button.

Or you could have spent the same effort posting this to ED, because at this moment I’m the only one telling them about this issue while everyone else is complaining to me, a guy with the same access to the DCS code as you: none. the mission timing is realistic. I’m not changing it. There is a full moon. If a core ED module/ feature/ bug is substracting from that realism, the solution is not for me to make the mission more unrealistic as a workaround for playability but for ED to fix their stuff. read the relevant chapter in ‘Fighter group’ and you’ll learn what it was like to take off in total darkness. If you don’t believe the mission, that is. @[ED]Ben can you please give us an update on this bug, and whether the team is working on a fix? Thank you.

So 1) there is a bug with the DCS lighting engine. As I said many times, I already reported it to ED. If you want it fixed, don't tell me, you're preaching to the choir. Tell THEM. (so that I'm not the only one whining about it) 2) in real life pilots didn't have gamma controls, so it was as dark as in DCS with the bug and full gamma. Just read about Lt. Frascotti. 3) therefore, there is nothing for me to fix. If ED fixes their lighting engine, you'll be able to 'cheat' by cranking the gamma. 4) just because people have opinions that differ from historical facts, I'm not gonna spend my time convincing each and every one of them. Sorry, I just don't have the time for that if I want to build and fix campaigns. History is history.

Thanks a lot NL for checking, much appreciated. The failsafe explosion happens 4 minutes after the damage. When I tested the mission it was always enough. I've now changed the damage to 'rupture' and will move the failsafe a bit later too, and link it to some zones because I need to make sure the player doesn't make it back over the lines

Hi, can you please send it to ED? It’s not something I can fix from the mission editor, sorry tru running a slow repair and the try installing again

For some reason dcs considered you dead after the ejection. No idea why but better finish inside the cockpit.

Campaigns can’t change sound levels. as for the timing I stand by point 4 in my first post.

Happy to hear that, and thank you for the kind words!

Thanks, I didn't know that. I'll update the mission.

@SkyWolfPL I ran the mission again. it worked. I tested the script separately. It worked. I tested the spawning of the Luftwaffe fighters, they spawned. I tested the startup, Blue 3 and 4 took off fine. I have no idea what's wrong with your install that gives you the error message, but as I said it usually happens when someone mentioned in the script is not alive. The Germans spawn 10 seconds before, so they must be alive. So I'm thinking about Blue 3 and 4, somehow your install got corrupted and they crash/ don't take off/ whatever.