Search Issue Tracker
Won't Fix
Votes
0
Found in
2022.3.66f1
6000.0.57f1
6000.2.0b4
6000.3.0b1
Issue ID
UUM-116907
Regression
No
Rendering issues when using the Triplanar Node in ShaderGraph
Reproduction steps:
1. Open the attached “WorldSpaceRenderingIssue.zip” project
2. Open the “Scene With Issue Visible” scene
3. From the Hierarchy, select the “Quad (2)” GameObject
4. In the Inspector, find the Transform Component and the Rotation property
5. Set the X Rotation value to 0.04
6. Observe the “Quad (2)”
7. Change the X Rotation value to 0.05
8. Observe the “Quad (2)”
Expected result: No artefacts or rendering issues are observed
Actual result: The Quad GameObject is rendered incorrectly, almost see-through/with artefacts
Reproducible with: 2022.3.66f1, 6000.0.57f1, 6000.2.0b4, 6000.3.0b1
Reproducible on: Windows 11
Not reproducible on: no other environments tested
Notes:
- Both precision modes yield the same artefact: flat meshes not aligned to primary triplanar axes render incorrectly, especially when part of larger non-axis-aligned meshes
- On non-planar meshes such as the Capsule, the issue consistently occurs and only disappears when the "UseWorld UVs" option is disabled in the shader properties
- The issue does not occur in Game view or the Player
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
- [URP] Crash on GameObject::QueryComponentByType when baking a Reflection Probe in an unsaved/untitled Scene
- No Icons are used for the Entry and Exit States in the Inspector when selected in an Animator Controller
- Crash on PlayerMain(int, char const**) when exiting Standalone Player with a Particle System in the Scene
- No Icon is used for the Runtime Animator Controller Type in a Search Window when assigning an Animator Controller in the Animator Component
- Unity Version Control server textfield’s text overlaps with the dropdown triangle button in the Explore repositories window when an organization with a long name is selected
Resolution Note:
The root cause of the effect you're seeing has to do with the alpha clip threshold. When equal to 1, some clipping optimizations happen which interfere with the intent of what you're trying to do. Either disable alpha clipping (should be an option in the graph settings for the shader graph) or make the alpha clip threshold less than 1 (eg. 0.9999) to avoid this case.
While this interaction isn't super desirable, any fix would likely result in a small runtime performance cost that we would want to avoid.