exil

Bäume kostet auch was aber nicht so sehr wie Gras finde ich, bzw. möchte ich nicht ohne Bäume leben Wenn du die Settings dabei zu weit runter schraubt, bauen sich die Bäume direkt vor deiner Nase auf, was ziemlich nervig sein kann.

In der Regel liegt das an zu wenig frames in Verbindung mit motion smoothing. Letzteres kommt nicht hinterher wenn die Geschwindigkeit zu hoch ist. So zumindest meine Feststellung. Flieg mal langsam mit der Huey tief und schau ob du das Problem dann noch hast. Achso ja, Gras & Büsche haben einen enormen impact im Tiefflug, so gern ich sie habe, bei mir sind die mittlerweile aus.

So, just to clarify, you're dropping below 45fps in the benchmark test? Because even with the described drops between 30 - 90% GPU usage I never dropped below 45fps in that test. And does your Gpu boost to the given boost clock and then drops down or does it even not reach the boost clock? Maybe test also with hwinfo and have a look at your maximum and average clock speed.

Thanks! Interesting... In that case I also have to investigate. My GPU is jumping around between 30 and 99% within seconds in fpsvr. Is that typo or are you talking about CPU? Because we talked about GPU usage.

I thought that too because mine was doing the same, but this seems to be pretty normal in modern GPU architectures. GPUs are altering every now and then to not overheat. If your Gpu would run at >90% all the time it would simply overheat. At least this is what some far more experienced users in a hardware forum told me when I asked the same question.

Are you sure you're benching the correct mission? Iirc the 'heavy' mission lasted a bit longer than the not so heavy mission. That could at least explain the missing frames.

That sound great but also a lot of work! Eagerly waiting for the results!

By the way: did any of you amd owners already tested the Sam VS. non-SAM in DCS? If it's close to 10% I would think about updating my mainboard.

Thanks a lot!

Could you be so kind and post your in-game settings and the mission you benched with as I would like to compare your results to my 6900XT? Edit: and I am, of course, also interested in the Radeon settings.

Thanks for the reply. Did delete Metashaders and fxo. Sure, half the native hz would be 45. But I sometimes dip down to 30fps, but my frametimes are in a 14 - 15ms range. But personally, I think it's not the card itself but more a steamvr problem. I'll investigate further after Christmas and let you know. By the way: Merry Christmas!

Cool, you're welcome! Now, with 8 - 12ms you can try and bump up SS for some more eye candy and see if that works. Or you can turn terrain shadows to flat. Now starts the "back and forth" game, depending on your personal preference. Some people love to have shadows, some don't and rather turn up more SS instead. It's really an iteration of what works for you and what not. Yeah, VR together with simulation is more or less the worst hobby you can have money wise. You'll invest a lot and will never be 100% happy because it's so demanding. But I couldn't and wouldn't go back!

We use fpsvr, a tool which measures and indicates your gpu and cpu frametimes Realtime. I am afraid you can only use it for wmr headsets using steamvr. It won't work with oculus software.

I think one of the main reasons for bad performance is visibility range. Bump that down to High or even Medium. In VR you won't notice that much of a difference. That setting is a GPU killer! Also you can try to experiment with Msaa and SS (after you lowered visibility range) . With SS bumped up you won't see a big difference between msaa on or off but the overall image is sharper. By the way: which GPU are you running?

Hälst du die 45fps mit den settings auch in Syrien im Tiefflug mit der A10? Ich habe da gerade noch ein wenig Probleme. Liegt aber glaube ich eher nicht an der Karte sonder am reprojection in WMR an sich.

Sorry for the late response. No, i uninstalled nvidia drivers without using ddu and put my 6900 in. But i didn't measure scientifically what happend to my CPU frametimes. I just saw, that the were mostly in the green in fpsvr and was happy with it. But i noticed another strange behavior: My GPU frametimes sometimes went up to around 15ms in GPU heavy scenarios on the syria map. When that happend with my 1080 and reprojection on (HP Reverb G1) i was still able to maintain 45fps. Now, with the same frametimes in the 6900XT it is sometimes locked at 30fps (although the headset is running with 90hz). When i switch off reprojection i am seeing around 50 - 60fps in the same area. So idk if its a WMR problem or an AMD drivers problem that causes it. (But maybe that is worth another topic and i don't wan't to hijack your threat).

Ich habe ein komisches Verhalten von wmr reprojection festgestellt. Ich komme bei fpsvr nie über 20ms. Mit aktivierte reprojection (immer an) kappt das teilweise bei 30fps. Ich habe reprojection dann mal ausgestellt und siehe da: ich erreiche irgendwas zwischen 50 und 60fps. Das komische, wenn ich bei 30fps die reprojection ausschalte und dann wieder einschalte habe ich wieder 45fps. Vielleicht liegt es bei dir auch daran. Edit: das Verhalten hatte ich bei meiner 1080 nicht (oder kann mich nicht dran erinnern).

Ja und nein. Den Bug gibt's derzeit nur bei der Reverb G2. Du hast aber recht was die native Auflösung angeht. Die Index hat 1440 x 1600. Die stellst du erstmal in Steam ein und dann schau mal mit deinen aktuellen Settings wie es läuft. Eigentlich müssten da deutlich mehr als 30Fps drin sein. Ich habe eine Reverb G1 mit Rx 6900xt und die läuft mit ähnlichen Settings wie deinen (und sogar mit terrain shadows auf flat) in Syrien mit der A10 auf relativ stabilen 45fps. Dass ganze mit 140% SS in steam. Edit: Versuchs mal mit Vsync aus.

Strange! I have no such problems here with GTX 1080 vs. my new Rx 6900xt. CPU frametimes stayed pretty much the same.

Ich kenne mich mit der valve nicht aus, aber die reverb kann man unter Windows auf 60hz laufen lassen. Dass bedeutet, dass jedesmal wenn Reprojection greift, die FPS auf 30 limitiert werden. Das wäre für mich zunächst das erste, wonach ich suchen würde und dies dann entsprechend umstellen. Des Weiteren empfehle ich dir fpsvr, gibt's im steam Shop für 4€ oder so. Da kannst du schauen, wie hoch die Frametimes der GPU und CPU laufen und prüfen was ins Limit läuft. Die 3090 müsste eigentlich mehr schaffen. Du kannst mal versuchen, die Sichtweite auf Mittel zu stellen und die terrain texturen auf niedrig. Macht optisch in VR kaum einen Unterschied.

Do you maybe have the DCS in game settings for this test? I have both, the 3090 and the 6900 at home and would like to compare!

@Aurelius Good to see that AMDs lower interface bandwidth doesn't really has an impact on DCS VR. At least with the 6900XT. I saw a lot of reviews where the 3080 outerperforms the 6800XT in 4K while it's the other way round in 1080p. People were reasoning that this has to do with the interface bandwidth (256 vs 384). Since there are no reviews regarding DCS especially in VR I had my doubts as well. I am really curious how the 6800XT handles DCS compared to the 3080 since they are on nearly the same price tag. If the results are similar to your comparison (3090 vs 6900XT) I would go AMD all the way (10 vs 16GB VRAM). And your test shows, that there is hope for Amd ;)

Sure about that? According to fpsvr I need the whole 8GB with my 1080 and the G1. Also I saw big improvements when I updated from 16GB to 32GB ram. And e. g. Syria needs around 23GB of ram!

Noticed a rather big hit on gpu frametimes when switching on interior lights (floodlights) in the A-10 after update. Something like 1.5 - 2 frametimes no matter if its day or night. Even noticed a little increase when switching on external lights. Still testing but my conclusion is, that performance is highly depending on the modules lightning.

Did the Job for me at least with HP Reverb. Fps are back to normal but i experience an invrease of Gpu frametimes, but still playable with mostly stable 45 Fps. System is a ryzen 3600x with gtx 1080. msaa off. Slrr off, water textures to Medium and shadows flat only.