I am a student using Unity for a research project since a very long time and recently some new kind of problem has been occurring in which after the game is quit, the opening scene suddenly shows ‘no display cameras’ and then the following dialogue box(find attached) shows up after which the whole project just gets deleted. This has happened for the fifth time when the project was lost and it has happened for the tenth or eleventh time that Unity quit unexpectedly. I have reported this issue several times but I never received any sort of intimation from your side. Kindly look into this matter because I have been a very old user of Unity. I have the latest version for both Unity and MonoDevelop.
I’m not able to find any known issues of this happening in the wild other than your report here. It’s difficult to say what exactly is causing this, but one of your bug reports shows a suspicious IOException right before the crash.
This leads me to believe that you have some code in your project that is interacting directly with the file system (through System.IO). It seems quite likely that this code is changing the current working directory of the Unity process somewhere, which will lead to Unity breaking.
First of all, thank you for looking into this matter. That is quite true. I was fixing an IO error and a runtime error occurred which was the case many times before as well but at one particular attempt, the project crashed. On my part, I did not attempt changing the working directory from my code.
Unlikely, you’re free to manipulate files in the project folder with System.IO all you want (that’s basically what IDEs do themselves).
I’m really not sure what would’ve caused the CWD to change in the first place. I skimmed your project and I couldn’t find anything that would cause a problem. If you find out anymore information, I’d be happy to hear.
