Search Issue Tracker

Won't Fix

Votes

0

Found in [Package]

1.4.8

Issue ID

BUR-1749

Regression

No

"ProcessTile (Burst)" Jobs are replaced with "ProcessTile" Jobs when the build is made with Xcode

Package: Burst

-

Reproduction steps:
1. Open the user's attached "NoMacBurstRepro.zip" project
2. In the Build settings select "PC, Mac & Linux Standalone" Platform
3. Enable "Create Xcode Project", "Development Build" and "Autoconnect Profiler"
4. Build
5. Open the Built project with Xcode and launch it
6. Go to Window > Analysis > Profiler and select CPU Usage Module
7. Select a frame and in the Timeline expand the Jobs section

Expected result: Jobs section in the Profiler is scheduling "ProcessTile (Burst)" jobs
Actual result: Jobs section in the Profiler is scheduling "ProcessTile" jobs

Reproducible with: 1.3.0-preview.10 (2020.3.32f1), 1.4.8 (2019.4.37f1, 2020.3.32f1), 1.6.4 (2021.2.17f1), 1.7.0 (2020.3.32f1, 2022.1.0b14, 2022.2.0a9)
Could not test with: 1.3.0-preview.9 and lower (build fails)

Notes:
- The expected result can be observed by disabling "Create Xcode Project" in the 2nd step
- Or the expected result can be observed by uncommenting the MacBurst.cs (Assets/Scripts/Editor/MacBurst.cs) file's content and by following all the steps

  1. Resolution Note:

    Burst doesn't support (and actually has never supported) building from a generated Xcode project. We've added it to our known issues for the next Burst release. There is a workaround: manually copying the Burst-generated bundle from the Xcode build directory into the final output app bundle.

Log in to vote on this issue

Comments (1)

  1. AndyJB_Unity

    Apr 04, 2022 10:16

    A sample script showing how to to copy the Burst-generated code into the app bundle.
    https://gist.github.com/AndyJB-Unity/bdd5e0d80084a171e45cab0aabfb88f5

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.

Latest issues

See all new issues