by Robert » Wed Jul 15, 2015 8:03 pm
It's all a tradeoff on settings and what works on a regular monitor may not be appropriate for VR.
As best I can tell, you want the FlyInside frames per second to stay pegged or very close to 75. When that number turns red, I am pretty sure that means you are dropping into high persistence mode. At any rate, try to keep that number at 75.
The FSX frames per second are also better up high but aren't quite as critical as the time warp frames as Dan time warps out of date frames to approximate as best as possible what a new frame should look like. I forget the cutoff where it turns red but try to keep it green as well.
All of that comes from adjusting your graphics and scenery settings, and some also comes from the planes you fly. The stock FSX planes are simple to draw and keep frames high. Some aftermarket planes have tons of detail, reflections on their surfaces, etc, and consume a lot of CPU/GPU cycles.
But no matter what, you want to keep the time warp frames at 75 and green, and the FSX frames green. It's probably somewhere around 45 that that one turns red. And in my experience, you just want to turn settings up in areas with complex scenery and then down until you get good numbers and it feels "right". In those settings comes the balance and unless you can just turn everything up to max and be good, the tradeoffs depend on what you value most - scenery contours, buildings, trees, other vehicles, animations, etc.
It's turning out to be a tough nut to crack, though. It really is kind of an art and there is a learning curve for me. Still climbing it.
HTC Vive Pro/P3D/DCS/X-Plane
Orbx FTX Global Base, FTX Global Vector, scenery, airport packs