Add new GLTF character model and loader functionality

[SachinSSh]

Objective

• Added a comprehensive GLTF animation viewer example that provides an interactive 3D inspection tool for developers working with animated GLTF assets. This addresses the need for a professional-grade animation preview tool that goes beyond basic playback controls.
• Inspired by: 'animation_mesh_control.rs' but significantly enhanced:

Solution

• Describe the solution used to achieve the objective above.

Testing

• Tested on Windows with multiple GLTF files containing various animation types
• Verified all controls work as expected (camera, animation switching, speed controls)
• UI responsiveness confirmed with real-time updates
• Animation loading tested with different GLTF structures

---

This example serves as both a learning resource for advanced animation handling and a practical tool for developers who need to inspect and preview GLTF animations during development.

[github-actions]

Welcome, new contributor!

Please make sure you've read our contributing guide and we look forward to reviewing your pull request shortly ✨

[SachinSSh]

hey! I'm new to this project, I don't know what these 3 checks are failed, can someone tell why they failed and what they are?

[github-actions]

The generated examples/README.md is out of sync with the example metadata in Cargo.toml or the example readme template. Please run cargo run -p build-templated-pages -- update examples to update it, and commit the file change.

[theotherphil]

At least some of the failing checks are for formatting and can be fixed by running cargo fmt.

[SpecificProtagonist]

The CI logs tell you what happened when you click on it ^.^

The toml format can be fixed by running taplo or by manually removing the leftover space.

You also need to run cargo run -p build-templated-pages -- update examples, which makes sure examples/README.md stays in sync.

theotherphil already mentioned that you need to run cargo fmt to fix the formatting of the Rust code. My recommendation is to set up your IDE to automatically run this when saving a file.

Finally, the mismatched_lifetime_syntaxes lint got added in the latest nightly Rust version. You don't need to do anything about it in this PR :)

[rparrett]

Could you please fill out the PR description? It would be helpful to know the motivation of this PR and what it is demonstrating that isn't covered by the animated_mesh_control example.

[SachinSSh]

The CI logs tell you what happened when you click on it ^.^

The toml format can be fixed by running taplo or by manually removing the leftover space.

You also need to run cargo run -p build-templated-pages -- update examples, which makes sure examples/README.md stays in sync.

theotherphil already mentioned that you need to run cargo fmt to fix the formatting of the Rust code. My recommendation is to set up your IDE to automatically run this when saving a file.

Finally, the mismatched_lifetime_syntaxes lint got added in the latest nightly Rust version. You don't need to do anything about it in this PR :)

Could you please fill out the PR description? It would be helpful to know the motivation of this PR and what it is demonstrating that isn't covered by the animated_mesh_control example.

ofc its different from 'animated_mesh_control' and 'custom_skinned_mesh' but its an undeniable fact that 'gltf_viewer_main' is heavily influenced by these.

[SachinSSh]

The CI logs tell you what happened when you click on it ^.^

The toml format can be fixed by running taplo or by manually removing the leftover space.

You also need to run cargo run -p build-templated-pages -- update examples, which makes sure examples/README.md stays in sync.

theotherphil already mentioned that you need to run cargo fmt to fix the formatting of the Rust code. My recommendation is to set up your IDE to automatically run this when saving a file.

Finally, the mismatched_lifetime_syntaxes lint got added in the latest nightly Rust version. You don't need to do anything about it in this PR :)

thanks buddy for explaining issue precisely, let me be friendly with taplo!

[SachinSSh]

ok , i have fixed the issues what's next now?

[SachinSSh]

hey can u tell me whats's next?

[SachinSSh]

Could you please fill out the PR description? It would be helpful to know the motivation of this PR and what it is demonstrating that isn't covered by the animated_mesh_control example.

hey can u tell me what's next?, I checked all tests.

[hukasu]

What is the license of the Gltf?

[SachinSSh]

What is the license of the Gltf?

MIT

[janhohenheim]

Nice idea! Some observations:

• Don't we already have a glTF viewer example somewhere?
• Also, we currently don't have a good solution for storing large files for example! yet, sorry! As such, you will have to remove the glTF you've provided and use something that already exists in tree, like the fox.glb

[SachinSSh]

Nice idea! Some observations:

• Don't we already have a glTF viewer example somewhere?
• Also, we currently don't have a good solution for storing large files for example! yet, sorry! As such, you will have to remove the glTF you've provided and use something that already exists in tree, like the fox.glb

Thanks, I purpose this commit for fully control on animations inside the glb/gltf model. Although simply demonstrating glb is already in animated_mesh_control, I just want to improve for better control over viewport and camera movement.

Fine, I remove that gltf, use already existed fox.glb