Flappie

Texture issues reported. 👍

OK, I see what you mean. That happens because you told him to do a "turning point" instead of a "fly over point". If you select the latter, it will work as expected.
f18c2_fly over point.miz

Hello and welcome to DCS. 😀
I believe the answer you're seeking is here:
 

Hi. Your DCS crashes when tasked to compile shaders.
Try uninstalling and reinstalling your GPU driver.

Thanks for the heads up. It's not about being in the cockpit, it's about being close or far from the light. The light disappears way too quickly.
Issue reported.

Your system drive is full:
Drive: C: Free Space: 0.2 GB Total Space: 237.9 GB File System: NTFS Model: Samsung SSD 850 EVO 250GB Drive: D: Free Space: 44.7 GB Total Space: 1907.7 GB File System: NTFS Model: Samsung 980 PRO with Heatsink 2TB Drive: E: Free Space: 31.3 GB Total Space: 953.9 GB File System: NTFS Model: Samsung SSD 970 EVO 1TB which means your pagefile cannot expand. Free up some space on your system drive (not only for the sake of DCS) and you should be good to go.
(actually your two other drives are also almost full)

Great work, @Skuva! Thank you.
Battle of Zugdidi issues are now reported. I'll keep you updated about the other two missions.

Hi, the problem was fixed internally a couple days ago. The fix should be part of the next OB update.
@FrostLaufeyson Your track proved very useful. I ran it in current OB and saw the problem, then ran it in ED internal build and saw the problem was fixed. It took me 5 minutes. This is one of the reasons why providing tracks is so important when posting about an issue. Thank you! 👍

Hi. There's an internal report about wrong names for jettisoned weapons.
Here's the list:
S-24B rockets is named "AN/AAQ-28 LITENING" (when jettisoned from MiG-29 / no such issue when jettisoned from Mi-24P) S-25L missile is named "AIM-9S (Green)" Kh-58 missile is named "AIM-9S (Orange)" Kh-25MPU missile is named "9K114 Shturm" KGMU-2 AO-2 is named "MPS-410" KGMU-2 PTAB is named "Kopyo" If you find other errors, please post them here so I can add them to the report.

Thank you.
This is what I get (AMD 3700X + GTX 1808Ti + 32GB of RAM):
From T0 to T1000 aprox 90 FPS at T1000 to T1200 aprox 100 FPS at T1200 aprox 82 FPS Variations are much less important than on your PC.
I see your PC is powered by an old CPU (i5-2550K, made in 2012) and your FPS sink when you're in the vicinity of bombers. I'm pretty sure your FPS counter reads "CPU bound" in red when your FPS sink. You should consider upgrading your PC, especially if you often fly missions with such large bomber formations.

Good! In case you get new crashes, the best thing to try is removing your "old" 32GB RAM sticks.

You're welcome.
Please try this:
 

Hey, I was about to test your track today.
You did something really weird: setting up an invisible FARP in an airbase perimeter (the black circle). At first, I thought a FARP/airbase conflict was the source of the issue, but it's not. I placed the FARP away from the airbase and I can confirme the issue. Crosswind + CH-47 + takeoff from FARP causes this. The issue is now reported.
In the meantime, if you want your CH-47 to take off properly from its airbase spot, simply remove the invisible FARP underneath it (no active FARP should be placed in an airbase perimeter), then ask it to takeoff from ground. It works.

Your report helped me discover it is a global issue. Thanks again.
If you don't want to see it anymore, you can untick the aircraft in the NS430 Special options menu.

Hi, please try these steps, one after the other:
 

You're welcome. I use Windows Defender as well and adding DCS as an exception did save me quite some time whenever DCS starts.
Talking about memory, DCS Preload Radius eats RAM. Don't neglect it when you try to optimize your settings.

Thanks for your detailed report. Devs are working on a fix.

Yes, it is a possibility. The crash message is not very helpful here. In this case, it's best to try different solutions. We often advise to:
Run a DCS cleanup and repair (in case the game files are damaged) Rename the Saved Games/DCS... folder (in case a user mod/setting/whatever is causing a conflict) I often advise the repair first because it does not alter custom settings. However, if you often use mods, it's best to try renaming the Saved Games/DCS... folder first.
Because mods are often source of trouble: they need to be adapted to an ever changing sim, and this takes time to detect issues, and more time to fix the mod code.
I'll keep an eye here. Let us know if your issue is solved for good.

Neutrals being visible in any Map View setting was reported earlier. I've just asked for some news.
I'll report the target icons being visible.

I've just tested in OB and the sounds are all here. It must be caused by a mod.

Thanks for your feedback.

Hi. This issue was solved in Open Beta. Are you using DCS Release version, 2.8.4.39731 ?

Hi. Takeoff from runway does not exist for Clients (MP). It only exists for Player (SP). Clients get moved automatically to an available parking spot.

Hi. Nowadays, DCS needs about 50GB to run a multiplayer game with medium to high graphics, on detailed maps such as Syria.
Your PC has a 6 GB pagefile, and 32 GB of RAM. Near the end of your log, DCS explicitly writes it lacks memory to perform its tasks.
You have three different ways to fix it:
Buy more RAM (you need a total of 64GB). Lower your graphic settings and preload radius. Set a bigger pagefile, and ensure it is stored on your fastest drive. Here's a guide. Choose this value for both init size and max size: 32768 (32GB). Make sure your drives have at least 50GB of free space.

Hi. The rotor brake axis bug was reported earlier:
And so was the rear panel lighting bug: