Skip to main content
RespawnDailyExplore

Neverness to Everness

Combat depth after twenty hours — follow-up

Curious how everyone else approaches this, because my way feels clumsy. The default settings are clearly tuned for a different setup than mine.

20 replies898 viewsStarted 4 d agoLast activity 3 d ago
  • combat

Page 1 of 2 · 21 posts

  1. Nightshard
    NightshardModOriginal post

    @nightshard · 26 Jul 2026, 17:05

    #1

    Curious how everyone else approaches this, because my way feels clumsy. The default settings are clearly tuned for a different setup than mine.

    I tested it across a couple of sessions and the difference was smaller than the forums made it sound. Hopefully this saves someone else the afternoon it cost me.

  2. Priya R.

    @priya_r · 26 Jul 2026, 17:05

    #2

    Only partly related, but that behaviour is intentional, even though it is poorly explained in-game.

  3. Priya R.

    @priya_r · 26 Jul 2026, 17:37

    #3

    Adding to the above: keep a note of what you changed, otherwise you cannot undo it cleanly later.

  4. Yusuf E.

    @yusuf_e · 26 Jul 2026, 18:47

    #4

    For what it is worth, keep a note of what you changed, otherwise you cannot undo it cleanly later.

    Report back once you have tried it.

  5. Lunarshade

    @lunarshade3 · 26 Jul 2026, 19:06

    #5

    The usual fix here is temperature is the usual culprit when performance degrades over a session.

    Others may have a cleaner method.

  6. Onyxshade

    @onyxshade40 · 26 Jul 2026, 19:23

    #6

    Depends on your setup, but broadly check whether an overlay is running before blaming the game itself.

  7. Sam F.

    @sam_f · 26 Jul 2026, 20:04

    #7

    Only partly related, but the trick is to change one thing at a time and actually note the result before touching anything else.

  8. Ella S.

    @ella_s · 26 Jul 2026, 20:39

    #8

    Agreed on most of this, except verify the files before anything else; it catches more problems than people expect.

  9. Vertexkaze

    @vertexkaze · 26 Jul 2026, 20:46

    #9

    Short version: keep a note of what you changed, otherwise you cannot undo it cleanly later.

  10. Iris F.

    @iris_f21 · 26 Jul 2026, 21:27

    #10

    Counterpoint: keep a note of what you changed, otherwise you cannot undo it cleanly later.

  11. Nightshard

    @nightshard · 26 Jul 2026, 21:37

    #11

    Not the answer you want, but region and server load matter more than most guides acknowledge.

  12. Ivan L.

    @ivan_l · 26 Jul 2026, 21:45

    #12

    Worth checking first: verify the files before anything else; it catches more problems than people expect.

  13. Glitchreed

    @glitchreed61 · 26 Jul 2026, 22:51

    #13

    Depends on your setup, but broadly the averages hide the problem; look at the one percent lows instead.

    Report back once you have tried it.

  14. Maya F.

    @mayaf · 26 Jul 2026, 23:17

    #14

    Worth checking first: temperature is the usual culprit when performance degrades over a session.

  15. Ines K.

    @ines_k · 27 Jul 2026, 00:20

    #15

    This is the bit people miss — region and server load matter more than most guides acknowledge.

  16. Glitchwave

    @glitchwave · 27 Jul 2026, 00:24

    #16

    Same boat here. you get most of the benefit from the first adjustment; everything after that is marginal.

  17. Astralkaze

    @astralkaze · 27 Jul 2026, 00:43

    #17

    This comes up a lot, so: give it a clean reinstall before assuming the hardware is at fault.

  18. Ivan Z.

    @ivan_z14 · 27 Jul 2026, 01:28

    #18

    The usual fix here is if it only happens in one mode, that narrows it down considerably.

  19. Aya D.

    @aya_d · 27 Jul 2026, 01:33

    #19

    Same boat here. it is almost always a setting rather than hardware, so try the free fixes before spending anything.

  20. Viperzen

    @viperzen · 27 Jul 2026, 02:08

    #20

    Worth checking first: do not copy someone else’s config wholesale — start from defaults and adjust to your own setup.