primal thunder
Hello. I'm new to 3D but not new to Godot, and I am making a prototype cycling game in 4.2. I have a mesh+skeleton for the rider and mesh+skeleton for the bike. Right now I have the character controller sort of working with the bike animated via code, but no animations for the rider yet. I'm using just a RigidBody3D sphere as the collision object and applying forces to that, then just having the meshes follow the sphere. Based on the KidsCanCode arcade car tutorial (https://kidscancode.org/godot_recipes/3.x/3d/3d_sphere_car/). I tried using VehicleBody3D with two wheels but found it very unstable.
Which path forward do you think makes the most sense:
-
Combine the meshes and skeletons into one model, and use Blender/Godot animations to animate everything, then a state machine to transition/blend between animations. I am already familiar with the basics of animation and Godot animation nodes, so this method initially feels more attractive. Especially since the models themselves are not interacting with the physics simulation. The downsides as I see them are 1) hard to dynamically change rider and bike models separately and 2) hard to animate rider getting off/falling off bike. I can live with those if this method is deemed significantly easier than #2.
-
Keep the meshes separate and use code (perhaps IK?) to have the rider "stick" to the bike. I played around with this a bit and had some success, but would have to learn a lot more about IK and rigging, I think.
-
Some other approach I have not considered?
Any experience / advice on which way might be best?
primal quest
