Minecraft Forums

Quote from MuzikBike»

Or, yknow, if only Mojang started working on it. Both of these being unlikely circumstances sadly out of our hands.

One thing I would like to see: would Tall Worlds work with any manual modifications that returns the far lands? Since cubic chunks are handled differently I kind of doubt the existence of Tall Far Worlds, and even then there could be a Far Sky, shrouding the whole world in a laggy darkness.

The far lands would still be there in a cubic chunk world. You might even get far-effects in the y dimension as well. =)

Far lands as terrain distortions are long gone. When using vanilla noise generator it would be there on Y coordinate, but vanilla noise generator is broken in cubic chunks incompatible way. The noise generator cubic chunks uses (flow-noise library) doesn't have far lands, but it's very east to bring them back.

As for other high coordinate glitches - I couldn't find any in 1.11.2, even when I got depth -1,000,000,000 working.

Coordinate precision at high magnitudes with floating point representations are still an issue, regardless of terrain generation. ie, at 30 mil meters away from zero, even the double type doesn't represent sub-meter distances very well.

You would need to modify flow-noise library that my and Cuchaz's version uses, CubicChunks doesn't use vanilla noise generator because it's broken when used with cubic chunks, and it just happens to work without cubic chunks.

As for coordinate precision - with double you have 15 decimal digits. Integer.MAX_VALUE uses 9 of them. That leaves 8 digits of precision which is still more than float has in total. I don't see it as an issue.

In vanilla/cubic chunks there are literally no issues at all at 1,000,000,000 blocks below y=0. I will make a video to show it.

I changed save format and I was able to extend it to over 1 billion blocks, and theoretically I could extend it all the way to (max 32 bit signed integer) - (some constant) (4096 would be good constant here) in both directions after I make ServerHeightMap work with it (the former OpacityIndex, now it only stores boolean flags)

Quote from Barteks2x»

As for coordinate precision - with double you have 15 decimal digits. Integer.MAX_VALUE uses 9 of them. That leaves 8 digits of precision which is still more than float has in total. I don't see it as an issue.

I've found that after accounting for even modest amounts of accumulated roundoff error, that 15 digits is closer to 11 or 12 in practice. So after 30 mil blocks away from the origin, we're left with maybe 3 digits, which is merely centimeter precision. That seems pretty close to the limit of the precision we need for accurate physics simulation in the game engine.

But whatever. Not many people hang out in the far lands anyway.

Maybe you are right, but I'm almost sure Minecraft does a lot of physics calculations in coordinates relative to the entity (I didn't check that). And for rendering even a centimeter precision is barely noticable error (it's 1/8th of a texture pixel)

Minecraft generally has surprisingly huge amount of code to make unreasonably big coordinates work.

As for why bother with such coordinates - just because I can, and because it's a useful thing for testing edge cases. And because some people will complain if you don't even if what you give is more than enough. There is no way any algorithm that iterates over world height based range will work at such place. It also showed me that some sounds stop working here - maybe because float is used to store sound source position? Or BlockPos packed into 64-bit value.

Anyway here is the video, it's very laggy and bad quality and has glitches because something is wrong with my system and I have no idea what. This is just to show that it can actually work without posting download link to compiled mod:

I could remove the hardcoded limit but I'm not going to double the work for something completely unnecessary.

In TWM at about -32000 lava is generated instead of stone I'm not sure why you can't see it, I guess something goes wrong with chunk loading. In my version stone with caves generates all the way down, but ravines become gradually more and more filled with lava as you go down (I didn't implement that for caves yet). And you can also get the caves/ravines that loop vertically, with the same seed.

The gravel layer is there because of inherently broken way TWM handles dirt/grass/gravel generation (which is based on how robinton's version did it). I have fixed it in my MC1.11/forge port by generating surface blocks in entirely different, more reliable way.

Robinton's version has far lands earlier than vanilla because it uses different constants for noise generation (higher frequency). And farlands do eventually stop because of what causes them - they are caused by integer overflow (internal position not fitting into a 32-bit integer), which causes fractional part of position to be calculated as greater than 1, which makes the noise values grow extremely high when that fractional position is used for interpolation. And since Y value is subtracted from noise value (multiplied by some bigger factor above certain point) it is possible for the subtracted Y so be greater than the noise value, which makes far lands disappear. They will also disappear extremely deep.

The noise generator I use doesn't have farlands because it loops around at the point where farlands would begin.

Also, in MC 1.6.4 back when I used modified vanilla generator (before the mod was open source, and before Cuchaz's TWM), I've seen *vertical* farlands:

You make me curious, I want to check it now

What I found at 3d corner far lands is really surprising. I expected to see either everything filled with stone, or everything empty. I saw neither. It was surprisingly close to playable nether-like cave world:

Screenshots:

Note: It took me quite a while to make all these images clickable fighting stupidity of minecraftforum editor modifying my markup, so there may be mistakes

You won't see anything because of water. But other than that it will look the same - sponge-like terrain. Butok, I will edit this post with screenshot from the bottom with water removed.

Quote from AetherialBedouin»

Well, massive kudos for attempting to take it on in the first place. I salute your determination.

From
what I understand, Barteks2x is carrying on from where you left off?
And you released a working version after all. So isn't it possible that
Mojang could take what work you two have already put into it, and
continue to carry the torch until it is finished?

Why would they do something only small percentage of users will notice and can possibly reintroduce massing amounts of bugs and takes forever to implement and restricts what you can do with terrain generation and some algorithms? For them, there is no point doing that.

Quote from MattTCreeper»

Can I see the vertex far lands (last pictures) underground?

I found many more interesting things when visiting the deep far lands. It looked mostly the same as farlands at the top... except at some point even farlands become more glitchy. The optimized interpolation code seems to give up on accurace and the terrain becomes gradually more and more blocky as you go down over hundreds of thousands of blocks. But then something interesting happens that I'm yet to find explanation for (I don't have a slightest idea for explaining it):

At one point there appears to be a plane along which for higher z coordinates and lower x coordinates all blocks stop generating (but only in the area of3d corner far lands). I have no explanation for why would such thing appear at all, let alone the absurdally weird slope: to stay on the plane, after going down 4000000 blocks you need to go exactly 1294300 blocks forward in X coordinate. I didn't have the determination go go through all of that again and find out the number for Z coordinate, but from the looks of it, you need to go twice as deep, while decreasing Z coordinate by close to the same amount. All the screenshots: https://www.dropbox.com/sh/hwt28zsxorehiuc/AAC-h7xm8c-PR4U62Zdzraiha?dl=0