Stal2k Posted June 18, 2018 Posted June 18, 2018 HI everyone, I know a lot of folks, myself included are tightly following VR performance. So, after some testing here are two things I figured out w/ the open beta. Your mileage may vary, but it helped me out. One of these we can work around ourselves, the other not so much. Issue 1 + Workaround: The issue is the beta seems to either default the ASW to disabled on startup and intermittently during play. I kept the Oculus debug display on that shows ASW status and it happened quite a bit. Might be something for others to validate so ED can look into it. How to fix: Simply hit CTRL-Num4 on your keyboard, this should set it to "auto" which is what you want. Some people prefer it disabled, but I like things nice and smooth inside the cockpit without looking like I'm flying under the influence. Oculus really nails their ASW, use it. The monkey wrench: The ASW hotkeys share a common binding with camera control keys in DCS. That means if you use HOTAS profiles and accidentally, for example, hit your trim button (those that use NOiD) may have either disabled ASW or toggled it to an undesirable setting. Pay attention to ANYTHING that is bound to ctrl+numpad. If you don't want to fly with the Oculus debug on, (duh) a good quick litmus test is to see if the slight ghosting/double vision exists if you look across your left/right cockpit panels. If so, humor me and hit ctrl-num4 and see if it clears up. Issue 2 - possible issue with this build: Is it possible either as a result of ASW or just internally vsync is defaulted to on when in VR? Even with ASW off, the frame rate remained locked at 45 steady. I replicated it whereas I could pull 90 frames easily in the stable, and before everyone starts telling me how trash VR is in the beta - I mirrored my settings with DF on in stable and framerates don't typically stay pinned at a number. Even if it were the case it wouldn't be pegged at 45 exactly. Is it possible some wires got crossed since the settings LUA still has old values like HDR even though it's not in the GUI? I believe when i first looked at it my sync was set to "true" even though it was unchecked in GUI. To be fair, it read false and was unchecked when I got locked to 45 FPS
Recommended Posts