Last edited:
Getting started: E D with your Rift
- Thread starter Para Handy
- Start date
I have the E D Profiler - I didn't get a chance to use it as Oculus took over. Will hope to do so when I reinstall.
Thanks for the set service to manual-start tip. I'll bear that in mind.
BTW - VA, I do have this installed as well as the lovely Eden voice pack (I have a thing for Norwegian ladies' accents) - not got it properly set yet, combination of not wanting to lose some of my bindings plus my variable accent (sometimes very Scottish, sometimnes Extremely Scottish) with windoze's voice recognition (I can't think what Russ Abott would do to it!).
AHA - well I never noticed that, thanks for that. (I can't rep you again yet, will remember to do so at some point, but have a virtual one in the meantime.
)
Last edited:
No problem, all your issues can be solved and you only have to set thing up once. Stay positive.
Not sure what "start in desktop" mode does but, how does that help him get the "enable HMD" option back in the graphics options menu considering he is trying to start ED without launching from it from OH as I read it. Or am I missing something here?
Yes you did.
6. Disable the "safety/health warning" on the same page.
7. Open privacy settings and set everything to "only me".
It doesn't, but he wasn't aware that ED can run in non VR mode from OH home.
Interesting. Not running Ed from there myself, I was not aware of that feature. Thanks for that clarification. My confusion by the response was that it doesn't work with his stated problem, if I understand it as he has explained it so far. It's early yet in the info garnering phase.
I read his complaint as he couldn't get a non-OH 2nd install (a "separate install") to run in VR because OH is controlling menu options in both installs despite only one being registered in Home. Hence the missing settings. If he is correct and it seems plausible, then he could try running the alt install in non-vr to see if he can regain these setting to turn on vr on in said separate install. if this is indeed the case he would not be using "start from desktop" option for the offending installation as he is not launching that one from Home. This all assumes I read him right. I am sure OP will clarify when he returns to the thread. Tis an interesting quandary at any rate. Cheers
dogbite;5734074.................... I read his complaint as he couldn't get a non-OH 2nd install (a "separate install") to run in VR because OH is controlling menu options in both installs despite only one being registered in Home. Hence the missing settings. If he is correct and it seems plausible said:
If you can, plug the sensors directly into the PC's MB USB 3 ports. Lots of reports of them not liking hubs and cards.
Last edited:
Well that was a little less convoluted. Thanks for the clarification. So it seems you have a work around for the moment. Your statement " if so it means some registry stuff is hanging in there from last night and I'll have to uninstall Oculus again and go back to my pre-yesterday restore point" seems logical enough. Perhaps just deleting any registry references Oculus left behind before re-installing would suffice. An earlier restore point, I would think, would also work. Let us know how you make out. GL
Last edited:
Yes indeed, I found that the sensors detected / interrpreted my 7-port USB3 hub (powered) as USB2 so wouldn't set up until I moved one to a case USB3 connector. It is my intention to fit a 4-port PCIe card and move less sensitive items onto that, leaving my mobo's USB3 connectors free for Rift use. I bought quite a good mobo when I built this PC last year but there are only 3 USB3 ports (plus one USB3.1c and 4 USB2) on the board itself and one riser (feeding my front panel) - I should have been more aware when buying.
Talking of "things" not being liked - does the Rift HMD tolerate an HDMI extension lead? I am just thinking about using a short extender so that I can plug-in as needed without access to the rear of the PC. Because even if I end up not using the Rift much in E D, I won't be sending it back - things like the ISS are just so amazing. (I will have to rearrange my layout though, I need much more space around the PC to cut down on the bruises!)
Last edited:
I use this one and it works fine for usb . https://www.amazon.ca/gp/product/B0179MXKU8/ref=oh_aui_detailpage_o00_s00?ie=UTF8&psc=1 I would image their hdmi extention would be of the same quality. Oculus has a list of recommend extenders somewhere on their site. I think they even sell them, if not mistaken. Naturally not all cables are created equally.
Last edited:
Just don't plug them in next to each other, if you can. They really should be on separate USB controllers. If you plug them all into the motherboard, spread them out, and ideally see if you can find out which ports are grouped together onto individual controllers, so that they don't share.
Cards are OK, as long as they're capable of the full bandwidth, per port, which means getting a multi-channel USB card to be absolutely sure that it can handle it. These usually start around $80 (US). The problems arise when people buy the less expensive cards, and then plug two sensors and the HMD into it together. Most single-controller cards won't handle that sufficiently, or they'll seem to work, but the tracking isn't great.
EDIT: You can also run afoul of having the cards competing with other cards for PCI bandwidth on the motherboard. Usually this isn't a problem, but if all else fails, it's worth checking. I looked at my motherboard's manual very carefully, and found that there is one 4x PCIe slot that doesn't divide up the bandwidth with the other slots, so I put my multi-channel USB card into that slot. Every board will be different.
Last edited:
Afaik it's not necessary to pick a special port.
https://en.wikipedia.org/wiki/PCI_Express
Wikipedia said:
I've had my sensors plugged next to each other without problems while running. Only issue I've had is sometimes the sensors not being recognized at boot up but unplugging and plugging always resolves the issue.
A lot of the time two sensors together will be fine. Add a third, or the HMD onto the same controller, and there may be issues, depending on your chipset. It's not a guarantee that it'll be problematic, but it's enough of a problem on some hardware that it's worth being aware of. If you have odd, intermittent tracking issues, it should be one of the troubleshooting steps to separate them. Or just separate them up front, so you know you won't run into that.
OK if I am understanding your issue correctly:
Right click on the task bar and select task manager. Left click the services tab. Left click anything on the list below and hit the 'O' key. Right click and select stop for OVRService and then the OVRLibraryService. If you launch ED now it will be windowed and VR is effectively switched off.
Oculus recommends running their Compatibility Test tool--downloadable from their website at https://support.oculus.com/1357437467617798, before installation of the Rift hardware and especially software. Doing this can prevent many complications later. The tool is very sophisticated and will analyze USB connectivity and hardware as well, among other requirements and makes recommendations on resolving these. Some crappy MB chipset implementations split USB 3.0 bus bandwidth and this is why using a dedicated PCIe daughter card is the best investment. I had to disable my Asus Maximus VIII onboard USB controllers in the BIOS and install the recommended replacement board and all random disconnects and systemic issues involving the sensors and detection of the Rift itself had ceased.
Dr. Kai's ED Profiler tool is mandatory for being able to switch multiple profiles (desktop/VR). Disabling services, unplugging and replugging hardware should not be necessary at all if everything is properly configured per Oculus' guidelines.
Countless hours can be wasted and the whole experience can be excruciating if these steps are not properly followed, because the current generation VR hardware is extremely demanding. I had both the Vive and Oculus CV1 since Day 1 and the drivers became more robust since the early days, but it's still far from a plug & play installation unless your system is fully compliant. The results with a fully optimized system are more than worth the investment in the end.
- So I would make sure the hardware is all sorted out and the tool shows all Green.
- Once that is done, I would do a full wipe and clean installation of Windows plus OEM drivers and only then proceed with the Oculus software installation and Rift setup.
- After the Rift is successfully setup and working with Oculus Home, then it would be the right time to start installing Elite Dangerous.
- Finally, load Voice Attack, EDDI, to configure key bindings and HOTAS virtual drivers, scripts and macros.
- Optional: HelloV.io is a free utility I also recommend for the CV1 to inject YouTube, Netflix, etc., to offset the boredom for those long exploration trips or worse, passenger missions..
Dr. Kai's ED Profiler tool is mandatory for being able to switch multiple profiles (desktop/VR). Disabling services, unplugging and replugging hardware should not be necessary at all if everything is properly configured per Oculus' guidelines.
Countless hours can be wasted and the whole experience can be excruciating if these steps are not properly followed, because the current generation VR hardware is extremely demanding. I had both the Vive and Oculus CV1 since Day 1 and the drivers became more robust since the early days, but it's still far from a plug & play installation unless your system is fully compliant. The results with a fully optimized system are more than worth the investment in the end.
One caveat with the Oculus compatibility tool-- It will fail you for USB compatibility if even just one USB port/controller is unsupported. I had one older card in my system, and even though I didn't plug the Rift devices into it, the tool still complained and considered USB compatibility to be a failure, until I removed the card. I wanted to replace it with a better one anyway, otherwise I would have ignored the warning. Unless they've changed recently, the tool doesn't show enough granularity to tell you which of your USBs is considered incompatible.