Philip Rideout

Yes this would be useful since the test we have currently doesn't create one from scratch. One strategy is to declare a lot of things on the stack, e.g.: ```c++...

Here's a more complete example of writing a gltf from scratch: https://github.com/prideout/par/blob/master/test/test_octasphere.cpp We could add a pointer to this from the README, or we could copy it into a unit...

I think this is a good thing to discuss, and it's worth mentioning that the Filament client deals with this by calling cgltf_validate in its debug build, which provides reasonable...

@JonathanWilbur This isn't a terrible limitation because you can treat the WebAssembly module as an allocator for all the typed arrays that you wish to create in your JS code.

I think this doc page would be less confusing if it had examples of the data flowing the other way. Currently it is only showing an example a number slice...

Note that WebGL 1.0 is now deprecated in ThreeJS, which is the most common way for developers to interact with WebGL.

I would love for a new version to be published. It would be especially useful to get the bytemuck feature that was added in #541.

FWIW, ClipDistance and CullDistance are available in the GLSL-ES 3.2 spec (not in earlier versions) however the API spec for ES 3.2 makes no mention of them in section 12.5...

Including a simple blitting function instead of a mipmap generator would be less controversial. Note that Vulkan provides `vkCmdBlitImage` with somewhat configurable filtering, but fixed to CLAMP_TO_EDGE wrapping behavior.

That's fine! Sent from my iPhone > On Mar 24, 2014, at 4:35 AM, Dave Kerr [email protected] wrote: > > Hi @prideout if you see this message can you let...