Terasology icon indicating copy to clipboard operation
Terasology copied to clipboard

Crash/Bug on trying to generate a world with josharias Survival

Open Irgendwer01 opened this issue 3 years ago • 4 comments

General Info

Terasology Launcher Version: 4.5.0 Terasology Version: 5.2.0 Operating System: Opensuse Leap 15.3 Onboard / Dedicated Graphics: Intel Graphics 3000 Java Version: installed on system: 11, shipped with launcher: 11

What you were trying to do

Generating a world with josharias Survival

What actually happened

Crashed

How to reproduce

  1. Select Terasology version 5.4.00
  2. Start Terasology
  3. Select gameplay josharias Survival
  4. Start game
  5. See error

Log details

https://pastebin.com/YGK9aj5a

Irgendwer01 avatar Dec 29 '21 23:12 Irgendwer01

Getting this updated with a note from Discord: this does not seem to happen with the latest Omega dist from Jenkins at the moment (not yet available by default in the launcher) - https://jenkins.terasology.io/teraorg/job/Terasology/job/Omega/job/develop/418/artifact/distros/omega/build/distributions/TerasologyOmega.zip

So in theory by the time we do the next release / launcher pre-release this issue should be resolved :-)

Cervator avatar Jan 01 '22 04:01 Cervator

This seems like a sporadic issue I've been experiencing once every while for the past year or so... Not sure, but I think I first saw it at some point after the JOML migration (which resulted in a bunch of out of bounds / off-by-one issues in general)...

@Irgendwer01 were you able to reliably reproduce it or did it only appear sporadically for you, too?

jdrueckert avatar Jan 07 '22 17:01 jdrueckert

I just ran into this with world the following world seed: ZH09EM8nkPwOc9Fy

18:40:26.838 [main] ERROR o.t.engine.core.modes.StateLoading - Error while loading org.terasology.engine.core.modes.loadProcesses.SetupLocalPlayer@6046dbf9
java.lang.IllegalArgumentException: Out of bounds: (-33, -33) for region BlockArea[(-30, -30)...(30, 30)]

skaldarnar avatar Jan 17 '22 17:01 skaldarnar

@jdrueckert Sorry for the late response, no I wasn't able to reproduce it, it happened me for a bit of time then the issue just was away in all versions

Irgendwer01 avatar Jan 29 '22 10:01 Irgendwer01