SignorMagnifico

I can confirm I'm also experiencing this black texture flickering issue on objects when motion blur is turned on in the latest DCS version 2.9.18.12722. This has been persistent across multiple patches, and I agree with @HR-Crumble that the issue occurs most commonly with "smoke logic/effects of varying types: fog, dust storm, missile smoke, engine smoke (F4, Migs, older jets etc), catapult steam, vehicle dust trails." Attaching a track file, screenshots, my graphics settings, dxdiag, and a YouTube video of the issue happening in hopes the dev team can replicate this and fix it. Turning off motion blur stops the flickering, but that's a band-aid. @Flappie Are you able to replicate this? DxDiag.txt textureflickering.trk

I noticed this bug in the Hunters Over the Yalu Campaign Mission 11. The Mig-15 AI is set to ace level and randomly crashes itself into the ground at the beginning of the mission when the player flight is taking off. The chance of the AI crashing itself is random as reflying the mission does not always result in the AI crashing. It seems to happen roughly 20 - 30% of the time. Track file and YouTube video of the bug attached. Recorded on DCS 2.9.17.12034. caseyjonesdead.rar

Thank you for the response and for checking with the team!

Thank you for looking into it!

I guess this is correct as is? No control loss seems to be happening during high speed dives.

This is absolutely a must-have to make the core sim better. It's quite a pain having to fast forward through a mission multiple times to capture more than one angle of the same scene. The replay system should also work just like a "replay" and accurately portray what happened. The AI doesn't make the same choices during the replay that it does in the original scene, so it's impossible to use the track file to capture cool angles of air to air or air to ground kills. Not all of us have an army of cameramen ready to record the scenes live on a moment's notice, either. Fantastic work on this! It must have taken many, many, many attempts to get it right.

In the current DCS version 2.9.16.10523 I noticed that I'm able to dive the Sabre at full throttle from 30,000ft, exceeding Mach 1.1, and I can recover from the dive without the use of air brakes. I haven't flown the Sabre in a while, but I recall that normally during steep dives, I had to deploy the airbrakes to ensure I could pull out of the dive. Additionally, there seems to be weird vibrations going on at the wing tips once it exceeds Mach 1.0. Track file attached. F86MachTest.rar

Good question! Based on the video, the 5080 outperforms the 3080Ti with MSAA. Here is how they compare with DLSS

I tested the performance of the RTX 5080 against the 3080 Ti in DCS World while running the sim with MSAA. If you’re thinking about upgrading, this is the video for you! The conclusion timestamp at the end of the video summarizes findings after I did some number crunching. I also tested these cards with DLSS running to see how it compares, and that will be ready in a few days.

Thank you! That worked for me.

+1 this is much needed for dynamic spawns

To be honest, this would make the interface much easier to use. For example, my CMDS settings do not vary mission to mission because I have the same preferences for that. What does change for me is the unique properties for each flight such as TACAN, ILS, radio, IFF, datalink, HARM codes, and waypoints, etc.

The intake fan turbines inside the engine scoops do not spin when the engine is starting up or running. They are fixed in place. I'm pretty sure they should be spinning if the engine is on. Happens in all maps/scenarios where the F-4 is present with the engine on. I didn't test AI. I only tested my own aircraft. DCS 2.9.8.1214

Update: After today's patch, the performance in-cockpit is still pretty bad. FPS in the high 50's for me in the cockpit. In external view, I'm getting 100+. Tried lowering the "in cockpit displays" option to the lowest resolution (512), and that made no difference. I would try the optimised textures discussed in this thread, but that would break IC, unfortunately. Did anyone notice improvements? Seemed the same to me.

Thank you, BIGNEWY.