Lag when switching between editor windows

Up until yesterday Unity was working fine, but now there is about a 6-8 second wait when switching windows for me to be able to then interact with objects within that window. For instance, say I've just done something in the inspector and click the scene view. I click, wait 8 seconds then have full, lag free use of the scene view. But then have to repeat that process when clicking onto another editor window.

This is the same for all projects no matter what version of Unity. After looking online I've tried the following
- Forcing opengl
- Updating drivers
- Switching to DX9 in player settings

All to no avail, so I'm open to any suggestions as to how I might get around this problem. Again I've never experienced this issue until yesterday, no errors, no warnings. Created new projects, same problem. Nothing out of the ordinary in Task Manager either.

 

Thank god, I am not alone! I have ben working with unity every single for over a year and it has just started doing this for me too.

Same problems, when changing focus to different parts of the editor there is a complete UI freeze for 6-10 seconds. The UI becomes completely unresponsive. It happens when changing focus to different window groups ie.: (with the default layout) Scene, Game and Asset store are one group, Hierarchy another, Project and Consoles are a group and Inspector is the final group.

Switching between items within a group doesnt cause any issue but the minute you click another group there is a delay were even the group you were just woring into is frozen. Clicking the File/Edit/etc menu does not cause a freeze but does become unresponsive when the UI is frozen.

I have tried:
-Complete uninstall of Unity, Visual Studio and Mono Develop. Including all folders (installation, temp, appdata, etc..), registries have been cleaned and whatever plugins each of them may have had were uninstalled.
-Installed windows updates
-Did a full virus scan including a scan from a rescue disc
-Ran a defrag on all drives
-Updated video drivers from AMD
-Disabled my onboard intel display adapter
-Tried forcing opengl and a different directx level
-I tried Analyzing the wait chain which shows 3 unity.exe proceses and it says: One or more threads of Unity.exe are waiting to finish network I/O but nothing specific shows up during the freezes.

Reinstalled the latest unity version, created a new empty project and BAM same problem.

Its unworkable. I have not been able to do a single bit of usefull work in unity for several days.

PLEASE HELP!

And before someone suggest reinstalling windows, everything else is working fine: Blender, Max, Photoshop, all my games NO HICCUPS anywhere. Even Unity works great as long as I don't switch window group within the app.

It's a really weird problem.

 

Thank you so much for that post. I do have an oculus, i'll run some tests and update if I find a workaround.
If you would like me to try anything on my system let me know.

 

For fox sake ... I was close to reinstalling the whole system today. Tried everything, including clean reinstall of all drivers, Unity versions and so on ... I would have never figured out that was Oculus/USB issue. For me it wasn't only switching windows, but it was practically every operation inside Editor ... right click... wait 5 seconds ... move cursor ... wait 5 seconds ...

If this helps some specs:
Windows 10, latest Nvidia drivers, Unity 5.6 and 2017 both behaving like this and YES! killing the Oculus process did fix the issue.

 

On my side I think the issue started when I added a 3rd oculus camera/sensor (with usb extender cable).
I kept it plugged in but I stopped all oculus related processes on my pc and Unity ran fine.
Thanks for the tip!

 

Yes, this problem must have started right when 1.17 was pushed, it makes so much sense in hindsight. I already had a third sensor plugged in -- but I did buy wireless USB headphones. Do you think opting in the Oculus beta build has any promise or are they not necessarily working on fix with you guys?
Thank you so much for your response.

 

Thanks for replying! So for me it was the oculus service. Stopped that and Unity was back to normal!

 

THANK YOU! As someone developing a VR Game, I was going crazy over this. Tried everthing, including reinstalling windows and http://answers.unity3d.com/questions/1393232/unity-editor-freezes-not-responsive.html . But nothing worked. Did not think of the USB devices. The offending device for me is my keyboard. Well, I was planning on replacing it anyway...

 

