We've started rolling out the release of Rift SI 1.22. This week's updates include numerous performance and stability improvements for Oculus Home and Dash, see full notes below.
Additionally, effective today, everyone has access to our updated Oculus desktop app, and you can opt in to the Rift Core 2.0 beta even if you aren’t enrolled in the Public Test Channel. Click here for details. Please continue to share feedback and suggestions through our Rift Core UserVoice Group, and report bugs via the in-app reporting tool.
Changes
Oculus desktop app:
Multiple Library locations
Install and manage your VR apps for Oculus across more than one hard drive or Windows folder
Library detail panel:
View detailed information about your use of each app, including playtime hours and achievements
Graphics:
Added 8x MSAA support
Rift Core 2.0 (Beta):
Oculus Home:
Graphics settings now have their own section within the Options menu
Implemented a number of rendering and performance improvements
Fixed several interaction and/or graphical issues with various objects
Dash:
Fixed an issue with keyboard rendering when the primary display has a scale other than 100%
Improved performance when running apps acquired from outside the Oculus Store
Addressed several Oculus Desktop application compatibility issues
Introduced fixes for a number of hardware compatibility issues
Classic Home will be available for some period of time, but will eventually be phased out. I haven't heard of this specific multi-monitor issue, so I recommend you submit a bug report so we can look into it. You can submit the report in the Help Center (lower left of Oculus app) by clicking Provide Feedback. Thanks.
I'm also having dual monitor problems. I'll submit a bug report when I get home from work, but the gist of it is: Old version of Oculus Home - everything working fine. In Windows I have 2 monitors - one main (large) monitor, one secondary (smaller) monitor, configured as side by side. New version of Oculus Home installed. Looks good, so I flipped the switch for Dash to see what it was like. Immediately, in Windows, my small secondary monitor became the 'main' monitor and the mouse cursor will not move onto the other monitor (making it unusable). If I look at the layout of the monitors, either in Windows display settings or the Nvidia settings, they are shown as arranged diagonally (so there is no common edge to move the mouse across). I try re-arranging them manually, but the change won't stick. I tried setting the large monitor back to being the 'main' one, and that change won't stick either. Tried closing Oculus Home - no effect. Rebooted - no effect. Switched Home back to Classic - no effect. So, basically, the new Oculus Home has ruined my computer for all other uses. I really don't think that the software for a peripheral should take over my PC like this, with no way to control what it has done!
Mmmm, for the first time I catch bugs with Oculus Dash on my configuration (yeahn, guess I was lucky). I was on beta but didn't see them during the beta, only now with the final 1.22 installed. I'm running latest Nvidia drivers drivers so I'll try revert to recommended ones just in case. My machine, like many others, was Meldown/Spectre patched, fall creator, so many factors can be involved here.
For the record this happened yesterday and again this morning (PC shutdown in between) after running Oculus Home without even wearing the headset I sometimes lost the display of the Windows start menu, display of the volume when I click once in the headphone icon top right, same with my network icon, etc. All seems running, PC seems fine. It's like if those displays wasn't made in my main monitor (my only monitor) and appear in the virtual hidden one created by Dash. To fix that my only way is CTRL-ALT-DEL and disconnect/reconnect my username (the only one, I'm Admin alone on that machine). During this disconnect time Windows said a task still running it couldn't stop, something about host task etc. can't remember, so I have to force disconnect.
Edit for the record 29/01/2017 : After switching to NVidia drivers 388.71 I didn't catch any bug described above. Could be fixed.
“Dreams feel real while we are in them, it's only when we wake up that we realize something was strange.” - Dom Cobb
"Be careful, if you are killed in real life you die in VR too." - TD_4242
@cybereality I did the repair, so my app was on classic and everything worked. Flip the switch to Dash in settings, app restarted and the same crash. At least with another repair I can go back to classic and use the Rift.
@Agterbosch I play most of the days with different games, so far I never seen anything like this. Vr games most of the days. Just had a 24hour race in Iracing Vr (with teammates), no crash. I think it is not my GPU, and I hope; just check the current prices!
Yea it's crazy, thanks to the cryptomining.. But good to hear that was not the problem man (y)
So I’ve had another problem popping up with 1.22 besides the occasional black screens. If I let my PC idle with the Oculus app running, my PC sometimes shuts down. No BSOD, and nothing in the event viewer prior to the shutdown, just an error message about rebooting after not closing cleanly.
It never happens during gaming, and I stress-tested my system last night and didn’t get any problems with prolonged CPU load, GPU load, Memtest, OCCT PSU stress test, etc. It has happened with Nvidia drivers 390.65 and 388.71 (both clean installed), but only since 1.22 rolled out.
I suspect that it only happens when Home is open and the black screen issue is happening—I know that for at least two instances, it was after putting the headset down when the screens wouldn’t light up. Another couple times, it was after launching Oculus, but I hadn’t put the headset on yet. I don’t think it has happened after successfully using the Rift and then letting the PC sit with Home running.
I'm kind of stumped. I’ve been trying to troubleshoot this for a few days but I’m not getting anywhere. I’m open to suggestions if anyone has any ideas.
Edit: had a shutdown without Oculus running, so this seems to be unrelated to Core 2.0.
No, there hasn't been a Meltdown BIOS or firmware update yet from my motherboard manufacturer, so just the Windows update for that issue.
I'm done with video driver testing, since I'm seeing exactly the same issues with both 390.65 and 388.71. I think my next avenue of testing will be turning off Home 2.0 while keeping Oculus 1.22, because my gut tells me that it's something to do with the extra virtual monitor that activates when Home/Dash is running. If I can go through ten or so boot cycles without seeing black screens or the shutdown problem with Classic Home, then that will narrow it down to Home 2.0.
I hope the new Dash version will have good support for the XBox controler. At this moment the use with the XBox controler is very coarse and I remember that the Rift was sold initially without the Touch and as I will certainly be more users who have no interest in acquiring the Touch so the base software support must take into account the interests of owners who only have XBox controler. Thanks.
