Search Issue Tracker
In Progress
In Progress in 6000.4.X, 6000.5.X
Under Consideration for 6000.3.X, 6000.4.X
Votes
0
Found in
6000.3.0f1
6000.4.0a5
Issue ID
UUM-128592
Regression
No
Shader flickering due to incorrect CBUFFER value for a frame in custom RenderGraph render pass
Steps to reproduce:
1. Open attached user's project "ShaderBindingIssue.zip"
2. Open the "SampleScene.unity" Scene
3. Enter to play mode
Expected results: no flickering on the outline effect
Actual results: outline effect is flickering
Reproducible with: 6000.3.0f1, 6000.4.0a5
Could not test on 6000.5.0a3 due to "Assets\Source\Rendering\Highlights\HighlightService.cs(149,65): error CS8601: Possible null reference assignment."
Could not test on 6000.0.63f1 and 6000.2.14f1 due to "Assets\Source\Rendering\Highlights\HighlightRenderPass.cs(554,53): error CS1061: 'SkinnedMeshRenderer' does not contain a definition for 'SetShaderUserValue"
Environment tested: Windows 11 24H2
Notes:
-Reproducible on macOS
-Reproducible with D3D12, D3D11, Vulkan
-Reproducible in Windows Standalone Player
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- 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
- Addressables content build fails but the Player build is successful when building a development build
Add comment