• _sideffect@lemmy.world
    link
    fedilink
    arrow-up
    7
    arrow-down
    2
    ·
    3 months ago

    I might get downvoted, but the fact that they are going to be using UE5, and knowing that other dev studios who have used UE for years continuously struggle with it, doesn’t give me hope on launch for this game.

    I expect the requirements to be sky high, and endless patches to come just to get it at 60 fps. (Don’t even get me started on dlss and an rtx 6000 series that will probably be recommended)

    • NocturnalMorning@lemmy.world
      link
      fedilink
      arrow-up
      11
      ·
      3 months ago

      I use UE5 as an Indie Dev, and I can honestly say if I hadn’t spent the better part of using UE5, I would go back and use UE4.

      There are still so many things they need to work out with UE5 for it to be at the level UE4 was/is. Things that worked fine in UE4 struggle performance-wise bcz they changed the algorithms so much, generally for the better, bit they haven’t seemed to figure out how to make a lot of things performant yet like they should be.

      That said, companies have a whole other level of support with their licensing agreements, so I wouldn’t take what I have to say with a grain of salt.

      Overall UE5 is a major improvement over UE4, it’s just gonna take time before features like world partition have all their bugs and kinks worked out. I would still prefer the old world composition solution for open world games over the new stuff after my most recent experience.

      You can build massive world’s with the UE4 solution of world composition, and they haven’t deprecated that, so they were at least smart about not getting rid of systems prematurely. And from my understanding they have no intention of depreciating the old system since so many people use it. Just my two cents on the subject.

      • _sideffect@lemmy.world
        link
        fedilink
        arrow-up
        2
        ·
        3 months ago

        Yeah, I use 5.1 for my personal project, and 4.2 at work, and I can see all the DEPRECATED DO NOT USE!!! in comments, that they still kept around for a while

        (But what’s funny, is that they didn’t even refactor some of their own code and still call those deprecated functions)

        • NocturnalMorning@lemmy.world
          link
          fedilink
          arrow-up
          2
          ·
          3 months ago

          That’s hilarious. I don’t muck around in the engine code myself. Haven’t had a need to do it. Also feel like that would be asking a lot of myself given that I don’t have any help with my projects.

          Sometimes I wish I’d go back and just use UE4, but I’m suffering the sunk cost fallacy. And I know eventually UE5 will be where it needs to be.

          I actually started using UE5 when my friend got into game dev a couple years ago, , so I told him I’d switch to Unreal and learn it with him. Had no idea it was a beta release when I agreed to that.

          • _sideffect@lemmy.world
            link
            fedilink
            arrow-up
            2
            ·
            3 months ago

            Even Fortnite by the engine devs themselves cant remove micro-stuttering, so what hope does anyone else have :P

    • Hypx@fedia.io
      link
      fedilink
      arrow-up
      8
      arrow-down
      1
      ·
      3 months ago

      I’m curious if there is any other engine they could’ve used (other than sticking with REDengine that is).

      And you should expect 30fps, not 60. Only the highest-end machines will see 60 fps.