Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.3.0f3
Issue ID
989529
Regression
No
MonoBehaviours with identical names but different Namespaces attached to the same object cannot be referenced in Inspector
Steps to reproduce:
1. Open attached “ReferenceTest.zip” Unity project
2. Open “Main” scene
3. Select “References” object in Hierarchy
4. Drag “GameObject” object from Hierarchy onto both “Test 1” and “Test 2” script references in Inspector
Expected results:
Both scripts are successfully referenced
Actual results:
One of the scripts cannot be referenced
Reproduced in: 2018.2.0a1, 2018.1.0b4, 2017.3.0p3, 2017.2.1p2, 2017.1.3f1, 2017.1.0a1
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
- “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
Resolution Note:
This particular case has been investigated thoroughly and we have decided, in the interests of protecting the stability and features of Unity for users that rely upon the affected versions, to not address this fix for the time being. We understand that this will cause problems for some users, and so may address in a future version.