That proves it’s not an unavoidable driver bug, and it’s consistent with my fix. BJS’s glTF loader reads each accessor into its own tight per-attribute VertexBuffer (it doesn’t bind one shared interleaved buffer to multiple slots with a straddling offset), so it never issues the boundary-crossing float32x3 fetch. My fix makes Lite do the same thing for exactly the offending attribute.