The memory issues in version 1.8 have, finally, made Minecraft completely unplayable for me, and for all people on low-end computers.
MogMiner & Lorgon111, Minecraft isn't just a game; it's a fundamental teaching tool for millions of kids, all over the planet. And that means it needs to be accessible to them, even if their equipment is low end.
This is a ramble of my experiences of Minecraft.
MogMiner, You don't have to watch this; just listen to it in the background, so you can understand how profoundly important it is to me that the garbage dump & FPS issues be addressed as quickly as possible, so everyone can play this game. Please. I'll never ask you for another thing.
Brian, you only need to watch out of the corner of your eye to see my performance on 2 iterations of MinecraftBINGO! I'll tell you now: it's abysmal.
Please watch the video. I explain better there.
Rollback Post to RevisionRollBack
My YouTube channel: http://www.youtube.c...er/GrannyGamer1 There's no wrong way to play MineCraft. Here, we'll discuss tactics, strategies, making the game accessible to people with disabilities.
My YouTube channel: http://www.youtube.c...er/GrannyGamer1 There's no wrong way to play MineCraft. Here, we'll discuss tactics, strategies, making the game accessible to people with disabilities.
1.9 is supposed to bring optimizations. They KNOW the lag is terrible. They will try to fix it. In the meantime, if it's truly unplayable you can play 1.7.10 via the launcher.
Rollback Post to RevisionRollBack
Truly he is my rock and my salvation; he is my fortress, I will not be shaken. ~Psalms 62:6
They needed to ruin Microsoft's reputation as much as possible.
No, that was a joke. What really happened is the new water temple structure. When one spawns, water placement lags the game lots. A possible solution would be to write the structure spawning code so that it doesn't create anything in the schematic's air blocks, rather than spawning water. If this wouldn't help, you could always generate the water in the chunk AFTER the temple had spawned.
I can't: play most servers on which I work, play most UHC, play many current minigames; play MinecraftBINGO! to record to YouTube in 1.8 In fact, as I said in the video, I can't record well in any versions later than 1.7.4 and very few viewers are interested in seeing videos from such old versions. You can see from the video how unplayable it is.
Rollback Post to RevisionRollBack
My YouTube channel: http://www.youtube.c...er/GrannyGamer1 There's no wrong way to play MineCraft. Here, we'll discuss tactics, strategies, making the game accessible to people with disabilities.
Maybe the biggest and the ugliest problem is the memory allocation. Currently the game allocates (and throws away immediately) 50 MB/sec when standing still and up to 200 MB/sec when moving. That is just crazy.
What happens when the game allocates 200 MB memory every second and discards them immediately?
1. With a default memory limit of 1GB (1000 MB) and working memory of about 200 MB Java has to make a full garbage collection every 4 seconds otherwise it would run out of memory. When running with 60 fps, one frame takes about 16 ms. In order not to be noticeable, the garbage collection should run in 10-15 ms maximum. In this minimal time it has to decide which of the several hundred thausand newly generated objects are garbage and can be discarded and which are not. This is a huge amount of work and it needs a very powerful CPU in order to finish in 10 ms.
Rollback Post to RevisionRollBack
My YouTube channel: http://www.youtube.c...er/GrannyGamer1 There's no wrong way to play MineCraft. Here, we'll discuss tactics, strategies, making the game accessible to people with disabilities.
As I say in the video, MogMiner & I had a friendly Twitter exchange about this; it's why I made the video.
Rollback Post to RevisionRollBack
My YouTube channel: http://www.youtube.c...er/GrannyGamer1 There's no wrong way to play MineCraft. Here, we'll discuss tactics, strategies, making the game accessible to people with disabilities.
MogMiner & Lorgon111, Minecraft isn't just a game; it's a fundamental teaching tool for millions of kids, all over the planet. And that means it needs to be accessible to them, even if their equipment is low end.
This is a ramble of my experiences of Minecraft.
MogMiner, You don't have to watch this; just listen to it in the background, so you can understand how profoundly important it is to me that the garbage dump & FPS issues be addressed as quickly as possible, so everyone can play this game. Please. I'll never ask you for another thing.
Brian, you only need to watch out of the corner of your eye to see my performance on 2 iterations of MinecraftBINGO! I'll tell you now: it's abysmal.
Please watch the video. I explain better there.
If you are planning to make a suggestion, please read this.
If you want to know more, you can read this.
For those who complain about post-Beta generation, you might want to see this.
No, that was a joke. What really happened is the new water temple structure. When one spawns, water placement lags the game lots. A possible solution would be to write the structure spawning code so that it doesn't create anything in the schematic's air blocks, rather than spawning water. If this wouldn't help, you could always generate the water in the chunk AFTER the temple had spawned.
Let's do some math.
1/3 = 0.333...
1/3 * 3 = 1
0.333... * 3 = 0.999...
1 = 0.999...
1 - 0.999... = 0.999... - 0.999...
0.0...1 = 0
0.0...1 * 10... = 0 * 10...
1 = 0
Quote:
sp614x posted a message on OptiFine HD A4 (FPS Boost, HD Textures, AA, AF and much more)
Minecraft 1.8 has so many performance problems that I just don't know where to start with.
Maybe the biggest and the ugliest problem is the memory allocation. Currently the game allocates (and throws away immediately) 50 MB/sec when standing still and up to 200 MB/sec when moving. That is just crazy.
What happens when the game allocates 200 MB memory every second and discards them immediately?
1. With a default memory limit of 1GB (1000 MB) and working memory of about 200 MB Java has to make a full garbage collection every 4 seconds otherwise it would run out of memory. When running with 60 fps, one frame takes about 16 ms. In order not to be noticeable, the garbage collection should run in 10-15 ms maximum. In this minimal time it has to decide which of the several hundred thausand newly generated objects are garbage and can be discarded and which are not. This is a huge amount of work and it needs a very powerful CPU in order to finish in 10 ms.