For perhaps 10 days now, I have experienced seemingly countless crashes while I work in the editor. Whether I am saving, creating, deleting, playing…it doesn’t matter. I enabled the debug logging, but it isn’t working. Each time a crash occurs, I receive the message that I don’t have debug logging enabled, when you can clearly see, in the upper left of the launcher, the words ‘Debug Logging Enabled’. Thus, I cannot provide a crash log of any kind to help clear this problem from my system.
I am the design lead on an open-world project that is close to alpha. If I can’t do my work without these constant crashes, our project is going to meet a very sad end. I would very much appreciate the assistance of Epic’s support staff in this matter.
Thank you,
Hello ,
If the crash reporter window is not giving you a call stack, that isn’t related to “debug logging”, it’s related to if you have the Editor Symbols for Debugging installed. You can install these through the Launcher by clicking on the Library tab, then clicking on the down arrow beside the “Launch” button for the engine version you’re using, then selecting “Options”. This will bring up a list of optional things to have installed and Editor Symbols for Debugging should be listed there. Please check the box and press Apply. It will begin downloading the symbols.
After that is done, please reproduce the crash and copy the callstack information here (Please copy/paste or put it into a text file instead of providing a screenshot).
Also, please provide the logs from your project. They can be found under the Saved/Logs folder in the project’s directory.
Forgot call stack…link text
Thank you for the logs. From looking at them, this seems to be a graphics related issue. Due to this, it could be related to your hardware or current graphics driver. Could you provide your dxdiag information? This is the line that lead me to that conclusion, due to the mention of D3D11 (Direct X 11):
Assertion failed: 0 [File:D:\Build++UE4+Release-4.14+Compile\Sync\Engine\Source\Runtime\Windows\D3D11RHI\Private\D3D11Query.cpp] [Line: 82]
Hm, I don’t see anything that stands out in the dxdiag. I do see in the log that this project is connected to perforce and it’s attempting to run some Perforce processes but can’t connect. I wonder if that failure is messing with the shader compiling that is spamming the log as well. Can you try make a copy of the project, opening the copy and disabling the Perforce source control for it and see if you still run into this issue?
The latest crash info
link text
Here is the call stack from the clone, which seemed to fair no better than the original. However, 3 of the crashes this evening were actually the computer simply freezing up, and requiring a reboot of the system. Most of the crashes seem to occur during the ‘compiling shaders’ part of the loading of the tile. Each time I start things up, there are fewer shaders to compile until I finally get them all, and can get on the map. Once in, though, crashes will happen at random moments while doing random things - click of the mouse, or click and drag, keystrokes, camera rotation
link text
Hello ,
I apologize for the delay but are you still experiencing this issue?