Ipotrick
Ipotrick
There is also the point that some devices dont support daxa at all. In that case we should emit a good error message, collecting all the features/properties missing for that...
Thanks for pointing that out @loopunit. I will take that into consideration for the new device selection.
Device creation is redone in 3.1
finished c api
killed rest of features for 3.0 to get it out as so much has changed already.
We will start doing regular releases soon with new versioning
the reinterpreting should probably be part of the image view type (that is a template parameter to TaskImageUse).
Is there currently no way to prevent this issue with the meshoptimizer directly?
Dumb question, but would it work to simply pass uvs as attributes within meshopt_simplifyWithAttributes to combat this for now?
I quickly tried it and passing uvs to meshopt_simplifyWithAttributes with a small weight and that fixes the issue i see with uv mirroring nicely 👍