Oculus Rift with DCS World Discussion

[mariner3302]

Turn off the frame counter and go enjoy yourself.

 

Can't agree more!! Folks get wrapped around the frame rate numbers. Just fly it!! If you have issues then things can be done but to waste time just trying to max your frame rate number is a waste of time.

 

For me, and I don't measure frame rates often, there is no difference between 25 fps and 50 fps. I use the performance tab of the Task Manager to diagnose when/if my system hiccups.

Edited June 14, 2019 by mariner3302

[Wicked.-]

Thanks for the tip.

 

So, I just got home, deleted the saved games folder as suggested. Changed game resolution to my native of 2560x1440. Clicked the VR preset in graphics option, then went over to the VR tab and the enable VR option was already ticked.

I then loaded into Cold and Dark in F-18 at Dubai, and FPS stay at 45fps, until I look to the left and FPS drop to 22.5 - but no crashes, SS in oculus tray tool is set at 0 and I'm not launching steam VR.

 

Also tried dropping resolution to 1920x1080, cold and dark at Nevada and frames were at 22.5 straight away

 

First and foremost, the resolution in settings has nothing to do with VR. You can set to 4096x3840 and it won't matter. Those settings only refer to your monitor when VR is not being used. Cockpit displays do matter and I would set it to the lowest option, 512 I think. Turn OFF MSAA, shadows, heat blur, depth of field, cockpit global lighting, terrain shadows and SSAA. Set water to medium, textures to low (to start with), basically set everything to medium when available or low to start with. Then go to the VR tab and set Pixel Density to 1.3. This is the main adjustment that has the most effect on framerate and image quality. Those settings should get you a smooth 45FPS in the single player missions. Also, 45FPS with ASW is the goal. Don't think of it like a monitor.

If these settings work start upping other settings like textures but forget about shadows and MSAA. Your system isn't strong enough. Or you can try to raise the PD to 1.4 and leave the other settings alone. It should be flyable and look good since you're new at it. Oh yeah, set preload radius to 2/3 of the max, take trees to 60%, turn off civilian traffic (low,if you must ;)), chimney smoke off, grass to like 10.

Good luck.

Edited June 16, 2019 by Wicked.-

[pimp]

How do you download older versions of the Oculus software? I'm wanting to try the 1.35 version since that's the last version before the Rift S. My DCS VR experience was much better before I used the Rift S which of course forced me to update the software. Are they still available for download?

[BigDuke6ixx]

How do you download older versions of the Oculus software? I'm wanting to try the 1.35 version since that's the last version before the Rift S. My DCS VR experience was much better before I used the Rift S which of course forced me to update the software. Are they still available for download?

 

There’s no way to roll back. Try updating your graphics drivers.

[pimp]

There’s no way to roll back. Try updating your graphics drivers.

Thanks for the info. I've already updated and rolled back my gfx drivers, but I still get ghosting in the fly-by camera and the wings when banking. Also, in the mirrors in the Tomcat. Maybe it's 2.5.5 and not the Oculus software.

[dburne]

How do you download older versions of the Oculus software? I'm wanting to try the 1.35 version since that's the last version before the Rift S. My DCS VR experience was much better before I used the Rift S which of course forced me to update the software. Are they still available for download?

 

Not really.

[Talonx1]

Thanks for the info. I've already updated and rolled back my gfx drivers, but I still get ghosting in the fly-by camera and the wings when banking. Also, in the mirrors in the Tomcat. Maybe it's 2.5.5 and not the Oculus software.

 

I've noticed lots of weird melting/ghosting for a long time but had basically gotten used to it. Especially during loading screens it would geg all wacky. Recently though I stopped setting pixel density in game and now leave it at 1.0 in game and use the debug tool to set it to 1.3 amd disable asw. In the process I also started changing a setting for "adaptive gpu performace scale" to off. No idea why but it completely gets rid of all the ghosting melting for me in dcs even in the loading screens. I also always launch dcs via the "file/launch app" drop down in the debug tool as it seems the most consistant way to ensure my oculus options apply properly 100% of the time.

[Svsmokey]

I've noticed lots of weird melting/ghosting for a long time but had basically gotten used to it. Especially during loading screens it would geg all wacky. Recently though I stopped setting pixel density in game and now leave it at 1.0 in game and use the debug tool to set it to 1.3 amd disable asw. In the process I also started changing a setting for "adaptive gpu performace scale" to off. No idea why but it completely gets rid of all the ghosting melting for me in dcs even in the loading screens. I also always launch dcs via the "file/launch app" drop down in the debug tool as it seems the most consistant way to ensure my oculus options apply properly 100% of the time.

 

Thanks for that "adaptive performance" tip ! I disabled it and immediately noticed increased terrain and object shadow draw distances , and the elimination of that annoying micro-stutter when looking to the side . Gonna try the pixel thing next , but even now , i am experiencing the best graphics/performance ever :)

 

