this post was submitted on 19 Sep 2024
130 points (97.1% liked)

PC Gaming

8400 readers
260 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.
  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
[โ€“] NocturnalMorning@lemmy.world 1 points 4 weeks ago* (last edited 4 weeks ago) (1 children)

Game engines are harder to make/update than you think, and if everybody's expertise is in a homegrown engine, you cant just expect the team to know newer technologies at the drop of a hat.

[โ€“] lemming007@lemm.ee 1 points 3 weeks ago* (last edited 3 weeks ago)

Understandable. At the same time, I can't see myself starting up ES6 and dealing with the same issues we've been dealing with in all Bethesda games: physics tied to framerate, input lag/mouse acceleration issues, distant land that looks like crap, loading screens for cities/caves, etc. It just feels so outdated when we have games with CryEngine that have none of these issues and run beautifully. With all the money Bethesda has, they can afford to license CryEngine and hire developers proficient in it.