While Oculus VR Runtime Service is running (in Windows Services), changing focus between Editor windows in any Unity project is followed by a 4-10 second freeze of all input. The sessions appear to be affected regardless size/complexity/version, as I tested on 3 different versions with 3 different active projects and 3 new empty projects (6 total tests)It seems to only be when you change between windows in the Unity Editor. If you stay in one window, it's able to run smoothly. Are there any solutions out there to this? It's as close to blocking as a blocker can be. It may also be related to the latest Windows 10 update, since I received both between sessions of Unity work.But, if I stop OVR Runtime Service, it works like a dream.Thanks for the help!

Yeah, replugging the sensors fixes that right up, but doesn't cure the Unity slowdown at all. I have been running the service about 7 hours now, and haven't seen the sensor issues today. Still got the slowdown though. My office has dubbed this "The Oculus Plague," and people are desperately fighting to prevent Oculus and Windows 10 from updating as much as possible, since 3 of us have caught it!I'm also on that same USB3.0 hub (FL).

Unity developer here.Yes, it is indeed USB related. Specifically, certain USB devices are far slower to enumerate than they should be. Normally this is a minor annoyance, and one that we're looking into fixing. But for some reason, with the 1.17 runtime update installed, we're getting Windows messages to re-enumerate USB devices whenever you click around from panel to panel in the Unity editor UI. This happens whether you have a headset plugged in or not, and with all recent versions of Unity whether you're working on a VR enabled project or not.Here's a link to the Unity forums discussing this issue in a bit more detail:https://forum.unity3d.com/threads/lag-when-switching-between-editor-windows.487352/#post-3181221

Okay, I've managed to solve it / work around it.Initially, I thought the HMD would only operate on a compatible USB 3.0 port, but on further reading it works fine on a USB 2.0 port. I left the sensors in the FL1100 card and plugged the HMD into the onboard USB 2.0, and now the problem is solved.If you're having the same problem on the same card, take your HMD off the FL1100 card and put it on your onboard 2.0 (with adequate power available..) and try it.This is the article that gave me the eurika moment: http://360rumors.com/2016/12/oculus-rift-and-touch-may-work-better.htmlThanks to everyone who chimed in and helped debug. To re-iterate, I think the problem is isolated to just instances where the HMD is running on an FL1100 chip..?

Same is happening for me.Have tried with multiple projects in various versions of Unity (5.6.3f1 and 5.6.1p1) and the same result of a few seconds pause when clicking from one Unity Editor view to another. For example after manipulating something in the Scene view, if I click on the Inspector view there will be a few seconds pause before Unity responds.If you look in the Windows Task Manager you can see the Unity process become "Not Responding" just before it recovers. Uninstall the Oculus software fixes the problem but make Oculus development a little tricky.

Unity Editor freezing on window-focus changes in OculusVR 1.17

43 Replies

Replies have been turned off for this discussion

cybereality
Grand Champion
8 years ago
Moving to Unity dev forum.
Massycat
Honored Guest
8 years ago
Same is happening for me.
Have tried with multiple projects in various versions of Unity (5.6.3f1 and 5.6.1p1) and the same result of a few seconds pause when clicking from one Unity Editor view to another. For example after manipulating something in the Scene view, if I click on the Inspector view there will be a few seconds pause before Unity responds.
If you look in the Windows Task Manager you can see the Unity process become "Not Responding" just before it recovers. Uninstall the Oculus software fixes the problem but make Oculus development a little tricky.
Massycat
Honored Guest
8 years ago
Current have Oculus app version 1.17.0.424527 (1.17.0.424315) installed.
jaconcha
Explorer
8 years ago
Not that this absolves Oculus Tech Support in any way, I think this may be Windows 10 Creators Update related. I got both at the same time, and other people at my studio are not experiencing the same issues with 1.17, but also haven't received the Windows update, yet.

I hope a fix for this is coming soon.
Anonymous
8 years ago
Posted on reddit regarding this, carlsagan79 requested some info to troubleshoot, no word since. Temporary workaround is to disable oculus runtime in Services, and edit in Unity. To
playback in unity, enable in services, wait couple mins, open oculus
desktop + play. Not great timewise, but works till hopefully patched by
oculus.
reddit posts
https://www.reddit.com/r/oculus/comments/6se0qb/unity_editor_freezing_after_rift_117_update/

https://www.reddit.com/r/oculus/comments/6sdf4c/oculus_rift_related_processes_have_started/
Clavus
Protege
8 years ago
Got the same issue, coincided with updating to the Oculus 1.17 update. Stopping OVRService is a temp fix for now.
rvpeterson
Explorer
8 years ago
Experiencing this same problem. Is there any fix other than stopping and starting the OVRService continiously?
catscratchjohnn
Honored Guest
8 years ago
I double posted by accident, but don't see a way to delete. So I'm editing the dupe to ask this question:

What USB controllers are people using?

I bought this new (Inateck/FrescoLogic) USB card because Oculus doesn't support the (Etron) USB controllers on my (Gigabyte) motherboard. The new card has worked fine for the past 6 months, until this update.

Anyone else using the same card or FL1100 series?
catscratchjohnn
Honored Guest
8 years ago
Same here. I've been re-installing everything trying to track this one down. Totally unusable on my home computer, though my work computer isn't affected. Stopping the Oculus VR Runtime Service stops the problem

Here is another (Unity) thread talking about it.
http://answers.unity3d.com/questions/1391741/unity-editor-severe-performance-delay-for-most-act.html

My home machine is using the following USB card and drivers

USB 3 PCI X Card (FL1100 chipset)
https://www.inateck.com/inateck-ktu3fr-5o2i-usb-3-0-pci-express-card.html?___SID=U

I can't do any VR development at home. Is there a way to rollback the runtime version?
rvpeterson
Explorer
8 years ago

imperativity said:

@rvpeterson

As posted above, this is an active issue that is being internally triaged at this time and a fix will be announced when this process has finished.

Of course, I appreciate that. I just wanted to know if anyone had perhaps found a 'hacky' workaround, instead of having to stop/start the OVRService continuously (pretty impractical for development).

catscratchjohnny said:

Same here. I've been re-installing everything trying to track this one down. Totally unusable on my home computer, though my work computer isn't affected. Stopping the Oculus VR Runtime Service stops the problem

I can't do any VR development at home. Is there a way to rollback the runtime version?

Thanks, that's saved me the bother of reinstalling everything - I'm so desperate I almost nuked my OS and started from scratch. Interesting that your work PC is fine.. Any ideas what might be different between your home and work PC?

Personally my set up is as follows:

Windows 10, using Oculus 1.17, Unity 2017.1, SteamVR SDK.
AMD FX-8320, Nvidia GTX 970 with 382.05 drivers
Also using the FL1100 chipset with 3.8.33709.0 driver

I'd also like to know if there's a way to rollback. Appreciate this isn't the solution Oculus want, but it's the solution we need right now to continue development.