Search Issue Tracker
Active
Under Consideration for 6000.5.X
Votes
0
Found in
6000.0.63f1
6000.2.14f1
6000.3.0f1
6000.4.0a5
6000.5.0a2
Issue ID
UUM-127884
Regression
No
"Type Mismatch" is shown instead of the Monobehavior reference when it is added during Play Mode through a function
How to reproduce:
- Create and open a new project
- Import the “SOReferenceBug.unitypackage” package into the Project tab
- Open the “Foobar“ Scene
- Enter Play Mode
- Select the “New Bar“ ScriptableObject in the Project tab
- Observe the “Foo“ field value
Expected result: The value references the “GameObject” in the Scene
Actual result: The value is displayed as “Type mismatch“
Reproducible in: 2023.1.0a1, 6000.0.63f1, 6000.2.14f1, 6000.3.0f1, 6000.4.0a5, 6000.5.0a2
Reproduced on: Windows 11 Pro (24H2)
Not reproduced on: No other environment tested
Note: The “Type Mismatch” seems to be only a visual bug, as the referenced object still can be highlighted by pressing on the field, and logic can be executed in the referenced object
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “FMOD failed to set the software format to the custom sample rate…” warnings are thrown as System Sample Rate value is being changed in Audio section of Project Settings window
- VFX Marquee selection does match the visual indicator
- “Invalid AABB aabb” errors are spammed when “Infinity” value is entered in Collider Component fields
- Editor Role does not sync with the MPPM Play Mode Scenario Role when entering Play mode
- Long asset names cause overlap with the “Find” function in search result tabs
Add comment