Panthera_Tigris

Is that toolkit one a better implementation than using the re-projection using the OpenXR tool?

Your conclusion seems to mirror mine that the extra v-cahce doesn't help with DCS much, unlike with other flight sims. BTW, the game is run on the frequency cores by default for me. Even though I selected "remember this is a game" in xbox game bar. The only way to run it on v-cahce cores is by using process lasso and selecting affinity. Not that it matters since results are the same for both of us.

No change for me because I was probably already GPU bound My CPU frame time was already 3-4 ms which is very good so I don't think it could have improved much. Meanwhile, my GPU frame time ranges from 12-15 ms. Guess I should reduce some settings because 15 ms is way too high with a 4090. CPU: 7950X3D GPU: 4090 FE Reverb G2 with 150% OpenXR resolution and max settings (except 2x MSAA) Also, the MT DCS is running on my non v-cache core for some reason even though I have it set to prefer v-cache in Process lasso. Not that it matters because even if I force it to run on v-cache, there is no perceptible change.

I am getting 60-65 fps on max settings (except 2x MSAA) and 150% in OpenXR. I can probably touch 90 if I reduce the OpenXR resolution and some other unnecessary stuff. This is on a Reverb G2. Anyway, downloading the MT patch now although it doesn't seem like I am CPU bottlenecked anymore. Edit: I gained maybe 1-4 fps with the MT patch. Which means I am def GPU bottlenecked now.

Got my 7950X3D yesterday and was testing it out pairing it with a 4090. Essentially, what I am trying to figure out is if the game benefits from the extra v-cahce on CCD0. MSFS and other sims benefit massively from v-cahce. Sadly, I am not seeing any difference when running the game on CCD0 or CCD1. Same CPU frame time and same overall FPS. Anyone else with this chip can confirm?

I am running my 4090 FE at 975mV@2750MHz with +200 core and +1300 VRAM. Haven't touched the power limit. Waiting for my 7950X3D to arrive before I tinker any more.

I am also about to buy this Molykote 55 since Nyogel is not available here. Sounds like it worked well for you?

Would really appreciate it if someone could do a quick TLDR! Dont want to watch the video.

I personally love campaigns and I am glad they are adding one to the Hind!

@Gunfighter6 I have almost the same specs as you: 10700K which is slightly faster and a watercooled 1080Ti. I run the Reverb at 150% SS!!! SSAA is soooo much better than MSAA in DCS. It's a double benefit - more clairty and also provides AA. Of course the aim is to maintain 45 FPS and then use reprojection. But in other sims, I can hit 90 FPS easily even with 150% SS on a Reverb.

Naah, I run my Reverb at 150% SS and its much clearer that way. It improves clarity enough that it makes MSAA sort of unnecessary (super-sampling is a form of antialiasing anyway). At that res, MSAA has no effect on cockpit and only on some distant buildings and power poles which are low priority anyway. The thing is if you can't get 90 FPS reliably, then it doesn't matter if you are at 75 or 50 because you will be on reprojection anyway.

@Adam. I don't know mate but it seems I am somehow the outlier here. I thought it was the VR shader mod that was making all the difference but apparently everyone else uses it too. Most of my settings are from this guide: https://www.gamersbynight.com/dcs-settings-vr/ FYI, turning off those windows setting in that guide also made a big difference. BTW, I do go below 45 FPS on the supercarrier but once in the air, its fine. I also turn off terrain shadows and just go max shadows in the cockpit instead. My conclusion is that its vert hard to get 90 FPS but very easy to get 45 FPS in DCS.

Same. I run at 45 FPS now with motion reprojection to 90. Turns out I can run my Reverb 150% SS, 2x MSAA and max shadows, terrain etc if I learn to live with 45 FPS + reprojection so yea.

No, thats not how it works Gunnars. Motion smoothing setting in SteamVR (for each individual app) applies motion reprojection to WMR headsets. It does not apply motion smoothing, even though it is called that. But that's ok since most people dont care about the difference. By default, motion reprojection is set to auto. Here, read these official patch notes: https://steamcommunity.com/games/719950/announcements/detail/3851080472164545100 Motion Reprojection Setting Changes This beta makes changes to how motion reprojection settings can be managed. Like before, the default.vrsettings file can be modified to specify the reprojection mode to use for all titles. As a reminder, the possible values are: disabled - motion reprojection is never applied. auto - motion reprojection is applied if the running title cannot maintain native framerate. motionvector - motion reprojection is always applied. Alternatively, if you're using Windows Mixed Reality for SteamVR in conjunction with the latest SteamVR release, you can now use SteamVR to manage motion reprojection settings on a per-application basis. To enable this functionality: Ensure you're running a supported version of SteamVR (1.10.28 or greater). Remove the "motionReprojectionMode" line from default.vrsettings. In the SteamVR settings, select Video > Per Application Video Settings. Select the title you're interested in, and change the motion smoothing option. Motion Smoothing Setting Use Global Setting - no application specific override. The global default mode is auto. Enabled - motion reprojection runs in auto mode, applying reprojection if the application cannot maintain native framerate. Disabled - motion reprojection is never applied for the application. Force Always-on - application runs at half-framerate with reprojection.

If you have motion reprojection on auto, then how come you are getting 55, 58, 59, 61 FPS etc? Shouldn't it switch on and render at 45 frames?