Rift View Terrible - Only 45 fps

[CrossWiseRanger]

BLUF:  New high performance computer built for DCS does not maintain over 45 fps in Rift with default VR preset settings, pixel density of 1.0, and A-10C cold on ramp.

 

On monitor, DCS runs at 170 fps. VRMark Orange Room test average of 262 fps.

 

Additionally, the video looks terrible when compared to a monitor. Finding an airfield is very difficult do to the lines shimmering and built up areas twinkling.

 

Have tried / checked: C-states, PCI power plan, computer power plan, affinity core, priority core, etc.

 

Help! What am I missing? How comparable is the Rift vs monitor view? I saw one post (which cannot find again) where simmer stated he was running all max settings while consistently getting 90 fps. Do I need to switch to DCS 2.*?

 

DCS World: 1.5.5.60565.216

[hansangb]

Make sure you have the latest NVidia drivers.

1.5.6 is much better in terms of stutter etc. So upgrade your DCS.

 

And in the past, 1.5x was better for VR. But recently, it seems like 2.x is better for VR.

 

Also, use Pixel density of 1.5 or so and it'll be easier reading HUDs/gauges etc.

[Cibit]

Loads of tips to help get the best out of the system, relax and read up on it instead of "the end of the world is nigh" posts. Try loosing the shadows as a first step. I have an antiquated rig that performs very well with the rift. Oh and the default refresh rate is 90 FPS for the rift, it defaults to 45FPS by virtue of ASW

[BlackLion213]

BLUF:  New high performance computer built for DCS does not maintain over 45 fps in Rift with default VR preset settings, pixel density of 1.0, and A-10C cold on ramp.

 

On monitor, DCS runs at 170 fps. VRMark Orange Room test average of 262 fps.

 

There must be something wrong. I have a i5 4790 @3.6 with a GTX970 and my system seems to be running better. I don't know much about troubleshooting computers, but there is hope because others seem to be getting much more out of it. Even with 1.5.5, your system should be able to generate good apparent performance (with ATW/ASW) at reasonably high settings.

 

My system lost about 30% FPS transitioning from a single 1080P monitor to VR running the default VR graphics settings. You inability to go above 45 FPS is built into the Oculus run time with ASW and just means that your system is not quite getting to 90 FPS. Unless you can get above 90 FPS, ASW will lower it to 45 and hold it there. My system is generally getting less than 45 in built up areas, but it is still quite livable.

 

Additionally, the video looks terrible when compared to a monitor. Finding an airfield is very difficult do to the lines shimmering and built up areas twinkling.

 

Adding in a bit of MSAA (2x-4x) makes a really big difference on appearance and really reduces the "shimmering", especially with distant objects such as buildings. Due to the lower res, images will never look quite as clear as a monitor with any current HMD (though the future will almost certainly deliver it), but my current settings look as nice as DCS did on the monitor with the addition of MSAA to default VR settings and a pixel density of 1.2.

 

Higher PD really helps with gauge legibility (though certain modules are quite clear at lower PD, like the Spitfire, Viggen, and MiG-21). PD probably has the biggest performance impact though, so recently I've shifted towards higher graphics settings with lower PD and I'm happier.

 

The key is to experiment and find the right combination. Even for my machine, the right balance has led to great appearance and good performance (though I will likely upgrade soon to have better FPS and somewhat higher PD).

 

In the meantime, check your drivers, make sure your oculus runtime is up to date, and maybe check the oculus compatibility tool. It really should get better and VR is an awesome experience.

 

-Nick

[Wolf8312]

Yup welcome to VR! I'd like to say you have many hours of flying ahead of you, but while this is true, equally you will also have many hours, indeed days and weeks, of often frustrating tinkering ahead of you!

 

I just sepnt half an hour mapping the mouse buttons to my HOTAS! I've been tinkering with it all week (I have a VIVE though) but now have to say have got it running pretty damned great and I am in love with it, in a way I never was before.

 

We VIVE owners have had a rougher time of it than you rifters too.

 

One thing, dont put pixel density too high.

 

I've got mine on 1.3 but this enabled me to jack up the MSSA (4x） and A filtering (4X), with high terrain and textures, among other things and its looking alot better now for me and more importanltly performing better too. I also followed the directions of this thread- https://forums.eagle.ru/showthread.php?t=172537

 

 

The thing is though some people might have standards that are just too high for the present standard of VR tech. Some people are maybe not going to be satisfied with this genration of headsets simply because they are junkies for graphical perfection. The kind of people who demand at all times 60 FPS (or better) or GTFO are probably going to be dissapointed when they come up aginst the resoloution issues, occasional ghosting, or just the very idea that they have to turn graphics settings down. Not saying you are one of these people just that make sure your standards are not too high. I get a bit of shimmering down in airports, and as for the clouds I tell myself I ate some LSD before take off!

 

