Gaia Clary
## Summary
GLB/GLTF uploads can produce different rigged mesh deformation than DAE uploads from the same source model when the model uses a bind pose that differs from the viewer skeleton rest pose.
## Context
Bind pose support is not directly exposed by Blender itself, although other tools such as Maya support this workflow. Both Collada/DAE and GLB/GLTF can represent bind-posed models through inverse bind matrices.
The Avastar Blender add-on explicitly adds bind pose support and collada support to Blender-5, so this issue can be reproduced and tested using Blender-5 with Avastar.
## Steps to Reproduce in Blender
  1. In Blender, create or open a rigged mesh that uses a bind pose different from the default viewer skeleton rest pose. typical use case: A-posed models with A-Pose as restpose.
  2. Export the same model from Blender as DAE.
  3. Export the same model from Blender as GLB/GLTF.
  4. Upload/import both files into the viewer.
  5. Compare the imported results at the vertex/deformation level.
## Actual Result
The GLB/GLTF import can deform differently from the DAE import, even though both files were exported from the same source model.
Visible differences can include child joint twists.
## Expected Result
DAE and GLB/GLTF exports from the same bind-posed source model should import with equivalent vertex-level deformation.
Mesh edges may differ depending on exporter triangulation, but the rigged vertex positions and deformation should match.
## Test Notes
This was tested with Blender using Avastar bind pose support by exporting the same bind-posed model as both DAE and GLB/GLTF, then comparing the uploaded viewer results.

Photo Viewer

View photos in a modal