• Hubi@feddit.org
      link
      fedilink
      arrow-up
      2
      ·
      3 hours ago

      Most UE5 games run like crap but they are not very prone to crashing in my experience.

    • I Cast Fist@programming.dev
      link
      fedilink
      arrow-up
      2
      ·
      edit-2
      3 hours ago

      I don’t play many UE5 games, never had problems with Pseudoregalia or Outpost Infinity Siege, the latter being really heavy on resources.

      I also thought Palworld was still on UE4? What’s the fix

      • Simon_Shitewood@lemmy.ml
        link
        fedilink
        arrow-up
        2
        arrow-down
        1
        ·
        2 hours ago

        The fix is so terrible that it comes with a warning only to do it if you’re absolutely sure you understand what you’re doing, along with the warning that I only know for certain that it works on a Ryzen 5 2600 CPU - it may work for other CPUs but I have no way to test that. It’s a fix I saw posted and ignored because, as the admin replied before locking said thread, it’s dangerous and there’s no reason it would actually work, but eventually independently found myself at: overvolt your CPU. Very carefully, just by a little bit. I don’t understand why it works, just that it fixed the regular crashes I had in Clair Obscur, Helldivers, and Palworld, and some of the crashes in Romeo Is A Dead Man (the latter also has other crashes related to the GPU). By all rights it shouldn’t work and suggests some very weird behaviour from UE5, but somehow it did. It comes with the side effects of needing really good cooling and potentially shortening the CPU’s lifespan, so it’s imperative you look for alternative solutions that aren’t stupid and dangerous first.