Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
14.0.0
Issue ID
1403042
Regression
No
Per-axis Wrap Mode is incorrect when Sampler State node is used in Shader Graph
How to reproduce:
1. Open the user's attached project
2. Observe the "Plane_PerAxis" and "Plane_PerAxis_SamplerState" GameObjects in the Scene view
Expected result: both Planes look the same (both show 2 light circles)
Actual result: Plane_PerAxis_SamplerState is different (shows 4 light circles)
Reproducible with: 12.1.5 (2021.2.15f1), 13.1.7 (2022.1.0b11), 14.0.0 (2022.2.0a7)
Could not test with: 7.7.1 (2019.4.36f1), 10.8.1 (2020.3.30f1) (project breaks after downgrading)
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
- [Dragon Crashers] Build fails in U6
- [Dragon Crashers] 4 Shader error messages on import
- [Dragon Crashers] Readme text is white on light grey
- Cursor stays in front of the first character when entering text in the TextMeshPro field
- Searching in Hierarchy causes unwanted component calls
Resolution Note:
By default, when a Material is set on a uniform, it's sampler state will also be set implicitly based on the texture. In this way, the Sampler State parameter on nodes is completely optional. You would only really want to use it if you're aiming to use many more textures than the allowed number of sampler states (usually 16), or if an imported texture is going to be used in more ways than it's import settings indicate.
Our Sampler State nodes are not currently robust enough to cover all of the possible sampler states available, but it's something that is currently being worked on as a new feature.