Search Issue Tracker
Won't Fix
Won't Fix in 1.8.X
Votes
0
Found in [Package]
1.8.0-pre.2
1.8.0
Issue ID
BUR-2075
Regression
No
[macOS] Builds don't use Burst when generated via "Create Xcode Project"
How to reproduce:
1. Open the attached “StandaloneBurstTest“ project
2. Build the project with “Create Xcode Project”, “Development Build” and “Autoconnect Profiler” enabled
3. Open the “build.xcodeproj” file in the build folder
4. Run the build
5. Open the Editor window (select “Window” → “Analysis” → “Profiler” in the main menu if the Profiler did not open automatically)
6. Click on any frame
7. Observe the length of the PlayerLoop() call
Expected result: The call takes 1-10ms to execute (Burst works)
Actual result: The call takes 15-30ms to execute (Burst doesn’t work)
Reproducible with: 1.8.0-pre.2 (2020.3.40f1, 2021.3.11f1, 2022.1.19f1, 2022.2.0b10), 1.8.0 (2023.1.0a13)
Reproducible on: macOS 12 beta (Apple M1)
Note: Doesn’t reproduce in the Editor or in non-Xcode builds
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
- Weight Brush Overlay text is clipped in Sprite Editor
- GameObject Transform scale values reset to their previously saved values when proportions are constrained and certain decimal values are entered in the Inspector
- Asset thumbnails in the Project window stay white when a referenced texture file is deleted and restored
- Crash on PersistentManager::ReadObjectThreaded when calling AssetDatabase.ForceReserializeAssets() multiple times in a row
- Scene becomes dirty when first opening an HDRP Template project
Resolution Note:
This is a known and documented technical limitation:
https://docs.unity3d.com/Packages/com.unity.burst@1.8/manual/building-projects.html#projects-that-dont-use-burst
Resolution Note (1.8.X):
This is a known and documented technical limitation:
https://docs.unity3d.com/Packages/com.unity.burst@1.8/manual/building-projects.html#projects-that-dont-use-burst