-
-
Notifications
You must be signed in to change notification settings - Fork 21.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Removing redundant errors during animation mixer cache update #85368
Removing redundant errors during animation mixer cache update #85368
Conversation
Hello, I'm not sure how to link an issue to this. This is a PR to resolve this issue: #85316 |
A more detailed commit message is necessary, you can learn how to edit those here: https://docs.godotengine.org/en/stable/contributing/workflow/pr_workflow.html#modifying-a-pull-request |
I remember we have removed similar errors in the past, but I feel that removing too many errors against path checking is inconvenient because the user cannot notice what is wrong in cases where the animation does not work. Perhaps we should reconsider implementations such as #69480. |
Added a proper commit message, let me know if there are anything I should add to it. Currently have only removed a redundant error message (there were two error messages every time the cache update ran into an invalid node, down to 1), I do not feel qualified to make a decision whether or not to remove the error entirely. I personally believe being told that a node doesn't exist every time the cache is updated can be confusing to a programmer, especially when it throws that error for animations that aren't in use. If possible, it would be nice to post an error only when running an animation that contains an invalid node, I have no clue how to implement this currently though. |
Prevent Animation Mixer from posting unnecessary errors when updating cache. When a node is invalid/deleted, any animations that reference that node throws two errors. This occurs for every animation in the animation mixer (even if those animations aren't being played), every time the cache is updated (whenever any animation is started, for instance). This quickly leads to a ton of error messages. This PR removes one of those error messages, the one for failing get_node by first doing a check with has_node_and_resource. Fixes #85316
I think it would be fine if AnimationPlayer could be checked at the |
Superseded by #86608. Thanks for the contribution! |
No description provided.