If you do a bunch of notes and map markings, at some point chosing any option of either writing note, selecting marking or deciding to erase something, game crashes. The main condition is that dedicated render has to be turned off. It happens sooner if game runs at 165 FPS in map than if locked at 60. Haven't tested in full vanilla so likely secondary condition is to have such map mods like additional map marking, scale slider, drawing etc. Error message is regarding some sort of memory or array overflow. If you need exact log data, I would glad to replicate crash to sent you log. While this bug is likely is on mods part, crash itself happens because of something in rendering when dedicated UI rendering isn't used what is interesting.
#Game crashes if you have too many map interactions
10 messages · Page 1 of 1 (latest)
What are you referring to by "dedicated render" ?
Apparently in English it is called "UI Offscreen Rendering".
By default it is turned on.
I see, are you able to replicate this in a vanilla game as well in that case?
Since we could not really mark it as a bug otherwise
I'll try tomorrow in fully vanilla game but I'm pretty sure it will take much longer, or maybe not.
I decided to try and replicate anyway. It seems that it isn't an issue in vanilla or it requires some sort of critical mass of already existing notes and markings. While I understand that bug was likely caused by mods it is still interesting that it happens. I found logs from the time I had this bug and before I turned offscreen rendering back, error message is just two lines:
[06-06-23 15:04:02.339] ERROR: General , 1686053042333> 1 790 733 405> GameWindow.uncaughtException> Unhandled java.lang.OutOfMemoryError thrown by thread MainThread..
[06-06-23 15:04:02.346] ERROR: General , 1686053042346> 1 790 733 412> ExceptionLogger.logException> Exception thrown java.lang.OutOfMemoryError: Java heap space at TByteArrayList.ensureCapacity line:186. Message: Unhandled java.lang.OutOfMemoryError thrown by thread MainThread..
Sorry if wasted time
That just seems like Java ran out of memory, which generally should not happen unless a lot of things go wrong