Search Issue Tracker
Won't Fix
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
- "Draw Additional Lights Shadowmap" calls increase when custom MaterialBlockProperty is used
- Crash on _platform_memmove when importing the "Dragon Crashers - URP 2D Sample Project" to a new 2D project
- "Shader is not supported on this GPU" warnings and and shaders are not loading when building the project for non-Chromium browsers
- [iOS][URP] The screen flickers and the "Execution of the command buffer was aborted due to an error during execution" error is thrown continuously
- Shortcut Manager shows empty conflict filter when resolving runtime conflicts involving different contexts
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