Hey so I’ve had a really annoying issue since I guess 2018.3 and that is Unity will often freeze when either compiling or entering play mode. Which often has me having to End Process. Which obviously leads to losing work often enough. It doesn’t seem to be project specific. It happens on completely new projects when I’m just messing around with something. I’ve not been able to figure out if its a specific asset or anything like that. I don’t know if anything specific causes it to happen. The only thing I could think of is I made the switch from visual studio to jetbrains rider in around the time this started happening.
Has anyone else experienced this? or does anyone have any ideas on how I can diagnose the problem when it does lock. In the past I’d probably have tried to use the Panic Button on the asset store but since it doesn’t work with 2018 I’m having a hard time with figuring this one out. I’ve tried entering debugger when it happens but it doesn’t seem to like pausing.
may be your broken script? or may be really fault with jetbrains. try to create new test project and make something as simple like moving cube, then see if freezes, try to switch back to VS, and if it is still freezing try reinstalling Unity (prefer latest version)
i know i am posting very basic solution, thats where we should start
Yeah I agree with you. The best place to start is always with something simple. Not using Rider in favour of Visual Studio admitting is the one thing I haven’t really tried. Purely because of how annoying visual studio is when you have many asmdef files with the constant assembly reloads. I don’t think its to do with any of my scrips since it happened multiple times on a project I downloaded for Visual Effect Graph. I didn’t create any scripts there myself I just played around with it. Not suggesting it is Visual Effect Graph though since I don’t have that in my main project and the freezing still happens. That being said now that I think of it Rider wouldn’t have been setup to work on that project and it still happened.
Same, in 2018.3.11, I think it might be Rider triggering recompile (despite setting that to off) and Unity just losing it’s mind (it’s set to not compile until playmode is exited). I am using an older version of Rider though because i’m worried that moving my massive project to a newer version of Rider might create more problems than solutions, just like using later versions of Unity. Simple workaround is to stop play mode when going back to your IDE.
