Fatal Error!
GetManagerFromContext: pointer to object of manager ‘RenderSettings’ is NULL (table index 18) UnityEditor.DockArea:OnGui()
After clicking OK, Unity crashes and brings up the error report window, if anyone else has had this problem, please help me fix it, I cant work on anything at the moment.
It looks to me like something within your Unity build got corrupted.
I’d recommend simply re-installing the editor. This will guarantee that your installation is working.
That was the first thing I tried, complete wipe and re-install, I have checked to make sure it left nothing behind and reinstalled, it was working fine yesterday, and now today I cannot open up my project, I can open a previous one but not my latest one. It is strange because an exact copy of my latest project will open up no problem through my laptop with the same version of Unity, but not on my desktop, and most of my work is done on my main desktop, it has all of the modelling and texturing programs I need and its a pain to keep having to transfer stuff between machines every time I make or change something.
I can start unity but when I try to load a particular scene in my project it always crashes.
The first time I was trying the 4.6 version, so I thougt it was a bug. I’ve install the 4.5.3f3 but it crashes too.
I have even tried with a previous one version of my project but it always crashes.
Hi, Catena,
Short answer, No, but we did manage to find a workaround, What has happened is your scene has become corrupted, forcing Unity to attempt to load some heavy code that doesn’t exist, causing it to crash.
Me and my team now make duplicates of our scenes when they are working to make sure this doesnt happen, it has happened 3 times today where the original has caused this crash, and so we load from the backup scene, I have found no way to recover the scenes and it is very annoying, we didnt have this problem until now, and all of a sudden, it happens 5 times, I think we have both stumbled onto a little glitch in Unity 4, something that I hope will be gone in both the 4.6 Beta and 5.
Good luck, sorry I wouldn’t be of greater help, and remember, Back up your scenes!
We’ve all been there. I once lost a scene I was working on for a very long time due to Unity randomly crashing and the scene getting corrupted.
All I can say is save often, consider backing up your files, and hope this doesn’t happen again!
I am getting this same problem. Is anyone else using procedural materials (sbar) in the scenes in question? It seems like this could be the link for me.
Guys, I’ve downloaded Unity 4.6 BETA 17 & 18 and both still has this issue… Is there any way we can get a patch for these? Or maybe like a patched DLL. I desperately want to finish my GUI code and still use procedural materials. Seems like such an odd choice I have to make?
There are no patches for the beta release, all the patches are rolled into a public release, the next one being on Thursday 11th of September (if all goes well in QA). So this public release will be rolled into the next 4.6 Beta.
Fatal Error!
GetManagerFromContext: pointer to object of manager ‘(null)’ is NULL (table index 5)
This at the load project wizard at start up. Don’t ever get a chance to load a project. Or use the bug reporter.
Yes I’ve tried clean re-install etc.
The only work around is if I delete my licence file and go through the online registration process. That gives me one session of using Unity. However as soon as I quit Unity same issue.
I’ve been having the same issue as thylaxene throughout all of the Unity 5 betas, its very time consuming to deal with this. I’ve had this very issue for v5 beta 12 & 13 chronically. Has anyone found a fix?
No fix as of yet, the problem is the scene defaulted to load when Unity starts up (the last scene saved) is corrupted.
I have found that the most prominent cause of this to be the use of procedurally generated materials (sbars), the kinds of materials supplied by Allegorithmic.
However this is not conclusive, but rather appears to be a constant when replicating the problem.
As for the Unity5 beta, it also appears to be a scene or project corruption, possibly occurring somewhere in conversion from a previous version, or simply as a result of something like procedural materials again, or none of the above.
We have had to completely rebuild that scene from scratch without those materials, for now its best to stick to textures made by yourselves, or regular textures created by someone else, stay away from procedural materials for now until this if fixed, we have been looking for a fix to this for a while now, I think its just best to start from scratch with those scenes, we have not found any way to recover or restore these scenes, even by deleting the materials from the project, but we are still looking.
I got this with 5.1 today, and in my case it happened right when Unity launched (so before showing the project list, not loading a project).
It seems that my case was related with Unity checking for updates, so to get around it I turned off network, opened unity, open the project and only then turn network back on.