Tomcat But I have a question: in what exactly did you see the value of this trash and why do you propose to discuss it

Language please! And also, try to be more constructive in your response.

DaveTheCoder Instead of talking about "the article", why not pick a specific idea that's in the article and discuss that?

I would like to repeat Dave here in order for this thread to be digestible and constructive.

@d2clon I did read the entire thread (took a while to see everyone's side here). I suspect you might be a bit misunderstood here, and that's probably due to trying to open up a discussion based on an entire pretty long-written article about many topics. If you want this thread to be helpful and productive, then try to break down the different areas to learn from and be solution-oriented. I'm sure that if there are good ideas to improve things, the people behind the engine would love to hear about it as long as it's constructive. Trying to keep a productive discussion about the entire article would probably need a big workshop with everyone included to get anything out of it.

    A lack of documentation... I wish one would elaborate. I am incredibly unbiased on game engines, Each one does things differently - some things better, others worse...

    With that being said, Godot 4 seems to have made quite a bit of changes compared to Godot 3.x, and I was learning Godot when they were branching from 2.x. I still don't know all the changes in 4.x.

    I suppose I could start there.
    Starting small, is there a doc that offers changes from 3.x to 4.x?
    How are the docs for C# vs GDScript? Is C# as good as an option for 4.x as 3.x or better?

    Start small, there's too much content to cover in those paragraphs to answer everything right away.

      Thanks, although I was referring to changes in GDScript, itself. IE I still have no idea how to make a variable public anymore. (It used to be export var var_name...)

      So far, I find GDScript in Godot 4 unusable. Is it harder? IDK, but it would take way too long to have to go through all the docs for it to find every single little change.

        Nerdzmasterz I was referring to changes in GDScript, itself.

        And how do you even organize the search for small changes? If you have ideas, you are welcome to suggest them. It is quite in demand and maybe someone will be interested in it.

        For now, I look through each new version report and look for things that concern me.

        Thank you! That helps a lot! It is true, though - if you change the name of the node type, it's incredibly hard to figure out what it's called.

        I'll double check, but I didn't see anything on export var yet. It's crucial as I often need to use variables from one node to another (enemy with X damage on the player, items offering Y health, etc.) Signals even seem different now.

        export becomes @export

        d2clon or try this one for size:

        Ill comment as i see people still pinging me about this issue. Modern godot has fixed most of the issues detailed here, and the architecture has changed enough that the 2 versions are not comparable. Even the tps demo used as the benchmark has changed significantly.
        This fork performance upgrades as detailed in posts above were done over the base of godot 3.3, and things have really changed since then. Also the fork is a experimental thing i created for fun so it goes into absurd levels just because i felt like it, like running shadow casting render logic in parallel threads or heavily parallelizing most of the renderer beyond what makes practical sense. It only really works for the TPS demo and its near guaranteed to be bugged for anything else.

        That's from the person that originally opened the issue in the first place.

        Nerdzmasterz a doc that offers changes from 3.x to 4.x?

        In addition to the official migration link posted that Toxe posted, there's an unofficial migration guide that may have additional information:
        https://gist.github.com/WolfgangSenff/168cb0cbd486c8c9cd507f232165b976

        Nerdzmasterz I find GDScript in Godot 4 unusable. Is it harder?

        GDScript in Godot 4 is an improvement over Godot 3. I've been using it for several small projects. The only challenge is that many API classes/nodes have been renamed, as well as some keywords. The "Search Help" feature that's built into the editor can be very useful. For example, try searching for export.

        MikeCL Language please!

        I am very apologetic, but I am using a translator and there are two terms for what I wanted to refer to: "trash" and "garbage". As far as I know they are both literary terms. I would be extremely grateful if someone could enlighten me on the difference in their usage and why one of them is undesirable.

        And also, try to be more constructive in your response.

        I'm trying very hard to be constructive. But it is extremely difficult to do so when the base of the proposed discussion is itself completely unconstructive. The article was even quickly deleted by the author ("garbage collection" is a well-established term in programming), which shows that the "arguments" and "reasoning" contained in it are too unreasonable.

          It is a very negative base to work on, I agree... but it's also a mountain that can't be fully examined in a few phrases. I wish, instead, people would just find a section of it and work on that.

          Tomcat but I am using a translator and there are two terms for what I wanted to refer to: "trash" and "garbage"

          I see. So the use of those words (I would say both of them) in this context can be very harsh and insulting and can be interpreted as hostile. You could just have asked the question without those words, and it would have been enough.

          Tomcat But it is extremely difficult to do so when the base of the proposed discussion is itself completely unconstructive.

          I understand you feel that way. But by asking politely, you might get an answer explaining the thought process and motivation behind it. I think it has already been discussed and explained the reasoning behind the article, so I'll leave it at that.

          You don't have to agree with it. Disagreements are fine. But being respectful and having a good tone is important.

          Nerdzmasterz So far, I find GDScript in Godot 4 unusable. Is it harder?

          I've been trying to figure it out since 4.0 appeared. I think I'm just starting to get the hang of it, but I'm probably unusually dense.

          • Toxe replied to this.

            Regarding the upgrade how-to documentation, I would like to praise how Rails does it. When I have to upgrade a project in Rails I never feel fear, because following this documentation has been always a holding hangs process.

            duane What are the issues with it?

            Granted, I only came to Godot two months ago and 4.1.1 is all I ever used, so basically I am young and naive, but so far it has been smooth sailing for me. Sure, I had some issues when renaming/moving scene files but those were always easy to fix.

            But I read so many complaints about Godot 4 and I always wonder if we are using two different programs because as I said I don't think I ran into anything that I would call a real issue. And I cannot remember a single crash.

            Or I am just not doing anything fancy and therefore don't even venture into the depths where the scary monsters lurk, who knows.

            I just don't want to have to go all the way back to Your First Game just to understand what the heck is going on. It's frustrating that using Godot 3.x for so long means all the coding I understand is obsolete in 4.x.

            Now, I did like how Unity would mention how an obsolete code was replaced with X. Even that would be incredibly helpful here in Godot 4.

            • Toxe replied to this.

              GDScript didn't really change all that much. Of course starting with a beginner tutorial would be a completely waste of time if you already know GDscript for Godot 3.

              I would go with the reference document instead: https://docs.godotengine.org/en/stable/tutorials/scripting/gdscript/gdscript_basics.html

              Takes 10-15 minutes to read through and contains all the important details, expect for node and API renaming. Most node renaming is kinda intuitive, basically just increased consistency. And the API changes on a specific nodes you can get by reading through the build-in documentation (F1). Takes also only seconds in most cases.

              Nerdzmasterz It's frustrating that using Godot 3.x for so long means all the coding I understand is obsolete in 4.x.

              Well now, that's quite a bit of hyperbole. Any programmer should be able to quickly switch from GDScript 3 to 4 and if you really cannot find the will to invest one hour (and that is already stretching it) into learning how to make the switch from GDScript 3 to 4 then, yeah, I''m sorry and don't know what to say.

              Personally I am happy to see evolution instead of clinging to old concepts just because it could be a small inconvenience to some. The shitshow that is the hesitation of the C++ committee not to shake the boat comes to mind.

              I'm a slow learner... It could take me a bit longer than that to grasp it.