Open Enverex opened 6 years ago
As usual, please attach a log with +esync,+server,+seh,+pid,+timestamp.
Log of +esync,+server,+seh,+pid,+timestamp attached. I killed it after a minute or two as it doesn't progress past that point.
Hmm, this is nontrivial to trace down. The application is spinning and doing d3d work up until the point where it's killed. If you can attach a log with the same channels and esync disabled, that may be helpful.
As requested. I left it on the menu for a few seconds (which is the part of the load process after the bit that gets stuck with ESync enabled). trace2.log.gz
Works fine without ESync, but never finishes loading on startup if ESync is enabled (the loading spinner just goes on forever).