Flappie

Devs answered: the initiator is linked to a vehicle. When in a Combined Arms slot and not in control of any vehicle, there is no initiator because there is no vehicle. But since the goal here is apparently to find "who?" rather than "which vehicle?", I'll ask them if it is possible to add a new field (something like "player_name").

I'm able to replicate a black veil for a split second. I hope it will be enough for devs to fix this issue. Thank again for identifying the mission, @Jayhawk1971.

I've found another common thing between both mission, Event 5, and CONQUEST from the other thread: in both missions, the fog ends with a thickness of 0 m. And since the issue happens at the end of each mission... I'll make some testing.

That's a start, thank you. For a moment, I thought the issue was caused by dynamic weather conflicting with fog, but there's only fog in Event 5. It must be fog, since this issue is almost as young as the new DCS fog.

I've never tried that, but that is a possibility. If you don't see any performance hit, you're good to go. But if you start witnessing issues you weren't witnessing before, you'll know the cause.

This is the exact same symptom. In that other thread, the track allowed me to reproduce the issue but only when I was about to land (I tested the landing light during flight). Both threads will be merged into one. Do you happen to have the track of this issue? Which mission from the campaign was it?

Here's an example of a Process Lasso user who had forgotten to unpark cores. Core unparked, performance issue solved. Please give it a go if your dcs.log shows such warning: 2025-02-25 05:07:46.799 WARNING EDCORE (Main): CPU HAS PARKED LOGICAL CORES (this can be source of stuttering and reduced performance especially on hybrid CPUs with P/E-cores)

It seems to work just fine when the initiator is a pilot. But it does not work when the initiator is using a special slot such as Game Master. I'll report this issue. Thanks for bumping this thread. It does not work from the Mission Editor either, but that sounds normal.

Thanks for testing this. I guess we can say, no script is causing this. Please attach: your dcs log file (Saved Games/DCS/Logs/dcs). your dxdiag.log file (here's how to get it).

The issue was caused by a strange modification of the mission (the UH-60A is "uncontrolled" yet starts in the air). Devs issued a fix which prevents the combination of these two settings at once). It will be applied in the next DCS core update.

Here's a video (made in Release) and a track. F-5e night.trk

I've asked devs about this while the fix was being done. This will be implemented later on. The full sequence is shown by ED's Belouga. RAZBAM needs to replace their Belouga version with ED's. See attached track: AI Mirage F1 uses ED's, AI Mirage 2000 uses RAZBAM's (the "chrome" one). Belouga_dfferences.trk

Thanks for your feedback.

Good news: the fix for the former issue you reported works for this issue as well.

Very clean design!

Your issue is not usual. It's most probably caused by something in your Saved Games/DCS folder. Some custom scripts cause such performance issues and I'm checking with you whether that's the problem here. Get well soon!

What I meant is they are bright yellow on my end. You two clearly have the same issue and you need to find what it is. Clearing shader cache is a good idea too. The next time you report visual issues, please attach screenshots in OP.

@Raffi75 The "zoom" feature of the Mi-24P module is not an actual zoom, it simply switches between two large pictures with different scales. Since there is only one picture, you see black when you try to display the second picture.

Your Export.lua is OK. If you have a "Hook" folder inside "Scripts", rename it to "Hook.bak" in order to disable it temporarily. Then launch DCS and see if that changes anything.

Yes, maybe my solution was kind of a placebo, I'm not sure, but I still get this issue from time to time. Maybe the issue is twofold. Anyway, devs are testing a fix.

I just cannot reproduce your issue with flood lights. With flood lights to the max, it's almost daytime in my cockpit even in a moonless night (Remastered F-5E). I've just watched @Bucic's video and now I understand what you two are talking about. The flood lights on the back appear white when they should be bright yellow. And they should emit light just like in the picture above. You guys should check your mods and/or try a DCS cleanup and repair.

It is not recommended to store DCS on an external drives, for two main reasons: Transfer speed. DCS reads a lot of files during flights. A relatively slow file transfer can cause stutters. USB disconnecting (rather a rare issue, but you don't want it to happen during flights). You can still give it a try and see what you get.

Yes, it makes a huge difference because it would ease the reproduction of the bug for devs. Do you have the mission file, or even better, the DCS track? @scommander2 Do you remember which targets you destroyed on the airfield? I think any unit can do as long as it leaves the brown crater, but just in case, that information could be useful.

Yes, there is some news. A fix is about to be tested.

I'm interested in perfecting both as long as I find good reference material of the real F-5E. You do have a real F-5E panel, or you built one from scratch? I want to see it anyway, but for the sake of reporting to devs, I need the real thing of course.