Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.2.19f1
2018.3.0b1
2019.1.0a1
Issue ID
1106472
Regression
No
LWRP project spawns multiple exception in UWP build
Steps to reproduce:
1. Download 1106472_repro.zip
2. Switch platform to UWP
3. Build project with IL2CPP backend
4. Open Visual Studio solution and build (Debug, x64, Local machine)
Actual results: multiple exceptions are thrown.
Exception thrown at 0x00007FFB1598A388 in New Unity Project (21).exe: Microsoft C++ exception: _com_error at memory location 0x000000EC130F2508.
Reproduced with: 2019.1.0a13, 2018.3.1f1
Note: Reproducible with x64 and x86.
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:
Why won't fix: this is not a bug. These exceptions are thrown and caught by D3D debug layer (which is enabled in debug builds). They do not happen in release or master builds.