Search Issue Tracker
Fixed in 5.6.0
Votes
0
Found in
5.3.4f1
Issue ID
809590
Regression
No
Asset Database only handles one of multiple colliding GUIDs
Materials in the project have colliding GUIDs. Simplest repro:
1. From Finder/Explorer, duplicate an asset twice (together with .meta)
2. Go back to Unity and notice that
- one of the new duplicate assets has been detected as a duplicate GUID and re-assigned
- the other one is left with a colliding GUID. this will eventually result in broken references, e.g. when exporting as a package (user case).
Reproducible: 5.2.4.f1, 5.3.4f1, 5.3.5p5, 5.4.0b24
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Add comment