Might as well stick with 4.5 at this point and focus on actually completing the damn thing

    • sp3ctr4l@lemmy.dbzer0.com
      link
      fedilink
      English
      arrow-up
      5
      ·
      6 days ago

      … How about a total revamp and expansion and improvement of the IK system in 4.6?

      Also, 4.7 will probably be finalized within 6 weeks, at the rate they’re going.

      Also also, I’m fairly sure the jump from 4.5 to 4.6 didn’t like, break anything.

      There’s new stuff, and then if its meant to replace old stuff, the old stuff is still there, just tells you its deprecated now, depending on your console/warn settings.

  • AceOnTrack@lemmy.blahaj.zone
    link
    fedilink
    arrow-up
    19
    ·
    6 days ago

    Unless there’s a specific thing you need in the newer versions, there’s no point upgrading. Use the framework you started with. Make your next project with the new framework.

  • ultimate_worrier@lemmy.dbzer0.com
    link
    fedilink
    arrow-up
    12
    ·
    6 days ago

    I’d switch to flake provisioning with Continuous Integration. A machine/runner on a cron would do CI on the latest flake update (latest Godot build) while I work, collecting issues as they arise (cachix is crucial for easing build times).

    That way, when I switch to the newest version, I’ll have a clear picture of:

    • The amount of technical debt I’ve built up
    • That everything is completely predictable.
  • lorty@lemmy.ml
    link
    fedilink
    arrow-up
    3
    ·
    6 days ago

    I know we take forever with projects but there really isn’t a reason to upgrade once you’re well on your way right?