What's even the point? I've never found a use beyond 20 with Optifine, and even that was just so I could see where the normal 16 max ends and then go a little further away when making an "ocean" in my adventure map.
32 is already crazy and even if your computer can run it it still messes most people up unless you have always played it like that. And while 64 would be really cool it would be very impractical. I usually use 8-16 depending on what I'm doing, the only time I really even use 32 is when I'm in my space-ship world (a void world where I build random space-ships I invent).
Lots of people have modded java MC and rendered 100 chunks. It just needs a good PC.
Computers get better all the time; 64 is probably fine, with a modern i5/i7, and a Geforce 1080 Ti.
Sure, those are expensive right now, but they won't be in a year or so.
I have that exact setup (with an i7) and the game runs at ~25 FPS and stutters at 64 chunks using Optifine. On top of that, the internal server overloads, causing block lag and mob desync.
It is in no way by any stretch of the imagination playable.
I have that exact setup (with an i7) and the game runs at ~25 FPS and stutters at 64 chunks using Optifine. On top of that, the internal server overloads, causing block lag and mob desync.
It is in no way by any stretch of the imagination playable.
Bedrock avoids the server lag issue by only updating chunks within 4 chunks of the player, which is one reason why it is able to render such large distances without lag, and something similar could be done for Java; I see little reason for all chunks within 64+ chunks of the player to be actively updated (4 is not that much though, perhaps set it to 10-16 max, similar to how 1.3.1-1.6.4 used a fixed update radius of 7 chunks independent of view distance (which itself was fixed at 10 in singleplayer unless you used Optifine) - this could also explain why some people found that 1.7.4+ performed much worse than older versions (even 10 chunks, the practical minimum due to a bug, is already nearly double the ticking chunks; 32 is nearly 19 times and 64 is 74 times).
Also, Bedrock sets the maximum render distance available according to your computer setup (available memory and GPU) in a finer manner than Java does, which is either 16 or 32 chunks based on allocated RAM (>= 2 GB for 32. That said, I've modded the server to load as many as 50 chunks (101x101 chunks total) to quickly generate a large area and memory usage was only around 600 MB since all those chunks were only loaded server-side and were not rendered; a gross inefficiency of the current client-server model is that both maintain their own chunk caches so twice as much memory is required).
64 render distance would be the one to see in minecraft
Sorry but this account is no longer used
I quit I no longer belong to these forums
I'll switch back to warzone 2100
Here's my coal dimensions mod for 1.11.2
i'm planning on making a coal dimensions picture stay tuned
EDIT:Link changed
https://1drv.ms/u/s!Aj03l635Obq6sWB3_c9BE618fXQj
http://www.minecraftforum.net/forums/minecraft-java-edition/discussion/2863204-newbie-to-minecraft
While on the other hand a player claims that 1.12.2 is running slow AND slower than 1.12
My game can barely handle 16
Why am I here
pretty sure my client would crash instantly, let alone my entire computer
EDIT: hold up http://optifine.net/changelog?f=preview_OptiFine_1.12.2_HD_U_C7_pre.jar
Click here to see dragons I've successfully raised! (EDIT: Veeeery old; I don't raise dragons anymore)
What's even the point? I've never found a use beyond 20 with Optifine, and even that was just so I could see where the normal 16 max ends and then go a little further away when making an "ocean" in my adventure map.
Stay fluffy~
Only the Bedrock edition can effectively run 64 chunks.
32 is already crazy and even if your computer can run it it still messes most people up unless you have always played it like that. And while 64 would be really cool it would be very impractical. I usually use 8-16 depending on what I'm doing, the only time I really even use 32 is when I'm in my space-ship world (a void world where I build random space-ships I invent).
Just curious, that's all.
What's "Bedrock edition"?
Just curious, that's all.
I have that exact setup (with an i7) and the game runs at ~25 FPS and stutters at 64 chunks using Optifine. On top of that, the internal server overloads, causing block lag and mob desync.
It is in no way by any stretch of the imagination playable.
Well well I seemto get 60 fps when playing 32 chunkss XD (Don't think I am crazy I just happen to have a gtx 1080)
Bedrock avoids the server lag issue by only updating chunks within 4 chunks of the player, which is one reason why it is able to render such large distances without lag, and something similar could be done for Java; I see little reason for all chunks within 64+ chunks of the player to be actively updated (4 is not that much though, perhaps set it to 10-16 max, similar to how 1.3.1-1.6.4 used a fixed update radius of 7 chunks independent of view distance (which itself was fixed at 10 in singleplayer unless you used Optifine) - this could also explain why some people found that 1.7.4+ performed much worse than older versions (even 10 chunks, the practical minimum due to a bug, is already nearly double the ticking chunks; 32 is nearly 19 times and 64 is 74 times).
Also, Bedrock sets the maximum render distance available according to your computer setup (available memory and GPU) in a finer manner than Java does, which is either 16 or 32 chunks based on allocated RAM (>= 2 GB for 32. That said, I've modded the server to load as many as 50 chunks (101x101 chunks total) to quickly generate a large area and memory usage was only around 600 MB since all those chunks were only loaded server-side and were not rendered; a gross inefficiency of the current client-server model is that both maintain their own chunk caches so twice as much memory is required).
TheMasterCaver's First World - possibly the most caved-out world in Minecraft history - includes world download.
TheMasterCaver's World - my own version of Minecraft largely based on my views of how the game should have evolved since 1.6.4.
Why do I still play in 1.6.4?