Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
1.2.16
Issue ID
1131867
Regression
No
[YAMLMerge] Tilemaps aren't updated correctly and sometimes display random Tiles from the Palette when downloaded from Collab
How to reproduce:
1. Open attached project (tilemap.zip)
2. Setup Collaboration
3. Change the way the Tiles are laid out in the Tilemap
4. Have another person change the Tiles too on his computer, but completely differently
5. One person should publish the Collab changes
6. Other person should download them and merge them with the current changes
7. Check that the downloaded Tilemap isn't the one that was submitted
8. Sometimes selected Tile can completely change into a different one
Reproducible with: 2017.4.22f1, 2018.3.8f1, 2019.1.0b6, 2019.2.0a7
Actual results: Tilemaps aren't updated correctly, and might change to a different one once selected
Expected results: Tilemaps should look exactly the same like the other person submitted, and they shouldn't randomly change once selected
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
Due to the age and low user pain of the issue, we are closing this as Won't Fix. We apologize for any inconvenience this may cause.