Search Issue Tracker
Won't Fix
Votes
1
Found in
2021.3.7f1
2022.1.11f1
2022.2.0a18
2023.1.0a4
Issue ID
UUM-10178
Regression
Yes
[M1] Cinemachine Group Composer has different behavior when the Editor is at Debug or Release mode
Reproduction steps:
- Open the attached project
- Observe the “Main Camera” GameObject’s position in the Game View or the Scene View
- Select the Debug Button in the bottom right of the Unity Editor Status Bar
- Select “Switch to debug mode”
- Observe the “Main Camera” GameObject’s position in the Game View or the Scene View
Expected result: The “Main Camera” GameObject is further away from the cube when the Editor is in Release mode
Actual result: The “Main Camera” GameObject is inside the cube when the Editor is in Release mode
Reproducible with: 2021.2.0a14, 2021.2.19f1, 2021.3.7f1, 2022.1.11f1, 2022.2.0a18, 2023.1.0a1, 2023.1.0a4
Not reproducible with: 2019.4.40f1, 2020.3.37f1, 2021.2.0a13, 2022.2.0a19, 2022.2.0b3
Reproducible on: M1 MacOS 12.4 (21F79)
Not reproducible on: Intel MacOS 12.4
Note: This issue is only reproducible on the Intel Editors running through Rosetta on M1 MacOS
Comments (1)
-
Yuchen_Chang
Dec 09, 2022 08:45
Hello! I've more information for this bug.
There is some really weird issue in CinemachineGroupComposer.cs line-217, that the calculation of a local variable named "targetDistance" is sometimes totally skipped (set to 0), if you don't "monitor" it. By "monitor", I mean Debug.Log() it, or set a break-point and check it's value.
It's a local variable (not a property with getter), so whether I monitor it or not, the value should not be changed. There is no "if()" or any other thing bothering the calculation, so I think it is some sort of compiler problem (or something similar).
(only happens in M1 mac + Intel Unity Editor (Rosetta) + release mode)A whole explanation can be seen under this unity forum post:
https://forum.unity.com/threads/target-group-composer-with-dolly-has-a-weird-issue.1344227/#post-8523881
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
- Dragging and dropping a system that contains event context to create nested VFX crashes the editor
- TextMeshPro UV2 custom data not rendering for off-screen text with RectMask2D in Unity 6
- Text overlap and is unreadable in Inspector > Terrain Paint Texture after creating new Terrain Layer
- Event "XRInputSubsystem.trackingOriginUpdated" triggers twice when recentering the view
- UITK TextField value is overwritten incorrectly by the converter result when Binding Mode is set to "To Source"
Resolution Note:
We suspect this is a bug in the Mono JIT, Rosetta, or the interaction between the two of them. We don't plan to correct this.