Oculus sensor tracking and greyout flashing issues with Elite Dangerous (Oculus 1.13 & 1.14)

Verlaine

V
I get the gray-outs and momentary tracking freezes with 1.14, too. I never had these issues with 1.12 or earlier. My Oculus software updated itself from 1.12 to 1.14 today, so I skipped 1.13 entirely. But now ED is pretty much unplayable. [mad]

Edit: support ticket with Oculus logged
 
Last edited:

Verlaine

V
Are you still seeing this issue after 2.3.01? I played several hours tonight, my first session since 2.3.01, and I've had one gray-out only. My previous session with 2.3 I'd get gray-outs no less than every minute or two.
 

etien

etien
X-Terminator said:
Thanks to RKODEY. I've posted this all over Oculus Forums, they have acknowledged they are looking into it. However, it does not solve all games e.g. RoboRecall...

OK Oculus, fix this plus add a Switch in OCULUS HOME to DISABLE ASW + NOT CAP to 45fps.

Jumps and Flashes are fixed by setting Affinity settings: -
Run ED then go to TASK MANAGER>DETAILS: Right-Click Affinity

ED64: cores 0-5 (this is the game Elite:DDangerous)
OculusVR: cores 6-7 (this file may be new in latest Public Test update)
OVRServer_64: cores 6-7

OCULUS must now code this so we do not require manual or autohotkey programs.
https://forums.oculus.com/community...-of-version-1-14-pc-software-update-for-april


BTW I put my PC to Sleep and so the only program I must set Affinity for each time is E:DD



KILLCARD wrote: -
"Actually, I don't think the game has anything to do with it. What I did to figure this out was:

1. Load up the Oculus + home.
2. Open up Task Manager and find the OVRServer_64.exe
3. Disable 1 of the cores and click apply
4. Check perforamance result in Oculus Home
5. Repeat Steps 3-4 until Tracking/Framerate in Oculus home dies then re-enable that core and continue to disable others.

You should find there will be one core that will make tracking practically dead if you disable it regardless of what other cores are enabled.. and another that will reduce tracking performance if its disabled. For me, as soon as I dropped core 4, everything went to .. with only Core 4 on it worked but with poor performance (slow tracking update, black border visible when rotating), until I enabled core 6 then it all worked fine.

I got this set up without any games running, just Oculus Home .. which leads me to think that it is somehow based on System/CPU/Operating system or some other factor. "
Click to expand...

Thanks a lot it works nicely for me
 

Talmanes

Talmanes
Verlaine said:
Are you still seeing this issue after 2.3.01? I played several hours tonight, my first session since 2.3.01, and I've had one gray-out only. My previous session with 2.3 I'd get gray-outs no less than every minute or two.
Click to expand...

I just played for a couple hours last night and noticed that it's greatly reduced. I still had greyouts, but they were not nearly as frequent. I also noticed that there was an oculus driver update, though I'm not sure if that played any role.
 

Mendes Soze

M
Thought I wade in with my experience....

Up until 2 nights ago I had the odd grey out / jump issue which first appeared around the Elite 2.3 update... which I assumed was the issue.

Half way through my Elite session I was notified Oculus needed an update, which I applied. I now no longer get the grey outs as far as I've noticed but what I do get is worse... quick disconnects of the HMD, black screen for a split second, not great while boosting through an asteroid field. It's fairly random, on average every 10 minutes or so.

I initially assumed it was to do with the Elite update I applied the same night but I have since tried other games, Robo Recall and Google Earth and the problem is seen in those apps too. Also the whole VR experience doesn't feel quite as smooth.

There's so much conflicting information on the internet and various forums... I now know it's not Elite only. I'm going to be trying the USB Power Management suggestions. I just hope it's not my Rift hardware and it certainly 'feels' like a software issue.

I'm yet to report to Oculus. Once I get chance I want to try a few things myself first. I'll report back if there is any success.
 

-VR- Max Factor

-VR- Max Factor
dape said:
this problem seems to affect only multithreaded CPU's. Havent heard anybody with an i5 complain. Running myself an i5 and do not have any of those symptoms
Click to expand...

I have an i5 and am now getting these issues, it was fine for 1.13, it forced me to update last night to 1.14 and it has broken it. Have no idea what they have done, but I am not a happy bunny.

I keep getting quick flashes of greyout as if the sensor stops working and it is very frustrating.
 
Last edited:

dape

dape
Max Factor said:
I have an i5 and am now getting these issues, it was fine for 1.13, it forced me to update last night to 1.14 and it has broken it. Have no idea what they have done, but I am not a happy bunny.

