iPad 5th generation 128 gigabytes Render distance wonβt stay at 14 it will change to 8 or 6
And I have a hi memory iOS device please fix I want to be able change reminder distance to 14 whenever I want
Linked issues
Attachments
Comments 11

Thank you for your report!
However, this issue has been closed as a Duplicate of MCPE-24148.
Your additional information and observations are very useful, so if you can add them to the comments section of the parent issue it would be appreciated.
If you have not, you might like to make use of the search feature before making a new ticket, as it's likely that the issue has been reported already.
Quick Links:
π Issue Guidelines β π¬ Community Support β π§ Feedback β π Game Wiki
Thank you for your report!
However, this issue has been closed as a Duplicate of MCPE-24148.
Your additional information and observations are very useful, so if you can add them to the comments section of the parent issue it would be appreciated.
If you have not, you might like to make use of the search feature before making a new ticket, as it's likely that the issue has been reported already.
Quick Links:
π Issue Guidelines β π¬ Community Support β π§ Feedback β π Game Wiki
Thank you for your report!
However, this issue has been closed as a Duplicate of MCPE-24148.
Your additional information and observations are very useful, so if you can add them to the comments section of the parent issue it would be appreciated.
If you have not, you might like to make use of the search feature before making a new ticket, as it's likely that the issue has been reported already.
Quick Links:
π Issue Guidelines β π¬ Community Support β π§ Feedback β π Game Wiki
This is different from MCPE-24148. That thread is talking about the limitations of render distance instituted in 1.2 for device hardware. This bug report is talking about variable render distance for a given device. While some gains can be made by closing other apps before opening MC, the real culprit here is that the app does not deallocate memory. It uses around 600-900 MB of RAM to load a world file. Then, if you switch to another app, that memory space is locked. When you come back into MC, It thinks you have less memory available than you do and decreases the render distance. I have found that if you don't chnage it, it is still set for 14 despite what the display says. However, I have an app that deallocates memory (apple tends to kill these apps because their official position is that they are not necessary) that I run before opening MC in between sessions.
This is different from MCPE-24148. That thread is talking about the limitations of render distance instituted in 1.2 for device hardware. This bug report is talking about variable render distance for a given device. While some gains can be made by closing other apps before opening MC, the real culprit here is that the app does not deallocate memory. It uses around 600-900 MB of RAM to load a world file. Then, if you switch to another app, that memory space is locked. When you come back into MC, It thinks you have less memory available than you do and decreases the render distance. I have found that if you don't chnage it, it is still set for 14 despite what the display says. However, I have an app that deallocates memory (apple tends to kill these apps because their official position is that they are not necessary) that I run before opening MC in between sessions.
This is different from MCPE-24148. That thread is talking about the limitations of render distance instituted in 1.2 for device hardware. This bug report is talking about variable render distance for a given device. While some gains can be made by closing other apps before opening MC, the real culprit here is that the app does not deallocate memory. It uses around 600-900 MB of RAM to load a world file. Then, if you switch to another app, that memory space is locked. When you come back into MC, It thinks you have less memory available than you do and decreases the render distance. I have found that if you don't chnage it, it is still set for 14 despite what the display says. However, I have an app that deallocates memory (apple tends to kill these apps because their official position is that they are not necessary) that I run before opening MC in between sessions.
This is different from MCPE-24148. That thread is talking about the limitations of render distance instituted in 1.2 for device hardware. This bug report is talking about variable render distance for a given device. While some gains can be made by closing other apps before opening MC, the real culprit here is that the app does not deallocate memory. It uses around 600-900 MB of RAM to load a world file. Then, if you switch to another app, that memory space is locked. When you come back into MC, It thinks you have less memory available than you do and decreases the render distance. I have found that if you don't chnage it, it is still set for 14 despite what the display says. However, I have an app that deallocates memory (apple tends to kill these apps because their official position is that they are not necessary) that I run before opening MC in between sessions.