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

Godot 3.5 break: Change Node Type in Scene Tree doesn't always update the Inspector #64313

Open
nautmeg opened this issue Aug 12, 2022 · 5 comments

Comments

@nautmeg
Copy link

nautmeg commented Aug 12, 2022

Godot version

3.5

System information

macOS Big Sur 11.6.8

Issue description

When you Change Type (change node type) in the Scene Tree window, the ice changes but the Inspector doesn't update with the new Class/Node information. For example if you change a Label to a Button, sometimes the inspector still shows the Label properties instead of Button properties.

Steps to reproduce

In your scene, create a Button, change the type to another Node Type, sometimes the Inspector will show the new node type, but other times it will continue to show properties for the Button Node. Reload Current Project fixes it... This doesn't happen every time and I'm not sure what the trigger is.

Minimal reproduction project

No response

@Calinou
Copy link
Member

Calinou commented Aug 12, 2022

Does it consistently work in 3.4.5?

@dehnda
Copy link

dehnda commented Aug 12, 2022

For me it does on Ubuntu 22.04.1 LTS with godot 3.4.5 stable [f9ac000].
Tested it around with all kinds of different nodes.

@nautmeg
Copy link
Author

nautmeg commented Aug 12, 2022

I should have said I went straight from 3.3 to 3.5. Can't remember now exactly which version of 3.3 I was on...

@jordo
Copy link
Contributor

jordo commented Aug 12, 2022

Can confirm we are experiencing this bug as well. It feels random and intermittent, but will try and take a screencap when it happens to show what it looks like.

@jordo
Copy link
Contributor

jordo commented Aug 15, 2022

Can confirm, we didn't seem to have this issue in 3.4.1 (previous version)

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

4 participants