Dylan Perks
Dylan Perks
The NVIDIA extension is significantly larger, so it would may require some work. But if all the functions Piers listed previously are built unconditionally as you said then yeah we...
I see. In which case @caramelli an issue should be opened for NVIDIA to document this extension. You can use the header snippet that Piers posted to wield these functions,...
Using the existing NV one is more conservative and it allows code to just work that already uses this internal extension (NVIDIA partners?) which is present on many devices today....
Awesome, can you advise on what tokens this extension has?
Affirmative, thanks. Will stitch something together. Should the contact for this extension be a NVIDIA contact or should I put my name in there?
> is there something I need to do? It should be fine for now. I'm going to stitch together a technical, textual specification and update the XML for these functions....
My proposed version will likely be heavily based on OES_fixed_point in writing so it might be worth looking at how that’s handled today. On Thu, 14 Jan 2021 at 01:47,...
Haven't spent much more time looking at this, personally don't have much motivation to do so given that OES_single_precision and OES_fixed_point cover most of NV_ES_1_1_compatibility, just with the OES suffix...
Could just add a type attribute to remove blocks which will accept either “remove” or “deprecate”
Yeah it'd be cool, but if you're preparing to go down the line of parsing the extension specs then that's a slippery slope at best! But yeah, fixing some little...