Search Issue Tracker
Won't Fix
Won't Fix in 1.8.X
Votes
0
Found in [Package]
1.8.8
Issue ID
BUR-2518
Regression
No
Burst fails to resolve the correct variant of precompiled assemblies when multiple versions are subject to Define Constraints
Reproduction steps:
1. Open the attached "PROJECTFILE" project
2. Make sure that Burst compilation is enabled (Jobs > Burst > Enable Compilation)
3. In Project Settings, observe that Scripting Define Symbols “VERSION2” is defined
4. In the Menu bar, select “Log Version” (“Test” > “Log Version”)
5. Observe the Console
6. In the Menu bar select “Log Version From Burst” (“Test” > “Log Version From Burst”)
7. Observe the Console
Expected result: Console displays “VERSION2” both times
Actual result: Console displays “VERSION1” when “Log Version From Burst” is clicked
Reproducible with: 1.6.6, 1.7.4, 1.8.8 (2021.3.30f1, 2022.3.9f1, 2023.1.12f1, 2023.2.0b9, 2023.3.0a5)
Reproducible on: macOS 13.4.1 (M1 Max)
Not reproducible 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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note:
There are no fixes planned for this Bug
Resolution Note (1.8.X):
Burst does not currently support precompiled assemblies.
If you try the repro but with non-precompiled assemblies it works as expected.