Since the Update - Update

I know I said that the latest Nvidia driver solved my problem, and it did for the most part. Sometimes it returns, and I have noticed something. When the problem occurs, I seem to be getting a fps reading of above 90 in VR. Normally the fps reading on the screen will stay within a few tenths of 90fps in VR, but it seems to be in the 120's and 130's when this graphic anomaly is present. It is as if the screen updates are too fast for the VR to handle.

Any thoughts?

Iam using Oculus launched from the desktop icon and not through Steam.

I have never used either of those tools. Except for FS 2 I use the Vive for VR, so I haven't delved deeply into the world of Oculus.

OK, shut off ASW from the debug tool. I was getting the graphics anomaly worse than ever, and now when I was seeing it the fps was reading 45 fps. What did I screw up?

FS 2 seems to turn ASW back on to Auto every time you run it.

OK. This is however a brand new problem for me, so something must have changed recently.

Here is how I have tried to shut off ASW. I went to the debug tool and clicked disabled. I closed the program, and reopened it to confirm that it still read disabled. It did. I ran FS 2 and got the graphics problems. I went back to the debug tool and ASW now read "Auto". Hmmm.

So, I reset it to "disabled". I restarted the computer to see if a restart was required to keep ASW disabled. I checked the debug program and it said ASW was disabled. I ran FS 2, and got the graphics distortion. I returned to the debug tool and once again the ASW setting had returned to "Auto".

You can see why I assumed that FS 2 was turning the ASW back on. Something is, and FS 2 is the only program I have run.

Any thoughts?

Roger Wilco.

Just a few more observations.

Leaving the debug tool open with ASW disabled doesn't seem to help. I assume that ASW is disabled with debug running and disabled selected, so disabling ASW may not be the key.

It is far, far worse in Chicago than anywhere else. It is very rare in the NYC scenery but the buildings in Chicago are often distorted.

Finally, lowering the supersampling (or whatever you call it in the menu, rendering something or other) from 2.0 to 1.6 removes the problem entirely. It seems to still be present at 1.7.

On a side note, it has been a blast flying slalom courses through the concrete canyons of NYC and Chicago in the Jungmeister during testing lol.

Quote from whitav8

Oldar,

The relationship between Super Sampling (Render Scale Factor) and ASW (which deals with not being at 90 fps) that you just mentioned is simply that a setting of Super Sampling above 1.5 exponentially takes more time (jumps from 30% additional time to 80% at SS=2.0 - depending on your video card) and therefore requires ASW on just about every frame - and therefore the graphics distortions. I always start with RSF/SS = 1.5 and work up a little until I see ASW kick in, and then back it off. Also, then it's more of a problem with highly complex scenery (big cities or complex airports) and therefore you should reduce RSF/SS if it becomes a problem.

Dave W.

How do you know when ASW "kicks in"?

And the point for me is that this is a very recent phenomenon. I have over 270 hours in the sim and I never noticed these graphic distortions until the last few days.

I'm just trying to be helpful. The distortions don't keep me from having fun, but they are real and I thought IPACS would like to know about what I am seeing.