Grey Screen flickers, screen lockup in Rift

[SimpleThe1st]

Is anyone having any of these issues?

I upgraded all of my BIOS firmware, windows firmware, intel firmware etc and now I am having big issues in BOS mainly and steam VR. Although my frame rates improved a lot, I am getting screen freezes, stuttering (even when around 90 fps on the screen counter) and random grey screens where the sensors show up in the screen along with the grid overlay while in-game. This often happens when I am squeezing the trigger and making hits on another plane and has been giving me heavy nausea and making the game unplayable.

 

I updated everything and overclocked my i7 4790K to 4.8ghz and also overclocked my gtx 970 so I thought that might be the problem even though heavy stress testing revealed a stable system. I am getting performance frame spikes in steam vr.

 

I thought this might be a head tracking issue, so I tried different sensor positions, but that hasn't changed anything, I also reset the overclock to default settings and still have the exact same issue.

 

Does anyone know what this might be? I can't find any forums where this has been an issue for anyone and I'm not savvy enough to trace the problem myself. I tried re-installing Steam and also moved my Oculus files over to the same hard drive as my steam ones and still having the same issues.

 

Any fixes or suggestions would be great!

Thanks everyone!

[dburne]

That is odd.

 

Probably first thing I would try is re-running the Oculus setup. Kind of a pain to go through the whole thing again, but oftentimes weird glitches can get solved this way. Pay careful attention to getting your sensors set for optimum placement.

Edited August 12, 2017 by dburne

[A_radek]

Two things to try come to mind.

 

Landscape distance level, is that set to normal? At x3 or x4 you could be exceeding your gpu ram, forcing it to swap with stutters as a result.

 

USB ports. Try switching those around. If you have the rift and sensor in USB 3.0, try 2.0 ports. Unplug any other high bandwidth devices you might have.

[chiliwili69]

Just a thought from my complete ignorance.

 

If you suffer this when you hit another plane, it when BoS is making the peak calculations for the damage model, fire, smoke, etc and it may halt for few miliseconds the transfer of data to be render in the GPU, so the grey screen with the two sensor appear.

 

Since this data is sent from the RAM to the GPU, the RAM speed could play a bigger role and it could bottleneck the whole system in peak moments.

 

Your RAM speed is 1333MHz, which is a low speed for the 4790K at 4.8.

I upgraded my RAM from 1866 to 2933 and obtained a boost in fps, but was not suffering your problem before changing it.

 

Upgrading the RAM is not cheap these days, so you could borrow a faster RAM from a friend or neighbour a give it a try.

[coconut]

 

 

the RAM speed could play a bigger role and it could bottleneck the whole system in peak moments

 

Not likely, I would say. The difference in delay between the two memory types is at most a few nanoseconds, which is about 10 million times lower than the kind of delay that would be noticeable as stutter.

 

I would bet on a_radek's guess. IIRC not all the VRAM on the 970 has the same performance, which could mean it's better to keep well under full VRAM use on that GPU.

[chiliwili69]

 

 

Not likely, I would say. The difference in delay between the two memory types is at most a few nanoseconds, which is about 10 million times lower than the kind of delay that would be noticeable as stutter.

 

I was meaning that the ram speed (133MHz) could be limiting the memory bandwidth data transfer required by BOS in VR.

1333MHz has a theoretical bandwidth of 21.3 GB/s, which is used to transfer the data between CPU <--> RAM <-->GPU.

Higher RAM speed will allow larger bandwidth.

 

How you will then justify from a theoretical point of view that we improve our fps when going to higher speeds? 

[Fran13]

I solved the grey screens problems today: In the VR neck band must be placed as low possible because inflareds. I was unable check my 6 before but now just works awesome

[I./JG68_Sperber]

S ! SimpleThe1st...

