I noted in my prior post that my VR was running extremely well as a result of some setting changes I’d made based on a YouTube video I’d found. I promised to post a link to that video, and it’s at the bottom of this post. It’s worth watching the entire thing, although the last 10 minutes or so you can probably scan through as it, for the most part, just makes and extended case for the use of the 3jFPS plugin. Here’s the list:

• I used the automatic overclock wizard in my BIOS to overclock my CPU. A 4.0 chip, it’s running at 4.6. I had already done this two years ago, so this isn’t a new change. DON’T OVERCLOCK YOUR CPU UNLESS YOU ARE COMFORTABLE WITH WHAT YOU ARE DOING AS YOU CAN PERMANENTLY DAMAGE YOUR PC.
• Based on the video, in my BIOS I also:
  • Disabled power management
  • Disabled CPU C states
  • Disabled Intel Speed Step
  • DON’T MESS WITH YOUR BIOS UNLESS YOU ARE COMFORTABLE WITH WHAT YOU ARE DOING AS YOU CAN PERMANENTLY DAMAGE YOUR PC.
• Using the NVIDA Inspector I overclocked by GPU by 80 on the clock speed and 200 on the memory speed. DON’T OVERCLOCK YOUR GPU UNLESS YOU ARE COMFORTABLE WITH WHAT YOU ARE DOING AS YOU CAN PERMANENTLY DAMAGE YOUR PC.
• Using Oculus Tray Tool I:
  • Set the performance to Maximum Performance Plan
  • Disabled USB Select Suspend
  • Set SuperSampling to 0
  • Left ASW alone — which is DIFFERENT from what he says to do in the video, because …
• … I prefer Oculus Debug Tool for setting the frame rate, as I can decide between fixing it at 45 FPS with AWS or without. I prefer without. This means I need to start the Debug Tool each time I load X-Plane, but I’m good with that.
• With SteamVR open I used the Advanced Open VR Settings plugin to:
  • Set SuperSampling to 1.6 (and I’ll probably up it to 1.8)
  • Set Compositor to 1.0
  • Set Enable ASF on
  • Leave the next three options off
• Using Project Lasso, I:
  • Enabled Performance Mode in the overall settings
  • With X-Plane and X-Plane VR running, in Lasso I:
    • Set XP’s priority to High
    • Set its CPU affinity to use virtual cores 2-7 (all but the first two)
    • Set the VRcompositor CPU affinity to virtual cores 0 and 1 (only the first two)
    • Note: If you are not using hyper threading, run XP on all but your first core, and run VRcompositor only on the first core. If you are hyper threading and have more than four physical cores, same principle applies (VRC on the first two, XP on all the rest).
• In Windows Power Management (which is in the Windows Control Panel settings), I set the power management profiles to Bitsum Highest Performance (which is a profile created by Lasso). If you don’t have Lasso, pick Highest Performance.
• In NVIDIA Control Panel, I:
  • Set the overall 3D profile Energy setting to Max Performance
  • Turned off Threaded Optimization in the XP profile
• I downloaded the Water Fix & Default Fog Control plugin and changed the value in the fog plugin to 0.3
• With X-Plane running, in the 3jFPS plugin Advanced Settings I:
  • Ran the wizard for a min FSP of 45 and max FPS to 46, and took the best FPS options in every other choice it gave me
  • Then I went back through the advanced settings and:
    • Reduced sliders in the LOD settings to the bottom of the green scale
    • Reduced min and max sliders in the visibility settings to the bottom of the green scale
• In X-Plane graphics settings I:
  • Set it to windowed mode as it seems to perform better minimized
  • Graphics to HDR (position 4)
  • Textures to max (position 4)
  • AA to FXAA (position 2)
  • Objects to almost max (position 4) — while he runs at max objects, I found it hurt my frames too much in busy areas
  • Shadows off, reflections off
• Finally, I did anything else I could do to reduce the CPU load while playing X-Plane:
  • Turned off Windows auto updates
  • Turned off NVIDIA Geforce Experience
  • Went into the SteamVR settings (using the headset) and turned off anything that would hit the network (friend alerts, etc.), turned off the overlay, etc. — basically just looked for anything that looked ancillary and deactivated it
  • Set Oculus Server to run in administrator mode, which seems to keep it from loading the full Oculus window unless I specifically open it

These setting are working extremely well for me, with solid 45FPS, very smooth performance, and few to no “grey flashes” or frozen views. I do think the changes to the power management settings throughout made a difference , for what that’s worth. It’s really a remarkably good experience, although your mileage may vary.

I could not stand the blue circle that SteamVR would put around you in the X-Plane VR cockpit. Thanks to Dan on YouTube I found this post by DazzyB on how to remove it. 30 seconds and it was banished forever. Here’s the method:

1) Quit SteamVR if it is already running (you don’t need to quit Steam itself).

2) Launch Explorer and then locate your main Steam folder.  Normally this will be located in C:\Program Files (x86) unless you installed Steam with the custom option.

3) Go into the ‘config’ folder and then open up the file called ‘steamvr.vrsettings’ in Notepad.

4) Copy and paste the following lines of code directly below the line that starts with the { character (located at the very top of the file)…

"collisionBounds" : {
       "CollisionBoundsColorGammaA" : 0,
       "CollisionBoundsColorGammaR" : 255
    } 
apoteketreceptfritt.com
 ,

5) Save and close the file.