Hello, just checking in from the Oculus forum (I'm "rvpeterson" over there). Is there any status on the fix for this? I know it's probably not 100% Unity's fault, but it's seriously slowing VR development down, and pretty unworkable right now.

Cheers,

 

I began having this issue after the 1.17 Oculus update, and I had both the HMD and sensor attached to the FL1100 USB 3.0 card. I was using Unity with the Oculus service stopped in order to continue using Unity. After seeing @FarmerBilly's solution over on the Oculus board, I moved my HMD from the FL1100 USB 3.0 to a USB 3.0 controlled by my motherboard. Unity is now working for me with the Oculus service running. Thanks to all for the info here!

 

Thanks for the explanation! This issue almost brought me to tears. Turned out it was a conflict with a FiiO USB headphone amp in my case. Unplugging it solved the problem, and stopping the service worked as well (but kinda useless for working on a VR project).

At first I thought it was just a problem with 2017.1 since I updated at the same time I ran into this problem. Good grief, what a headache.

I may try the Oculus beta build to see if that fixes the issue altogether.

 

I have the 3 sensor oculus sensor setup for room scale VR. The 3rd sensor was plugged into a USB2 port. Moving the 3rd sensor to a USB3 port solved the issue for me. I have been working in Unity now for 2 days since the move. So far so good. I never quite understood why Oculus recommended 2 sensors to be on USB3 and the 3rd can be on USB2. Perhaps all three sensors should be on USB3. Motherboard is an MSI Z270 SLI. I had this problem on both Unity 5.6.2 and 2017.1 by the way.

 

Well after a couple more days. It seems I am back to getting lag. Does not seem as bad, but it has clearly come up. I might unplug the 3rd sensor all together and see what happens.

 

Below is a link to the fix i used and it worked for me, hope it helps others here. I had this issue on different version of unity from 5.6 to 2017
https://forums.oculus.com/developer...g-on-window-focus-changes-in-oculusvr-1-17/p2

I moved my HMD USB 3.0 from the FL1100 (3.8.33709.0) to a USB 3.0 on my motherboard, and that solved it. My 2 sensors are on the FL1100 USB 3.0 and my HMD is on the ASRock motherboard USB 3.0, Unity is working fine now.

I had Oculus USB issues for over a year now my sensors connect disconnect randomly i tried all the fixes i found (power bios and other settings) got the recommended USB 3.0 PCI it had 3 things plug into it and still i get a disconnect and quick reconnect. Now i have only the 2 sensors on the dedicated PCI card due to the OVRService and unity issues.

 

after the newest Oculus Update 1.18 Unity crashes when I hit play.

Unity Editor [version: Unity 2017.2.0b2_a9976befbe0f]

Unity.exe caused an Access Violation (0xc0000005)
in module Unity.exe at 0033:406f3da7.

Error occurred at 2017-09-11_231014.
C:\Program Files\Unity 2017.2.0b2\Editor\Unity.exe, run by Dev.
62% memory in use.
12232 MB physical memory [4578 MB free].
24520 MB paging file [13218 MB free].
134217728 MB user address space [134212694 MB free].
Read from location 00000110 caused an access violation.

Context:
RDI: 0x005fb178 RSI: 0x00000000 RAX: 0x63dfe960
RBX: 0x00000000 RCX: 0x00000000 RDX: 0x005fb178
RIP: 0x406f3da7 RBP: 0x005fb1b0 SegCs: 0x00000033
EFlags: 0x00010202 RSP: 0x005fb0d0 SegSs: 0x0000002b
R8: 0x00000000 R9: 0x00000000 R10: 0x00000001
R11: 0x63dfe960 R12: 0x00000005 R13: 0x05560990
R14: 0x38614cf8 R15: 0x00000004

Bytes at CS:EIP:
48 8b 81 10 01 00 00 48 85 c0 74 65 8b 40 18 83



Module 1
C:\Program Files\Unity 2017.2.0b2\Editor\OpenRL_pthread.dll
Image Base: 0x80000000 Image Size: 0x0000f000
File Size: 42496 File Time: 2017-07-03_175346
Version:
Company: Open Source Software community LGPL
Product: POSIX Threads for Windows LPGL
FileDesc: MS C 32 bit
FileVer: 2.9.0.0
ProdVer: 2.9.0.0

Module 2
C:\Program Files\Unity 2017.2.0b2\Editor\OpenRL.dll
Image Base: 0x80000000 Image Size: 0x00c30000
File Size: 12654592 File Time: 2017-07-03_175346
Version:
Company: Imagination Technologies, Inc.
Product: OpenRL™
FileDesc: OpenRL™ Library
FileVer: 1.5.100.0
ProdVer: 1.5.100.0

Module 3
C:\WINDOWS\SYSTEM32\xinput1_3.dll
Image Base: 0x00400000 Image Size: 0x0001e000
File Size: 107368 File Time: 2007-04-04_185422
Version:
Company: Microsoft Corporation
Product: Microsoft® DirectX for Windows®
FileDesc: Microsoft Common Controller API
FileVer: 9.18.944.0
ProdVer: 9.18.944.0

Module 4
c:\program files\nvidia corporation\nvstreamsrv\detoured.dll
Image Base: 0x0f000000 Image Size: 0x00006000
File Size: 18880 File Time: 2017-08-18_063614
Version:
Company:
Product:
FileDesc:
FileVer: 0.0.0.0
ProdVer: 0.0.0.0

Module 5
C:\WINDOWS\SYSTEM32\MSVCR100.dll
Image Base: 0x5fe00000 Image Size: 0x000d2000
File Size: 829264 File Time: 2011-06-11_011538
Version:
Company: Microsoft Corporation
Product: Microsoft® Visual Studio® 2010
FileDesc: Microsoft® C Runtime Library
FileVer: 10.0.40219.325
ProdVer: 10.0.40219.325

Module 6
C:\WINDOWS\SYSTEM32\MSVCP100.dll
Image Base: 0x5fee0000 Image Size: 0x00098000
File Size: 608080 File Time: 2011-06-11_011538
Version:
Company: Microsoft Corporation
Product: Microsoft® Visual Studio® 2010
FileDesc: Microsoft® C Runtime Library
FileVer: 10.0.40219.325
ProdVer: 10.0.40219.325


== [end of error.log] ==

 

just another heads up, I have this problem as well on OSX, and logging out of my account in Unity editor solve the issues for me.

here is the reference source
https://answers.unity.com/questions/1421084/unity-editor-stuttering.html

one downside is that you can't enable Unity services anymore but that's not an issue with me since there is better alternative

 

Is this still an issue? I am getting the "wait chain waiting for network i/o" issue and I happen to have an oculus. It seems to happen whenever I leave Unity alone for a while to alt tab or something. I am currently using 3.0f3. I don't have my oculus plugged in, but the OSVR service and whatnot were still running up until just a few minutes ago.

I disabled them all after seeing this thread.

 

Hi, I'm also still seeing this issue in 2017.4.3f1. I've disabled oculus processes but I'm still getting heavy stuttering just navigating the scene view. It goes back to normal once it's loaded the whole scene. Typically this behavior occurs right after making a build. Could that be it?

 

Mine was a mix and match of the running "Nvidia Containers" that showed up when starting a game along with the overlay, Windows Defenders "Realtime Protection" needing to be turned off, as well as the Oculus stuff. After having handled those I have not had a single performance issue since my post up there.

 

Hi, has there been any progress or solution on this? Having Oculus service running still freezes Unity editor window for about 5 seconds every time you focus it. That makes it very painful when going back and forth between Unity and IDE.

Manually stopping Oculus service does help, however that's not really a solution.

 

Bump! Still having this problem in 2019.1

 

And I have the same problem too. 2019.1.6f1

 

Any updates on this? its been happening for years now. Really annoying to be constantly waiting for unity to respond, sometimes up to several minutes for a single click

 

workaround:
Disable Auto Refresh in the preference. Use Ctrl+R to refresh manually.

 

Hello dears,

Got the same issue as everybody else on this thread, and nothing really worked for me.
Windows 10, working on Oculus Quest and Unity 2019.2.12.f1