The render distance limit makes worlds feel smaller. 1/4 as big as they were in 1.17. I used to play rendering 16 chunks with C&C experimental features and a simulation distance of 6 chunks. But I am now stuck with 9. The limit feels somewhat debilitating because I can't find where I'm going as well as I used to. Readers, please note that I do not mean for this to be an angry post. (angry at Mojang) I mean for it to by a respectful discussion/argument. I feel as though the estimates of how much lag a device will suffer from are incorrect. If it's RAM that's used to determine the maximum render distance, I would like to make it known that mobile devices aren't as limited to using RAM as desktop devices. When needed, they can use a large amount (I've had 7 GB used once for C.O.D. Mobile.) of their storage space as ram, making use of their actual RAM as a desktop device would cache. So, rather than using ram to determine how many chunks may be rendered, I believe that the processor specifications would be a better option. The iPhone SE (1st generation) meets the minimum Java Edition system requirements. I have an iPhone 8 that meets the recommended system requirements and I experience hardly any lag when rendering 16 chunks with a simulation distance of 6 chunks and C&C experimental features. I used to set huge masses of would on fire (In the 20, 30 and 40 thousands of blocks) and still get 16–20 fps.
Please sign in to leave a comment.