Map creator ignores Map Settings

[Tami]

I play maps with Grass only for certain reason, then i have to throw a map, if i see something like this. My settings dont allow other biomes than Grass/Water but the map creator trolls me by setting dots for dirts on the map and this is no coal. I dont like dirt ... its dirty

[SilverWarior]

Based on my understanding of how Factorio terrain generation works the game creates heightmap by placing bunch of controll points with different height and then using interpolation for calculating height for all the points in between these controll points. Since the game doesn't use linear interpolation but probably cubic or logarithmic interpolation this could cause for certain areas to have either biger or lower height than wanted.
And since the game finally decides where each terrain type should be placed by setting certain height range for each terrain type this previously mentioned problem of keeping heightmap height within predefined limits creates some discrepancies.

Now best solution for this would be to completly remove the height checks for terrain types that have ben set to none in terain generation settings and make sure that bottom terrain type uses heightrange which is lower than upper terrain height limit, upper terrain type uses heightrage which is higher than lower terrain height limit, and all rest to use heightrage between lower and upper terrain height limits


I apologize if this post is hardly understandable by most of you but it is hard to explaing this without me teaching you of either Fractal heghtmap generation or Perlin Noise heightmap generation and how different interpolation systems work.

[ssilk]

I would explain so: the terrain generation has some calculation inaccuracy. And to remove it, the generator first should calculate his inaccuracy, before he sets his terrain-limits and calculate the terrain.

[SilverWarior]

I would explain so: the terrain generation has some calculation inaccuracy. And to remove it, the generator first should calculate his inaccuracy, before he sets his terrain-limits and calculate the terrain.

You can calculate and then limit inacuracly when you have finite maps, but doing so with infinite maps is practically imposible due to the reasons why these inacuracies ocur.

[cube]

This is really weird and I have no idea why this happens, but in 0.8.0 the terrain will be done in a completely different way (we're moving everything to the autoplace mechanism to enable biomes in 0.9), so this bug should disappear.