Search Issue Tracker
Fixed in 13.0.0
Votes
0
Found in [Package]
10.6, 10.5
Issue ID
1362034
Regression
No
[ShaderGraph] Transform direction from view to world is outputing a wrong result
Steps to reproduce:
- See attached screenshot for nodes layout : vec3(0,1,0) -> transform direction from world to view -> transform direction from view to world -> subtract
Expected : the subtract result should be (0,0,0) (with maybe some floating point errors)
Result : Subtract is not (0,0,0), the transform from view to world direction is apparently working like a transform position and breaks the calculations.
Reproduces with : Unity 2020.3.15f2 / Shadergraph 10.6, 10.5
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 (fix version 13.0.0):
Transform node now correctly observes the direction conversion type.