darkman222

Yes. Technically it does not matter if I have 2.5 ms of CPU frame time now or much more. But having headroom is a good thing for sure, and you can see in the frame time Graph in the comparison that it just does not stay below 11 ms it goes above it. And its not only just a spike. Its like 2 seconds or sometimes even more of just immersion breaking stuttering. I think that the architecture of the AMD processor is much more suited for DCS. Also bad things like DCS processes being calculated by the slower non X3D part of the processor or core parking issues seem to be sorted out by the most recent generation of AMD processors. I can highly recommend to switch to AMD if someone considers a new PC or even if you are the lucky ones that have their decision already taken by a faulty i9 processor that killed itself. In my case its more likely that the mainboard killed itself, but lets see what Intel and Asus Tech Support will tell...

I could not use the same track because my previous Intel PC just died without a warning. But its from a recording from DCS dogfighters. From days with comparable amount of users online. But I can say for sure, with the intel it has been like around 8 ms CPU frame time occasionally breaking the 11 ms barrier, creating VR stutters. And with the AMD the CPU frame time NEVER goes higher than 4ms. Most of the time 2.5 ms. Same on other servers or huge SP missions. The difference is massive even without a technical perfect comparison.

@iceman06I just tried your track file in 2d without any issues. I also tried it in VR which immidiately shows if something tanks performance. But even in VR its a smooth ride. See my CPU frame time graph from fpsVR. Only minimal CPU frame time spikes. Which wont cause any issue. I would not see any relation to the F16 radar altimeter. Must be a coincidence. Coming from an Intel switching to AMD I must say that Intel processors have a vey small L3 cache compared to AMD. I switched to AMD a week ago and the CPU frame time is now half compared to with the Intel. Dont take it personal but a 5 year old PC in the configuration you are using is not considered top tier for DCS. You can eliminate the radar altimeter causing issues with the same test on the caucasus map on the borders of the modelled area, where there is not much geometry to render. In your track file I would suspect the airfield, houses etc geometry being loaded and unloaded to cause the stutters. Probably use the DCS low graphics preset and replay your track file with that and see how it performs. That way you can reduce the workload of geometry and textures being loaded and unloaded as possible cause of the sutters.

I was wondering if the Mainz-Finthen Army Airfield will be added to the Germany CW map. It should be already modelled in the current phase. Although it is a small airflied it was used in CW by the US Army as a helicopter base. I hope you can bring this airfield to DCS too. See its Wiki Article here: https://en.wikipedia.org/wiki/Flugplatz_Mainz-Finthen

Alright. Thanks again for all the useful hints. For everybody who interested in the outcome. Here are the system specs of both systems. Note that the Intel system always was running around 8ms to 9 ms CPU frame time. Also see the yellow spikes in fpsVR on the CPU frame time graph that go up to 12 ms or more. This creates the annoying stutter in VR. In comparison the AMD system I have now stays well below 4ms CPU frame time most of the time. It even goes down to 2.5 ms. Which the Intel sytem never managed. Over all the money was well spent. No long lasting stutters. There are some micro stutters from time and again. But I dont see them on the CPU or GPU graph. But in general its a real smooth ride now using the Varjo Aero. ******************************************* ********************************************************************************************* *********************************************************************************************

Its the exact same configuration. i9 13900KS replaced by Ryzen 9950x3D together with a RTX 4090 and the Varjo Aero. DCS settings set to VR-preset. 90 Hz was no problem before either. But the CPU occupation was higher in general. Now I barely get any CPU frame time spikes. Its like night and day. From what I read about the differences of the two CPUs it could be that the huge L3 cache of the Ryzen makes a big difference in my setup.

Thanks for all the useful hints here. I went with Ryzen 9950X3D. The system is running now. And wow. On servers where I had around 6ms CPU frame times, spiking up to 12ms even up to 19ms with the Intel -> On these servers I now have between 2,5 ms to 4 ms. No spikes at all, no more stutters. I will try to give you guys a better comparison looking into my stutters video archieve. I cant compare directly any more as the Intel system is dead. But its a huge improvement!

Thanks for the explanation about the 9900x3d. Makes sense why nobody talks about it. I found this video of a spanish speaking youtuber. He is testing the 9950x3D and the 9800x3D in Vr in this video. Unfortunatey he seemed to have bottlenecked his test with the GPU. He has a lot of setting to high. I thought the RTX 5090 would handle it. But he has a CPU frame time chart in the end, which shows that the 9950x3d gives some kind of improvement to the CPU frame time. Here is the video at 6:00 min: Or see this screenshot:

Thanks for the opinions. So the money I will spend is not the main consideration. Improving stutters is. Seems like abandoning Intel and going AMD is the way. From the youtube tests people do with the 9800x3d vs the 9950x3d the fps gain is minor. But the tests are done in 1080p resolution. Which tends to reduce the advantage of a fast CPU. We also have the 9900x3d nobody seems to talk about for unkown reasons.

Thanks guys. Would you say, with the AMD, I will see improvements in CPU frame time aka CPU bottleneck stutters compared to the Intel CPU?

Since my PC died yesterday, I am thinking of switching to AMD coming from Intel. I had the i9 13900KS before. Using VR ( Aero and now the MeganeX) together with a RTX 4090. Depending on the DCS online server or complex single player missions I had severe stutters due to long CPU frame times 12 to 19 ms = CPU bottleneck. As I need a replacement PC soon, I dont want to dig too deep and too long. So the basic questions are: 1) If I compare the single thread rating here: https://www.cpubenchmark.net/compare/5684vs6549/Intel-i9-14900KF-vs-AMD-Ryzen-9-9950X3D both CPU seem to have pretty much the same performance. BUT the L3 cache is much higher for AMD with 128 MB (Intel only 36 MB) will this potentially give less stutters in VR? Also the clock speed is 1,1 Ghz faster on the AMD. 2) Is there any issues running a RTX 4090 (upgrading to RTX 5090 later) on an AMD system for VR (Aero and MeganeX) use? Thanks in advance for the quick help!

Reproduction: -SP mission. One house in the middle, first ring of houses 250 ft, second ring of houses 500ft. STP in the exact middle on the middle house. Make sure its altitude sits on ground level. -F16 with three bags, hot start, so everything is set up correctly -fly for 2h in any direction, and return and check the waypoint that should be in the exact middle -check INS drift after 2 hours = 400 ft -refuel, repeat: INS drift after 4 hours = 1000 ft -refuel, repeat: INS drift after 6 hours = 1300 ft This was the maximum INS drift I could measure. If you fly around the STP you can bring it to match better due to paralax. I suspect a higher drift in altitude to contribute to the big visible offset. Track attached. https://www.dropbox.com/scl/fi/vb32dm3o09bztxvyvjiry/ins-drift-6-hours.trk?rlkey=50p1ixlfl17rg6b536zremeit&st=7hm9nemo&dl=0

You have the MeganeX also? And your lighthouse setup works? How far are the light houses from your seat?

Thanks. Well that gives about + 15 fps. But the low resolution area is barely noticeable. Maybe I just play with higher foveation. The only thing that still stands out is the bad tracking behavior. I can see it especially when the game is paused. It often likes to fade to grey screen, when tracking is lost which is even more annoying.

No, where would I set it? In DCS there is only the quadviews option. OpenXR toolkit crashes DCS when jumping in the jet. Where can I set foveated rendering?