this shuts down rumors that bethesda will move to unreal engine for ES6

  • Hemingways_Shotgun@lemmy.ca
    link
    fedilink
    English
    arrow-up
    8
    ·
    8 hours ago

    At this point there is nothing that they could do to make Creation Engine feel “new”. I don’t understand why they keep beating that dead horse.

    A couple of months ago, I had some extra money, so I bought Starfield because I had an itch to go back into my Crimson Fleet character.

    The problem was that a couple of weeks before that, I had also purchased a game that I had wanted for years, but could never justify spending the high price of new games on, Red Dead Redemption 2. In comparison, Starfield just felt so…lazy… in ways both big and small, beyond the common issues like repetitive dungeons, barren worlds, loading screens, etc…

    The biggest thing I noticed immediately was the effect of bumping into people as you’re walking. If you compare a Rockstar Game (Or even an assassin’s creed game), where npcs will make a comment, will move out of the way, get upset, etc… Whereas in Bethesda can’t be bothered to do anything except slide you to the right when bumping into a character, who doesn’t react or flinch in any way.

    I started noticing those little things fucking everywhere. And I have to believe that little limitations like that are because it’s running on an engine that is older than dirt.

    • eRac@lemmings.world
      link
      fedilink
      English
      arrow-up
      9
      ·
      8 hours ago

      Nah. They are detecting the collision in order to push the player, so the engine is doing the work already. They could easily add an on_collision_player event in the NPC controller that fires at that point to handle NPC reaction.

      The age of the engine impacts things like loading screens, poor use of modern hardware, etc. The 2004-era NPC handling is simply a reluctance to do any more than the bare minimum.