Skip to main content
RespawnDailyExplore

Technical Support

Neverness to Everness — Controller detected in Windows but not in game

Reposting with more detail after my last thread got no traction. It seems to depend heavily on region, which nobody mentions anywhere.

18 replies433 viewsStarted 4 Jun 2026Last activity 18 Jun 2026
  • controllers
  • support
  1. Riftcrow
    RiftcrowOriginal post

    @riftcrow · 4 Jun 2026, 14:51

    #1

    Reposting with more detail after my last thread got no traction. It seems to depend heavily on region, which nobody mentions anywhere.

    Marking this solved once something actually works.

  2. Shadowstein

    @shadowstein · 5 Jun 2026, 04:16

    #2

    The usual fix here is the wiki number is theoretical; real results are always a bit lower.

  3. Pilot KX

    @pilot_kx · 5 Jun 2026, 19:14

    #3

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

  4. Leo R.

    @leo_r · 7 Jun 2026, 20:00

    #4

    I went through this last month. that behaviour is intentional, even though it is poorly explained in-game.

  5. Zephyrash

    @zephyrash · 8 Jun 2026, 06:42

    #5

    From experience, do not copy someone else’s config wholesale — start from defaults and adjust to your own setup.

    Worth a shot before anything drastic.

  6. Echofen

    @echofen · 8 Jun 2026, 16:58

    #6

    Had the exact same issue. worth testing on a second account to rule out something profile-specific.

  7. Theo N.

    @theo_n27 · 9 Jun 2026, 09:29

    #7

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

  8. Aya H.

    @aya_h10 · 10 Jun 2026, 08:09

    #8

    In my testing, worth testing on a second account to rule out something profile-specific.

    Good luck, it is a common snag.

  9. Jonas S.

    @jonas_s · 11 Jun 2026, 03:39

    #9

    Had the exact same issue. give it a clean reinstall before assuming the hardware is at fault.

  10. Aria D.

    @aria_d19 · 11 Jun 2026, 22:21

    #10

    Speaking as someone who got it wrong initially, if it only happens in one mode, that narrows it down considerably.

    Others may have a cleaner method.

  11. Auroralynx

    @auroralynx · 12 Jun 2026, 08:04

    #11

    Speaking as someone who got it wrong initially, do the cheap diagnostic first — it costs nothing and rules out half the causes.

  12. Driftlynx

    @driftlynx · 12 Jun 2026, 18:09

    #12

    This comes up a lot, so: the averages hide the problem; look at the one percent lows instead.

    Worth a shot before anything drastic.

  13. Pilot KX

    @pilot_kx · 14 Jun 2026, 17:13

    #13

    Worth checking first: this changed for me after the last patch, so older threads may steer you wrong.

  14. Theo H.

    @theo_h · 14 Jun 2026, 22:04

    #14

    Not the answer you want, but do not copy someone else’s config wholesale — start from defaults and adjust to your own setup.

  15. Neonash

    @neonash20 · 16 Jun 2026, 08:30

    #15

    Quick correction to the above: the defaults are conservative on purpose, so there is usually headroom to gain.

  16. Neonloop

    @neonloop · 16 Jun 2026, 16:05

    #16

    For what it is worth, it depends heavily on your specific setup, so take any single number with a grain of salt.

  17. Nightshard

    @nightshard · 17 Jun 2026, 05:40

    #17

    Slightly different take — it is almost always a setting rather than hardware, so try the free fixes before spending anything.

    Worth a shot before anything drastic.

  18. Vertexvex

    @vertexvex · 17 Jun 2026, 22:47

    #18

    Agreed on most of this, except it is almost always a setting rather than hardware, so try the free fixes before spending anything.

  19. Novawolf

    @novawolf17 · 18 Jun 2026, 17:15

    #19

    Only partly related, but check whether an overlay is running before blaming the game itself.

Be specific and civil. Referral links are removed automatically.