when enlarging a map all data is deleted and/or shows incorrect location. on Samsung Galaxy s7
Linked issues
is duplicated by 3
Attachments
Comments 4
This is NOT a dupe of MC-16948. Please reopen this.
@unknown If you wish to discuss this issue further and get community support, may I suggest taking it to a forum environment: https://redd.it/5njy8a
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Feedback – 📖 Game Wiki
First noted 0.16.0, persists in 1.0.0 MCPE Realms, iOS 10.2, iPhone 6s. Zoom 0 maps work fine, and you can add compasses and rename them. When you resize to zoom 1, they are blank in the area where the small map was created. If you resize to to zoom 2, and the map's center is changed to (0,0) , regardless of where they were created or resized (please see attached). (The zoom 2 map containing (0,0) should center at (192,192)). Resize to zoom 3 and 4, they are blank again. I have not been able to determine where the centers for Zoom 1,3,and 4 are, if they work at all. Oddly, this only happens in Realms (see attached for difference in single player/local vs Realms). In the same seed on single player, the maps work as expected. As a result, in MCPE Realms (survival mode) the only useable maps are zoom 0, and one location of a zoom 2 map.
Same problem with resizing (note that all map data is supposed to be deleted when resizing):
I can create a map which draws successfully, and added a compass to it, but when I resize the map with an anvil (in the same spot I created it) and view it, the map stays blank. Bug persists up to maximum zoom. I tried moving around, but no drawing. Dropped map and picked it back up, put it in a chest, renamed it - nothing works. Repeated this error three times. In two instances, at zoom level 2, the maps resized maps recentered to Spawn quadrant, which was 2 full (level 2) maps away (to the right/south-if sun rises east). The Level 4 zoom map seems to have a different location I have not found. This is on a Realms server, survival, iPhone 6s, iOS 10.0.2.
Duplicated by MCPE-18393, MCPE-18751, MCPE-18764. Dupe of problem mentioned in comments of MCPE-16948 (though original complaint seems to be works as intended.)