Search Issue Tracker
By Design
Votes
0
Found in
2017.2.0b1
Issue ID
923312
Regression
No
Overwriting tiles in the tile palette leaves dead tiles in the palette that cannot be used
This is actually a misunderstanding of how it works. Some explanation:
- Palette only has Tiles, never Sprites or Textures
- If you drag in Sprite or Texture, a new Tile asset is generated. You get to choose the save path in a dialog.
- Palette can have the same tile multiple times.
What happens in the video:
1. You have an existing tile (A) in the palette
2. You drag in a sprite
3. Unity wants to generate new Tile (B) based on your Sprite
4. For your new Tile (B), you choose the path of an already existing Tile (A)
(5. All existing references to old tile (A) seem to break, but a ghosts still persists.)
I think the step #5 reveals a bug about how tilemap doesn't handle missing references optimally, but we will make a new fogbugz for that.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- ProfilingSampler.Get() returns null and makes the Player only render black when building a Release Build
- Search text field visual controls for the Path binding in an Input Actions Asset is misaligned
- Display issues in VideoPlayer when using Screen.SetResolution on certain Google Pixel devices
- Crash on Texture::TextureIDMapInsert when opening a specific project
- Null reference exceptions occur when ScriptableObjects saved in the same .asset file are referenced in runtime
Add comment