This worked for me as well. I assigned ED to cores 1 and 2. Then assigned Oculus to cores 3 and 4. Smooth tracking and no grey flashes. Now I have to learn autokey to make it easier to set each time.
Thanks rkodey!
Oculus sensor tracking and greyout flashing issues with Elite Dangerous (Oculus 1.13 & 1.14)
- Thread starter Talmanes
- Start date
This worked for me as well. I assigned ED to cores 1 and 2. Then assigned Oculus to cores 3 and 4. Smooth tracking and no grey flashes. Now I have to learn autokey to make it easier to set each time.
Thanks rkodey!
Ok... I suppose it's time for me to make a compiled version of the Autohotkey script, to make it easy for anyone to try. Set it and forget it.
I still seem to be experiencing the flashes. They're not as frequent as they were with 1.3.01, but damn...still annoying as all hell. I estimate I get maybe 2-3 per minute. Affinity does nothing.
What I don't understand is why does Oculus support tell you to plug their 3.0 sensor USB into a 2.0 slot in order for it to work (which it doesn't very well)? Why can't I plug in my sensor AND headset into the inateck? I still think there's some kind of USB issue going on here.
These flashes don't make the game unplayable anymore, but I can't do more than an hour or so before I get frustrated and annoyed. I miss the good old days of 1.12
What I don't understand is why does Oculus support tell you to plug their 3.0 sensor USB into a 2.0 slot in order for it to work (which it doesn't very well)? Why can't I plug in my sensor AND headset into the inateck? I still think there's some kind of USB issue going on here.
These flashes don't make the game unplayable anymore, but I can't do more than an hour or so before I get frustrated and annoyed. I miss the good old days of 1.12
Why can't you?
I'm seeing these issues but only in ED. On 1.14 and i5 6600k. Greyouts every minute or so for a second. Also seems to correspond with an audio glitch / crackle.
Both sensors (I have touch) plugged into motherboard based USB3 slots.
Both sensors (I have touch) plugged into motherboard based USB3 slots.
Last edited:
Haven't played much in VR recently as have been troubleshooting multi crew connection. Tried playing this morning and this is actually worse than I thought. I get micro-glitches actually every 5 - 20 seconds and occasional HMD disconnects. Only seems to happen in ED for me. Roborecall and Google Earth via Oculus home are both fine. I'm launching ED via the launcher directly (Steam install).
i5 6600k, Asus strix 980ti, Win10 Creator update and Oculus 1.14. Both sensors and the HMD are connected directly to USB 3 slots on the motherboard (no external USB expansion cards).
The glitches are a half second loss of tracking, dimmed colours, a head bob like the view is being reset and a glitch in the sound (crackle).
I tried the core affinity solution but it makes it worse for me; causing slow tracking.
i5 6600k, Asus strix 980ti, Win10 Creator update and Oculus 1.14. Both sensors and the HMD are connected directly to USB 3 slots on the motherboard (no external USB expansion cards).
The glitches are a half second loss of tracking, dimmed colours, a head bob like the view is being reset and a glitch in the sound (crackle).
I tried the core affinity solution but it makes it worse for me; causing slow tracking.
Messed around today with this. Tried the current beta build of the Oculus run time. which on it's on own didnt fix anything however...
After restarting Oculus home said that it could not detect the HMD via HMDI. I was using a display port to HDMI adapter and so I plugged the rift directly into a HDMI port. I then started ED and I get far far fewer disconnects. I still had a couple but maybe one or two per hour than one every few seconds.
Worth trying?
After restarting Oculus home said that it could not detect the HMD via HMDI. I was using a display port to HDMI adapter and so I plugged the rift directly into a HDMI port. I then started ED and I get far far fewer disconnects. I still had a couple but maybe one or two per hour than one every few seconds.
Worth trying?
So I've been in regular contact with both FDev and Oculus on this issue. Oculus has requested another set of logs, and asked for my Mobo model # P8277-V (Deluxe). We'll see if they can figure anything out.
As for FDev, here's what they suggested:
Thanks for getting back to us. Here's the issue: since 2.3 it's not supposed to be possible to launch VR through the Frontier launcher. Somehow you're still able to do this. You must be some kind of wizard.
What you'll want to do is launch Elite Dangerous through Oculus Home. Assuming you have this already installed, you can add ED to your Oculus library by logging in and claiming a key here: https://www.frontierstore.net/frontier_partnerkeys/index/index/
I will give this a try tonight and report back.
Edit: That link didn't end up working for me. I had to log into my FDev acct at https://www.frontierstore.net, click My Account -> Product Access keys -> Partner Keys
As for FDev, here's what they suggested:
Thanks for getting back to us. Here's the issue: since 2.3 it's not supposed to be possible to launch VR through the Frontier launcher. Somehow you're still able to do this. You must be some kind of wizard.
What you'll want to do is launch Elite Dangerous through Oculus Home. Assuming you have this already installed, you can add ED to your Oculus library by logging in and claiming a key here: https://www.frontierstore.net/frontier_partnerkeys/index/index/
I will give this a try tonight and report back.
Edit: That link didn't end up working for me. I had to log into my FDev acct at https://www.frontierstore.net, click My Account -> Product Access keys -> Partner Keys
Last edited:
Are FD joking, I am launching ED VR through frontier launcher as well. I Think many are!
So they want you to register ED in Oculus home and then download the whole thing again just to be able to launch it from O home?
Last edited:
One other thing; before I started ED (through launcher not Oculus Home) I re did the sensor setup for touch. Not sure if that matters but whichever of the changes I made worked. Just played for 2 hours without a glitch once!
X-Terminator
Banned
Talomes it will not rid the Flashes/Grey outs/Jumps as it has already been reported by many on the Oculus Forum for other games launched from Home.
I did warn you that Oculus Help is a joke and now we see that FD Help is also! But hey, we are now all considered to be...
Oculus Home starts when a game has VR selected as a Mode OR you simply put on the HMD (like magic!)
Some have got this solved by unplugging HMD and back again after reboots without it.
I did warn you that Oculus Help is a joke and now we see that FD Help is also! But hey, we are now all considered to be...
"WIZARDS"
and just to think they used to burn Witches in the dark ages hehe!
Tell us how it did not work and now you have 2 game installs taking up needless drive space...Oculus Home starts when a game has VR selected as a Mode OR you simply put on the HMD (like magic!)
Some have got this solved by unplugging HMD and back again after reboots without it.
Last edited:
You are probably right X-Terminator. However, I also get no audio out of my Rift with the Ed Launcher unless I change my audio playback to the Rift as "default". This is the only Rift game/app that requires the "default" setting. Hopefully, with the Oculus Home launcher I won't have to keep switching my default playback device.
I installed the Oculus Home version recently after having used the Steam version. My settings and key bindings were the same, as both installs use the same user files.
X-Terminator
Banned
Just tried Unplugging HMD fully and reboot, Replug and boot. PC felt like it loaded much smoother with icons instantly. At times my Nvidia drivers would not load and require the Disable/Enable Reboot to work again rather than the long re-install methods.
Oculus VR programs all retain the last used Affinity Settings and it worked great and actually for the 1st time ever I was getting 55fps in SC to then have ASW (disabled) cap back down to 45 constantly juggling it.
ED64.exe I now leave on ALL Cores and is fine.
I reset the Affinity to ALL Cores for Oculus Programs (6) and get 1 flash within 1min. These are much rarer than were previously anyways but get these each 10mins or so unless I do the Affinity trick of only last 2 Cores for all OCULUS progs.
i.e. I do not need to set anything at all EVEN after any future Boots but use Sleep anyways by choice. SiMPLE.
- - - Updated - - -
I just use the Win10 Speaker Icon on lower Right to do this and is no big deal for a WIZARD
My next challenge is changing the USB2 PCI card to a USB3 PCI (rare - not PCIe) I just bought for deciding if to purchase Touch if it works ok with it . At present non of the Oculus Hardware can even find the old one so have them on the motherboard (which they claimed was non-compatible! Not for a WIZARD!!!)
Oculus VR programs all retain the last used Affinity Settings and it worked great and actually for the 1st time ever I was getting 55fps in SC to then have ASW (disabled) cap back down to 45 constantly juggling it.
ED64.exe I now leave on ALL Cores and is fine.
I reset the Affinity to ALL Cores for Oculus Programs (6) and get 1 flash within 1min. These are much rarer than were previously anyways but get these each 10mins or so unless I do the Affinity trick of only last 2 Cores for all OCULUS progs.
i.e. I do not need to set anything at all EVEN after any future Boots but use Sleep anyways by choice. SiMPLE.
- - - Updated - - -
I just use the Win10 Speaker Icon on lower Right to do this and is no big deal for a WIZARD
My next challenge is changing the USB2 PCI card to a USB3 PCI (rare - not PCIe) I just bought for deciding if to purchase Touch if it works ok with it . At present non of the Oculus Hardware can even find the old one so have them on the motherboard (which they claimed was non-compatible! Not for a WIZARD!!!)
Last edited:
When you say unplugged, do you mean the HDMI, USB, or both?
X-Terminator
Banned
Both and powered down also. It changed nothing for the Flash issue. Affinity is my fix.
Last edited: