Corrupted editor within one project only. V3.05-stable_win64

Question

Hi Everyone,

I have been working on a project for a number of months now and suddenly out of the blue as of yesterday I am getting a corrupted editor for this particular project only. This particular project loads and runs fine, I do think the project takes a little longer to load than the rest.
Project also shows empty in the editor, no asset paths, no node tree displayed etc.

All other projects load fine and run fine except this one, so something is going wrong with this particular project, I just have no idea what and how to fix it.
I suspect I might need to repair a file somewhere, anyone have any idea whats going on?

Comments

Are you sure that it doesn't just take longer to load the startup scene? For some bigger scenes of mine it takes quite a few seconds before the editor responds after starting it up. During that time it seems like the project is empty. What you could try to do is creating a backup and then deleting your .import folder, maybe something went wrong there.

---

Any errors being logged to the console window that starts with the editor on windows? if using linux then run the editor from a terminal and you should see the output there

Answer 1

Hi Everyone,
I figured out the problem, the editor was running out of memory.
I checked the console window as suggested by Squatnet and was getting the following error::
"Error: Message queue out of memory. Try increasing 'messagequeuesize_kb' in project settings"

I checked message queue size and doubled it from 1024kb to 2048kb and the project seems to be working now.

I'm not sure what editor functionality this relates to? however my project appears to be working now. The reason I didn't catch this first time round was that the console was constantly cycling this error message making it difficult to read, I had to screenshot it lol!

Is there anywhere that goes into depth with the project settings, memory allocations, inner workings etc? I think it would be a great help if we had documentation we could fall back on in order to diagnose problems like this.

i've attached a image of what I was getting for anyone curious about this problem.

Thanks to omggomb and squatnet for your suggestions, much appreciated.