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
- The previous element in the array is modified when assigning an Asset to a new element of AssetReferenceT
- Unity Perforce Integration: VCS Connection Active State Fails via CLI with Valid Inputs
- Joint Gizmos for anchor and connectedAnchor do not respect their defined bodies when Swap Bodies is enabled
- Project Settings window opens up with a blank details pane when the "Configure" button is clicked in the Package Manager after installing the Cloud Diagnostics package
- [UI Builder] Viewport's gizmos for Margin and Padding disappear when dragging to modify the value and the cursor leaves the Spacing section
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.