I get really strange choppy editor experience when testing the game, and a little bit in general. While I realise that running the game in editor is going to be worse than standalone, my machine isn’t a slouch and it has a definite pattern to it-
If I’m inspecting an item that is actively moving/etc it will be choppy in a weird fashion. It’s like it’s running at ‘60frames in one second, but followed by a quarter second of no frame.’ So it will move smoothly and then stop.
It’s definitely editor+(hardware specific?) related, like if something is being inspected or if items are being created or destroyed (hierarchy).
For what it’s worth my machine is a - Phenom || six core 1100t black edition.
8gb
Geforce GT440 1gb factory overclocked.
It is a 64bit version of windows 7 home.
Not going to win any ‘legendary’ awards but definitely not slow. One reason I think the machine IS important is my wife’s rig (which is a mirror) has a similar issue. Any help?
I've had similar issues, actually- I'm still tracking them down though. It's definitely something that can happen.
– syclamothYou might check if it matters which object(s) you're inspecting? It could be that there's a particular component inspector in the mix that's causing the slowdown -- could be requiring a lot of CPU power, or taking enough memory to force swapping, or performing some blocking operation on the main thread. Various bits of the editor can cause slowdowns. I don't think I've seen anything quite like what you're mentioning on a regular basis, yet, though.
– rutterI experience a similar pattern too. I haven't been able to pinpoint the source but restarting Unity usually solves the problem for a while. I suspect its memory-related but what do I know?
– by0log1cYou're not using a while() statement are you? I find these really drag down performance.
– IndieScapeGames