I keep getting quick flashes of greyout as if the sensor stops working and it is very frustrating.
Click to expand...

thanks for the update. That is bad news. I have not played with 1.14 yet but fear the worst. So far I never had any greyouts or flashes
 

Mendes Soze

M
Max Factor said:
I have an i5 and am now getting these issues, it was fine for 1.13, it forced me to update last night to 1.14 and it has broken it. Have no idea what they have done, but I am not a happy bunny.

I keep getting quick flashes of grey out as if the sensor stops working and it is very frustrating.
Click to expand...

Hmm, I find it interesting that some people have grey outs, and some people, me, have short HMD disconnects. I'm wondering if these are different symptoms of the same problem?

I'd suspect so and it's related to what you have plugged where. I may swap my HMD USB over to a sensor USB. By doing that if my "blackouts" become "greyouts" then that would at least hint to it being a USB driver / Oculus update issue.

Saying that it may still be that I still get grey outs but I haven't noticed them as yet... though not acceptable I'd still prefer them to the short terrifying blacknesses.
 

AstroCreep

AstroCreep
For those experiencing grey outs are you running through Steam with SteamVR? Only ask as I get these grey outs but not with Elite, with just one Racing Sim yet others are perfectly fine. Tracking doesn't seem to be an issue in Elite or other games just this one in particluar and narrowing down the cause is tough.

I've come to call it an "IBB!" - Irritating Bug!
 

Neo-ST

Neo-ST
Updated to 1.14.
Still bad.
Stutters, skips tracking.
Now I'm getting a new effect, dipping. As if you suddenly...dipped, then got up quickly again.
All noticed in Oculus home.
 
Last edited:

rkodey

R
For those of you still getting the grey-outs: Can you try monitoring your CPU usage, to see if there's high(er) CPU usage when the grey-outs seem to happen?

For me, there was a high correlation, even though I have a fast CPU. I came up with a fix that seems to have made my Oculus track smoother than I've ever seen before. NOTE: I'm not sure this is a universal fix. A few people said it worked, and a few said it has not.

So, if you're seeing higher CPU usage when the greys happen, try:

See post earlier in this thread:
https://forums.frontier.co.uk/showt...13-amp-1-14)?p=5415720&viewfull=1#post5415720

Or, more info here:
https://forums.frontier.co.uk/showt...rience-Guide-Compendium?p=5402459#post5402459
 

buyback

buyback
rkodey said:
For those of you still getting the grey-outs: Can you try monitoring your CPU usage, to see if there's high(er) CPU usage when the grey-outs seem to happen?

For me, there was a high correlation, even though I have a fast CPU. I came up with a fix that seems to have made my Oculus track smoother than I've ever seen before. NOTE: I'm not sure this is a universal fix. A few people said it worked, and a few said it has not.

So, if you're seeing higher CPU usage when the greys happen, try:

See post earlier in this thread:
https://forums.frontier.co.uk/showt...13-amp-1-14)?p=5415720&viewfull=1#post5415720

Or, more info here:
https://forums.frontier.co.uk/showt...rience-Guide-Compendium?p=5402459#post5402459
Click to expand...

Hey Rkodey,

did you already try to turn off hyper threading instead of setting cpu affinity ?
 

rkodey

R
buyback said:
Hey Rkodey,

did you already try to turn off hyper threading instead of setting cpu affinity ?
Click to expand...

Nope, but that's something else to try!

But, with HT enabled and my Autohotkey affinity solution, I'm running nice and smooth. (I prefer to keep HT enabled.)
 

dape

dape
just updated to ED 2.3.02 and OH 1.14. Playing for about 30 minutes, scouting a planet for Geysers, riding the SRV... No Greyouts or flashes whatsoever.
I am launching ED via the ED Launcher, maybe that makes a difference?!

Edit: 1 sensor
 
Last edited:

[VR] Frank_G

[VR] Frank_G
dape said:
just updated to ED 2.3.02 and OH 1.14. Playing for about 30 minutes, scouting a planet for Geysers, riding the SRV... No Greyouts or flashes whatsoever.
I am launching ED via the ED Launcher, maybe that makes a difference?!
Click to expand...

I am also playing via ED launcher and i sometimes get a single flash, but nothin annoying or frequent, so it is absolutely no problem. I am using a 2 sensor setup.
 

CptXabaras

CptXabaras
Playing on ED launcher, 1 sensor. Only one time I saw one gray flash has been at first loading when the orange ship hologram is spinning. No other issue so far
 
You must log in or register to reply here.
Back
Top Bottom