-
Bug
-
Resolution: Invalid
-
None
-
1.15 Pre-release 3
-
None
-
Java 1.8.0_51, 64 bit, Windows 10 version 1903, RAM: 4 GB (2 GB allocated for Minecraft), CPU: AMD A8, Integrated GPU.
-
Unconfirmed
-
(Unassigned)
I play on a low-end hardware, and I usually play Minecraft with Optifine for faster rendering. And, 1.15 really stress the client the higher the render distance I set, even if I am not loading new chunks. I usually play at unlimited max framerate, but I tested it at 30 fps and the absurd increments of ms ticks is still happening.
At 2-3 chunks, it is healthy at 8 ms ticks
At 4 chunks, it is immediately at 20 ms ticks.
5 chunks, 40 ms ticks; 6 chunks, 75 ms ticks; 7 chunks, 100 ms ticks; 8 chunks, 120 ms ticks.
Obviously the higher the render distance, the slower the client will be. But, at 1.14.4, without Optifine, at 10 chunk render distance I can get around only 40 ms ticks at highest when not loading a chunk.
The new system looks good in FPS count because it feels fast. I suggest that there should be an option whether you want FPS or the chunk loading to be prioritized.
Quick message: "I really want to cheer you all to make Minecraft a better game. Most people in my country have potato computers so I hope that extreme optimization of Java Edition would pave the way for more accessibility for lower-end hardware. Good luck and thank you all devs! You are doing great so far with 1.15!"