Not my meme, I stole it from someone else. You wouldn’t know them, they go to a different community.

  • PenisWenisGenius@lemmynsfw.com
    link
    fedilink
    arrow-up
    4
    ·
    edit-2
    4 months ago

    Get good at c++. Learn how to use open source 3d rendering engines like Ogre or Irrlicht. Find an open source physics engine you like. Combine into 1 program, now you have a game engine that can be developed on any os and you’ll be able to optimize your game far more than you ever would on unity or unreal. Use open source everything and don’t pay a cent for any software. I’m fairly certain the game Kenshi was developed this way more or less and by just 1 person too.

    That is a way to develop an entire game that doesn’t support enshitification. I don’t know who needs to see this so there it is. Not supporting enshitification can extend further than just sticking to gimp and blender.

    • Mossy Feathers (She/They)@pawb.social
      link
      fedilink
      arrow-up
      7
      ·
      edit-2
      4 months ago

      Last I checked Adobe doesn’t have any 3d game engines, so that’s not really a solution, heh. (Also, godot is already a FOSS 3d engine which is gradually replacing Unity)

      Additionally, developing a game requires many, many different parts. It’s not just the engine, it’s making the models, it’s making the materials, textures, shaders, programming, scripting, writing, and so on. Some, like 3d modeling, already have decent FOSS tools (Blender for example). Others, like the Substance suite (material authoring and texture painting) or Photoshop (image editing) don’t have a good enough FOSS alternative to be replaceable. Furthermore, many studios have specialized plugins or companion programs the studios developed or purchased which are only compatible with Substance, Photoshop, etc.

      So you’re not just fighting game engines, you’re fighting every step of the process. Adobe (and Autodesk, fuck Autodesk too) products, when used, tend to be deeply embedded in most professional workflows. You’d have to replace the software and any specialized plugins or programs designed specifically to interface with the software. I mean, good luck, it’s just a hell of a lot more complicated than you seem to think.

      • PenisWenisGenius@lemmynsfw.com
        link
        fedilink
        arrow-up
        3
        ·
        edit-2
        4 months ago

        Making a game isn’t easy regardless of which software ecosystem you use. People just need to know there are options.

        “more complicated than I seem to think”. I’m not going to dox myself just to win an argument. I still stand by my claim that there are viable ways to develop fairly complex games that don’t involve the unity + a bunch of corporate shit nor unreal + a bunch of corporate shit.

        • Mossy Feathers (She/They)@pawb.social
          link
          fedilink
          arrow-up
          2
          ·
          4 months ago

          You say they’re viable, but most people don’t want to make their own engine to make a game. Most people wanna make a game, not a game engine. Furthermore, while I honestly believe that the FOSS community could easily match commercial projects, doing so requires people to acknowledge the software’s shortcomings, talk to the professional users about what kinda UI they want, and so on. That means you can’t throw lines at them like “user inexperience” or “just learn a new program”. They’re professionals, having to learn a new program cuts into their income. Learning new programs means they aren’t making things, which means they aren’t making money.

          I know I’m kinda rambling a bit and may not be super coherent (if so, I apologize, I’m running on low sleep), but I’m not trying to be a doomer or say “that’s impossible”; I think what I am trying to say is that I don’t think the FOSS community currently has all the necessary software features or ease of access for professionals.

          • FrostyCaveman@lemm.ee
            link
            fedilink
            arrow-up
            1
            ·
            4 months ago

            Last time I tried to develop a game I accidentally built a game engine instead. Consequences of just doing what seems interesting instead of focusing on building an actual thing

      • andrew_bidlaw@sh.itjust.works
        link
        fedilink
        arrow-up
        2
        ·
        4 months ago

        Last I checked Adobe doesn’t have any 3d game engines, so that’s not really a solution, heh.

        Macromedia Flash wakes up to find itself in a coffin under two meters of concrete with a tombstone calling it a dozen of different names.

        Idk which one it was at the time, but when I installed Flash into my systems back then they did promote their capability to create 3d games.

        Adobe (and Autodesk, fuck Autodesk too) products, when used, tend to be deeply embedded in most professional workflows.

        Can’t disagree. They both also love to litter their data all over the system. Worse than malware in that department.