Combat depth after twenty hours

Page 1 of 2 · 30 posts

1. ESElla S.

   Ella S.Original post

   @ella_s · 6 Jun 2026, 02:41

   #1

   Adding my findings in case they help someone. Once it clicked, it felt obvious, but getting there took far longer than it should have.

   Thanks in advance to anyone who chips in.

2. ESElla S.

   Ella S.

   @ella_s · 6 Jun 2026, 02:41

   #2

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

3. SOSolarzen

   Solarzen

   @solarzen5 · 7 Jun 2026, 13:15

   #3

   The usual fix here is give it a clean reinstall before assuming the hardware is at fault.

4. DBDeniz B.

   Deniz B.

   @deniz_b29 · 8 Jun 2026, 15:27

   #4

   This is the bit people miss — that behaviour is intentional, even though it is poorly explained in-game.

5. DBDeniz B.

   Deniz B.

   @deniz_b29 · 8 Jun 2026, 18:22

   #5

   Had the exact same issue. nine times out of ten it is a driver or a background process, not the thing you suspect.

6. JSJonas S.

   Jonas S.

   @jonas_s · 10 Jun 2026, 22:35

   #6

   In my testing, if it only happens in one mode, that narrows it down considerably.

   Others may have a cleaner method.

7. ECEchoridge

   Echoridge

   @echoridge97 · 11 Jun 2026, 17:28

   #7

   Worth checking first: you get most of the benefit from the first adjustment; everything after that is marginal.

8. NENeonash

   Neonash

   @neonash20 · 14 Jun 2026, 04:32

   #8

   Depends on your setup, but broadly you get most of the benefit from the first adjustment; everything after that is marginal.

9. ECEchomoth

   Echomoth

   @echomoth5 · 14 Jun 2026, 04:54

   #9

   I went through this last month. the difference is real but small enough that you may not notice it while playing.

10. LULunarshade

    Lunarshade

    @lunarshade3 · 14 Jun 2026, 17:33

    #10

    Not the answer you want, but the defaults are conservative on purpose, so there is usually headroom to gain.

11. MLMaya L.

    Maya L.

    @maya_l · 15 Jun 2026, 01:22

    #11

    Short version: you get most of the benefit from the first adjustment; everything after that is marginal.

12. NENeonloop

    Neonloop

    @neonloop · 15 Jun 2026, 18:30

    #12

    Same boat here. the trick is to change one thing at a time and actually note the result before touching anything else.

    Worth a shot before anything drastic.

13. GLGlitchwave

    Glitchwave

    @glitchwave · 15 Jun 2026, 21:37

    #13

    The usual fix here is the averages hide the problem; look at the one percent lows instead.

14. SKSora K.

    Sora K.

    @sora_k · 17 Jun 2026, 10:38

    #14

    From experience, that behaviour is intentional, even though it is poorly explained in-game.

15. BLBlazelynx

    Blazelynx

    @blazelynx32 · 18 Jun 2026, 01:46

    #15

    This comes up a lot, so: you get most of the benefit from the first adjustment; everything after that is marginal.

16. COCobaltfox

    Cobaltfox

    @cobaltfox · 20 Jun 2026, 14:05

    #16

    The usual fix here is give it a clean reinstall before assuming the hardware is at fault.

    Good luck, it is a common snag.

17. IHInes H.

    Ines H.

    @ines_h · 21 Jun 2026, 00:09

    #17

    Worth checking first: nine times out of ten it is a driver or a background process, not the thing you suspect.

18. RIRiftlynx

    Riftlynx

    @riftlynx · 22 Jun 2026, 02:05

    #18

    Quick correction to the above: verify the files before anything else; it catches more problems than people expect.

19. KBKai B.

    Kai B.

    @kai_b · 22 Jun 2026, 04:46

    #19

    This is the bit people miss — do not copy someone else’s config wholesale — start from defaults and adjust to your own setup.

20. MLMika L.

    Mika L.

    @mika_l · 24 Jun 2026, 00:01

    #20

    In my testing, it depends heavily on your specific setup, so take any single number with a grain of salt.