Search Issue Tracker
Feature Request
Votes
0
Found in [Package]
15.0.0
Issue ID
SGB-488
Regression
No
[ShaderGraph] Voronoi output can not be used directly for Colorspace Conversion
Steps to reproduce :
- In a shadergraph, do the nodes setup as bellow :
!image-2023-03-10-19-05-09-708.png!
Expected : Both Colorspace Conversion nodes should display the same preview
Result : HSV -> RGB conversion only works if some nodes are placed between the Voronoi and Conversion. Multiple combinations are possible.
Notes :
While adding an operation in between the nodes fixes the preview, it is not enough to fix the final rendering of the shader on an object :
!image-2023-03-10-19-19-23-556.png!
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Resolution Note:
This is an awkward side-effect of how preview code gen differs from the final shader code gen. Some sanitization and value normalization occurs to make sure the outputs of a preview provide meaningful feedback in a color range.
In this case-- if you were to saturate and then normalize the voronoi node output, it would then work with the colorspace conversion node. The Contrast, Saturation, and Hue nodes can also be used to translate the voronoi output in a few different ways.
This speaks to a larger need to improve support for HSV and maybe have better documentation on what a node's expected output ranges are. I'm marking this as a feature request, as it speaks to a few less intentionally designed pieces of the tool leaving a user with unclear feedback.