Search Issue Tracker
Fixed
Fixed in 1.6.7, 1.7.4, 1.8.0-pre.2
Votes
1
Found in [Package]
1.6.6
1.7.3
1.8.0-pre.1
Issue ID
BUR-1900
Regression
Yes
Burst does not recompile Scripts when they have been compiled once before
Reproduction steps:
1. Open the attached project
2. Open the "Procedural Mesh.unity" Scene located in the /Assets/Scenes folder
3. Make sure "Enable Compilation" is enabled under Jobs > Burst in the Toolbar
4. Enter the Play Mode and observe the Square Grid in the Scene view
5. Uncomment Line 52 in the SharedSquareGrid.cs Script, located in /Assets/Scripts/Procedural Meshes/Generators folder
6. Enter the Play Mode and observe the Square Grid in the Scene view
Expected result: a lot of triangles should be seen in the Square Grid
Actual result: the Square Grid has not changed
Reproducible with: 1.6.0-pre.2, 1.6.6, 1.7.3, 1.8.0-pre.1 (2020.3.36f1, 2021.3.5f1, 2022.1.7f1), 1.7.3, 1.8.0-pre.1 (2022.2.0a18, 2023.1.0a1)
Not reproducible with: 1.4.11, 1.5.6 (2020.3.36f1, 2021.3.5f1, 2022.1.7f1)
Could not test with: 2019.4.39f1 (MeshData struct is not present)
Reproducible on: Windows 10 (21H2)
Note: using 2022.2.0a18 and 2023.1.0a1 Editor versions, I was not able to downgrade Burst below 1.7.2, but the issue is still present
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Crash on ResizeScriptingList<ScriptingObjectPtr> when passing an undeclared variable to the results parameter for GameObject.FindGameObjectsWithTag
- [Android] "Screen.safeArea.y" always returns values outside of the Safe Area when the device is in Portrait orientation
- Frame spike due to many TreeRenderer.TreeUpdated calls when repositioning terrains in large Scenes
- Crash on GameObject::RemoveComponentFromGameObjectInternal when reparenting Text GameObjects
- [IL2CPP-GarbageCollector] Changing GCMode might permanently disable GC in a multithreaded context
Add comment