Arseny Kapoulkine
Arseny Kapoulkine
I "wrote" a script that generates a synthetic test asset that might be helpful here ("wrote" is quoted because the code is generated by GPT Codex, I've lightly reviewed the...
It feels like `EXT_mesh_gpu_instancing` should at the very least have a non-normative note saying that inconsistent scale sign (or maybe negative scale in general) is not supported well in renderers...
> support depends only on the runtime/browser, and not the device/CPU There is some dependency on CPU features too - I'm not sure caniuse report incorporates this. I would not...
I've updated the PR with the [1.0 version](https://www.npmjs.com/package/meshoptimizer/v/1.0.0) of the decoder module; it's more or less the same in terms of size as the original comments indicate (+-20 bytes post...
Per https://github.com/KhronosGroup/glTF/pull/2517#issuecomment-3657759361 this extension is in "review draft" and so hopefully this PR can be reviewed now. For testing, assets from this comment could be used: https://github.com/KhronosGroup/glTF/pull/2517#issuecomment-3440081285 (glTF-Sample-Assets will get...
For completeness, here's an updated version of the asset used by three.js 'webgl_loader_gltf_compressed' example; it can be copied to `examples/models/gltf/` folder to test this PR as well. (it seems better...
These extensions have not been merged; they are also multi-vendor, so support is not guaranteed. I have briefly looked at them in the past and it might make sense to...
I've seen the nested extensions in the prior EXT_ proposal but this one is the first KHR_ one so I'll comment here. I was very surprised to see the nesting...
I think the texture slots are not quite the same situation - these are nested objects with each individual object being extended, vs nested extensions that are being proposed here....
> Despite the fact that we're referring to other .d.ts files, yeah... Amazingly, it looks like the import *must* be from `meshopt_decoder.js` despite the fact that this file doesn't exist....