Search Issue Tracker
Fixed in 10.1.0
Votes
0
Found in [Package]
9.0.0-preview.34
Issue ID
1240099
Regression
No
[ShaderGraph] Only one Parallax Occlusion Mapping node instance can be used inside the shader graph
Reproduction steps:
1. Open the user's attached project ("Multiple POM Bug.zip")
2. Open the repro scene ("Error")
3. Inspect the in the Scene/Game views
Expected result: The plane should show a lot of red color as the shader compares the UV output of two Parallax Occlusion Mapping nodes using different height maps
Actual result: The plane is completely green
Reproducible with: 2019.4.3f1, 2020.1.0b15, 2020.2.0a17
Couldn't test with 2018.4 (minimal package version not supported)
Reproducible with package versions: 7.3.1, 9.0.0-preview.34
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
- Isometric Tilemap incorrectly sorts Tiles when Sort Order is set to "Bottom Right" or "Top Left"
- [WebGL] Audio track with a loop point defined plays from the start when looping
- [Android] Semaphore.WaitForSignal causes ~200ms stalls when Dithering Node in a ShaderGraph is enabled on Samsung J7
- "Branch Group" tools have missing tooltips
- ExecuteMethod uses cached data when running validations after a CI checkout
Resolution Note (fix version 10.1.0):
The Parallax Occlusion Mapping node has been moved to ShaderGraph so URP can use it too, we also added the possibility to have multiple POM nodes in a single graph.
This work will be available in the 10.x packages.