koobas.hobune.stream
Unity 5 _ Game freezes on play when any script is added to the project.
I've been using Unity for a few years now, and when i downloaded Unity 5 and tried to add even the simplest script, the play button freezes the program and necessitates a force quit. When i try to reopen that same project, the project doesn't even open, it just stops at Compiling Scripts (50% done).
I've read about this happening to lots of people, but no answer as to why this is happening. Any help would be greatly appreciated, as Unity is now unusable until I can figure this out.
I'm having the same exact issue here. Other help threads indicate there's a popup hidden in the background, but I've checked as many ways as possible, and there is none.
Question: Do you have a mono process running in the background chewing up a whole processor or two when play or Compiling Scripts hangs? If so, does it stay after you close down unity until you kill the process directly? I'm assu$$anonymous$$g this process is related to $$anonymous$$onoDevelop tools for compiling unity scripts. Every time Unity freezes on scripts, a new instance of this process rears its ugly head.
All projects that were working for me just last week will freeze on script compiling now. Project versions freshly downloaded from repositories that have not changed since this problem began are having the same issue, so it can't be project file related.
I've tried uninstalling and reinstalling Unity, deleting Unity preferences, clearing pram, no luck. I did the same last week when the problem first arose, and despite no luck on any of those steps, Unity script compiling worked again briefly after I created a new project and moved files from another project into it.
After that, ALL projects worked... for a couple days, and now the same freezes are back. I tried all the same steps to solve the problem again (reinstalling, clearing pram, etc INCLUDING transferring to new project.) Nothing's worked. And even a new project with a fresh install of Unity will freeze on adding a single new default monobehaviour script.
This is a really nasty bug, and it grinds work entirely to a halt. I hope someone has a suggestion for this I haven't seen.
