• Phoenixz@lemmy.ca
    link
    fedilink
    English
    arrow-up
    25
    ·
    1 year ago

    I’m pretty sure there are open source alternatives to this?

    Anybody care to shine some light on which projects would be comparable, and how they stack up against unity?

    • tsuica@lemmy.ml
      link
      fedilink
      English
      arrow-up
      33
      ·
      1 year ago

      Godot, it’s the most mature of the bunch. It’s a little different than Unity, but it’s definitely very user friendly, really powerful and has an active community.

      • floofloof@lemmy.ca
        link
        fedilink
        English
        arrow-up
        11
        ·
        1 year ago

        Godot feels nicer to work in than Unity. The object model is better designed and more intuitive. I hope this gives Godot a big boost.

    • Throwaway4669332255@lemmy.world
      link
      fedilink
      English
      arrow-up
      23
      ·
      1 year ago

      Godot is probably the best choice for open source game engines. Its got funding and full time developers working on it.

      Stride3D is probably the closest open source clone of Unity. It was developed by Silicon Studio as a commercial game engine but they eventually stopped and open sourced it. Its got a ton of modern features including vulkan and direct x 12 support. It has an active community too, but no full time staff making new features.

    • angrymouse@lemmy.world
      link
      fedilink
      English
      arrow-up
      11
      ·
      1 year ago

      There is, unreal besides being a product has its source available and Godot focus on the same niche most of unity games were. But the problem never was the lack of replacement, the problem is, a game with years of development on unity whould not easily switch to any alternative, they have assets from unity store, scripts made for unity, UIs using unity specific stuffs, even network protocols could be bounded with unity. Change this is an herculean task and most of the games are in barely maintenance mode, imagine a full rework. So these games should be pulled of the market and thrown in the garbage to avoid new installations.

      • Cosmic Cleric@lemmy.world
        link
        fedilink
        English
        arrow-up
        2
        ·
        1 year ago

        But the problem never was the lack of replacement, the problem is, a game with years of development on unity whould not easily switch to any alternative

        I read that there’s a porting tool from Unity to Godot out there. Never used it, have no idea how well it works, but that is a possible option.

      • Buffalox@lemmy.world
        link
        fedilink
        English
        arrow-up
        2
        arrow-down
        1
        ·
        edit-2
        1 year ago

        Godot focus on the same niche

        Not exactly, Godot is 100% free and open source, Unreal is only partially.

        Edit:

        I misread, the meaning is that Godot and Unity is serving the same niche, which is true. Except for those who want true Open Source, then Godot is the clear choice.

        • angrymouse@lemmy.world
          link
          fedilink
          English
          arrow-up
          4
          ·
          1 year ago

          Sorry, I was trying to say that Godot gas the same niche of unity, in the sense of both are widely used for indie and small games

        • angrymouse@lemmy.world
          link
          fedilink
          English
          arrow-up
          1
          ·
          1 year ago

          This is true for most of software out there, but most of the game industry operates with a small margin, and when you look to games individually, most of the games that are still selling (think about GoG games) are not worth any developer time

        • nybble41@programming.dev
          link
          fedilink
          English
          arrow-up
          1
          ·
          1 year ago

          The most valuable thing is an experienced team who thoroughly understand both the specifications and the implementation as well as the reasoning behind both. Written specifications are great as onboarding and reference material but there will always be gaps between the specifications and the code. (“The map is not the territory.”) Even with solid specifications you can’t just turn over maintenance of a codebase to a new team and expect them to immediately be productive with it.