Search Issue Tracker
Fixed in 2021.2.X
Votes
0
Found in
2019.4
2020.2
2021.1
2021.1.0b4
2021.2
Issue ID
1310994
Regression
No
Assembly Definition Use GUIDs value reverts to previous value when applied with no References
Reproduction steps:
1. Open the attached project ("MultiASMDEFBug.zip")
2. Open "AssemblyOne.asmdef" asset in Inspector window
3. Tick Use GUIDs to false, press apply
4. Open different asset in Inspector and return back to "AssemblyOne.asmdef"
Expected result: Use GUIDs is false
Actual result: Use GUIDs reverts to true
Reproducible with: 2019.4.21f1, 2020.2.5f1, 2021.1.0b7, 2021.2.0a5
Could not test with: 2018.4.32f1 (no Use GUIDs option)
Note:
- If reference is set Use GUIDs works as expected
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- APV data is sometimes incorrectly loaded from multiple baking sets when loading a scene
- GC Alloc spikes occur when calling UnityEngine.Resolution and UnityEngine.RefreshRate with Equals() and GetHashCode()
- Type error is thrown when a new ComputeShader is instantiated after destroying previous ComputeShader
- APV data becomes incorrect when reselecting the currently active Baking Set
- Launch screen image exceeds the screen bounds on IPad when building for iOS
Add comment