I get bombarded with error messages, does anyone knows what the mean and how to get rid of them?

Wuerzelpilz

It has something to do with the animation tree but I have no clue what exactly... everything works, it's just very annoying to look at. It happens without pressing on play, so it isn't my code this time, I used AnimationNodeStateMachine. Edit: here's the project https://drive.google.com/file/d/104L7RBVZOwu2Cvfw9Zp3bW3fpg29UhQJ/view?usp=sharing

cybereality

Check those 6 messages in the debugger and see if that helps.

Wuerzelpilz

@cybereality said: Check those 6 messages in the debugger and see if that helps.

so after restarting my PC, the flood of errors are gone...somehow... strange. But there are still some left.... Errors with node not found, don't know how that can happen, I didn't moved anything and an error on AnimationTree Reset... no clue what this one means. so onready var player_sprite = $HeroIdle is wrong? Is there something wrong with the hierarchy? I don't know C++

Edit: I'm using v3.4.stable.official [206ba70f4]

cybereality

Try using get_node instead of $. Like:

onready var player_sprite = get_node("/root/TestLevel/Player/HeroIdle")

Wuerzelpilz

@cybereality said: Try using get_node instead of $. Like:
onready var player_sprite = get_node("/root/TestLevel/Player/HeroIdle")

I already tried this variation but it doesn't make any difference :|

Megalomaniak

Does HeroIdle actually have a texture/spritesheet applied? And is it a AnimatedSprite or a Sprite node?

Wuerzelpilz

@Megalomaniak said: Does HeroIdle actually have a texture/spritesheet applied? And is it a AnimatedSprite or a Sprite node? yes it has a texture applied to it, it's a sprite node, not animatedSprite.

Edit: here's the project https://drive.google.com/file/d/104L7RBVZOwu2Cvfw9Zp3bW3fpg29UhQJ/view?usp=sharing

Megalomaniak

You had some (leftover?) garbage tracks in your AnimationPlayer RESET animation. Deleting those got rid of the errors.

Also, you had mixed up which direction on the Y axis is which in the AnimationTree such that (lets call it) "south facing" frame was shown when moving in negative screen y("up").

Wuerzelpilz

@Megalomaniak said: You had some (leftover?) garbage tracks in your AnimationPlayer RESET animation. Deleting those got rid of the errors.

Also, you had mixed up which direction on the Y axis is which in the AnimationTree such that (lets call it) "south facing" frame was shown when moving in negative screen y("up").

Thanks, finally no errors anymore. But I'm still not sure about the purpose of this reset?! Couldn't find it in the docs.

Calinou

But I'm still not sure about the purpose of this reset?! Couldn't find it in the docs.

The RESET track was added in Godot 4.0. It's automatically created when you create new tracks. It's designed to ensure the animation can be reset to an "initial" state while in the editor. Previously, the initial value of your autoplay animation would be enforced when opening the editor, causing unnecessary changes to be saved to scene files.

The fact that old tracks are not cleaned up in RESET automatically is likely a bug, which I reported here: https://github.com/godotengine/godot/issues/55489