I have the same Problem with my OR ;(

After 140h without Problems...

The problem started with the Update from the OR Software....

All other Games with OR running very good and the Tracking is very good too.

 

I have no Problems with my HTC Vive and IL2.

 

Dont find a solution..... ;(

 

[dburne]

 

S ! SimpleThe1st...

I have the same Problem with my OR ;(

After 140h without Problems...

The problem started with the Update from the OR Software....

All other Games with OR running very good and the Tracking is very good too.

 

I have no Problems with my HTC Vive and IL2.

 

Dont find a solution..... ;(

 

 

 

Have you tried re-running setup?

​Sometimes after an Oculus software update that helps.

[I./JG68_Sperber]

S! dburne,

i check new USB Drivers, install OR New, install IL2 new, older and new NVIDIA drivers, with 2 Sensors, 3 Sensors and 4 Sensors, and little other thinks...

CPU and GPU is Freezes at the same time for 1-5 sek. after Frezzes is all ok..90 FPS in game and in the menü.

The freeze is irregular and has nothing to do with the CPU and GPU performance.

 

Now i test HTC Vive without any Problems...SS 2,4 and 90 FPS ....very nice..

[dburne]

S! dburne,

i check new USB Drivers, install OR New, install IL2 new, older and new NVIDIA drivers, with 2 Sensors, 3 Sensors and 4 Sensors, and little other thinks...

CPU and GPU is Freezes at the same time for 1-5 sek. after Frezzes is all ok..90 FPS in game and in the menü.

The freeze is irregular and has nothing to do with the CPU and GPU performance.

 

Now i test HTC Vive without any Problems...SS 2,4 and 90 FPS ....very nice..

 

Well that is certainly very odd, sounds like for some reason your USB 3.0 might be struggling with the Rift sensors.

Doesn't the Vive tracking use USB 2.0?

Edited August 14, 2017 by dburne

[TG-55Panthercules]

Well that is certainly very odd, sounds like for some reason your USB 3.0 might be struggling with the Rift sensors.

Doesn't the Vive tracking use USB 2.0?

 

Maybe you're onto something - I noticed in my Rift box there was a notification warning not to put more than one sensor in a USB 3.0 port (and to put any additional sensors in USB 2.0 ports - it didn't say why, but apparently there's some issue of some sort there).

[SimpleThe1st]

Just a thought from my complete ignorance.

 

If you suffer this when you hit another plane, it when BoS is making the peak calculations for the damage model, fire, smoke, etc and it may halt for few miliseconds the transfer of data to be render in the GPU, so the grey screen with the two sensor appear.

 

Since this data is sent from the RAM to the GPU, the RAM speed could play a bigger role and it could bottleneck the whole system in peak moments.

 

Your RAM speed is 1333MHz, which is a low speed for the 4790K at 4.8.

I upgraded my RAM from 1866 to 2933 and obtained a boost in fps, but was not suffering your problem before changing it.

 

Upgrading the RAM is not cheap these days, so you could borrow a faster RAM from a friend or neighbour a give it a try.

I've tried just about everything. It seems it may have something to do with that new oculus update that came out, as I wasn't having this problem before the date that rolled out when I first got the rift. I was having a lot of bad frame drops and nausea, but absolutely no screen locks.

 

It will happen 1 second into the game when the frame counter is at 90fps or at any frame rate, or it could happen 5 seconds, or 15 seconds in and come and go every few seconds. It's 100% guaranteed to happen in loading screens. 1 plane, multiple planes, it doesn't matter.

 

Of note is the fact that it happens even in the spiderweb grey screen landscape of the steam version loading screen, with complete lock ups there.

 

This isn't happening in DCS world which really surprises me, I am getting a couple of frame drops and stutters in there, but no grey screen or full screen lockup issues like in IL2. No issues in loading screens either.

 

It's at the point where yes, I have tried all the solutions listed above. Overclocking of my CPU and GPU has no effect on the grey screen and locking issue, and there is no difference to the issue no matter what graphic setting I have. This is highly infuriating and is totally killing my VR buzz for il2 as I basically bought my Rift just to fly in this game. I've seen everyone raving about it on here but it after a quick couple of flights in DCS and with all the trouble, I'm at a bit of a loss. Any ideas not mentioned here? I don't really want to go saving up for some RAM when that may not be the issue if I can start saving up for a better graphics card. My current setup gets a 11,368 in firestrike. Is that too low and what is causing these issues?

[A_radek]

When you say every other game works fine, are those others run through occulus home? Or have you tested other VR games through steam?

 

Another thought, have you installed any il2 mods? Terrain ini file, reshade, 4K skins? And if not are you running any overclocking or nice to have software in the background? Other than steam and occulus home that is.

 

Also, il2 is very CPU dependent. Are CPU temps ok? Just to make sure no auto throttling is going on.

 

While annoying and persistent, don't give up. It sounds like a fixable problem. When I first tried the rift it was on my old rig i7 920 @4.0, Gtx970. It only had usb 2.0 and while frame rates were often at 45 it did not suffer these stutters. This was a while back so not the latest occulus or steam versions.

[I./JG68_Sperber]

Yesterday night, I make a re-install from the oculus set up.

After that the Tracking are bedder but the freezes comes again.

The Problem is to 100% the new oculus software (USB) and IL2...

The Vive have only USB for the headset.

Edited August 15, 2017 by I./JG68_Sperber

[chiliwili69]

 

 

It will happen 1 second into the game when the frame counter is at 90fps or at any frame rate, or it could happen 5 seconds, or 15 seconds in and come and go every few seconds. It's 100% guaranteed to happen in loading screens. 1 plane, multiple planes, it doesn't matter.

 

As you describe this now, I think it has nothing to do with RAM speed. It seems to be related to Oculus software upgrade and SteamVR lossing tracking. The problem is that you can not roll-back the upgrade. It the past Oculus allowed to run older versions but since they launch Oculus Home not anymore.

 

More people like SPerber (we don´t know their rig specs) are reporting the issue, so it is not an isolated issue.

 

Do you run SteamVR or SteamVR Beta?

[SimpleThe1st]

When you say every other game works fine, are those others run through occulus home? Or have you tested other VR games through steam?

 

Another thought, have you installed any il2 mods? Terrain ini file, reshade, 4K skins? And if not are you running any overclocking or nice to have software in the background? Other than steam and occulus home that is.

 

Also, il2 is very CPU dependent. Are CPU temps ok? Just to make sure no auto throttling is going on.

 

While annoying and persistent, don't give up. It sounds like a fixable problem. When I first tried the rift it was on my old rig i7 920 @4.0, Gtx970. It only had usb 2.0 and while frame rates were often at 45 it did not suffer these stutters. This was a while back so not the latest occulus or steam versions.

 

DCS World running through Steam is working fine, so I think it seems to just be related to iL2.  No mods installed, no 4k skins, I pulled back the overclocking to stock for both the CPU and GPU and this has no effect on the issues.  I have a watercoooler on my CPU and temps seem quite low, so I don't know why it would be throttling.  Since it's only happening on iL2 I figure it must be a software issue.

Maybe you're onto something - I noticed in my Rift box there was a notification warning not to put more than one sensor in a USB 3.0 port (and to put any additional sensors in USB 2.0 ports - it didn't say why, but apparently there's some issue of some sort there).

Tried that fix and it doesn't affect anything.  It says that if you have a 3rd sensor or more, they need to be connected to USB 2.0.

I've tried multiple options, Rift usb in 3.0 and 2.0, Rift in 3.0, sensors in 2.0, All USB in 2.0 and the result is still the same.

 

It doesn't appear to be a tracking issue as I kept an eye out through the bottom of the rift on the Steam VR mini window and it showed no tracking warnings while the issue happens.  This will happen on loading screens while I am looking straight ahead as well, so I highly doubt that its a physical tracking issue.

As you describe this now, I think it has nothing to do with RAM speed. It seems to be related to Oculus software upgrade and SteamVR lossing tracking. The problem is that you can not roll-back the upgrade. It the past Oculus allowed to run older versions but since they launch Oculus Home not anymore.

 

More people like SPerber (we don´t know their rig specs) are reporting the issue, so it is not an isolated issue.

 

Do you run SteamVR or SteamVR Beta?

I didn't have the option to choose between Steam VR and Steam VR Beta.  How do I know which version I am running?  I can't recall seeing a Beta tag or option to choose between the two. (I've also re-installed Steam and all games again to try fix this).

 

I really do get the feeling it's related in some way to the Oculus update....

S! dburne,

i check new USB Drivers, install OR New, install IL2 new, older and new NVIDIA drivers, with 2 Sensors, 3 Sensors and 4 Sensors, and little other thinks...

CPU and GPU is Freezes at the same time for 1-5 sek. after Frezzes is all ok..90 FPS in game and in the menü.

The freeze is irregular and has nothing to do with the CPU and GPU performance.

 

Now i test HTC Vive without any Problems...SS 2,4 and 90 FPS ....very nice..

So you use the Vive and you had similar issues and now you don't have the issues?

I solved the grey screens problems today: In the VR neck band must be placed as low possible because inflareds. I was unable check my 6 before but now just works awesome

Neck band?  What's a neck band?

[SimpleThe1st]

Two things to try come to mind.

 

Landscape distance level, is that set to normal? At x3 or x4 you could be exceeding your gpu ram, forcing it to swap with stutters as a result.

 

USB ports. Try switching those around. If you have the rift and sensor in USB 3.0, try 2.0 ports. Unplug any other high bandwidth devices you might have.

I can't see it being related to landscape levels, as it the issue neither gets better or worse according to any graphics settings.  Plus it happens in loading screens, including the main loading screen for the game when you sign in for the game and first open it.  There are also multiple times when the game just quits when I try to load it, or it diverts me to the steam vr menu after I go to load. Plus already tried multiple USB switches.

[dburne]

 

Tried that fix and it doesn't affect anything.  It says that if you have a 3rd sensor or more, they need to be connected to USB 2.0.

I've tried multiple options, Rift usb in 3.0 and 2.0, Rift in 3.0, sensors in 2.0, All USB in 2.0 and the result is still the same.

 

 

 

Have you ever ran the Oculus Compatibility Checker?

 

The Rift and it's sensors can be finicky on the type of USB 3 controllers. The check sometimes will flag controllers that are known to cause issues with the Rift. I did this after I ordered the Rift, it flagged my onboard ASMedia USB 3 Controller as known to cause issues,  so I got the Innateck USB 3.0 powered add in card, and mine has been solid for me in every respect.  I have two sensors and the Rift plugged into it.

​Of course no telling why you are getting the experience you are, just trying to cover all the bases.

[I./JG68_Sperber]

I have now contact to Oculus support.

I send the Diagnostic files to Oculus...

 

@SimpleThe1st

 

Yes i have the HTC Vive too.

 

HTC Vive is running perfect with IL2!

All other VR Games with Oculus Rift running perfect also the Tracking.

 

The Problem ist only IL2 and Oculus ;(

[Fran13]

 

Neck band?  What's a neck band?

 

 

https://d3nevzfk7ii3be.cloudfront.net/igi/QRaQveDpKKcNvXrN.medium

 

In that link you should be able check all Oculus inflared located in your back. Those spots should be visible by your Camera or a Grey screen will be displayed. 

[dburne]

I have now contact to Oculus support.

I send the Diagnostic files to Oculus...

 

@SimpleThe1st

 

Yes i have the HTC Vive too.

 

HTC Vive is running perfect with IL2!

All other VR Games with Oculus Rift running perfect also the Tracking.

 

The Problem ist only IL2 and Oculus ;(

 

When using the Rift, is Il-2 the only game you play through Steam VR?

[I./JG68_Sperber]

I play only IL2 with VR.

All other VR games are for testing... I test with Steam VR and without.

No Problems, the Tracking with 3 Sensors are perfect.

[SimpleThe1st]

Have you ever ran the Oculus Compatibility Checker?

 

The Rift and it's sensors can be finicky on the type of USB 3 controllers. The check sometimes will flag controllers that are known to cause issues with the Rift. I did this after I ordered the Rift, it flagged my onboard ASMedia USB 3 Controller as known to cause issues, so I got the Innateck USB 3.0 powered add in card, and mine has been solid for me in every respect. I have two sensors and the Rift plugged into it.

​Of course no telling why you are getting the experience you are, just trying to cover all the bases.

Yes I ran that with everything plugged in before I bought the rift. Does something change if you run it after plugging one in?

[dburne]

Yes I ran that with everything plugged in before I bought the rift. Does something change if you run it after plugging one in?

 

No, it would be the same.

 

I am clueless at this point, no idea why you would have great tracking in your other games but not in BoS.  I have been flying it pretty heavily since the VR release, and have never had an issue like that. 

If you have rerun the setup and  your sensors are showing good along with the HMD  ( in the settings/devices tab on monitor), you really should be good to go.

 

Dang computers  can be so finicky at times. Hope it gets worked out for you soon!

[SCG_Fenris_Wolf]

Silly idea, but might it be lag, if you're playing MP ? I've had that on Wings. The old hamster powering it sweats and coughs regularly.

[SimpleThe1st]

No, it would be the same.

 

I am clueless at this point, no idea why you would have great tracking in your other games but not in BoS. I have been flying it pretty heavily since the VR release, and have never had an issue like that.

If you have rerun the setup and your sensors are showing good along with the HMD ( in the settings/devices tab on monitor), you really should be good to go.

 

Dang computers can be so finicky at times. Hope it gets worked out for you soon!

I sure appreciate the help and I hope it gets figured out as well!!

Silly idea, but might it be lag, if you're playing MP ? I've had that on Wings. The old hamster powering it sweats and coughs regularly.

I haven't even got to multiplayer yet. This is just in a quick mission. Would love to be able to play a multiplayer game in vr..

[chiliwili69]

Another silly idea but,  is there any sunlight, mirror, reflection glass which could mesh your sensors?

 

Also, Have you tried with just one camera sensor?  (the original Rift, and also the DK1 and DK2 only used one)

 

 

I didn't have the option to choose between Steam VR and Steam VR Beta.  How do I know which version I am running?

 

You know if you run the Beta by the name of the application. Mine is "SteamVR" so it is the main branch application. If your application is named "SteamVR Beta" than is the Beta.

Also you can know that by the version of the application. If it begins by 149xxxx it is the main one. If it begins by 150xxxx then it is the Beta.

[SimpleThe1st]

I found a few answers to similar problems over here for anyone else who has a similar issue:

https://forum.il2sturmovik.com/topic/28573-game-version-2009-discussion-open-vr-support/page-10

 

I ran this line of code (just Added the line about the false for force fade bad tracking):

 

Navigate to ...Steam\config and open steam.vrsettings (using notepad++) .

 

Delete contents and paste

 

{

"steamvr": {

"mirrorViewGeometry": "0 0 960 540",

"forceFadeOnBadTracking": false

}

}

 

 

Thanks to user peregrine7 for that one which has stopped the grey screen showing up. I still have the complete frame freezing while the sound and game keeps running in the background. Task manager doesn't seem to be showing any changes in CPU load when this occurs, also no additional memory load on the RAM although even the task manager seems to freeze a bit when it happens. I'm a bit ignorant, but Would the fact that the game continues to play in the background somehow and then jumps to wherever the plane ended up due to control inputs during the screen freeze mean that it's a graphics card issue?

 

It's possible that it's a tracking issue, the steam vr icon shows the headset as tracking normally though when it happens. I noticed that after the freeze, the frame counter resets to close to 0 fps! I'm starting to think that this is perhaps a software issue somewhere.

 

I have also used a number of settings in Nvidea control panel that I found here for my GTX 970:

http://www.tomsguide.com/faq/id-3079723/optimize.html

 

These seem to have helped with a few things. If I could just get rid of the screen freeze now, I would be ready to really enjoy VR!! Thanks for helping me narrow it down so far!!

 

Another silly idea but, is there any sunlight, mirror, reflection glass which could mesh your sensors?

 

Also, Have you tried with just one camera sensor? (the original Rift, and also the DK1 and DK2 only used one)

 

 

You know if you run the Beta by the name of the application. Mine is "SteamVR" so it is the main branch application. If your application is named "SteamVR Beta" than is the Beta.

Also you can know that by the version of the application. If it begins by 149xxxx it is the main one. If it begins by 150xxxx then it is the Beta.

I do have a ceiling light up in the corner in the back. I will have to try running the game in the day to eliminate that as a cause. I guess I could try it in the dark...

 

Pretty sure I'm running regular Steam VR as there's no beta writing that I can see anywhere.

 

Will try with just one sensor, no light source in-room and see if that changes things. If that's the case, it's a sensor issue.

 

Only other thing I can think of is that I'm running Oculus and Steam on a 7200 rpm 1tb hard drive and windows 10 on a 250GB SSD. That may be causing a bottleneck somewhere?

[SimpleThe1st]

I'm not sure what the problem was, but I wiped everything and ran a clean install of windows. Combined with all the tweaks above (which there is no way I would have figured out without the forum help) I am up and running again, with very few freezes now, other than mainly in loading screens. I have nausea again but that's just due to the frame drops and stuttering. Thanks everyone for your help! Now onwards in the quest for an increase in fps!!

[chiliwili69]

 

 

I have nausea again but that's just due to the frame drops and stuttering. Thanks everyone for your help! Now onwards in the quest for an increase in fps!!

 

Glad to see your problems went away! Sometimes a clean install solves everything.

 

It would be interesting to know the performance you get for a 4790K @4.8 with the 970 card. If you have a chance you could try to run the VR test before any hardware upgrade:

https://forum.il2sturmovik.com/topic/29322-measuring-rig-performance-common-baseline/