IN-62740 - VisionOS - Volume To World Node behaviour changes after Shader Keyword enabled

[Stijn2097]

It appears that the PolySpatial node Volume-to-World is changing behaviour when a shader keyword is enabled. Probably triggering a recompile for the shader and this somehow affects the Volume-to-World output.
My guess is that the Volume-to-World is using the default volume camera values (1,1,1) and updates this only when the shader is recompiled.

Before:

After:

Shadergraph Shader:

https://unity3d.atlassian.net/servicedesk/customer/portal/2/IN-62740

[kapolka]

Thanks for the report! I believe I found the issue (VolumeToWorld is getting overwritten by an erroneous value sent from Unity along with the other globals, like keywords), and should be able to include a fix in an upcoming bugfix release.