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
All of the shader intrinsics seem to artificially depend on UAV-related data.
It doesn't really make any sense at all why min3 would be reading a UAV...
This prevents using the ddx/ddy instructions on anything that previously used any intrinsics, as it generates a silly error(x3662) based on this false UAV dependency.
I guess the UAV is used some sort of marker. Is there not some other way of doing this that wouldn't break so much stuff?
Thanks
The text was updated successfully, but these errors were encountered:
The atomic op on the UAV is our mechanism for telling the shader compiler to insert the instructions into the shader code. The final ISA doesn't actually reference the UAV.
The ddx/ddy issue is an unfortunate side effect. We'll look into ways to get around this.
Which instructions do you need? min3 and max3 have been removed from the intrinsics in the latest AGS version because our shader compiler inserts them automatically now.
All of the shader intrinsics seem to artificially depend on UAV-related data.
It doesn't really make any sense at all why min3 would be reading a UAV...
This prevents using the ddx/ddy instructions on anything that previously used any intrinsics, as it generates a silly error(x3662) based on this false UAV dependency.
I guess the UAV is used some sort of marker. Is there not some other way of doing this that wouldn't break so much stuff?
Thanks
The text was updated successfully, but these errors were encountered: