Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.31f1
2022.3.12f1
2023.1.18f1
2023.2.0b15
2023.3.0a11
Issue ID
UUM-54194
Regression
No
Script incorrect calculation results in Player when Intel 64-bit Architecture is selected on a macOS Silicon device with Development Build and Script Debugging settings turned off
Reproduction steps:
1. Open the attached "PROJECTFILE" project
2. Open the Build Settings window (File > Build Settings)
3. Select the “Intel 64-bit” Architecture
4. Make sure that Development Build and Script Debugging is turned off in the Build Settings
5. Build And Run
5. Observe the Player
Expected result: Calculations are correct, “Expected result: 78.059906. Actual result: 78.059906” is visible in the Player
Actual result: Calculations are incorrect, “Expected result: 78.059906. Actual result: 0” is visible in the Player
Reproducible with: 2021.3.31f1, 2022.3.12f1, 2023.1.18f1, 2023.2.0b15, 2023.3.0a11
Reproducible on: macOS Ventura 13.6 (M1 Max)
Not reproducible on: macOS Sonoma 14.0 (Intel)
Note:
-Issue is reproducible only when the Intel 64-bit Architecture is selected on a macOS Silicon device with Development Build and Script Debugging settings turned off
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
After investigating this appears to be isolated to only running intel x64 binaries within the Rosetta emulation on MacOS arm64 devices. As with other issues discovered in this area the recommended fix is to run binaries that are native to the architecture to avoid emulation.