Search Issue Tracker
Active
Under Consideration for 6000.5.X
Votes
0
Found in
6000.0.64f1
6000.3.1f1
6000.4.0b1
6000.5.0a3
Issue ID
UUM-129875
Regression
No
[DX, Vulkan] Shader starts acting unexpectedly when SV_primitiveID is used in a Hull/Domain Shader
How to reproduce:
- Open the “SV_PrimitiveIDBuggy.zip“ project
- Open the “bug_primitiveid” Scene
- Select the “Assets/ExampleCode/Unlit_NewUnlitShader.mat“
- In the Inspector, increase the “Index Value“ from 0 to 1
- Observe the Scene view
Actual result: Shader triangles form into a cube regardless of the SV_PrimitiveID value
Expected result: Shader triangles displaced by the value of SV_PrimitiveID
Reproducible in: 2023.1.0a1, 6000.0.64f1, 6000.3.1f1, 6000.4.0b1, 6000.5.0a3
Reproduced on: Windows 11 Pro (24H2)
Not reproduced on: No other environment tested
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Different text alignment in the column header in Entities "System" window
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
- PolySpatial “Trying to set shader on a Material Variant.” error is printed in the console when entering Play Mode
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
Add comment