You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Using the Fuse Variables from the Camera results in error, as they are defined with DefinedSemantics, which creates shader code using the streams prefix (which is wrong, as they are only stage variables).
Fixing this by Replacing DefinedSemantics with DefaultIn removes the error and works for nodes NearClipPlane and FarClipPlane (no more compile error and output values make sense).
However, it does not fix the problem for ViewSize and AspectRatio nodes. The generated shader code looks correct, however, their values will always be zero.
Writing a custom shader by hand using those variables works as expected though, so somewhere something in the chain goes still wrong when setting the values.
Describe the bug
Using the Fuse Variables from the Camera results in error, as they are defined with DefinedSemantics, which creates shader code using the streams prefix (which is wrong, as they are only stage variables).
Fixing this by Replacing DefinedSemantics with DefaultIn removes the error and works for nodes NearClipPlane and FarClipPlane (no more compile error and output values make sense).
However, it does not fix the problem for ViewSize and AspectRatio nodes. The generated shader code looks correct, however, their values will always be zero.
Writing a custom shader by hand using those variables works as expected though, so somewhere something in the chain goes still wrong when setting the values.
The text was updated successfully, but these errors were encountered: