It would appear that steam is not catching that Last Epoch is quitting a non-insignificant number of times on my system.
The fix is trivial, but lightly annoying - Task Manager, force quit steam, restart steam.
Let me know if you want me to do any testing, but so far I am sitting at 4 known instances, and I’ve only played a handful of days.
Hey. Welcome to the forums…
If the game stops abruptly (crash, apphang etc) or doesnt close correctly this can and does obviously happen. As the game is in beta these kind of things to happen fairly often unless you take certain steps to focus on game stability rather than eye-candy/pushing settings.
The key here is to find out why the game is ending without closing properly.
The player.log (and any error.log that might have been created in the crash folder) & dxdiag export (or Windows Event Viewer) will provide more information into the possible cause of this.
If you post these then maybe we can see what the underlying cause of the frequent crashes are.
Of course, when I get home from work this evening, I will append those to this post.
But for clarity, the client is not crashing. This happens nearly every time I finish my session, and close the game with “return to desktop” from the menu.
Its probably in the AppHang state which will not show the user any error but it would be in the dxdiag diagnostic section and hopefully the player.logs will have something that indicates what is happening…
Best case it could point to something simple like a gpu driver update… Worst case, the info could help the devs see what is causing the problem and add it to the list of things to fix…
LogPile.zip (44.7 KB)
As requested, here are the logs.
The problem is running about 80%+ of the client quits. So far, only one crash to desktop, but that was multiple sessions ago, after leaving the client running unattended for 8-12 hours.
Hey… Thanks for posting this information.
A few potential things come to mind when looking through your setup:
Your hardware is fine. Graphics Drivers & OS updates look fine.
Your dxdiag diagnostic is not showing any LE crashes - memory related or otherwise. It usually does if LE is having hassles… Seems like Audible is having hassles and there are some Windows Store updates that are not happening but nothing that I would consider serious or things that would neccessarily relate to LE.
You are using an ultrawide display resolution - this has occassionally caused some odd issues with LE in the past - nothing that I can confirm as a specific know problem but its something to remember when moving onto in-game settings.
The player.log is not showing any obvious crash notices (beyond some common debug info that I see in most peoples logs) but it is showing a few debug message that are not that common. Specifically “BoxColliders does not support negative scale or size.” and “Failed to create agent because it is not close enough to the NavMesh”. These seem to be related to specific maps that you have loaded so its unlikely that is a primary cause of the failure to close the game properly. This is something only the Devs are likely to be able to understand (or perhaps someone experienced in Unity development).
Your in-game settings. Now you are running decent hardware so these specs would logically be fine barring the fact that LE is in beta and is unoptimised when it comes to performance and stability. It may very well be that you need to dial back on some of these settings, even with your hardware, in favour of more stability. The one thing you MUST enable is the framerate limiting - if you do not do this, LE will max out your GPU for no apparent reason and the game gets very fishy when this happens for long enough. I have seen it max out a GPU while standing in town which makes zero sense. I recommend that people do one of two things - set the framerate limit to around what their monitor can handle AND/OR watch their GPU usage and use the limits to make sure that the GPU stays at a decent average usage while in town (say 60-70%) and leave some headroom for the GPU to handle the busy in-game play moments. (Obviously all of this is directly influenced by your quality settings & resolution).
Side note. Since your post, I have been watching my Steam processes while playing etc and have noticed that Steam doesnt always release processes of games (not just LE) immediately. I started and stops a few different games and noticed that I ended up with 3 or 4 steam processes that didnt shutdown after playing - they didnt hog resources but they didnt terminate on their own. Perhaps this is something that could be more to do with Steam than LE… An interesting thing would be for you to try the standalone LE launcher and see if it leaves the LE processes running like steam does.
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.