I've seen some say they went back to playing on monitors because they wanted to play with high graphics again. Personally I could never do it, when the VIVE was having its DCS problems a few months back rather than going back to track IR I simply quit playing!

 

For me high graphical perfection is irrelevent because monitor flying now for me, is more like manipulating a pretty picture, whereas VR feels like actually flying and being present in the aircraft. EVen though in some ways it doesent look as good I still argue equally in another hard to put into words way it looks 100 times better. I'm dying for BOS to get VR support so I can start playing it again!

 

Its hard to tell how high your standards are without being able to see exactly how it is performing on your rig。Post your settings if you like. One thing to be aware of is the in game DCS VR automatic settings that you can choose in the options screen looks terrible a horrible shimmery mess. Follow that thread I gave you and if you still aint satisfied after that then try lowering your standards!

 

I disagree about 2.0 performing better than 1.5.5 though. I mean in some ways it is, but its much less stable for me. Mig 21 is unplayble (endless flashes) and I am still getting the occasional flash in and out from the game and the steam background even on playable aircrafts. This has nothing to do with my rig, its the same thing happening with 1.5.6 though nowhere near as bad just a symptom of alpha I suppose...

[CrossWiseRanger]

Cibit

 

Have been through numerous posts on this forum and several others. Tried the recommendations that pertained. No joy.

 

Spent quite a few hours with the Oculus Toolbar benchmarking the differences in settings of both DCS and computer. That was interesting to say the least. 90 fps is 11 milliseconds per frame. The average GPU application time was greater than 13 milliseconds - which means would never meet 90 fps.

 

Learned that even when the Oculus output drops to 45 fps, the computer load is not reduced. Oculus continues pushing 90 fps but just discards every other frame. If Oculus could be set to run at an actual 45 fps (or better 60 which would be doable), we all could be flying around with higher sim settings.

 

My expectations started out high believing that the videos posted were what people actually saw through the Rift. How would you describe what you see Rift vs monitor? Please calibrate my expectations.

[Wolf8312]

Cibit

 

Have been through numerous posts on this forum and several others. Tried the recommendations that pertained. No joy.

 

Spent quite a few hours with the Oculus Toolbar benchmarking the differences in settings of both DCS and computer. That was interesting to say the least. 90 fps is 11 milliseconds per frame. The average GPU application time was greater than 13 milliseconds - which means would never meet 90 fps.

 

Learned that even when the Oculus output drops to 45 fps, the computer load is not reduced. Oculus continues pushing 90 fps but just discards every other frame. If Oculus could be set to run at an actual 45 fps (or better 60 which would be doable), we all could be flying around with higher sim settings.

 

My expectations started out high believing that the videos posted were what people actually saw through the Rift. How would you describe what you see Rift vs monitor? Please calibrate my expectations.

 

Haha well I tried in the post above so not sure if I can! I've honestly got it running very well but hard to say if what I think is great will satisfy you too. It's certainly not a shimmering mess and looks great to my eyes except maybe a bit jaggy close to the ground. But only a bit, like I said above if one is the type to be OCD about graphics and FPS then what I think is great might not be for other people. But who knows maybe you haven't configured it right. Can you post a screen shot of your settings?

 

Way up high I think it looks great, you may get a bit of ghosting sometimes when one looks sideways and the clouds can be buggy. I am also someone who can't stand shimmering in VR but MSSA AF and a pixel density of 1.3 for me has made it very smothe. I haven't even checked my fps, all I know is I'm never bothered by it.

 

 

 

 

What version of the game are you running?

[DayGlow]

If you are locked in at 45fos that means Asynchronous Space Warp is running.

 

https://forums.oculus.com/community/discussion/44941/how-to-disable-asw

[Cibit]

Cibit

 

Have been through numerous posts on this forum and several others. Tried the recommendations that pertained. No joy.

 

Spent quite a few hours with the Oculus Toolbar benchmarking the differences in settings of both DCS and computer. That was interesting to say the least. 90 fps is 11 milliseconds per frame. The average GPU application time was greater than 13 milliseconds - which means would never meet 90 fps.

 

Learned that even when the Oculus output drops to 45 fps, the computer load is not reduced. Oculus continues pushing 90 fps but just discards every other frame. If Oculus could be set to run at an actual 45 fps (or better 60 which would be doable), we all could be flying around with higher sim settings.

 

My expectations started out high believing that the videos posted were what people actually saw through the Rift. How would you describe what you see Rift vs monitor? Please calibrate my expectations.

 

If I had your rig then I would expect to get max FPS with everything maxxed out in the settings. I keep tweaking my system settings to try for the best I can get from my rig. To be fair it does remarkably well for such an old CPU. My haste for a new upgrade has declined slightly when I see how well comparatively it copes with DCS versus newer machines.

 

Control + number pad 1 iirc disables ASW and may be a thing to try as that will stop oculus wasting frames and locking you to 45 fps