|
When Unity hangs itself, there's no Debug.Log-output at all. Ist that because it doesn't get called or because it doesn't get drawn? The first option doesn't make too much sense, because if there are Debug-calls before the defective code, Unity can't possibly crash without calling those first. So that second option leads me to my question: When does the editor get drawn? Thanks & Greetz, Ky. Edit as a side-note:
(comments are locked)
|
|
Not really an answer on your question but although the editor often doesn't show the last few log messages, they still end up in the Editor log file on disk. To answer your question a bit, I assume the log console of Unity is synchronous like the rest of unity seems to be so it updates the displayed entries once every frame or so. So although the log entry can be added to the internal log list it isn't added to the visual representation of the console window, this probably is a separate datastructure to handle cleaning the log or culling the non-error entries at start of play and stuff. Of course this is pure guesswork and could be totally wrong. This is sorta correct. Trust the editorlog more than the consolewindow when you have Unity totally hanging
Jan 28 '10 at 08:53 AM
Lucas Meijer 1 ♦♦
thank you for this information. Sorry I never came back to accept... I was hoping, someone could provide a more complete answer (and then forgot about this question)... =/ Just one little question, before I accept: where do I find the Editor log on disk? ^^' Edit: Found the answer http://answers.unity3d.com/questions/9739/how-can-i-find-editor-log-file.html Thanks & Greetz, Ky.
Jul 13 '11 at 02:24 PM
SisterKy
(comments are locked)
|
