Slow, Laggy scene camera Unity 2019.x

Hello all,

For a while now (unity 2019.2,2019.3.x [Currently running 2019.3.8]) the scene camera is very laggy/slow and keeps moving long after I let go of the WASD buttons - even with small/basic scenes. I have tried so many things including:

• Change from DX11 to OpenGL Core
• restart many times
• Delete my graphics drivers using DDU and reinstalled
• countless new scenes
• turning off animated textures, sky, fog, etc
• changing graphics level to lower settings
• turning off GSync
• Changing display settings per other forum posts I've seen
• ensured nothing else was running such as Virus scanner, performance monitors, etc.
• Changing clipping distance for SceneCamera to 500
• Disabling PageFile
• Using Task Manager to close any programs that monitor hardware, virus scanners, and overclocking software
• Happens on both Intel XEON and Ryzen platforms
• Happens in Unity 2018.x aswell

I am so at a loss as to why this is happening and it is making unity useless to me. This has been going on for some time now, I have been to page 4 on google I even did the

Code (CSharp):

1. UnityEditor.EditorPrefs.SetBool("DeveloperMode", false);

thing I found, I checked the performance monitor and all it tells me is something about the camera updating (100+ MS).

Hardware:
GTX 1070ti overclocked
Ryzen 3900x overclocked
32GB 3200GHz Corsair Vengence ram
PNY SSD (512GB, 56% full)
850Watt Platinum PSU Corsair.

My hardware SHOULD be able to run unity just fine - I've even tried many fresh installs of Unity with and without unity hub...

Am I just SOL with an unfixable issue? Its so frustrating....

 

If you the far view distance for the Scene camera to something low (such as 1000m) does it get any better?

Also, when you have the project open, is there a very large difference between the amount of RAM in use and the committed amount? Windows could be over-using the pagefile, and then lagging when it retrieves data from it (I had this happen before with an older laptop). You can disable the pagefile if this is the issue, but it will cause programs to crash if you use more then 32GB RAM (unlikely when running Unity, but still possible).

 

Unity is using aprox. 5GBs of ram. Changing clipping distance to 1000m does not help at all.

 

There should be a camera button on the top right of the Scene tab, click it and it will show the scene camera settings.

 

I found it, but even setting it to 100m doesn't help.

 

Oh

Does it get better if you disable your pagefile? (instructions here) Since you have 32GB RAM disabling it shouldn't cause any problems.

 

Run profiler on the editor while moving around. Provide more detail about the results here.

 

When making changes in other UI elements, such as lighting, settings, browsing the Hierarchy it runs smoothly and quickly but as soon as I start moving the scene camera the frames/performance drops like a rock and the camera will keep moving sometimes as much as 10 seconds after letting go of any of the WASD buttons.

Disabling PageFile did not help, even after a reboot.

 

The issue is not present in an empty scene, but populating it with a plain, some trees, a small amount of grass and some rocks from a NM pack stars to cause the issue and the more I add the worse it gets. I was using after burner by MSI and I just disabled it to test, made no difference.

 

When in play mode or standalone build mode it runs perfectly fine. Good FPS and no lag/choppiness. I am in the default layout at the moment, so the Scene view and Game view are in separate tabs and not both visible at the same time but can be switch to them individually.

Graphics: CPU: Main 99ms Render Thread: 1.5ms
Batches 696
Tris: 1.8m Verts: 3.1M
SetPass calls: 119
Shadow Casters: 0
Animations: 0

on URP


I tried closing the game tab so it wasn't open, no change I also went into the Layers menu and hid all so there wasn't much in the scene and that also made no difference, still the same issue. This is beyond weird and so stressful. I do appreciate you all trying to help, I just ordered a NVMe m.2 PCIe Gen 4 drive so maybe that well help. I dunno, I am running out of options here and this doesn't seem to be a common issue so it could be anything..

 

No, just the one.

 

If I am in play mode, it runs buttery smooth, only and when I am messing with the Hierarchy, project view, etc it is fine. The lag only happens when I try to move the sceneview camera

 

Sadly, this has been happening since before Gaia. I'll check Aura as soon as I can.

 

Hi, just wanted to say we are having this issue in 2019.3.14f1 and are using Aura 2 as well. However I get this issue even with Aura Preview disabled.

 

Unfortunately it doesn't seem to be the issue on our side



It seems like any drop in performance will trigger this bug. The scene view isn't running any slower than previously in 2019.2, and there is barely a noticeable drop in performances when I move the scene camera. It's almost as if user inputs are being buffered faster than the FPS should allow, thus it keeps firing for a while after you let go. It does seem to get worse the lower the FPS, but I think this is a specific bug hidden somewhere and will always occur the moment performances drop for any reason.

Interestingly, another of our programmers has reported a very similar issue, only this time in the game itself! In one of our larger scenes, he says that keyboard and mouse inputs would keep firing long after being released and the player would keep moving. Surprisingly, using the gamepad instead of keyboard and mouse did not result in this issue. I have not tested this myself so I can only relay his experience, but I believe I noticed it as well in one of the lighter playground scenes I was working in where the player kept walking for half a second after letting go.

Perhaps this could be a bug in 2019.3 with the new Input System package version 1.0.0 which we are using? @POC0bob can you confirm whether you are using the new Input System as well? I'll try to see if I can reproduce the issue soon this week in a fresh project with a script designed specifically to lag up the editor.