Talk:Frame rate

Chunk Loading
I would like to know more about what determines which chunks will be loaded in single player at any given time under various circumstances. I understand that, on singleplayer, it is a function of my render distance, and I see the table says that on Far, 10,816 chunks will be loaded at all times, but I do not fully understand exactly which 10,816 chunks are being loaded.

Is it a 104x104 chunk square, or is it more roughly circular? If it is, as I suspect, a square, where in that square is my current chunk? Obviously, it is somewhere near the middle, but there is no "middle" chunk if there is an even number of chunks. If the loaded chunks along the x-axis are numbered 1 - 104, then would mine be number 52 or number 53? Put another way, if my current chunk is (0,0) do the loaded chunks extend from -52 to 51, from -51 to 52, or some other rule?

I am trying to devise a hard limit for how far away from my home I can roam without unloading my home chunk. Thank you for any clarification you can provide.

--Agiar2000 04:36, 16 October 2012 (UTC)

Chunk visibility discrepancy

On server.properties, it says 'far' is 9 chunks, but here it says 16. I think here is correct, because on a default-configured server, switching from "normal" to "far" only increases view slightly, and using optifine, Normal+32 is the same visible distance as "far"

98.109.213.229 07:23, 4 May 2013 (UTC)

Pocket Edition total Chunks and Sections
I apologize for not putting up the total chunks or sections for Pocket Edition's max render distance. I just don't know how to do the math for that. May somebody put it up or at least give me the formula for it? _GameFreak667 (talk) 20:21, 30 December 2013 (UTC)


 * Done, assuming PE uses chunks and sections. Number of chunks is (render distance * 2 + 1)2, number of sections is 16 times the number of chunks. -- Orthotopetalk 01:31, 31 December 2013 (UTC)


 * Pocket Edition released an option for 512 chunks. How many blocks and sections would that be? GameFreak667 (talk) 19:41, 12 July 2014 (UTC)

Optimine?
If i'm correct, Optimine hasn't been very active, as Optifine is still up and running. Because of this, I'll remove the reference to Optimine.

AgentPaint (talk) 04:54, 9 April 2014 (UTC)AgentPaint

More mods to improve FPS / decrease lag
Aside from optifine, FPSplus and optileaves, (some of these are out of date) are there any other mods that improve FPS? Or any super secret technique to improve FPS? Or even a texture pack that reduces lag (i've heard they don't exist though). Thanks in advance! SirTulip (talk) 13:03, 16 November 2014 (UTC)

What to do with this page
Should this page be merged with Debug screen, made into a tutorial, merged with some other page, or left as is and linked better (placed in the Minecraft navbox template)? –Goandgoo ᐸ Talk Contribs 13:39, 7 July 2015 (UTC)


 * It seems like a mix of stuff that belongs in other places. I would move the second section to a tutorial like it belongs, and the third section to options (since it is about chunk rendering, not frame rate). After that, all the leftover content could be made into a paragraph debug screen, as a single number on the debug screen is really not enough for a full article (though it is enough for the tutorial). – KnightMiner  t/c 15:08, 7 July 2015 (UTC)