Add support for MAXAR_mesh_variants #773
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
…e variants also added new functionality for variants
| Thanks for the pull request @nithinp7!
Reviewers, don't forget to make sure that:
|
| @nithinp7 can you please open a PR for the cesium-native side of this one? |
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Add this suggestion to a batch that can be applied as a single commit. This suggestion is invalid because no changes were made to the code. Suggestions cannot be applied while the pull request is closed. Suggestions cannot be applied while viewing a subset of changes. Only one suggestion per line can be applied in a batch. Add this suggestion to a batch that can be applied as a single commit. Applying suggestions on deleted lines is not supported. You must change the existing code in this line in order to create a valid suggestion. Outdated suggestions cannot be applied. This suggestion has been applied or marked resolved. Suggestions cannot be applied from pending reviews. Suggestions cannot be applied on multi-line comments. Suggestions cannot be applied while the pull request is queued to merge. Suggestion cannot be applied right now. Please check back later.
Builds on: CesiumGS/cesium-native#465
Added support for MAXAR_mesh_variants. GlTF nodes using the extension can now switch between multiple meshes, each representing a unique named variant. This is useful for representing things such as damage states (e.g., a vehicle parts that are pristine, damaged, destroyed, etc.).
Added a blueprint API to query and change the current variant mesh of a glTF node.
In this example, the tire mesh variants are switched from "Pristine" to "Damaged" when "hit".