Skip to content
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

Broken animations during transition 3.x to 4.x #77524

Open
Miskler opened this issue May 26, 2023 · 14 comments
Open

Broken animations during transition 3.x to 4.x #77524

Miskler opened this issue May 26, 2023 · 14 comments

Comments

@Miskler
Copy link

Miskler commented May 26, 2023

Godot version

4.0.3.stable

System information

Win 10, i5-11400H, 16GB RAM, RTX3050M

Issue description

When switching from 3.x to 4.x, all AnimationPlayer's stopped working in my project. This problem occurs both in the editor and in the running project, which leads to errors.
ScreenRecorderProject135

Another thing I noticed in my project is that most of the nodes in the scene have gray names. Maybe it has something to do with it?
image

Steps to reproduce

I threw off the scene in which this error occurs. If you need the whole project, it is fixed in my profile - kHUTER. What is noteworthy is that this problem is not observed in projects created on 4.

Minimal reproduction project

load.tscn

@AThousandShips
Copy link
Member

AThousandShips commented May 26, 2023

@Miskler
Copy link
Author

Miskler commented May 26, 2023

@AThousandShips The difference between my topic and those you refer to is that the node erases the animation there for users, but for me it simply cannot reproduce it (without errors in the console)

@AThousandShips
Copy link
Member

AThousandShips commented May 26, 2023

Thank you for clarifying, as I said it was unclear what was wrong

@Miskler
Copy link
Author

Miskler commented May 26, 2023

@AThousandShips I tried to describe the problem as much as possible in my post. Can you tell me what other information I need to provide?

It would also not be superfluous to put the tags "bug" and "need testing" above my post :)

@AThousandShips
Copy link
Member

AThousandShips commented May 26, 2023

All you said about it was

all AnimationPlayer's stopped working in my project

So it's hard to tell, that's why I asked if those might be related

Which leads to errors

Can you please add what those error messages are?

I can't add tags, no more than you can, you'll have to wait until someone else does

@Miskler
Copy link
Author

Miskler commented May 26, 2023

@AThousandShips Another thing I noticed is that the animation simply cannot be reproduced. I can change the position of the animation, the animation can move to the selected state, but it cannot be reproduced.

ScreenRecorderProject136.mp4

@AThousandShips
Copy link
Member

AThousandShips commented May 26, 2023

By "reproduced" do you mean played? I don't know what you mean, but your video shows it not playing when pressing play

@Miskler
Copy link
Author

Miskler commented May 26, 2023

@AThousandShips The errors that I mean are in-game, for example, the function waits endlessly for the animation to end, it switched to playback mode, but in real life it does not play, which leads to "errors"

@Miskler
Copy link
Author

Miskler commented May 26, 2023

@AThousandShips As you can see on the videos and gifs that I threw off earlier, when I click on the animation playback buttons, the animation name is indicated in the node properties, as well as the ability to move the animation slider is taken away from me until I turn off its "playback"

@Miskler
Copy link
Author

Miskler commented May 26, 2023

I start using the poke method to check the working (on the left) and the non-working (on the right).

The only thing I noticed is that a strange identifier was assigned to the worker
image

I don't see any more differences between the working and non-working version. I want to remind you that I gave an example in the article. Here is an example of a working scene with which I compared: lazer.tscn

@Miskler
Copy link
Author

Miskler commented May 26, 2023

I don't have enough qualifications to understand the cause of the bug alone, but for some reason I need to prove that I'm not a deer and there is a bug after all.

@AThousandShips
Copy link
Member

AThousandShips commented May 26, 2023

but for some reason I need to prove that I'm not a deer and there is a bug after all.

What? I am simply trying to figure out what you're having problems with, in order to help you, I'm not calling you unintelligent or unknowing, I'm just trying to work out what you are saying because there's a language barrier here

@Zireael07
Copy link
Contributor

Re gray names, I think it wrongly converted the process mode of your topmost mode. When this happened to me, all the children nodes were paused and that's why they were gray in the tree

@Chaosus Chaosus added this to the 4.1 milestone May 27, 2023
@Miskler
Copy link
Author

Miskler commented May 27, 2023

@AThousandShips Okay. I'm sorry I was too rude, I'm just very upset by the fact that I got a very unpleasant bug that does not allow me to continue working in version 4.

@YuriSizov YuriSizov modified the milestones: 4.1, 4.x Jun 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants