Gunnars Driver

Glad you’re happy! :) You are well worth this after a long time of stutter issues ! Yes, as DCS isnt amoung the most well designed games it isnt possible to set all sliders to maximum and still enjoy it. Despite this, I found myself at 90 fps on the supercarrier. Had tuned the SS to 100% (due to pimax) and back on the Reverb I had 90 fps with sbsolutely no stutter and also 90 fps in moste other cases. I had a Asus strix 2080 OC that was a bit further clocked and everything worked nice before, still the increase in DCS performance is really really good. Not cheap, but still worth it :) Once again, congrats to the solution you needed ! :thumbup:

You got a message....

Yep, just saw that. Maybe knew but had forgotten.

[Edit]Delited, just found out StramVR motion smoothing is in fact motion reprojection. Didnt know, or had forgotten...

If you use the WMR version its ”motion reprojection”. If you use stemVR version its ”motion smoothing”. If you have oculus its ”ASW”. Different name, same basics but not exatly the same. Some are better some are worse.

:)

If we need to be really correct in ”auto” we have no motionsmoothing or forcing at 90fps. If 90fps, motionsmoothing is off and we keep the vsynced 90. below 90fps but not lower than 45, we force 45fps, and motion smoothing is on.

Theres different options: motionsmoothing = On casuses motionsmoothing on always, only 45fps. Auto =motionsmoothing on between 89 down to 45. I only use auto.

I also started with VR when the Oculus Rift CV1 arrived. Theres more to do with WMR before you are up and running but the good guides at vr4dcs.com should be enough. The extra work is very well worth it and if you get the fpsvr app, you will be able to tune the VR and DCS graphic settings in a fraction of the time. For me the total time used to get running and all setups done was way less with Reverb. When you start using WMR /Reverb, you sont know all software and settings needed. Thats why you should follow a guide the first time.

This is the reprojection setting I recommend for now: Red oval circle: default is = none and should be changed to auto. Open, change text between " ...and..." Save. Open again and check it was saved (says "auto" when opened) This file can be in different locations. If you dont know where it is, search for default.vrsettings.

A classic thing here in the VR forum is that people have problems. We try to help by saying "you must check this or/and that". The guy with problems doesnt check but continue with other tests and trys and aks questions about new stuff and then we might miss the issue. Theres only on way to make sure it will be fixed. Getting it right, step by step. This will also meaning that some checks will just be checking values or settings that already is correct.

The DCS VR preset isnt what I would recommend to use. It is only a combination of settings that ED formed to try VR. These might be to high and cause stutter on a computer with older hardware or a VR headset with high resolution. The other way around for a top of the line computer, settings not optimized. So, you want to tune the settings without using the VR-preset. Can you confirm that you only se 90fps or 45 fps and not a continously changing fps number ? (reprojection working...) Because if you dont have reprojection the gaming wont be smooth. This is critical to even try to come any further. Because I (or other in the thread) will try to give tips for nice settings but if we not are 100% sure reprojection work you will have a mess and no smooth gaming. Its really not even an idea to continue if we havent cleared that thing.

In Windowes Mixed reality the setting should be resolution = 4320x2160. (it might not affect gaming, probably only in the WMR waiting room, but to be safe). Also, set 90fps there. In SteamVR set the slider to as close as possible to 2160x2160, should read 100% also. Didnt hav a picture of 100% for DCS tab These tabs multiply on each other so you really need 100%(about 2160x2160) to get true 100% Supersampling.

So, I had a Asus strix OC 2080ti before I got my asus strix 3090 OC. Havent tuned any settings( things can be tuned up but I will tune for my new Pimax 8KX). If you use my settings it should work nice. What DCS aircrafts do you have? Because F-14, or mainly Heatblur doesnt run as nice as others. I think you should use another one when doing the initial tuning. Maybe lower settings for F-14 later but the initial plan should be to get it to work properly without the extra burdon from F-14. I dont remember, do you have fpsvr ? (A must, its 4USD /Euro and well worth it for tuning. For me it made the rtuning take one evening instead of several weeks). We need to start by making sure you actually have got reprojection to work. IOf working, you should really never see any fram times between 45 and 90. Cause reprojection either uses 90 fps when the computer is up to it or else it uses 45 fps and "doubles the frames"(not really, but the short explaination). So, varying fps between 45 and 90 shouldnt be there. Some tuning or checks can be done with the projection of but if you can not start it so it actually do reproject, you will have stutter. If you start steam and look in the biblio you should have "Windows mied reality for SteamVR -Beta, 1.2..444 -do you se that one ? You should also find Steam VR -Beta - 1.15.8 -got that one also ? The nvidia control panel settings should be as this guide: https://vr4dcs.com/2020/10/19/nvidia-control-panel-settings/ ( I have my W10 in swedish language, otherwise I could have posted screen dumps.) use per application setting, add DCS if needed) VR prerendered frames - use 3 or 4. In Steam VR, do not use higher supersampling yet = should be set to as close as 2160 times 2160 as possible which should correlate to 100% at least if the beta is used both in global and per application setting. In DCS use these settings, but tune down the clutter/grass and trees visibility.

original Oculus Rift did have problems with some USB3.0 ports, like asmedia, which couldnt be used. The true intel 3.0 did work fine however. I dont know if this is fixed for Rift or if the other Oculus have the same issues. Reverb: I dont know, havent had any issues or read about limitations. what should be done is to use intel 3.0 USB that sits directly to the motheroard, to ovoid issues. Other ports might work fine but if there is any trouble you should set it up the safest way first to see that it works and then try the other solutions.

For me it doesnt give the same numbers. GPUz and fpsvr show the VRAM used by one process. performance tab in task manager gives total use, which covers what seems to be windows use + the gpuz/fpsvr value. In all of these the reported VRAM usage varies( se an earlier post in this thread. If a game would really only use 5 or 8 Gb, why would the reported VRAM say for example 16 Gb and also vary during gaming? The age of the article doesnt matther. When microsoft implemented this feature to the task manager (Fall creators update; spring 2018) this feature was implemented. I’d say a lot of this discussions has its origin in some missunderstandings. For me, the windows developers worlds is more thrustworthy.

Windows numbers is correct after Fall Crestors update. At least this is what microsoft Direct X states on their developers blog: https://devblogs.microsoft.com/direc...-task-manager/

USB3.0 is good enough. No problems

And here: https://vr4dcs.com/2020/10/19/nvidia-control-panel-settings/

Here https://vr4dcs.com/2019/09/10/reverb-settings-for-dcs/

The guide is updated, but not the date on top. For example it said windows 10 version 1903 or 1909 before. Now ot says 2004 which is from this spring. There a newer version which I use and this works good as well. I think almost everything works the same for the setup despite upgraded firmware. Earlier you needed to use SteamVR Beta-version to make 100% Supersampling to be about the same as the native resolution but I think the non beta is updated to work the same. Anyhow, I still use the beta with the latest version and it works very well. —> Do the setup as the guide and then we can discuss settings from that point to make DCS rock. https://vr4dcs.com/2019/08/08/moving-from-oculus-to-reverb/ Cannot post more than one link, Ill do another post.

I think theres plenty oof knowledge here. But the easiest way to start is to follow the reverb guide at vr4dcs. Follow that guide and you are safe

Happens with WMR, dunno why. Easy fix: Press Alt+Tab until DCS is selected then hit numpad 5 to recenter. Done. Always works.

Did you lower the cpu clock to 4.9 ? What should be checked, to be sure it isnt a problem( this step might be jumped if you are a very experienced overclocker, then you know this for sure already) is to check that the cpu really does the anticipated clock freq on all cores, and during the whole gaming session. Use HWinfo64 or something like this ( I run my CPU @5.2 when gaming but I lowered the clock for a 3d work the other day, havent DCS-ed since). Whart we need is to se that we keep the set clock speed on all cores and during the gaming. Some settings(actually the default settings is supposed to) allow the CPU to clock down from turbo to a lower freq. If we have overclocked to 4.9 or 5.0 but the clock automatic lowers after 30-60s we may be down at the stock clock of 3.6 to 4ghz or so, and then we of course get bad performance... If you reset the bios and then set XMP ( which normally only sets the RAM clocks to the extreme memory profile) its possible/probable that your cpu doesnt keep 4.9 or 5 during the game. Use the HWinfo window, to gaming and look at it from time to time. It should nver show a lower value then your set clock, exept from small deviations due to the measuremens and maybe variation in the bus clock( so, for 4900mhz 4997 to 4902 or so is ok). otherwise, do you use fpsvr ? its extremely helpfull and easy to use for tuning. Next thing, I find different module vendors to produce a lot different level of smooth gaming, and F-14 (by Heatblur) isnt the best when it comes to smoothness. The AJS37 viggen by Heatblur is the same. So, do the tuning with another aircraft and get it smooth. Then maybe find a lower setting for F-14 but dont expect it to flow as smooth as the better aircrafts, unfortunately. By the way, did I say anything abvout the reverb guide at vr4dcs.com ? Follow this guides, both for reverb setup and windows and nvidia control panel. Initially, before you learn how it works with the reverb/WMR it is not easy to oveclook some settings, causing stutter.

I have the G1 (also Rift and Pimax 8KX). I wonder if you have gotten the reprojection to work? For me WMR reprojection is very good and I dont notice when it shifts between 90 fps and 45 with reprojection. SteamVR reprojektion(motionsmoothing) is also good but for me but I felt WMR motionreprojection best. Oculus and Pimax reprojection is prone to ghosting but with WMR I dont get it. Do you use fpsvr? If reprojection is used you should o ly se 90 or 45 fps. The frame rate do not constantly vary if reprojection is working. Also, it is very easy[/] to bog down any computer in DCS. If you havent tuned DCS settings for the reberb when coming from the Index(?) I can say that we should expect stutter or at least non smooth gaming. If you use fpsvr and tune the settings you will find that you need a little extra headroom on the CPU and GPU frame times to get completely smooth gaming. I recommend reading the Thuds guides at vr4dcs.com for the Reverb setup and the initial tuning. There is good tips for this there. Do not do the misstake to begin with high settings because you think your hardware(for example 3090) is invincible. In DCS, it just isnt. I have a 9900KS@5.2Ghz + a Asus Strix 3090 OC.