Search Issue Tracker
Active
Under Consideration for 6000.6.X
Votes
0
Found in
6000.3.11f1
6000.4.0f1
6000.5.0a9
6000.6.0a1
Issue ID
UUM-137255
Regression
No
Crash on CreateResourceWithTag when rendering Custom Lighting ShaderGraph material while Forward+ is enabled and Keep Lighting Variants is disabled
How to reproduce:
1. Open the attached “IN-137163” project
2. Open the “New Shader Graph” located in the Assets folder
3. Uncheck the “Keep Lighting Variants“ box
4. Navigate open the “PC_Renderer” in the Inspector (Assets > Settings)
5. Change the Rendering Path to “Forward+”
6. Click on the Shader Graph tab and move around
7. Observe the crash
Reproducible with: 6000.3.11f1, 6000.4.0f1, 6000.5.0a9, 6000.6.0a1
Not reproducible with: 6000.0.71f1 (no “Keep Lighting Variants” option)
Reproduced on: Windows 11
Not reproduced on: No other environment tested
Notes:
- The Editor freezes for ~3 minutes before the crash occurs
- Not reproducible with DX11 or Vulkan
First few lines of the stack trace:
0x00007FFF7C9861E0 (Unity) CheckDeviceStatus
0x00007FFF7C96F314 (Unity) GfxDeviceD3D12::ReportResourceCreationError
0x00007FFF7C961735 (Unity) GfxDeviceD3D12::CreateResourceWithTag
0x00007FFF7C91DC79 (Unity) BufferD3D12::CreateBufferResource
0x00007FFF7C91FF59 (Unity) BufferD3D12::InitializeResource
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment