Search Issue Tracker
Fixed in 2022.2.X
Fixed in 2020.3.X, 2021.2.X, 2022.1.X
Votes
0
Found in
2020.2.0b14
2020.3
2020.3.25f1
2021.2
2022.1
2022.2
Issue ID
1396529
Regression
No
"UnityEngine.SystemInfo.processorFrequency" value in M1 Macs is 0 in Player
How to reproduce:
1. Open attached project "M1Frequency.zip"
2. Go to Build Settings and build
3. Open the Player and observe the number
Expected result: Processor Frequency is 2400
Actual result: Processor Frequency is 0
Reproducible with: 2020.2.0b14, 2020.2.7f1, 2020.3.25f1, 2021.2.7f1, 2022.1.0b2, 2022.2.0a2
Not reproducible with: 2019.4.34f1
Could not test with: 2020.2.0b13 (Crash when opening Player)
Note: Reproducible in the Player, not reproducible in the Editor
Note: Only backport to 2020.3 as that's the first LTS with Apple Silicon support
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 (fix version 2022.2):
Fixed in: 2022.2.0a5
Resolution Note (fix version 2022.1):
Fixed in: 2022.1.0b10
Resolution Note (fix version 2021.2):
Fixed in: 2021.2.13f1
Resolution Note (fix version 2020.3):
Fixed in: 2020.3.31f1