Frames still locked at 45 , though-weird !

[sea2sky]

Thanks for that "adaptive performance" tip !

 

 

Where is it located? NVIDIA control panel?

[Svsmokey]

Program files>Oculus>diagnostics>oculus debug tool in file explorer . I had to leave it running , as it would not save the "off" setting .

[pimp]

I've noticed lots of weird melting/ghosting for a long time but had basically gotten used to it. Especially during loading screens it would geg all wacky. Recently though I stopped setting pixel density in game and now leave it at 1.0 in game and use the debug tool to set it to 1.3 amd disable asw. In the process I also started changing a setting for "adaptive gpu performace scale" to off. No idea why but it completely gets rid of all the ghosting melting for me in dcs even in the loading screens. I also always launch dcs via the "file/launch app" drop down in the debug tool as it seems the most consistant way to ensure my oculus options apply properly 100% of the time.

Wow, I think you found something with disabling the "Adaptive GPU Performance Scale". My ghosting issues with fly-bys and the wings morphing when banking is eliminated. The side views aren't completely smooth, but they are better. My fps does go up when do a fly-by for example, but in cockpit(Tomcat w/ mirrors on) it stays around 45. Thanks for the tip. normally stuff like this doesn't work for me. :)

[Talonx1]

Program files>Oculus>diagnostics>oculus debug tool in file explorer . I had to leave it running , as it would not save the "off" setting .

 

I've read in some places they say to turn it off or it can cause stutters but I haven't had that problem. I always open oculus, open debug, set my settings then launch DCS from the debug tool and then leave it open. It's worked perfect every time.

[DeltaMike]

Hello guys, just picked up an Oculus rift myself and new to the VR party.

So far, I have delted the Metashaders folder and FXO to try force new ones. Graphics wise I have changed game resolution down to 1080p from 1440p and picked the VR preset in graphics as I though it would be low enough to get a benchmark to tweak.

 

Joined friends server with little AI in not too much, but the game just keeps crashing before the startup has even finished

Specs are

AMD 2600X

16GB 2666MHz

GTX980Ti

 

Is DCS that bad for VR? I seem to get good performance on ACC with decent graphics too

 

Any help would be massively appreciated

 

Not a lot of people are flying a 980ti in VR so it may be hard to benchmark. On paper it should work. Try the following settings:

Textures high

Terrain textures low

PD=1.2

MSAA off

Shadows off

Vis range med

Trees 60%

Civ traffic, grass, clutter, smoke off

 

Monitor resolution only affects your monitor, and doesn't affect VR performance. Set this, and everything else, as desired.

 

As for crashing in MP, think about memory problems. Update your MOBO bios, check your memory timings. Think about buying an SSD and migrate DCS to that to reduce your load times. If all else fails there's a setting in regedit that you can use to increase the timeout value but I'll leave that for somebody who knows what they are doing (I did it, and it worked, but can't find the reference now)

Edited June 20, 2019 by DeltaMike

[Kirkey_badgers]

Not a lot of people are flying a 980ti in VR so it may be hard to benchmark. On paper it should work. Try the following settings:

Textures high

Terrain textures low

PD=1.2

MSAA off

Shadows off

Vis range med

Trees 60%

Civ traffic, grass, clutter, smoke off

 

Monitor resolution only affects your monitor, and doesn't affect VR performance. Set this, and everything else, as desired.

 

As for crashing in MP, think about memory problems. Update your MOBO bios, check your memory timings. Think about buying an SSD and migrate DCS to that to reduce your load times. If all else fails there's a setting in regedit that you can use to increase the timeout value but I'll leave that for somebody who knows what they are doing (I did it, and it worked, but can't find the reference now)

 

 

I have DCS on it’s own SSD, and setup a cache too on an ssd just to ease the load if required as DCS seems to crash without that even before VR. Everything is upto date bios etc. Maybe for DCS at least better CPU/GPU or combo is required. Trying to decide if 2060 will be enough or just wait longer until I can get a 2080 - or wait to see what the 2060 super will be like. Maybe adding another 16GB may help too? Seem to be pretty smooth overall as said can do racing games on High detail levels with ASW and no jitters.

[DeltaMike]

There's a theory that dcs wants as many texture mapping units as you can throw at it. Consider a Vegas 56 if you want to go cheap. Or a 1080.

 

Doesn't sound very glamorous but upgrading to a b450 Mobo with decent ram helped me a lot. I'll probably gen one of the new ryzen CPUs when they come out.

 

Only so much you can do with Oculus. Don't spend a fortune on your GPU, just get one that'll work in dcs

[Svsmokey]

My 1070 does very well with the Rift . My graphics priorities are shadows ( low cockpit , flat terrain) , civil traffic (low) , water (high) and msaax2 . Trees are at 62% . I'm getting a very fluid experience solo very low over the Caucasus with it and these settings . (I'm a mud-mover in the Hornet) I don't think I'm benefiting from the VR optimisation at this point so there is room for improvement yet ...

Edited June 22, 2019 by Svsmokey

[Ziptie]

I’ve noticed an improvement in the efficiency of DCS now and can move many settings higher than previous. I must say, however small the feature may seem, the shadow of your head now moving inside the cockpit is amazing! Follows the movement of your head in real life while bearing the headset and adds a very deep and additional layer of immersion. Cheers for that

[Svsmokey]

My 1070 does very well with the Rift . My graphics priorities are shadows ( low cockpit , flat terrain) , civil traffic (low) , water (high) and msaax2 . Trees are at 62% . I'm getting a very fluid experience solo very low over the Caucasus with it and these settings . (I'm a mud-mover in the Hornet) I don't think I'm benefiting from the VR optimisation at this point so there is room for improvement yet ...

 

