Oculus Setup [apparently] ran without issue and installed everything.
Double clicked the Oculus icon, nothing happens. Right click and hit "Run as administrator" nothing. No runtime errors, no popups at all. I've repaired the installation, I've reinstalled, and I've restarted my computer.
Hmm I haven't tried SteamVR, I'll give that a crack.
I noticed some stuff about drivers for things I don't use any more in one of the diagnostic logs and so I went through and cleaned out old AMD drivers (I used to have a R9270x before my GTX970), and some other old ones with pnputil and ran through the installer again. No joy 😞
Edit: Exact same experience. Calibration appears to work in Steam VR, head tracking works, but no display.
Same service errors with headset plugged in: [Service_2016-03-31_18.24.19.txt] 18:31:04.231 {!ERROR!} [OAF ERROR] LifeCycle\LifeCycleAppTracker.cpp(123) : App exited unexpectedly: oculus-client (1971039) [Service_2016-03-31_18.24.19.txt] 18:31:05.793 {!ERROR!} [OAF ERROR] os\file.cpp(593) : The parameter is incorrect.: (1971052) [Service_2016-03-31_18.24.19.txt] 18:31:05.793 {!ERROR!} [ApplicationPackage] WaitForProcess failed: The parameter is incorrect.: (1971052) [Service_2016-03-31_18.24.19.txt] 18:31:05.793 {!ERROR!} [OAF ERROR] LifeCycle\LifeCycleAppTracker.cpp(123) : App exited unexpectedly: oculus-client (1971039) [Service_2016-03-31_18.24.19.txt] 18:33:08.987 {!ERROR!} [HW:Health] [HMD::setLEDMode] Failed to match trackingSettings.
As a last ditch I did a full uninstall, deleted all the Oculus related folders from program files and appdata and did a reinstall using a freshly downloaded copy of the installer and still no joy 😞
If anyone else has this issue and is looking for more information I've also created a post on the Oculus subreddit to see if anyone over there has experienced this issue previously and has any ideas of a fix.
@MagnusFurcifer can you look at logs at C:\Users\<you>\AppData\Roaming\Oculus\OculusClientError-*.txt and maybe upload a few? It sounds like the client is launching, is connecting to the service, but is then crashing quickly.
I ended up rebuilding my rig with Windows 10 and now everything is working fine 😞
I guess that confirms it is something related to computer and not the HMD. I wonder if there is a dependancy on a kb that pro/enterprise 8.1 doesn't get?
Ha ha, I resorted to the nuclear option last night too. A clean install of Win10 solved my problem 😐 . Not the resolution I was hoping for, but after I get everything else moved over and installed I can finally move on with my life.