Page 1 of 1

[0.16.4]Broken map gen at x -22000

Posted: Mon Dec 18, 2017 4:07 pm
by Bilka
I travelled to x -22000 and y 13000 only to be met with broken map gen: Image.
The map was created in 0.16.4 and never opened in another version. Here is the save: https://drive.google.com/file/d/1W65xtA ... sp=sharing . Player Bilka is in the spot where the map gen is obviously broken.

Re: [0.16.4]Broken map gen at x -22000

Posted: Mon Dec 18, 2017 8:24 pm
by orzelek
You were to curious? ;)

Re: [0.16.4]Broken map gen at x -22000

Posted: Mon Dec 18, 2017 10:39 pm
by Ayamari
I can reproduce the problem, but much earlier. Both freeplay and sandbox. At x <= -10'000 the map generator blows up with sharp vertical edges and artifacts.
Explored a sandbox map from -12'000 to +12'000 in both axes:
x <= -10'000 -> clearly visible artifacts
x >= +10'000 -> looks fine (tested up to +12'000)
y <= -10'000 -> looks fine (tested up to -12'000)
y >= +10'000 -> looks fine (tested up to +12'000)

Tested both 0.16.5 and 0.16.6. Both break at x <= -10'000.
Repro:
- start sandbox with default options
- scroll to approx. x = -10'000
- explore y +- 1'000 and x += 2'000
- notice sharp edges and artifacts

Tested 3 randomly generated sandbox maps, all had the problems visible within (-12'000, -1'000)->(-10'000, +1'000) area, so this is at least fairly reliable.

Re: [0.16.4]Broken map gen at x -22000

Posted: Tue Dec 19, 2017 10:16 pm
by TruePikachu
To confirm, the map generator was working fine this far away from spawn back in .15?

Re: [0.16.4]Broken map gen at x -22000

Posted: Wed Dec 20, 2017 3:49 am
by Rseding91
TruePikachu wrote:To confirm, the map generator was working fine this far away from spawn back in .15?
I can confirm it worked perfectly in 0.15 right up to the artificial limit of +- 1 million.

Re: [0.16.4]Broken map gen at x -22000

Posted: Tue Dec 26, 2017 9:58 pm
by lotzik
this keeps happening in 0.16.7

Re: [0.16.4]Broken map gen at x -22000

Posted: Wed Dec 27, 2017 2:57 am
by Rseding91
lotzik wrote:this keeps happening in 0.16.7
Because it's resolved for the next release which isn't out yet.