this post was submitted on 28 Mar 2024
142 points (96.7% liked)
PC Gaming
8568 readers
567 users here now
For PC gaming news and discussion.
PCGamingWiki
Rules:
- Be Respectful.
- No Spam or Porn.
- No Advertising.
- No Memes.
- No Tech Support.
- No questions about buying/building computers.
- No game suggestions, friend requests, surveys, or begging.
- No Let's Plays, streams, highlight reels/montages, random videos or shorts.
- No off-topic posts/comments, within reason.
- Use the original source, no clickbait titles, no duplicates.
(Submissions should be from the original source if possible, unless from paywalled or non-english sources.
If the title is clickbait or lacks context you may lightly edit the title.)
founded 1 year ago
MODERATORS
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.
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)
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.
Even Fortnite by the engine devs themselves cant remove micro-stuttering, so what hope does anyone else have :P