andykswong / mugl Goto Github PK

These webgl2 draft extensions let you start instanced drawing from an arbitrary base instance, very much like firstInstance in WebGPU:

• https://www.khronos.org/registry/webgl/extensions/WEBGL_draw_instanced_base_vertex_base_instance/
• https://www.khronos.org/registry/webgl/extensions/WEBGL_multi_draw_instanced_base_vertex_base_instance/

It'd be nice to use them if they're available

Optimize the size of the model viewer / glTF module, targeting <10 KB (with no/minimal extensions support).

• Code optimization
• Optimize and minify shader
  • Support for no OES_standard_derivatives extension
  • Support for WebGL2
• Allow some features to be turned off

Uncaught ReferenceError: process is not defined

Add more comprehensive input parameter assertions, and make them tree-shakeable for minimal runtime overhead.
Currently, some checks still exist on production build, while others rely on the following pattern for tree-shaking:

if (process.env.DEBUG) {
  console.warn(...);
}

It'd be nice to be able to do some compute stuff with this library, and to reuse the compute output buffers in render pipelines

Ensure support for desktop and native mobile with examples:

• Support running on WASM
• Support expo-gl (Android, iOS, web, Electron)
• Support node-webgl (desktop)
• TBD - Support other JS runtimes: QuickJS, Duktape

Features:

• glTF based scene graph model
• glTF files and resources loader
  • glTF JSON
  • GLB
  • buffers
    • .bin
    • data URI
    • lazy-loading
  • images
    • jpg / png
    • buffer view
    • data URI
    • lazy-loading
• Renderer support for standard glTF properties
  • scene / node
  • camera (ortho/perspective)
  • accessors / buffers / bufferViews
    • sparse
  • texture / image / sampler
    • mipmap
  • material
    • with alpha-blending
      • partially working, missing depth sorting
  • mesh
    • morph
    • Support for vertex color with vec3 of UNSIGNED_BYTE / UNSIGNED_SHORT
  • skin
  • animation
    • cubic spline animation
• Support for essential extensions
  • KHR_lights_punctual
    • allow extra lights to be specified
  • EXT_lights_image_based
    • allow IBL background image to be specified
  • EXT_mesh_gpu_instancing
    • Support for particle system
  • EXT_texture_webp
• Support for material extensions
  • KHR_techniques_webgl
  • KHR_materials_unlit
  • KHR_materials_clearcoat
  • KHR_materials_ior
  • KHR_materials_sheen
  • KHR_materials_specular
  • KHR_materials_transmission
  • KHR_materials_variants
  • KHR_materials_volume
  • KHR_materials_pbrSpecularGlossiness

Optimize the size of the model viewer / glTF module, targeting <20 KB (with no/minimal extensions support):

• Optimize and minify shader
• Code optimization
• Allow some features to be turned off

Add UBO support in WebGL2 backend

Add readPixels method to device to support GPU mouse picking. This may require WebGL2 to avoid blocking: https://developer.mozilla.org/en-US/docs/Web/API/WebGL_API/WebGL_best_practices#use_non_blocking_async_data_readback

This should be an extension instead of core device feature

Description

Chrome webgpu support is around the corner, should be finally enable by default in chrome 113 in like ~3 weeks.

Is mugl will remains purely webgl2, or is there any plan to also handle webgpu (maybe providing some webgl2 fallback).
The syntax is really similar and having the combo webgpu + assemblyscript binding sounds really promising.

Add support for WebXR and multiview (OVR_multiview2 / OCULUS_multiview).
This should be an extension instead of core device feature

Consider handling context lost:

• Add context lost flag and callback
• Reset WebGL state on restore
• Allow resources to be reinitialized

Reference: https://www.khronos.org/webgl/wiki/HandlingContextLost

Nano Backend Improvements:

• Consider dropping WebGL2 support to keep it minimal
• Document unsupported features
• Further optimize bundle size

Add sRGB texture support, which is available in WebGL2 or in WebGL1 via EXT_sRGB: https://developer.mozilla.org/en-US/docs/Web/API/EXT_sRGB

• Device
  • Utils
  • GL2 Backend
    • Resources
    • Pipeline state merge logic
    • Rendering device
  • WebGPU Backend

Expose API to check WebGPU and WebGL limits.
Ref:

• https://alteredqualia.com/tools/webgl-features/
• https://developer.mozilla.org/en-US/docs/Web/API/WebGL_API/WebGL_best_practices
• https://www.w3.org/TR/webgpu/#limits

Currently I simply check the URI suffix for GLB, which may not be good enough. We can instead always load the content as binary and check for the GLB header magic.