Search Issue Tracker
Not Reproducible
Not Reproducible in 6000.5.X
Votes
0
Found in
2022.3.61f1
6000.0.47f1
6000.1.0f1
6000.2.0a9
6000.3.0a1
6000.4.0a1
6000.5.0a1
Issue ID
UUM-103853
Regression
No
A 404 page is opened when selecting "Open Documentation" on the HDRP Emission Node in Shader Graph
Steps to reproduce:
- Create or open any HDRP Project with the Shader Graph package installed
- Create any Shader Graph in the Project Browser
- Create an Emmision Node
- Right click it and select "Open Documentation"
Actual results: A 404 page opens
Expected results: Emission Node documenation opens up, just as any documenation does with all other nodes
Reproducible with versions: 2022.3.61f1, 6000.0.47f1, 6000.1.0f1, 6000.2.0a9
Tested on (OS): Windows 11, macOS 15
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
Thank you for reporting a bug to Unity.
We have investigated the issue but were unable to reproduce it with the information provided. This can happen due to differences in environment, project setup, or steps taken.
We will close this case for now. If you're able to share additional details such as different projects, steps, hardware/software configuration, or logs - please let us know, and we'll be happy to re-evaluate.
Resolution Note (6000.5.X):
Thank you for reporting a bug to Unity.
We have investigated the issue but were unable to reproduce it with the information provided. This can happen due to differences in environment, project setup, or steps taken.
We will close this case for now. If you're able to share additional details such as different projects, steps, hardware/software configuration, or logs - please let us know, and we'll be happy to re-evaluate.