1553ee98ff
# Objective In #17905 we swapped to a named field on `ChildOf` to help resolve variable naming ambiguity of child vs parent (ex: `child_of.parent` clearly reads as "I am accessing the parent of the child_of relationship", whereas `child_of.0` is less clear). Unfortunately this has the side effect of making initialization less ideal. `ChildOf { parent }` reads just as well as `ChildOf(parent)`, but `ChildOf { parent: root }` doesn't read nearly as well as `ChildOf(root)`. ## Solution Move back to `ChildOf(pub Entity)` but add a `child_of.parent()` function and use it for all accesses. The downside here is that users are no longer "forced" to access the parent field with `parent` nomenclature, but I think this strikes the right balance. Take a look at the diff. I think the results provide strong evidence for this change. Initialization has the benefit of reading much better _and_ of taking up significantly less space, as many lines go from 3 to 1, and we're cutting out a bunch of syntax in some cases. Sadly I do think this should land in 0.16 as the cost of doing this _after_ the relationships migration is high.
72 lines
2.5 KiB
Rust
72 lines
2.5 KiB
Rust
//! Skinned mesh example with mesh and joints data loaded from a glTF file.
|
|
//! Example taken from <https://github.com/KhronosGroup/glTF-Tutorials/blob/master/gltfTutorial/gltfTutorial_019_SimpleSkin.md>
|
|
|
|
use std::f32::consts::*;
|
|
|
|
use bevy::{math::ops, prelude::*, render::mesh::skinning::SkinnedMesh};
|
|
|
|
fn main() {
|
|
App::new()
|
|
.add_plugins(DefaultPlugins)
|
|
.insert_resource(AmbientLight {
|
|
brightness: 750.0,
|
|
..default()
|
|
})
|
|
.add_systems(Startup, setup)
|
|
.add_systems(Update, joint_animation)
|
|
.run();
|
|
}
|
|
|
|
fn setup(mut commands: Commands, asset_server: Res<AssetServer>) {
|
|
// Create a camera
|
|
commands.spawn((
|
|
Camera3d::default(),
|
|
Transform::from_xyz(-2.0, 2.5, 5.0).looking_at(Vec3::new(0.0, 1.0, 0.0), Vec3::Y),
|
|
));
|
|
|
|
// Spawn the first scene in `models/SimpleSkin/SimpleSkin.gltf`
|
|
commands.spawn(SceneRoot(asset_server.load(
|
|
GltfAssetLabel::Scene(0).from_asset("models/SimpleSkin/SimpleSkin.gltf"),
|
|
)));
|
|
}
|
|
|
|
/// The scene hierarchy currently looks somewhat like this:
|
|
///
|
|
/// ```text
|
|
/// <Parent entity>
|
|
/// + Mesh node (without `Mesh3d` or `SkinnedMesh` component)
|
|
/// + Skinned mesh entity (with `Mesh3d` and `SkinnedMesh` component, created by glTF loader)
|
|
/// + First joint
|
|
/// + Second joint
|
|
/// ```
|
|
///
|
|
/// In this example, we want to get and animate the second joint.
|
|
/// It is similar to the animation defined in `models/SimpleSkin/SimpleSkin.gltf`.
|
|
fn joint_animation(
|
|
time: Res<Time>,
|
|
children: Query<&ChildOf, With<SkinnedMesh>>,
|
|
parents: Query<&Children>,
|
|
mut transform_query: Query<&mut Transform>,
|
|
) {
|
|
// Iter skinned mesh entity
|
|
for child_of in &children {
|
|
// Mesh node is the parent of the skinned mesh entity.
|
|
let mesh_node_entity = child_of.parent();
|
|
// Get `Children` in the mesh node.
|
|
let mesh_node_parent = parents.get(mesh_node_entity).unwrap();
|
|
|
|
// First joint is the second child of the mesh node.
|
|
let first_joint_entity = mesh_node_parent[1];
|
|
// Get `Children` in the first joint.
|
|
let first_joint_children = parents.get(first_joint_entity).unwrap();
|
|
|
|
// Second joint is the first child of the first joint.
|
|
let second_joint_entity = first_joint_children[0];
|
|
// Get `Transform` in the second joint.
|
|
let mut second_joint_transform = transform_query.get_mut(second_joint_entity).unwrap();
|
|
|
|
second_joint_transform.rotation =
|
|
Quat::from_rotation_z(FRAC_PI_2 * ops::sin(time.elapsed_secs()));
|
|
}
|
|
}
|