MCPE-20718New created worlds do not enter when their rendering distance is at least 4
Steps to Reproduce
1.When we create New Worlds on the loading screen they do not enter when their rendering distance is at least 4
Linked Issues
Attachments1
Created Issue:
Created worlds do not load when it is on the world's construction screen instead of simply loading the screen stays frozen
Steps to Reproduce
1.When we make a world that does not enter when it is on the world construction screen (load bar) instead of when the bar load you enter the world, it happens that the screen is frozen
Obs: This Bug is happening in version 1.1.0.0
Steps to Reproduce
1.When we
make a world that does not enter when it is on the world construction screen (load bar) instead of when the bar load youenterthe world, it happens that the screen is frozenObs: This Bug is happening in version 1.1.0.0
Steps to Reproduce
1.When we create New Worlds on the loading screen they do not enter when their rendering distance is at least 4
Obs: This Bug is happening in version 1.1.0.0
Created worlds do notload when it is on the world's construction screen instead of simply loading the screen stays frozenNew created worlds do not enter when their rendering distance is at least 4
Steps to Reproduce
1.When we create New Worlds on the loading screen they do not enter when their rendering distance is at least 4
Obs: This Bug is happening in version 1.1.0.0
![[Mojang] Adrian Östergård](../../../data/assets/gravatar/nighter.jpeg){kind=small}
is duplicated by
This Bug is happening in version 1.1.0.0
![[Mojang] Mega_Spud (Jay Wells)](../../../data/avatars/users/92696.png){kind=small}
is duplicated by
relates to
Duplicate of MCPE-20718
Bugs confirm MCPE-20718 i try this and it works 
Duplicate of MCPE-20718
Maybe this will help you fix the bug MCPE-20718
It only happens when your render distance is at minimum(4).
This bug still seems to happen in 1.1.0.1 (Device: Samsung Galaxy Tab 3V, with 4.4.4. Kitkat)
Thanks on this now i know and i can play may world again 😊
This has been reported as fixed in an earlier version.