godot-demo-projects VS tps-demo

For a menu that appears next to the object in 3D space take a look at: https://github.com/godotengine/godot-demo-projects/tree/master/viewport/gui_in_3d

You can improve on it by looking at existing stuff you might have missed there are: - demo projects - docs - other implementations, including some seemingly recent ones

Check out 2D in 3D demo project.

Since Godot 4.0, you have access to the content_scale_factor Window property, which is effectively a 2D scale factor that can be used with any stretch mode. You don't need to change the UI theme or scale Control nodes manually – doing so will lead to difficult-to-resolve problems. Check the Multiple Resolutions demo for 4.x.

The Godot 4 Platformer 3D demo uses a grid, and for me it doesn't have the issue you mentioned. Project here - https://github.com/godotengine/godot-demo-projects/tree/master/3d/platformer

Hello, thank you so much for your detailed answer! In the site, there's a demo project (Saving and Loading (Serialization) demo project) that helped me get a better grasp of how saving/loadng works. However, in this project exists only one scene/level, if i have multiple scenes/levels, how do i save those so the player will continue from the scene they saved on? Do i do this from the var save_dict ? How do i go about this?

Project from open source demo available here: https://github.com/godotengine/tps-demo

The TPS demo uses AnimationTree root motion and is updated in _physics_process(). It should work in theory, as lawnjelly tested it numerous times while working on the physics interpolation PR. Maybe he had to modify parts of the demo and didn't open a pull request for it yet, though.

And yes, shaders are not cached, so that's responsible for some lag spikes. Calinou made a more optimized demo version, maybe you want to check it out: https://github.com/godotengine/tps-demo/pull/111

The TPS demo runs slowly because it uses GIProbe in high quality mode by default. If you use lightmaps instead, you'll find it runs much faster: https://github.com/godotengine/tps-demo/pull/111

Some additional information: The images on the right run with about double the framerate. The images on the right are using new techniques available in Godot 3.4, while the images on the left can be done in Godot 3.4, 3.3, and 3.2. For even more information, see this pull request: https://github.com/godotengine/tps-demo/pull/111

You're not supposed to commit the .import/ directory. It's for storing hashes of the assets the engine already processed on your machine. See example an of a gitignore file here.