The Meaning of Life, the Universe, and Everything.
Join Date:
4/27/2015
Posts:
60
Member Details
I'm attempting to test out MCPE Win10 in hopes of transitioning from MCCE and I'm now testing various distance limits for machinery/redstone etc.
I've found that minecarts stop working when traveling out of view from the player. This happens somewhere between 65 to 80 blocks but the console limit is 224 blocks from my last notes. Does anyone know the definitive limits for rail and minecart distances? Basically as soon as the cart stops being rendered it'll be stuck in that position - moving the player a block or so closer allows it to start moving again.
I don't know the exact answer, but I do know that MC "infinite" worlds work with "chunks" or small parts of the world in memory at a time, because computers can't hold a whole "infinite" world in memory at once like consoles can with their much smaller worlds. So the current "chunk" is in memory and works normally. As so as you (or, in this case, another object) moves to a new "chunk", the new one is loaded into memory, and the old one is saved. (That's why wheat doesn't grow unless you're nearby.)
Short version: Infinite worlds work different than (smaller) console worlds.
The Meaning of Life, the Universe, and Everything.
Join Date:
4/27/2015
Posts:
60
Member Details
Console worlds are plenty large nowadays and 64 blocks is just 4 chunks away... Surly MCPE Win10 can do at least as well...
For comparison, a string a redstone >256 blocks long works in MCPE so things are definitely ticking very far into the distance.
Edit: Redstone signals can loop 256 blocks out and back no problem. However, a hopper clock will only work 4 chunks away from the current player's chunk This is awful.
Each [ ] represents 16 blocks. [P] is the player, [*] is an active chunk. Chunks run from bedrock to build-limit.
[*]
[*][*][*]
[*][*][*][*][*]
[*][*][*][*][*][*][*]
[*][*][*][*][P][*][*][*][*]
[*][*][*][*][*][*][*]
[*][*][*][*][*]
[*][*][*]
[*]
I'm attempting to test out MCPE Win10 in hopes of transitioning from MCCE and I'm now testing various distance limits for machinery/redstone etc.
I've found that minecarts stop working when traveling out of view from the player. This happens somewhere between 65 to 80 blocks but the console limit is 224 blocks from my last notes. Does anyone know the definitive limits for rail and minecart distances? Basically as soon as the cart stops being rendered it'll be stuck in that position - moving the player a block or so closer allows it to start moving again.
I don't know the exact answer, but I do know that MC "infinite" worlds work with "chunks" or small parts of the world in memory at a time, because computers can't hold a whole "infinite" world in memory at once like consoles can with their much smaller worlds. So the current "chunk" is in memory and works normally. As so as you (or, in this case, another object) moves to a new "chunk", the new one is loaded into memory, and the old one is saved. (That's why wheat doesn't grow unless you're nearby.)
Short version: Infinite worlds work different than (smaller) console worlds.
Remember: all Minecraft's are not the same.
Console worlds are plenty large nowadays and 64 blocks is just 4 chunks away... Surly MCPE Win10 can do at least as well...
For comparison, a string a redstone >256 blocks long works in MCPE so things are definitely ticking very far into the distance.
Edit: Redstone signals can loop 256 blocks out and back no problem. However, a hopper clock will only work 4 chunks away from the current player's chunk This is awful.
From other empirical evidence it looks like MCPE does use a 4 chunk radius for mob spawns, rail, and machinery ticking (reddit, experiments).
For anyone stumbling on the thread later:
MCPE is just not good in its current state...