Search Issue Tracker
Fixed
Fixed in 6000.0.66f1, 6000.3.5f1, 6000.4.0b4, 6000.5.0a5
Votes
1
Found in
2022.3.54f1
6000.0.31f1
6000.1.0a8
6000.2.0a1
6000.3.0a1
6000.4.0a1
6000.5.0a1
Issue ID
UUM-91203
Regression
Yes
Crash on vkNegotiateLoaderLayerInterfaceVersion when rendering a specific particle system with an Emission Rate over Time of 35 or more using Vulkan
How to reproduce:
1. Download Vulkan SDK
2. Open the attached "IN-90377" project with launch arguments “-force-vulkan” and “-force-vulkan-layers“
3. Open the “crashY” scene
4. Select the “Rats” in the Hierarchy
5. Observe the crash
Reproducible in: 2022.2.0a12, 2022.3.54f1, 6000.0.31f1, 6000.1.0a8
Not reproducible with: 2021.3.47f1, 2022.2.0a11
Reproducible on: Windows 11
Not reproducible on: No other environments tested
Notes
- Not reproducible on Direct3D11, Direct3D12, OpenGL
- If the Editor is manually set to Vulkan without using launch arguments, the Editor freezes
- Issue reproduces in a new project (with launch arguments) when applying the Custom Vertex Streams in the Particle System Renderer only when the Rat mesh is also added and Emission Rate over Time is greater than or equal to 35
- Does not reproduce in the Player
First few lines of the stack trace:
0x00007FFBB206BBD8 (VkLayer_khronos_validation) vkNegotiateLoaderLayerInterfaceVersion
0x00007FFBB20CEA40 (VkLayer_khronos_validation) vkNegotiateLoaderLayerInterfaceVersion
0x00007FFBB1E483DF (VkLayer_khronos_validation) vkEnumerateInstanceLayerProperties
0x00007FFBCBB9C4DD (vulkan-1) vkResetEvent
0x00007FF662D4EC81 (Unity) vk::CommandBuffer::BindVertexBuffers
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
- VFX Graph particles are not culled when using URP and Frustum Culling is enabled on VFX Mesh Output
- 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
Resolution Note:
Fixed in 6000.5.0a5
Resolution Note (fix version 6000.5.0a5):
Fixed in 6000.5.0a5
Resolution Note (fix version 6000.4.0b4):
Fixed in 6000.4.0b4
Resolution Note (fix version 6000.3.5f1):
Fixed in 6000.3.5f1
Resolution Note (fix version 6000.0.66f1):
Fixed in 6000.0.66f1