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.
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.
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.
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 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.