Closed Sergio0694 closed 10 months ago
I would recommend you to keep the Math
/MathF
detection for one release, not to support calling the methods, but to raise an error to guide the user in the right direction. "Don't use Math/MathF, use Hlsl instead." Some devs will be legitimately lost without this, and it will just seem like it's a bug in ComputeSharp. It's the polite thing to do ...
Description
This PR removes support for using
Vector2
,Vector3
,Vector4
,Math
andMathF
APIs in shaders. This was error prone and not really well supported anyway (lots of methods were still not usable from shaders). So with this, using HLSL primitives and APIs is actually required, which makes the shader code much more explicit and easier to understand, and with better separation.