HP Reverb G1 issues

[Kula66]

I had a 1080ti and Rift S and got good (not great) performance with DCS settings set fairly high, around 40FPS - happy simmer. I then bought an HP Reverb G1, but my 1080ti just didn't have the grunt to run it. So, I waited until the new nvidia cards cam out and got a 3090. Installed the card and the Rift S is super smooth at high settings and on the Syria map - 40FPS, but very smooth.

 

Now, plug in the HP Reverb and the view goes to hell ... when you roll the 14 at 15k', the ground just turns into a stuttery/teary mess. In fpsVR says the card is running at 60-70% as is the CPU - the odd red spike, but mainly steady orange. I've tried turning settings down in WMR and SteamVR (70%) and it makes no difference. I've deleted shaders, Nvidia control panel is set to default. Latest drivers. etc.

 

Is there something I'm missing??

 

[Motomouse]

Settings?

CPU?

frametimes?

 

[Svsmokey]

Were you running a high pd in dcs settings for the S ? . Try 1.0 .

[Kula66]

Hi, no I was running 1.1 on the rift S, then up to 1.3 on the HP and back to 1.0 ... no real difference to the tearing. I literally took out a well running Rift S/1080ti and replaced them with a G1/3090. I've tried various settings and still get the issue.

[Kula66]

If I change to default VR settings, I get GPU frametime 10, CPU 15, 60FPS and 30% reprojection ... and I still get judders when I roll the 14 over land - and it now looks horrible!

[Kula66]

Tried renaming DCS.openbeta folder ... no difference

[Gunnars Driver]

PD should be set to 1.0 and all SS should be done in SteamVR. The setting in SteamVR isnt logic, the generic SS multiply with the per application SS, so you should not use both. To start, use only 100% in both generic and per application.

 

The setup overall for WMR has some possibilities to get it wrong. I suggest to follow the reverb guide in vr4dcs.

 

The DCS settings:

Shadows should be flat or of.

Terrain textures, start with low

Heat blur = off

MSAA start with OFF

Depth of field = OFF

Lens effect = none

motion blur=OFF

SSAA= off

Clutter and grass= begin with minimum.

Trees visibility = start with low setting.

Chimney/smoke = 0

Anisotropic filtering 2x for start.

Terrain shadows = flat

Cocköit global illum = OFF

 

Also, make 100% sure that you are able to activate and deactivate reprojection. Its really a key to success. Suggest reprojection "auto", which should give you 45fps for most of the time. If you see values between 45 and 90 fps more than very brief there isnt any reprojection and the ride will not be smooth.

 

Get the fpsvr app, 4 usd at steam, tuning and understanding what is the limiting factor is very easy with fpsavr (also detecting other problems that causes stutter etc). Its easy to see what part: CPU, GPU, RAM or VRAM, that is the limiting factor and also easy to detect the effect of changed settings - tuning has never been as easy.

 

The initial setup for Reverb:

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

 

Plus the tunings that can be done in nvidia control panel:

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

[Kula66]

Hi GD, thanks for the info. I have the fpsVR app ... thats where I got the figures. I think the DCS VR settings are pretty low. When I first added the 3090/G1, with my old Risft S DCS settings, I was getting a pretty solid 45. Setting to DCS VR, it was 60-75, but still getting the tearing/juddering when rolling over land (not a town).

[Gusti]

I run DCS on a reverb G1 with an RTX2080TI on a 9900k. I did setup my system according Thudˋs VR4DCS guide https://vr4dcs.com and since then it runs well. Make sure to have motion reprojection activated (you need to edit a file within steam vr for that and sometimes you have to reedit it after automatic steam updates, see Thud‘s guide for that). If you change graphic settings, delete fxo and metashaders 2 folder in „username“/Saved Games/DCS.openbeta folder from time to time, this may help as well. In addition, I run a game booster software after PC start in order to shut down unnecessary windows processes and I also run MSI afterburner in order to max out my GPU.

[Kula66]

Thanks all, I'll run through the Thuds guide and see what happens

[Gunnars Driver]

I have the Reverb G1 (also have OR CV1 and Pimax 8KX). I have en 9900KS@5.2Ghz and Asus Strix 3090 OC. Had Strix 2080ti OC before and it did run really good with the Reverb.

 

A lot of people start by using way to high settings. DCS in not easy driven for the hardware and very different from other games when it comes tohardware needs. I suggest start with settings low enough to be sure that it should keep above 45 fps at (almost) anytime. This should give smooth gaming when using reprojection. If it doesnt keep 45fps we need to find the reason. Maybe wrong BIOS settings for the CPU, not allowing it to run att full speed all the time, or problems with DCS( shaders etc).

For starters, when testing do not use a complex mission that bogs the CPU and or GPU down.

Beginning with too high settings will not be a good idea.(it doesnt matter you have the 3090). The goal is to get smooth gaming without stutter and then slowsly increas the settings step by step and when getting "non smooth gaming" or stutter that is too much for your own taste, back of until DCS is smooth enough again. The final settings depends on personal taste and acceptance to stutter or non smooth video. We are all different when it comes to this.

 

You can see the frame times and the load on % on the most loaded core of the CPU and also the load on the GPU in fpsvr. use that information to tune.

[Gunnars Driver]

Thanks all, I'll run through the Thuds guide and see what happens

 

What CPU and at wich clock speed? overclocked ?

RAM memory? size and RAM-speed ?

[Kula66]

32GB RAM 7700k at 5Ghz-ish ... can't remember the RAM speed.

[Kula66]

The thing that is odd, is that no matter what I change, 15k' over Hatal (?) on the Syria map, if I roll the plane the ground tears/judders ... 720 in WMR(its blury, 60Hz (I can see it flickering), everything on low/off (in DCS), reprojection running (as shown in fpsVR), 1.0 (in DCS VR) etc. all still judder/tear.

 

So I guess it is something else. But in the Rift S, 100% smooth with the 3090, even on high settings.

[Kula66]

This is from someone else: https://steamcommunity.com/app/71995...7914201741384/

 

See https://forums.eagle.ru/forum/english/dcs-world-topics/input-and-output/virtual-reality/vr-issues-aa/7130543-3090-reverb-motion-reprojection-frame-drops

 

Disabling motion reprojection and 60Hz certainly improves it ... but 60Hz is a bit flickery :( GPU is only about 50% busy now!

[Gunnars Driver]

32GB RAM 7700k at 5Ghz-ish ... can't remember the RAM speed.

 

If I change to default VR settings, I get GPU frametime 10, CPU 15, 60FPS and 30% reprojection ... and I still get judders when I roll the 14 over land - and it now looks horrible!

 

In what game mission ?

How is your 7700 set up ? Doest it run @5ghz on all cores and does it do it all the time ?

 

The frame timings seems odd. I have a 9900ks at 5.2, but I also have run it in 5.0. You CPU frame times is much higher than mine. I also more or less dont see cpu frame times ablove 10 if not on a heavy populated server. My CPU/GPU frame time portions are the other way for me: GPU is more or less always higher.

 

And, I can use decent high settings and have a very smooth ride. Of course, the aircraft type makes a difference as som moduel makers seem to produce much more hard driven modules.

 

You should check your bios setup so you know you get the most of the system. Suspect there is more to get fron your system. HWinfo64 would be. Usefull.

15ms is very close to the 60fps limit for 60hz(16.67ms). Per definition fpsvr only measures the dcs thread frame time. There can be other processes taking time from that same cpu core making the real frame time higher. I have tested this in my computer and for me this is NOT the case. Frame timing correlates very good to actual fps for the limiting part so it mostly shouldnt be an issue. However, you might wanna get yourself a better marginl to the actual max frame time limit for the selected headset frequency/Hz. If you use 60hz the maximum frame time limit is 16.67ms, but to not get frames every now and then that shoots above 16.67ms you need to perhaps aim for 12 ms or less as the ”normal” you se.

Most probably your cpu make frametimes that is above the limit which causes stutter.

 

Disabling motion reprojection and 60Hz certainly improves it ... but 60Hz is a bit flickery :( GPU is only about 50% busy now!

 

60hz is flickery for most people, I think. I dont like it so 90 fps is the way to go for me.

​​​​​​​

Why not use 90hzx and reprojection that gives the headroom for 45fps/22.2ms max frame time ?

 

 

 

 

[Kula66]

Even with just 1 aircraft! I dropped it to 4.9GHz, all cores running same. Even on very low settings, I get 'juddering', but only when I roll the aircraft. I only fly the 14, but will test another. I've just updated Windows 10 ... no different. I'm no wizard with over-clocking, but I've reset my BIOS to defaults and then reset it to XMP, then reset to 5GHz again ... no difference.

 

I did try 90Hz and reprojection, that's what I started with! Nothing I've changed so far as really fixed the issue ... apart from swapping back to my Rift S!

[Gunnars Driver]

Even with just 1 aircraft! I dropped it to 4.9GHz, all cores running same. Even on very low settings, I get 'juddering', but only when I roll the aircraft. I only fly the 14, but will test another. I've just updated Windows 10 ... no different. I'm no wizard with over-clocking, but I've reset my BIOS to defaults and then reset it to XMP, then reset to 5GHz again ... no difference.

 

I did try 90Hz and reprojection, that's what I started with! Nothing I've changed so far as really fixed the issue ... apart from swapping back to my Rift S!

 

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.

 

[Kula66]

Does the reverb need USB 3.1 or is USB 3 fast enough?

[Gunnars Driver]

Does the reverb need USB 3.1 or is USB 3 fast enough?

 

USB3.0 is good enough. No problems

 

[Kula66]

Thanks. My Rift plugs into a dedicated 3.1 powered PCI card, when I plug the HP into that card, I get a WMR error and it has to go into a main board USB 3.0 port.

[Gunnars Driver]

Thanks. My Rift plugs into a dedicated 3.1 powered PCI card, when I plug the HP into that card, I get a WMR error and it has to go into a main board USB 3.0 port.

 

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.

 

 

[Kula66]

Reset the BIOS, reseated cards, checked all cores at 49x and they stay at 4900Mhz +/- 4. Still juddering in the roll - regardless of the DCS settings, high or low its the still the same. Tried all the USB ports, seems to only work in about 50% ... it does have asmedia ports.

 

With DCS VR settings selected, I'm getting 60-70FPS ... but still get juddering if I roll :( Back to the Rift S.

[Burnerski]

I have not went through the whole thread and I'm sure you have this set correctly. Check that you application resolution adjustment in steam VR is set to approximately 2160X2160.

[Gunnars Driver]

Reset the BIOS, reseated cards, checked all cores at 49x and they stay at 4900Mhz +/- 4. Still juddering in the roll - regardless of the DCS settings, high or low its the still the same. Tried all the USB ports, seems to only work in about 50% ... it does have asmedia ports.

 

With DCS VR settings selected, I'm getting 60-70FPS ... but still get juddering if I roll :( Back to the Rift S.

 

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.