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
- [OpenGLES][XR] Zooming in on the camera's URP opaque texture causes "double vision" on Quest in OpenGLES3
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
Add comment