Imma start my "Dev log" here if you dont mind.

Hello, im new here. Kinda trying my luck with making a video game on PC.

This thread will be my personal dev journey on some specific problems i encounter, finding ways to make something that i would like to have in my game.

This is not a game thread, just a research on how to and how not to do things in Godot, Blender, and other places.

As for starter:

Here is Some things ive researched so far https://godotforums.org/d/42678-how-to-sync-character3d-animation-to-movement-in-godot

As for todays post:

Here is what im working on. Statemachine (coded) that switch states when needed. At the moment figuring out how to handle jump animations. I would like them to be dynamic as per if you request a jump while running then you would jump of the first foot that hits the ground.

At the moment i have a jump animation cooked in blender for right foot. And so to demo

Here is where you can see when i press jump button and when the char starts jump anim.

The problem as you have noticed is. for some reason, when animation finishes, i have animation_finished() signal connected to change state back to run and start playing run animation, but you can see that it takes more than 3 frames or even more (im guesstimating).. and so it looks like it is stuck in place for a while.

Im sure this is not the optimal way to do thing, but its how i figured it out.

Basically its like this:
I have hardcoded function calls in animation when it runing:

func set_foot():
	right_foot_down = !right_foot_down
	if right_foot_down:
		debug_ui.update_label("right_foot_down","Foot down: Right")
	else:
		debug_ui.update_label("right_foot_down","Foot down: Left")

its just a boolean.

Also the hardcoded function call resets every time i reimport animations.. does anyone know how to keep those hardcoded function calls? My animations are saved to .resfiles on import.

And when im in run state i check:

func physics_update(delta:float) ->void:
	# Handle jump.
	if player.jump_request and player.right_foot_down and player.anim_player.current_animation_position  <= 0.1:
		state_machine.change_state("runjumpr")

When the run_jump_r state starts:

func enter(_previous_state:State=null) -> void:
	previous_state = _previous_state

	player.anim_player.play("RunJump_32_R",custom_blend)
	player.jump_request = false
	player.right_foot_down = !player.right_foot_down
	player.anim_player.animation_finished.connect(animation_done)

func physics_update(_delta:float) ->void:

	player.move_and_slide()

func animation_done(animation_name:String):
	player.anim_player.animation_finished.disconnect(animation_done)
	state_machine.change_state("run", self)

So the problem is either it takes more time to call the animation_finished signal or something else.