webxr-webgpu-binding

Sounds good! Yeah so I have no sophisticated tools, just guessed calculations done mostly at run time (add up how much do gpu compressed textures should take for a model, mesh+blendshape memory estimates, other data structures). And obv for audio and animations just ensuring what’s not needed is never in memory and just knowing how much the biggest ones cost. To come up with an estimate of an upper bound and obv with lots of testing. ios safari doesn’t even publicly expose how much memory usage is allowed to a tab (and it changes) so really the final test is that stuff stops crashing. But my testing put the crash window between 500mb-1gb on an iphone pro. over 1gb usually guarantees a crash. Not really enough to make a proper game by today’s standards but hey they shipped gta san andreas at 32mb ram on ps2 so I’m sure I can push things fu

Not a very expansive post. Here's a few more things WebGPU is missing (at least on the web): - Push constants (wgpu has them as a native feature for all backends) (allows avoiding a uniform buffer write and bind) - Texture binding arrays (https://docs.rs/wgpu/latest/wgpu/struct.Features.html#associ...) (allows for rendering multiple materials at the same time) - Multiview rendering (https://docs.rs/wgpu/latest/wgpu/struct.Features.html#associ...) needed for WebXR bindings (https://github.com/immersive-web/WebXR-WebGPU-Binding/blob/m...)