...Aand todays Oculus update set me back again . Zucked again !

[majapahit]

...Aand todays Oculus update set me back again . Zucked again !

Oculus updated, so,

tried DCS, switched shadows back on after muliplayer missions Off,

smooth @ steady 45 fps

I was researching VR goggles update "S" / Reverb, now this bought me some time.

Somehow AAR is a lot smoother too?

YMMV

Edited June 23, 2019 by majapahit

[Kirkey_badgers]

There's a theory that dcs wants as many texture mapping units as you can throw at it. Consider a Vegas 56 if you want to go cheap. Or a 1080.

 

Doesn't sound very glamorous but upgrading to a b450 Mobo with decent ram helped me a lot. I'll probably gen one of the new ryzen CPUs when they come out.

 

Only so much you can do with Oculus. Don't spend a fortune on your GPU, just get one that'll work in dcs

 

Hmmm this is very interesting, so I have seen some Vega 64's on ebay 2nd hand of course for similar prices to the RTX2060, so you would say the Vega is better buy of the two? I have even seen a liquid cooled one at £359, don't quite have the money yet though!

[pimp]

I am getting the black screen with sound still going with my CV1 now. I have to close DCS and then the screen comes back on in Oculus home. Anyone else experiencing this with their CV1?

[Svsmokey]

I am getting the black screen with sound still going with my CV1 now. I have to close DCS and then the screen comes back on in Oculus home. Anyone else experiencing this with their CV1?

 

I had it yesterday (once) after the Oculus update . There are many ways to launch DCS in VR , and another worked . Rebooting may have helped as well . I had to resolve sound problems too , so i can't be more specific about the solutions as there were several reboots , DCS launches and sound settings involved .

Still working my way thru problems caused by that update , which i neither needed or wanted , nor had the option to revert . Think my Oculus days are about over .

[pimp]

I had it yesterday (once) after the Oculus update . There are many ways to launch DCS in VR , and another worked . Rebooting may have helped as well . I had to resolve sound problems too , so i can't be more specific about the solutions as there were several reboots , DCS launches and sound settings involved .

Still working my way thru problems caused by that update , which i neither needed or wanted , nor had the option to revert . Think my Oculus days are about over .

I feel your pain. I just had another update required message.

[majapahit]

I am getting the black screen with sound still going with my CV1 now. I have to close DCS and then the screen comes back on in Oculus home. Anyone else experiencing this with their CV1?

Replug the plug underneath the mask? (Find YT to remove the mask)

[DeltaMike]

To follow up on the texture mapping unit thing, I surveyed my team yesterday. We are all either on Rift or Rift S.

 

1060 (80 TMU): player is dissatisfied but he is competitive, plans to upgrade soon

 

1070ti (152 TMU): player is satisfied and very competitive

 

Most of our players are on 1080's (160 TMU) and I find myself using basically the same settings, getting the same performance with my Vega 56 (224 TMU). We can run high terrain texture, cockpit res 1040, medium shadows (depending on the server), med vis range, and either MSAAx2 or PD 1.2.

 

For comparison, I would submit the two best cards for DCS are probably the 1080ti (224) and the 2080ti (272). There's a marginal improvement here, you should be able to run MSAA and PD 1.2-ish at the same time, which I personally feel looks great. Wish I could do it, not sure I want to spend the $$$$ tho.

 

People are eager to see how the Radeon VII with its 240 TMU's fares in DCS (we will see if the theory holds).

 

Benchmarks in other games don't quite equal DCS.

 

I think there are some bargains out there, personally I'd drop $300 on a Vega or a 1080 before I'd spend $800 on a 2080.

 

But also some false economies, the 1060 might be one. And remember the action is always at the margins. Which I take it is the main gripe about the 2080ti, in DCS at least you get a marginal improvement over the 1080ti, at a really high cost.

 

None of this applies to HMD's with higher pixel counts than the Oculus, I imagine that's a whole nuther ball game

Edited June 24, 2019 by DeltaMike