With lights off, no one is going to see you easily anyway. You should also be getting formed up on it ASAP as this is a time sensitive flight, take too long on checking and they get away.
Hi @xavnl
The first part of the Briefing will be the same as before mission start, but if you scroll further down you will see the debrief part talking about what went down.
Hi @theIRIEone
You say you are running mods like the NTTR range mod?
That might be your problem. As I mentioned in my previous post:
The No.1 Rule with DCS Campaigns... If you have ANY mod that is NOT purchased from the DCS Store, it will probably cause issues.
SRS and OpenKneeboard(Mostly VR users) seem to be ok, as we test these missions using both.
Make sure to remove any and all mods before flying campaigns. (Check out OVGME, I use it daily and it works well)
Unfortunately, a mod that worked for years and causing no issues can suddenly start causing problems. The NTTR one was the root of many campaign issues I personally had in the past.
Tacview was the next one causing issues for me.
I just ran the opening part of the mission, track attached, and there was no issue. The S3 wasn't anywhere near ready to taxi when I got the taxi pop up.
All worked fine and I only have SRS and Open Kneeboard.
Thanks for this but I ran a full pc format. Re-installed all mt DCS items and it is working better than before. Maxed out settings looking amazing with 100+ frames in most cases. Just Syria still hurt the FPS but not badly enough to cause stutters.
Jakes's post in Mission 5 Blue Balls was marked as the answer