Godot 3.5 to 4 Conversion C#

I've started the process of converting my C# godot 3.5 proj to 4.0 since Godot just hit RC 1 for Godot 4.

I decided it'd be worth it for the efficiency gains but I was also pleased to see the extremely simplified move and slide method as well as the grounded and constant velocity additions to the CharacterBody3D class. I figured given the amount of time it takes to bake a simple lightmap I should probably just upgrade to 4 first.

I ran the auto converter which seems a tad buggy and changes a few things it shouldn't but it seems mostly ok.

Major things to note are:

Luckily I haven't really gotten far in actually making maps so all i have are prototype maps that would've been tossed out anyways. Most of the work has been on the characters, so rebuilding them should get me most of my progress back. I'll probably have to reanimate the particle effects, luckily I didn't have very many. On top of that my old file structure was a mess so this gives me a chance to reorganize anyways.

C# properties are now capitalized properly so they go from lowercase to uppercase now. This includes things like Vector3.x > Vector3.X. GlobalTransform.origin -> GlobalTransform.Origin

In C#, all physicsprocess and process functions are now double instead of float...but Vector3 operators still operate on floats, which is just a bit annoying.

Signals must now all have EventHandler as a suffix.

GPUParticles3D should be GpuParticles3D.

RID is Rid despite docs referring to it as RID, same as the GPUParticles thing.

No bind method for callables yet, apparently it'll be fixed sometime.

IntersectRay went from taking a bunch of parameters to a single query (that uses the same parameters)

File class > FileAccess

JSON is now Json and has to have a Json object created to parse the string.

GetViewport().Size property is gone, now its GetWindow().Size

GetWorld3d().GetNavigationMap does not exist in C# at least, use the NavigationMap property 

This didn't seem to be documented but collision layers and masks start from 1 instead of 0 now. This had me confused on a strange bug for at least a couple of days.

Another weird thing was if your gravity is too high and move on slopes is constant, you cannot move up slanted platforms (depending on how slanted it is). For my game I don't want any slow down or slipping when on a slope. It doesn't matter even if you set the wall angle to very high, it won't move. Weird issue but workable.

I don't know if this class was available in Godot 3, but ShapeCast3D is more suited for immediate interactions and area3D is stated to have a lag of a few frames, so I'm replacing my attack area with it.

I'll keep updating until my project is fully working again. As of March 25th, most things are working, save for minor collision issues and remade particle effects.

Comments

Post a Comment

Popular posts from this blog

First Post

Image
  I just posted my first video about a 3d hack and slash made in Godot Engine + C#. I chose C# because I wanted the practice, even as its given me a good number of problems, mostly involving documentation.  Right now most of the technical work has been dumped into the combat system, an extensible system that allows me to add/remove attacks and different weapons with ease. It lets me specify the next chaining move (and this can change based on if the player has swapped weapons), different particle effects, animations and more. Some other small behind the scenes technical work is as follows: Action queueing/Input buffering: This allows the player to "queue" actions so that they're executed immediately when they're valid. For example, the player can hit jump before they land and it'll cause them to jump again or they can mash the attack button during a combo and the next attack comes out right after the minimum time allowed for the previous. This makes the combat sys
Read more

March 17 update

Image
 I've been importing the level design from blender using Godot's blender import (which is seriously convenient) and realized I had an issue when it came to making collisions. I'd be clicking and generating for all meshes, and on top of that they'd be the less efficient, over detailed collision meshes. On top of that if I made even a single change to the level...it'd be a huge pain. This week aside from finishing up much of the laboratory assets, I made some tool scripts. One in blender to create a collision mesh from a custom mesh and auto rotate/scale/translate to each prop. Another as a godot editor plugin to auto create all the static objects from those collision objects from blender and assign them proper collision layers. I still need to do some more, as the current plugin doesn't handle interactable objects, just static props, but it gets rid of a lot of tedious work. With that and the combat system almost done, I think I'm ready to start work on actua
Read more

July 16 Update

Image
 As usual, lots of stuff, but I forgot to update regularly. I added in all of the basic special attacks. I'm still missing a fair bit of sound effects and particle effects, but I added in the base ones needed to just tell what the boss is doing. I tried to keep the GUI near the player. So invincibility is an effect around the player/boss. Weapon swaps can be seen above the player's head. Only the HP is shown in the right corner. Fixed a bunch of annoying bugs, still have a few minor ones. Added in a new attack for Sera that hopefully challenges players in dodging. Still have one more attack I want to implement for Sera then I think the prototype boss fight design is set and I just need to polish. The die state is in for the player and the dialogue can now have effects on the environment. I was going to switch to a plugin but given that i'm already having some issues with the scatter plugin I'd rather use my own solution for now. I think I'll probably rework my dialo
Read more