Search Issue Tracker
Fixed
Fixed in 2021.3.30f1, 2022.3.11f1, 2023.1.11f1, 2023.2.0b7, 2023.3.0a6
Votes
0
Found in
2021.3.18f1
2022.2.11f1
2023.1.0b8
2023.2.0a6
Issue ID
UUM-30210
Regression
No
Different numbers are logged from a fixed float array of numbers compared to the numbers that were added to the array if using the ARM64 architecture editor
How to reproduce:
1. Open the user’s attached “Fixed Array Test.zip” project
2. Enter Play Mode
3. Observe the console window
Expected result: Numbers before and after “=“ are the same
Actual result: Numbers before and after “=“ are not the same
Reproducible with: 2021.3.18f1, 2022.2.11f1, 2023.1.0b8, 2023.2.0a6
Could not test with: 2020.3.46f1 (No ARM64 architecture)
Reproduced on: macOS (13.0 Beta) (M1)
Not reproduced on: macOS 13.2.1 (Intel)
Note: Not reproducible with X64 architecture editors
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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Resolution Note (fix version 2023.3.0a6):
Fixed in: 2023.3.0a6
Resolution Note (fix version 2023.2.0b7):
Fixed in: 2023.2.0b7
Resolution Note (fix version 2023.1.11f1):
Fixed in: 2023.1.11f1
Resolution Note (fix version 2022.3.11f1):
Fixed in: 2022.3.11f1
Resolution Note (fix version 2021.3.30f1):
Fixed in: 2021.3.30f1