The problem of crash rollback when ets2 is upgraded to version 1.46 [MOD]

[GSS_SEU]

How to remove post?

[Reinhard]

As this is the only open, not-locked threads of the 3 topics you started I put it here:

No, nobody gave you a suggestion how to solve it, suggestions were just about to get rid of those thousands of warnings which made the log unreadable.

This you achieved in the log you send me via PM, you didn't read my answer yet. Please share this log link in this thread, don't open another topic.

Here is my answer I gave to you already privately:

This is the end of your log:

Code: Select all

00:04:25.741 : <ERROR> [gfx] Failed to assign pool segment (models) for incoming allocation of size 91228
00:04:25.741 : <ERROR> [gfx] Failed to assign pool segment (models) for incoming allocation of size 282312
00:04:25.741 : <ERROR> [gfx] Failed to assign pool segment (models) for incoming allocation of size 38596
00:04:25.741 : <ERROR> [gfx] Failed to assign pool segment (models) for incoming allocation of size 5468
00:04:25.741 : <ERROR> [gfx] Failed to assign pool segment (models) for incoming allocation of size 12764
00:04:25.741 : <ERROR> [gfx] Failed to assign pool segment (models) for incoming allocation of size 2992
00:04:25.741 : <ERROR> [gfx] Failed to assign pool segment (models) for incoming allocation of size 488880
00:04:25.741 : <ERROR> [gfx] Failed to assign pool segment (models) for incoming allocation of size 93584
00:04:25.741 : <ERROR> [gfx] Failed to assign pool segment (models) for incoming allocation of size 4464
00:04:25.741 : <ERROR> [gfx] Failed to assign pool segment (models) for incoming allocation of size 827424
00:04:26.490 : <ERROR> d:\buildbot\slaves\win_slave\final_build_ets2_oculus_windows_bin_steam_x64\build\prism\src\p3core\collections\arrays\arrays_base_impl.h(491): ??A?$array_t@Ur_buffer_segment_t@prism@@@prism@@QEAAAEAUr_buffer_segment_t@1@_K@Z: Index outside array boundaries.

Looks like you run out of graphics RAM. But I can't tell you why.

So maybe another one can tell you more if you share that log.

But anyway, one solution would be to disable some of your mods, one by one, and check for the result. I'm convinced this is a mod problem, because the unmodded 1.46 game has no memory problem.