Search Issue Tracker
By Design
Votes
0
Found in [Package]
1.8.12
Issue ID
BUR-2604
Regression
No
“no Burst” and “SubtractTerrainBakerJob” warnings are thrown when reimporting subscenes
How to reproduce:
1. Open the “NoBurstIssue“ project
2. Open the “Assets/GameProject/Scenes/MainGame.unity” scene
3. Wait until all Background Tasks are completed
4. In the Hierarchy window select the “GeneratedEnvironment” subscene
5. In the Inspector within the “Sub Scene” script Component select the “Reimport All” button then select “Yes”
6. Observe the Console
Expected result: No warnings are thrown
Actual result: Multiple “no Burst” and “SubtractTerrainBakerJob” warnings are thrown
Reproduced with: 1.8.12 (2023.2.7f1, 2023.3.0b4)
Could not test with: 1.8.9 (2022.3.18f1) (Could not resolve compilation errors), 1.8.11 (2021.3.34f1) (Project is using the Entities package which is unsupported)
Reproduced on: Windows 10 (by reporter), Windows 11
Not reproduced on: No other environment tested
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
- Default Preset application and Reset() method execution order is different when adding a Component via the Inspector versus calling Reset via the Component context menu
- Scene view is not outputting HDR when the "Use HDR Display Output" option is enabled, DX12 is selected as the Graphics API, and URP/HDRP is in use
- Sprite Atlas results in suboptimal packing even when "Allow Rotation" is enabled
- References placed in a UnityEvent change to the same reference when multi-selecting their GameObjects
- "ShadowCaster2D" Component doesn't work when the "Casting Source" is set to "Polygon Collider 2D"
Resolution Note:
I'm going to close this as as-designed, because it is the (current) expected behaviour, for asset import workers to run without Burst compilation. It's an unfortunate limitation that we hope to address in the future.