It had been a few years since I last played Minecraft, so i thought I might give a new survival game a chance. I opened up the launcher, installed version 1.8.4, and put the video settings through the roof since my computer can undoubtedly handle it. I tried to create a world to see what kind of frame rates I was getting, but got stuck on a screen that read "downloading terrain," which I found pretty odd since I was in single player. I turned the settings down and was able to load into a world, but shortly after I noticed that any chunks not immediately visible when first entering the world would refuse to load. NPCs and other entities were unresponsive, motionless and it ultimately acted as if I was on a crashing server, or something.
After Googling it, I found that this was apparently due to the save being corrupted. No tutorials, threads, or anything else I could find said anything about them corrupting on creation, though. I saw a ton of people in the comments of YouTube videos with the same problems, however, no one seems to know how to fix it.
That's what happens if you use extreme render distances, which require a "supercomputer" (i.e. very high end), as a moderator literally said in the following bug report - even with such a computer you have to wait a long time for the world to load and run stably; it really isn't surprising that the render distance was only 16 chunks for so long (and in my experience it has to be lowered to get similar performance, especially server performance, which explains the mobs not moving/lagging and all):
[Mojang] Grum (Erik Broes)added a comment - 21/Aug/14 6:28 AM
Stop having silly high distances (32) and expect things to load instantly if you have a subpar computer (you basically need a super computer and even then you are going to sit and wait 30+ seconds for the data to generate).
Consider that 32 chunk render distance loads four times as many chunks as 16 chunks, and a staggering sixteen times as many as 8 chunks, and that's why it is so demanding. Basically, even if you have a high end computer you are pushing it too hard.
Also, "downloading terrain" is perfectly normal and I see it whenever I load a world or go to another dimension - you are actually running a server even in singleplayer (since 1.3.1) and the client communicates just as if it were hosted on another computer (within memory, not over the network). This will also happen on new world creation if your render distance is higher than about 12 chunks, since the game only creates a 25x25 chunk area as the default spawn area when a world is first created (during "building terrain"), anything else will be generated separately.
That's the thing... I believe I mentioned in the original post that this happens despite what graphics settings I use.
Also, considering that before the 32-chunk render distance update I was able to use the "extreme" setting (which I believe is at least 32... maybe higher) within OptiFine without any of these problems, I think this is kind of on Mojang. I payed $30 for their game. Instead of just telling us not to "use silly render distances," they should be fixing the issue. Minecraft has always been badly optimized.
It had been a few years since I last played Minecraft, so i thought I might give a new survival game a chance. I opened up the launcher, installed version 1.8.4, and put the video settings through the roof since my computer can undoubtedly handle it. I tried to create a world to see what kind of frame rates I was getting, but got stuck on a screen that read "downloading terrain," which I found pretty odd since I was in single player. I turned the settings down and was able to load into a world, but shortly after I noticed that any chunks not immediately visible when first entering the world would refuse to load. NPCs and other entities were unresponsive, motionless and it ultimately acted as if I was on a crashing server, or something.
After Googling it, I found that this was apparently due to the save being corrupted. No tutorials, threads, or anything else I could find said anything about them corrupting on creation, though. I saw a ton of people in the comments of YouTube videos with the same problems, however, no one seems to know how to fix it.
Thanks in advance.
Computer specs:
>i5-3570K (water-cooled, 4.2Ghz)
>12Gb (3x4) of 1600Mhz, CAS 9 RAM
>8Gb Radeon R9 290X (water-cooled, 1.11Ghz)
>Minecraft running off of THIS SSD
That's what happens if you use extreme render distances, which require a "supercomputer" (i.e. very high end), as a moderator literally said in the following bug report - even with such a computer you have to wait a long time for the world to load and run stably; it really isn't surprising that the render distance was only 16 chunks for so long (and in my experience it has to be lowered to get similar performance, especially server performance, which explains the mobs not moving/lagging and all):
Consider that 32 chunk render distance loads four times as many chunks as 16 chunks, and a staggering sixteen times as many as 8 chunks, and that's why it is so demanding. Basically, even if you have a high end computer you are pushing it too hard.
Also, "downloading terrain" is perfectly normal and I see it whenever I load a world or go to another dimension - you are actually running a server even in singleplayer (since 1.3.1) and the client communicates just as if it were hosted on another computer (within memory, not over the network). This will also happen on new world creation if your render distance is higher than about 12 chunks, since the game only creates a 25x25 chunk area as the default spawn area when a world is first created (during "building terrain"), anything else will be generated separately.
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?
That's the thing... I believe I mentioned in the original post that this happens despite what graphics settings I use.
Also, considering that before the 32-chunk render distance update I was able to use the "extreme" setting (which I believe is at least 32... maybe higher) within OptiFine without any of these problems, I think this is kind of on Mojang. I payed $30 for their game. Instead of just telling us not to "use silly render distances," they should be fixing the issue. Minecraft has always been badly optimized.
OK.
Stop shouting at people who are trying to help.
How did you pay $30 for minecraft?
Extreme render distance is 32 chunks no higher.
OptiFine is a mod. Not the game.
Some people have amazing computer which is the reason behind the "silly" render distance.