Search Issue Tracker
By Design
Votes
0
Found in [Package]
9.0.0-preview.29
Issue ID
1242448
Regression
No
ShaderGraph does not throw an unsupported feature error when Normal from Height Node is used with DXR
How to reproduce:
1. Open the attached project named "Case_1242448"
2. Open the Test shader graph
3. Observe that Normal From Height node is connected to the Master
Expected result: A clear error is thrown notifying that the Normal From Height node is not compatible with DXR
Actual result: Graph throws a compilation error, however, it does not indicate the use of unsupported node
Reproducible with: 2019.3.14f1(7.3.1), 2020.1.0b9(8.1.0), 2020.2.0a11(9.0.0-preview.29)
Could not test with: 2018.4.23f1(Ray tracing was not yet available)
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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Resolution Note:
We are tracking this functionality as a new feature request internally. The first iteration of the new warnings can be tracked on our public roadmap, here: https://portal.productboard.com/8ufdwj59ehtmsvxenjumxo82/c/44-pipeline-dependent-nodes . This specific warning case is captured and will be included in the final release of our Pipeline Dependent node warnings.