tutorials/migrating/upgrading_to_godot_4.5

[giscus[bot]]

tutorials/migrating/upgrading_to_godot_4.5

For most games and apps made with 4.4 it should be relatively safe to migrate to 4.5. This page intends to cover everything you need to pay attention to when migrating your project. Breaking change...

https://docs.godotengine.org/en/latest/tutorials/migrating/upgrading_to_godot_4.5.html

[Energyxxer]

This article fails to mention the behavior changes to Resource::duplicate and the inclusion of Resource::duplicate_deep.
godotengine/godot#100673
In 4.5, deep duplication only duplicates resources internal to the resource file it's called on, whereas 4.4 duplicates everything. So if you were deep duplicating a resource that contained references to other external resources, now those external resources are not duplicated. You must call Resource::duplicate_deep(RESOURCE_DEEP_DUPLICATE_ALL) instead to keep the old behavior.

[Calinou]

Pull request opened:

• Document Resource.duplicate(true) behavior change in Upgrading to Godot 4.5 godot-docs#11292

[jil-hue]

I think the changes to get_coords_for_body_rid should be mentioned. If your project relies on detecting cells based on the rid, you need to set TileMapLayer.physics_quadrant_size to 1.

The conflict is better explained here:
godotengine/godot#105489

[Calinou]

Pull request opened:

• Document TileMapLayer physics chunking caveats in Upgrading to Godot 4.5 godot-docs#11294

[petersgiles]

I used to be able to use Command+Q to break out of the running debug session and go back to the Godot editor. now it prompts and if you agree it closes the whole Godot app.

[Calinou]

This is likely because game embedding is now supported on macOS, while it was only on Windows/Linux in 4.4. If you disable game embedding in the Game screen (click the 3 vertical dots and uncheck Embed Game on Next Play), it should work like it did in 4.4 and prior.

Remember that keyboard shortcuts go to the currently focused window, and this includes game embedding too. If you click outside the game window and press Cmd + Q, it will send the shortcut to the editor, hence the quit request.

[lukebickell]

Resource default value saving was changed: godotengine/godot#107049
This may result in breaking changes if you have different @export and _init defaults for a Resource.

See godotengine/godot#110466

[artturipi]

a_star behaviour has changed when calculating a path starting from a disabled point. Before it calculated the path happily, but now returns an empty list of points. This is fine and can likely be considered a bug in the previous version, but still broke my project's movment system until I figured out what was going on. :)

[artturipi]

Also means I need to enable the starting point, calculate the path and disable the starting point again for every query I make to a_star. Likely not a big deal performance wise. Still, it seems quite normal to start from a disabled point blocked by a game character and checking where they can move. Checking for paths that start from an empty point seems more rare, but this does make a_star work with less exceptions, so I guess that's good.

[blumm96]

There could be an option in the get_id_path function to be able to start from a disabled point because of the scenario that you described, especially since the behavior is changed from 4.4

[petrik33]

Thank you so much, was trying hard to figure out what's wrong with pathfinding since update and turns out to be exactly the same case

[Mickeon]

Some projects, but most notably for addons, may erroneously include property usage when customizing project settings with ProjectSettings.add_property_info, which now generates a warning because property usage flags do not actually work on project settings (see godotengine/godot#103944).

[Rhxydos]

This article fails to mention the addition of the Logger class.

[AdrienUfferte]

Yes !
If you have a class "Logger" or a Global named "Logger", it will display an error message everywhere
"static function not found"
I finally understood the only way for me to solve it was to rename my global from "Logger" to "Log" and to do a big "Replace All" in all my code.

Not very problematic, but it can be frightening at first

[AdrienUfferte]

I'm not sure if it was a good idea, but I tried to propose a change in the migrating doc :
godotengine/godot-docs#11306

[aobrem]

After upgrading to 4.5, version control users may notice minor diffs upon saving a scene, such as properties getting reordered. If you'd like to re-save all your scenes and resources to get all these changes over with, consider using the built-in tool that does that: Project -> Tools -> Upgrade Project Files.

[tripodsan]

After upgrading to 4.5, I noticed that Camera2D limits of 0 are now handled differently. In 4.4 it seems they were ignored, where as in 4.5, an new flag limit_enable controls the camera limits. This is related to the new editor checkboxes, but in my case had the effect that the camera position was completely off in my game.

[Devwarlt]

Thanks for pointing this out. I didn't notice any change on my project after this implementation, because I managed to disable this flag manually.

[DinoMC]

After upgrading to 4.5, my Camera2D was moved an entire half screen upward (= player completely offscreen) due to an apparent change in how camera limits work. I think this should be listed as a breaking change.

More details:

My scene is very wide, but the same height as my viewport resolution (360px) so I want the camera to only move horizontally. To achieve this, I set both the limit_top and limit_bottom to 0, and that worked in 4.4 (kept the camera centered, ie. as if at position (0,180) initially in the scene).

In 4.5, when doing this, the camera is now centered on (0,0) instead, only showing half of my scene vertically.
I had to update the limit_bottom to 360 instead (leaving limit_top at 0) to achieve the previous behavior.

(PS. this is different than the above comment as unchecking the box didn't fix my issue. I don't think a value of 0 was ignored previously for limit_bottom, as claimed)