Search Issue Tracker
Fixed in 4.3.X
Votes
0
Found in
Issue ID
559952
Regression
Yes
Changing script on a monobehavior breaks the component editor
Repro:
1) Add a script to e.g the Main Camera
2) Change the script using ObjectSelector
3) Notice that the cogwheel disappears and context menu is not available on right click.
We found that the editor.target is null for this editor (component) and that the regression is caused by b51b8ace823c ("Fix monobehaviour == null returning true if there is a monobehaviour with that instanceID but it is not actually referencing the right object. case 539463")
Outcommenting the following in ScriptingObjectOfType.h fixes this issue:
if (temp->GetClassID() == ClassID(MonoBehaviour))
return false;
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
Add comment