This may be a bug, this may not, but the maximum render distance has gone down from 14 to 6 chunks. As having a render distance of just 6 chunks makes the game far less enjoyable I am hoping this is a bug and not a deliberate decision to limit the amount loaded to help with all the memory problems that are being experienced with the latest update.
Linked issues
Attachments
Comments 83
migrated
What helped me if you play on an apple device was to refresh the app then it let me render my distance to 14 chunks.
I hope this helped 🙂
What helped me if you play on an apple device was to refresh the app then it let me render my distance to 14 chunks.
I hope this helped 🙂
What helped me if you play on an apple device was to refresh the app then it let me render my distance to 14 chunks.
I hope this helped 🙂
What helped me if you play on an apple device was to refresh the app then it let me render my distance to 14 chunks.
I hope this helped 🙂
I did a lot of fiddling and managed, somehow, to get it back again by loading an old 1.8 game first. A hard reboot also helped. Thank you.
I did a lot of fiddling and managed, somehow, to get it back again by loading an old 1.8 game first. A hard reboot also helped. Thank you.
I did a lot of fiddling and managed, somehow, to get it back again by loading an old 1.8 game first. A hard reboot also helped. Thank you.
I did a lot of fiddling and managed, somehow, to get it back again by loading an old 1.8 game first. A hard reboot also helped. Thank you.
This is not a bug, render distance depends on your device, try getting a new device like the newer iPads or phones 🙂
This is not a bug, render distance depends on your device, try getting a new device like the newer iPads or phones 🙂
This is not a bug, render distance depends on your device, try getting a new device like the newer iPads or phones 🙂
This is not a bug, render distance depends on your device, try getting a new device like the newer iPads or phones 🙂
Depending on how well your device preforms, MCPE may raise or lower the maximum render distance allowed. Ths is Working as Intended to prevent devices that are currently low on resources from lagging as much.
Depending on how well your device preforms, MCPE may raise or lower the maximum render distance allowed. Ths is Working as Intended to prevent devices that are currently low on resources from lagging as much.
Depending on how well your device preforms, MCPE may raise or lower the maximum render distance allowed. Ths is Working as Intended to prevent devices that are currently low on resources from lagging as much.
Depending on how well your device preforms, MCPE may raise or lower the maximum render distance allowed. Ths is Working as Intended to prevent devices that are currently low on resources from lagging as much.
Dr Awesome, Thanks for that and after clearing another gigabyte so that I had two spare it then started allowing me more chunks. Seems to need one heck of a lot of space..
Dr Awesome, Thanks for that and after clearing another gigabyte so that I had two spare it then started allowing me more chunks. Seems to need one heck of a lot of space..
Dr Awesome, Thanks for that and after clearing another gigabyte so that I had two spare it then started allowing me more chunks. Seems to need one heck of a lot of space..
Dr Awesome, Thanks for that and after clearing another gigabyte so that I had two spare it then started allowing me more chunks. Seems to need one heck of a lot of space..
By resources I was referring to RAM, not disk/internal memory.
By resources I was referring to RAM, not disk/internal memory.
By resources I was referring to RAM, not disk/internal memory.
By resources I was referring to RAM, not disk/internal memory.
Dr Awesome, I assumed that you were but I am back to 14 chunks rendering distance after clearing a lot of space, deleting old MCPE worlds and doing a hard reboot. I have no idea how iOS or MCPE memory handling works, unlike XP, but having more free disk space did the trick. I had tried a hard reboot many times before and it still got slower and slower but having more free space has stopped that. Weird...
Dr Awesome, I assumed that you were but I am back to 14 chunks rendering distance after clearing a lot of space, deleting old MCPE worlds and doing a hard reboot. I have no idea how iOS or MCPE memory handling works, unlike XP, but having more free disk space did the trick. I had tried a hard reboot many times before and it still got slower and slower but having more free space has stopped that. Weird...
Dr Awesome, I assumed that you were but I am back to 14 chunks rendering distance after clearing a lot of space, deleting old MCPE worlds and doing a hard reboot. I have no idea how iOS or MCPE memory handling works, unlike XP, but having more free disk space did the trick. I had tried a hard reboot many times before and it still got slower and slower but having more free space has stopped that. Weird...
Dr Awesome, I assumed that you were but I am back to 14 chunks rendering distance after clearing a lot of space, deleting old MCPE worlds and doing a hard reboot. I have no idea how iOS or MCPE memory handling works, unlike XP, but having more free disk space did the trick. I had tried a hard reboot many times before and it still got slower and slower but having more free space has stopped that. Weird...
Still affects version 1.2 on devices fully capable of much more render distance. Such as newer models of the iPad Pro, iPhone 8, Samsung Galaxy Note 8, and many more devices with the power to handle higher render distances.
Still affects version 1.2 on devices fully capable of much more render distance. Such as newer models of the iPad Pro, iPhone 8, Samsung Galaxy Note 8, and many more devices with the power to handle higher render distances.
Still affects version 1.2 on devices fully capable of much more render distance. Such as newer models of the iPad Pro, iPhone 8, Samsung Galaxy Note 8, and many more devices with the power to handle higher render distances.
Still affects version 1.2 on devices fully capable of much more render distance. Such as newer models of the iPad Pro, iPhone 8, Samsung Galaxy Note 8, and many more devices with the power to handle higher render distances.
This surely does not work as intended. I agree with Ramon that this is a bug and should be reopened.
This surely does not work as intended. I agree with Ramon that this is a bug and should be reopened.
This surely does not work as intended. I agree with Ramon that this is a bug and should be reopened.
This surely does not work as intended. I agree with Ramon that this is a bug and should be reopened.
On Android devices, please go to (system not Minecraft) Settings > General >Application manager and slide to the running tab. To raise the render distance Minecraft needs aprox. 700 MB of free ram. I found this applies to my Samsung Galaxy Tab 4 which is much less powerful than the Note 8 and iPhone 8. If you have more than 700MB of free RAM and are still stuck at 6 chuncks, ticket may be reopened.
On Android devices, please go to (system not Minecraft) Settings > General >Application manager and slide to the running tab. To raise the render distance Minecraft needs aprox. 700 MB of free ram. I found this applies to my Samsung Galaxy Tab 4 which is much less powerful than the Note 8 and iPhone 8. If you have more than 700MB of free RAM and are still stuck at 6 chuncks, ticket may be reopened.
On Android devices, please go to (system not Minecraft) Settings > General >Application manager and slide to the running tab. To raise the render distance Minecraft needs aprox. 700 MB of free ram. I found this applies to my Samsung Galaxy Tab 4 which is much less powerful than the Note 8 and iPhone 8. If you have more than 700MB of free RAM and are still stuck at 6 chuncks, ticket may be reopened.
On Android devices, please go to (system not Minecraft) Settings > General >Application manager and slide to the running tab. To raise the render distance Minecraft needs aprox. 700 MB of free ram. I found this applies to my Samsung Galaxy Tab 4 which is much less powerful than the Note 8 and iPhone 8. If you have more than 700MB of free RAM and are still stuck at 6 chuncks, ticket may be reopened.
6 chunks shouldn't even be an option as you are just playing in a constant fog. This is a bug and probably has something to to do with the vast amount of space/memory that Microsoft requires for a dump file now. No point as I cannot play it like this anyway. Boy, I wish I hadn't taken the upgrade....
6 chunks shouldn't even be an option as you are just playing in a constant fog. This is a bug and probably has something to to do with the vast amount of space/memory that Microsoft requires for a dump file now. No point as I cannot play it like this anyway. Boy, I wish I hadn't taken the upgrade....
6 chunks shouldn't even be an option as you are just playing in a constant fog. This is a bug and probably has something to to do with the vast amount of space/memory that Microsoft requires for a dump file now. No point as I cannot play it like this anyway. Boy, I wish I hadn't taken the upgrade....
6 chunks shouldn't even be an option as you are just playing in a constant fog. This is a bug and probably has something to to do with the vast amount of space/memory that Microsoft requires for a dump file now. No point as I cannot play it like this anyway. Boy, I wish I hadn't taken the upgrade....
iPad Air running iOS 11 also has the 6 chunks issue, when it could run 14 chunks easily before the 1.2 update.
iPad Air running iOS 11 also has the 6 chunks issue, when it could run 14 chunks easily before the 1.2 update.
iPad Air running iOS 11 also has the 6 chunks issue, when it could run 14 chunks easily before the 1.2 update.
iPad Air running iOS 11 also has the 6 chunks issue, when it could run 14 chunks easily before the 1.2 update.
An iPhone 7 or newer device shouldn't be regressed to a 6 chunk render distance. They may not have 8GB ram, but they are certainly capable of rendering three times the number of chunks. Besides, if it's based off performance or memory, why does my 8GB OnePlus 5 limit to 22 chunks and my 16GB PC with a GTX 1080 limit to 60 chunks? Something screwy is going on, but I can't see it with all this fog.
An iPhone 7 or newer device shouldn't be regressed to a 6 chunk render distance. They may not have 8GB ram, but they are certainly capable of rendering three times the number of chunks. Besides, if it's based off performance or memory, why does my 8GB OnePlus 5 limit to 22 chunks and my 16GB PC with a GTX 1080 limit to 60 chunks? Something screwy is going on, but I can't see it with all this fog.
An iPhone 7 or newer device shouldn't be regressed to a 6 chunk render distance. They may not have 8GB ram, but they are certainly capable of rendering three times the number of chunks. Besides, if it's based off performance or memory, why does my 8GB OnePlus 5 limit to 22 chunks and my 16GB PC with a GTX 1080 limit to 60 chunks? Something screwy is going on, but I can't see it with all this fog.
An iPhone 7 or newer device shouldn't be regressed to a 6 chunk render distance. They may not have 8GB ram, but they are certainly capable of rendering three times the number of chunks. Besides, if it's based off performance or memory, why does my 8GB OnePlus 5 limit to 22 chunks and my 16GB PC with a GTX 1080 limit to 60 chunks? Something screwy is going on, but I can't see it with all this fog.
Issue exists in 1.2.1. I’m pretty sure an iPhone 7 Plus runs 22 chunks since I saw that on my cousins’ phones, and that thing has 3 GB of ram! This has to be a bug and needs to be addressed.
Issue exists in 1.2.1. I’m pretty sure an iPhone 7 Plus runs 22 chunks since I saw that on my cousins’ phones, and that thing has 3 GB of ram! This has to be a bug and needs to be addressed.
Issue exists in 1.2.1. I’m pretty sure an iPhone 7 Plus runs 22 chunks since I saw that on my cousins’ phones, and that thing has 3 GB of ram! This has to be a bug and needs to be addressed.
Issue exists in 1.2.1. I’m pretty sure an iPhone 7 Plus runs 22 chunks since I saw that on my cousins’ phones, and that thing has 3 GB of ram! This has to be a bug and needs to be addressed.
Please confirm that you have at least 700 Mb free of RAM to reopen. Just because an iPhone has 3 Gb of RAM does not mean that there is enough free RAM for Minecraft to expand its render distance as RAM can be taken up by the OS, open apps and other system needs. As far as some of the Developers are aware, RAM is the only thing checked for Render distance. Specs are not checked. Please confirm sufficient RAM to reopen report.
Please confirm that you have at least 700 Mb free of RAM to reopen. Just because an iPhone has 3 Gb of RAM does not mean that there is enough free RAM for Minecraft to expand its render distance as RAM can be taken up by the OS, open apps and other system needs. As far as some of the Developers are aware, RAM is the only thing checked for Render distance. Specs are not checked. Please confirm sufficient RAM to reopen report.
Please confirm that you have at least 700 Mb free of RAM to reopen. Just because an iPhone has 3 Gb of RAM does not mean that there is enough free RAM for Minecraft to expand its render distance as RAM can be taken up by the OS, open apps and other system needs. As far as some of the Developers are aware, RAM is the only thing checked for Render distance. Specs are not checked. Please confirm sufficient RAM to reopen report.
Please confirm that you have at least 700 Mb free of RAM to reopen. Just because an iPhone has 3 Gb of RAM does not mean that there is enough free RAM for Minecraft to expand its render distance as RAM can be taken up by the OS, open apps and other system needs. As far as some of the Developers are aware, RAM is the only thing checked for Render distance. Specs are not checked. Please confirm sufficient RAM to reopen report.
Please Note: This bug report is explaining that the Render distance is lowered compared to previous updates. This is true and previous updates have required more RAM to stabilize and enhance the game with new features. Thus Minecraft needs more RAM to expand the Render distance which is not a bug if you do not have enough RAM. This ticket has been resolved as Working As intended for that reason. If you can show that Minecraft's render distance is blocked by somethingbother than RAM, please do so here.
Some tips for clearing RAM:
Delete unused and uneeded apps that can use up background RAM
On Android go to Settings > General > App Manager > and slide to the running tab to see whichbapps are taking up RAM.
Please Note: This bug report is explaining that the Render distance is lowered compared to previous updates. This is true and previous updates have required more RAM to stabilize and enhance the game with new features. Thus Minecraft needs more RAM to expand the Render distance which is not a bug if you do not have enough RAM. This ticket has been resolved as Working As intended for that reason. If you can show that Minecraft's render distance is blocked by somethingbother than RAM, please do so here.
Some tips for clearing RAM:
Delete unused and uneeded apps that can use up background RAM
On Android go to Settings > General > App Manager > and slide to the running tab to see whichbapps are taking up RAM.
Please Note: This bug report is explaining that the Render distance is lowered compared to previous updates. This is true and previous updates have required more RAM to stabilize and enhance the game with new features. Thus Minecraft needs more RAM to expand the Render distance which is not a bug if you do not have enough RAM. This ticket has been resolved as Working As intended for that reason. If you can show that Minecraft's render distance is blocked by somethingbother than RAM, please do so here.
Some tips for clearing RAM:
Delete unused and uneeded apps that can use up background RAM
On Android go to Settings > General > App Manager > and slide to the running tab to see whichbapps are taking up RAM.
Please Note: This bug report is explaining that the Render distance is lowered compared to previous updates. This is true and previous updates have required more RAM to stabilize and enhance the game with new features. Thus Minecraft needs more RAM to expand the Render distance which is not a bug if you do not have enough RAM. This ticket has been resolved as Working As intended for that reason. If you can show that Minecraft's render distance is blocked by somethingbother than RAM, please do so here.
Some tips for clearing RAM:
Delete unused and uneeded apps that can use up background RAM
On Android go to Settings > General > App Manager > and slide to the running tab to see whichbapps are taking up RAM.
Render distance is always 6 chucks for me on iPhone 7, regardless of whether I have other apps open in the background. It has to be a bug!
Render distance is always 6 chucks for me on iPhone 7, regardless of whether I have other apps open in the background. It has to be a bug!
Render distance is always 6 chucks for me on iPhone 7, regardless of whether I have other apps open in the background. It has to be a bug!
Render distance is always 6 chucks for me on iPhone 7, regardless of whether I have other apps open in the background. It has to be a bug!
While some say this isn’t a bug, something isn’t right. I have an iPhone 6S and an IPad Pro, and both are stuck on 6 chunks. I found on the wiki that 6 chunks is the limit for low end devices, but I don’t think a IPad Pro is low end. I can get it to 14 chunks sometimes if I completely restart it, and it runs just fine.
While some say this isn’t a bug, something isn’t right. I have an iPhone 6S and an IPad Pro, and both are stuck on 6 chunks. I found on the wiki that 6 chunks is the limit for low end devices, but I don’t think a IPad Pro is low end. I can get it to 14 chunks sometimes if I completely restart it, and it runs just fine.
While some say this isn’t a bug, something isn’t right. I have an iPhone 6S and an IPad Pro, and both are stuck on 6 chunks. I found on the wiki that 6 chunks is the limit for low end devices, but I don’t think a IPad Pro is low end. I can get it to 14 chunks sometimes if I completely restart it, and it runs just fine.
While some say this isn’t a bug, something isn’t right. I have an iPhone 6S and an IPad Pro, and both are stuck on 6 chunks. I found on the wiki that 6 chunks is the limit for low end devices, but I don’t think a IPad Pro is low end. I can get it to 14 chunks sometimes if I completely restart it, and it runs just fine.
Reopening based on developer input. It should be based on total RAM not available RAM
Reopening based on developer input. It should be based on total RAM not available RAM
Reopening based on developer input. It should be based on total RAM not available RAM
Reopening based on developer input. It should be based on total RAM not available RAM
Closed as Duplicate of MCPE-24148 As MCPE-24148 has information attached to it internally about the issue.
Closed as Duplicate of MCPE-24148 As MCPE-24148 has information attached to it internally about the issue.
Closed as Duplicate of MCPE-24148 As MCPE-24148 has information attached to it internally about the issue.
Closed as Duplicate of MCPE-24148 As MCPE-24148 has information attached to it internally about the issue.