oculus and frame drops.

[Holmer]

Hey guys.

 

so i got the oculus bundle and its amazing flying around. but my mid end rig dont seem capable of giving me a good framerate. so can you guys help me out. what i should upgrade or some optimization i havent gotten right ?.

 

I havce everything on low. but my pixel density is at 1.8-2.0 (otherwise i cant read the diels or anything.

 

I get alot of framedrops looking out the cockpit and looking fast around. and its not a smoothe experience. also the gound looks like it still pictures loading in (sometimes.)

 

load radius is at 10.000

and its just flying around with no enermyes.

My rig is:

 

P67 sabertooth MB.

I7 2700 K. (oc to 4.4.)

Gtx 1060 6 GB.

16 Gigs 1800 mhz rAM.

 

and its installed on a ssd. so what is killing my frames ? :)

 

Sorry for the bad english.

-Holmer :pilotfly:

[Buckeye]

oculus and frame drops.

 

With that card your PD will need to be lower. Also, turn all shadows off. With a 1060 you're barely going to be able to have anything turned on to achieve solid FPS.

 

Also check out the VR section of the forum, these questions have been answered countless times, and in much greater detail than I've provided.

 

 

Sent from my iPhone using Tapatalk

Edited August 26, 2017 by =Buckeye=
Typos

[javelina1]

Try flying with a PD of 1.5. (as you increase PD, it's almost an exponential load. 1.8-2.0 is in the range of a 1080Ti, from what most post).

[Knock-Knock]

Indeed.

Im doing as much as I can, to not drop below 45fps, cause it gets real choppy and nasty below that, in VR. So Im usually around 1.2-1.3 PD in 1.57, and atm, all the way down to 1.0 in 2.1.1. In both cases running 2xMSAA - hurts less and looks better in 2.1.1, than 0xMSAA and say 1.3-1.4 PD for example.

 

A small example of how the total pixel amount increases with PD.

PD 1.0 is a total of 2.6 million pixels.

1.5 is 5.8 million

2.0 is 10.3 million

2.5 is 16.2 million.

 

A 4K display has 8.3 million.

1080p has 2.07

 

So as already mentioned. PD down - a lot, shadows off, terrain shadows off, water low, view distance low or med, tree's all the way down. If you have civilian traffic on, switch it off - hogs cpu resources. You pre-load radius you should be able to run at 100.000+. Depth of Field, stay well clear of that. And limit MSAA (especially in 2.1)

 

I know it hurts killing the candy, but you really want as many fps as you get can, and have as much of buffer as possible.

But start low, then you can always crank it up, if you have a overhead. Much better than giving up candy ;).

Edited August 26, 2017 by Knock-Knock