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:

  1. Be Respectful.
  2. No Spam or Porn.
  3. No Advertising.
  4. No Memes.
  5. No Tech Support.
  6. No questions about buying/building computers.
  7. No game suggestions, friend requests, surveys, or begging.
  8. No Let's Plays, streams, highlight reels/montages, random videos or shorts.
  9. No off-topic posts/comments, within reason.
  10. 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
you are viewing a single comment's thread
view the rest of the comments
[–] _sideffect@lemmy.world 2 points 7 months ago (1 children)

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 2 points 7 months ago (1 children)

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 1 points 7 months ago

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