Skip to main content
RespawnDailyExplore

Neverness to Everness

Endgame loop — is there enough to come back for? (mobile side)

Long-time lurker, first proper post. Rolling back to the previous version made the problem disappear entirely.

20 replies559 viewsStarted 25 d agoLast activity 16 d ago
  • discussion

Page 1 of 2 · 21 posts

  1. Kai B.
    Kai B.Original post

    @kai_b · 5 Jul 2026, 11:29

    #1

    Long-time lurker, first proper post. Rolling back to the previous version made the problem disappear entirely.

    Two settings appear to interact in a way the menu does not hint at. Still open to better approaches if anyone has one.

  2. Nora V.

    @nora_v · 5 Jul 2026, 22:07

    #2

    In my testing, check whether an overlay is running before blaming the game itself.

  3. Zoe T.

    @zoe_t · 6 Jul 2026, 01:19

    #3

    Same boat here. if it only happens in one mode, that narrows it down considerably.

  4. Hana H.

    @hana_h · 6 Jul 2026, 12:25

    #4

    Same boat here. ignore the loudest advice; the boring answer is usually the correct one here.

  5. Riftlynx

    @riftlynx · 6 Jul 2026, 23:37

    #5

    Speaking as someone who got it wrong initially, nine times out of ten it is a driver or a background process, not the thing you suspect.

  6. Onyxwave

    @onyxwave · 7 Jul 2026, 20:51

    #6

    Not the answer you want, but the averages hide the problem; look at the one percent lows instead.

  7. Theo T.

    @theo_t · 8 Jul 2026, 04:17

    #7

    Not the answer you want, but the safe move is the reversible one — you can always undo it if it makes things worse.

    Others may have a cleaner method.

  8. Halcyonkite

    @halcyonkite · 8 Jul 2026, 08:07

    #8

    Same boat here. do the cheap diagnostic first — it costs nothing and rules out half the causes.

  9. Halcyonkite

    @halcyonkite · 8 Jul 2026, 16:27

    #9

    I went through this last month. worth testing on a second account to rule out something profile-specific.

  10. Halcyonryu

    @halcyonryu · 9 Jul 2026, 01:15

    #10

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

  11. Astralnyx

    @astralnyx99 · 9 Jul 2026, 17:45

    #11

    Only partly related, but you get most of the benefit from the first adjustment; everything after that is marginal.

    Worth a shot before anything drastic.

  12. Sora K.

    @sora_k · 9 Jul 2026, 20:39

    #12

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

  13. Cobaltmoth

    @cobaltmoth81 · 10 Jul 2026, 20:48

    #13

    This comes up a lot, so: the difference is real but small enough that you may not notice it while playing.

    Let us know which part worked.

  14. Echobyte

    @echobyte · 10 Jul 2026, 22:47

    #14

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

  15. Yusuf V.

    @yusuf_v · 11 Jul 2026, 20:04

    #15

    Same boat here. if it only happens in one mode, that narrows it down considerably.

  16. Deniz B.

    @deniz_b · 12 Jul 2026, 05:16

    #16

    For what it is worth, it is almost always a setting rather than hardware, so try the free fixes before spending anything.

  17. Marco H.

    @marco_h · 12 Jul 2026, 06:13

    #17

    From experience, worth testing on a second account to rule out something profile-specific.

  18. Crimsonnode

    @crimsonnode86 · 12 Jul 2026, 19:09

    #18

    This comes up a lot, so: the difference is real but small enough that you may not notice it while playing.

    Good luck, it is a common snag.

  19. Damian Piszczek

    @damianpiszczek · 13 Jul 2026, 07:35

    #19

    Agreed on most of this, except it depends heavily on your specific setup, so take any single number with a grain of salt.

  20. Lunarpulse

    @lunarpulse · 13 Jul 2026, 08:03

    #20

    Not the answer you want, but it depends heavily on your specific setup, so take any single number with a grain of salt.

    That fixed it for me, at least.