Difference between revisions of "Graphics Settings and Performance"
(Created page with "Flight simulators are demanding applications. They can be tuned down to run smoothly on old laptops, or loaded up to bring a modern desktop to its knees. Performance is even...")
Revision as of 21:04, 28 July 2016
Flight simulators are demanding applications. They can be tuned down to run smoothly on old laptops, or loaded up to bring a modern desktop to its knees. Performance is even more critical with virtual reality. For an optimal experience you'll want to spend some time balancing graphical quality, smoothness, and crispness. FlyInside is a demanding program, you'll want to make sure that your computer meets the specifications listed under Hardware Setup. If not, you'll need to use especially conservative graphical settings for an enjoyable experience.
Virtual reality tricks the user into believing they are in a virtual world. To do so, it needs to update the image the pilot sees, nearly instantaneously, as they turn their head. Any lag breaks the illusion, and can even induce nausea. Modern HMDs run at a steady 90fps, and anything lower is unusable. At the same time, HMDs introduce additional overhead over conventional graphics, in terms of stereo overhead, and the need for reduced latency. If your flight simulator is running at 70fps normally, it may only hit 35-50fps with FlyInside. You'll need to adjust your graphics settings accordingly.
Flight simulators rarely achieve 90fps, certainly not with any consistency. FlyInside bridges the gap using asynchronous timewarp. Even if your flight simulator is only running at 30fps, FlyInside takes each image from the simulator and displays it multiple times, rotating it to account for head movement. This way head rotation still feels smooth, and VR still feels good, even at lower frame-rates.
Once you are loaded into an aircraft cockpit in FlyInside, press your interact key. You'll see the FlyInside Tag appear, which shows FPS in a format such as "FPS: 55/90". The first number is your simulator frame-rate, while the second number is the asynchronous timewarp frame-rate.
Asynchronous Timewarp FPS
FlyInside tries to keep asynchronous timewarp running at a steady 90 fps (or 75 fps for the Oculus DK2). If this number drops lower you'll experience judder, a very uncomfortable sensation. While asynchronous timewarp is generally robust, certain conditions can still result in judder.
- Let's say you feel judder, and see a frame-rate like "FPS: 25/60". This is a case of computer overload. Your simulator is overloaded and running slowly, and is also not leaving enough room for asynchronous timewarp to breath. You'll need to turn down simulator or graphics settings as described below.
- On the other hand, you may feel judder, but see a frame-rate like "FPS: 110/72". In this case, the simulator is running very efficiently, so efficiently that it is starving asynchronous timewarp. Turning up graphics settings may actually help asynchronous timewarp and make VR feel smoother. You can also set a frame-rate limit from your flight simulator's settings as described below.