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

Revert new scene change algorithm #85298

Conversation

RandomShaper
Copy link
Member

The more I think about it, the more it seems these changes didn't really improve anything by themselves. Much of the issues were of the kind solved now by #85280.

This reverts commit 8bebabd.
This reverts commit 4354cd8.

Fixes #85251.
Supersedes #85279.

This reverts commit 8bebabd.
This reverts commit 4354cd8.
@RandomShaper RandomShaper added this to the 4.2 milestone Nov 24, 2023
@RandomShaper RandomShaper requested review from a team as code owners November 24, 2023 09:34
DEV_ASSERT(!current_scene);

pending_new_scene = new_scene;
call_deferred(SNAME("_change_scene"), new_scene);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does this have to be a named call?

@RandomShaper
Copy link
Member Author

After deeper discussion, the new algorithm also has strengths, so until we can find the best of both worlds, the new one is kept. There are very easy ways to emulate the former and the new one will be perfectly documented.

@RandomShaper RandomShaper deleted the classic_scene_change_is_back_in_town branch November 24, 2023 10:42
@YuriSizov YuriSizov removed this from the 4.2 milestone Nov 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

get_tree() returning null immediately after calling change_scene_to_file() in _process or _physics_process()
4 participants