Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
0
Found in
5.4.3p1
Issue ID
854279
Regression
Yes
Unity crashed on applying layer linker settings after re-compiling and re-importing Weaver dlls
Steps to reproduce:
1. Open attached project
2. Open Weaver pro solution in VS (case_85196-Kybernetik\Source Code\Weaver pro)
3. Open Window -> Weaver -> Layer Linker.
4. Add new layer (don't apply changes!)
5. Re-build Weaver pro solution in VS
-- Post build event moves compiled dlls to Assets folder
6. Go back to Editor
-- Unity imports dlls and recompiled scripts. Un-applied Layer Linker Settings message appears twice
7. Press "Apply and Generate Script" twice
Results: Unity crashes
Reproduced with: 5.4.0f1, 5.4.3p1, 5.5.0f1, 5.6.0a3
Does not reproduces with: 5.3.6p7
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
Add comment