Skip to main content
Join the Fortnite developer community

Sign in

Developers and their communities you followed will be shown here. Sign in to join the discussion.


  • Explore communitiesFind your community

Mouse Look Stops Working When Using Analog Joystick Despite "Lock Input Method as Mouse" Being Enabled

Posted inEpic Gamesvia 🐛 Bug Reports
OskarUK
OskarUK
OskarUK25 days ago
OskarUK25 days ago

Since the latest Fortnite update, mixed controller + keyboard + mouse input is no longer working correctly.

I use a MaxxStick analog joystick for movement, keyboard for other inputs, and mouse for aiming/camera control. This setup worked perfectly throughout the previous week, including immediately before the latest update.

My relevant settings are:

  • Ignore Controller Input: OFF

  • Lock Input Method as Mouse: ON

Before the update, I could simultaneously use:

  • MaxxStick → movement

  • Keyboard → keyboard inputs

  • Mouse → camera/aiming

After the update, Fortnite now appears to switch between controller and mouse input methods when the MaxxStick is used.

For example, if I enter a match using the mouse, mouse look works normally. If I then use the MaxxStick, controller movement works, but mouse movement/looking stops working. Mouse buttons and keyboard inputs can still register.

The issue can also be observed when switching input methods through the ESC menu. If I open the menu, move the MaxxStick, then close the menu, Fortnite switches to controller input and allows the joystick to work. Conversely, switching back to mouse input restores mouse look. There is a brief delay/a few joystick movements while Fortnite appears to recognise the change in input method.

The MaxxStick and mouse both work correctly outside Fortnite, and there were no hardware or configuration changes between the last working session and the first affected session.

Expected behaviour: With "Lock Input Method as Mouse" enabled, Fortnite should continue accepting mouse movement for camera control while simultaneously accepting the MaxxStick for analog movement and the keyboard for other inputs.

Actual behaviour: Using the MaxxStick causes Fortnite to switch its active input method to controller, preventing mouse movement/camera control while controller input is active.

This appears to be a regression introduced with the latest update and specifically affects mixed analog-controller + keyboard + mouse setups.

OskarUK
OskarUK
OskarUK25 days ago
OskarUK25 days ago

CommunitySupport
CommunitySupport
CommunitySupport24 days ago
  • Staff
  • Developer
CommunitySupport24 days ago
  • Staff
  • Developer

Hello. Thank you for the detailed description of the issue and the provided video. We've passed the info on for investigation. 🕵️‍♂️

MTHR_GoOse
MTHR_GoOse
MTHR_GoOse22 days ago
MTHR_GoOse22 days ago

Same for me.

ecyclops
ecyclops
ecyclops22 days ago
ecyclops22 days ago

I am having the exact same issue.

S3muta
S3muta
S3muta21 days ago
S3muta21 days ago

(Win11) I did some testing with my maxxstick, based on a report I saw on reddit. I used ViGem and VDX to force my stick to emulate ps4, and I found that things worked normally unless I left my mouse inactive for a few seconds while moving the stick. At this point, the mouse would stop working (like the reported issue) until I stopped moving the stick for a similar period of time. After leaving the stick inactive, the mouse would begin working once again and would function normally as long as I didn't exceed the timeout... All of this to say that there is a difference in behavior (if not an outright workaround) using this method. I'm not sure if I prefer setting the maxxstick to emulate WASD (clunky, but reliable) or the method outlined here (functional, but likely to flake out at the worst time...)

user avatar
User deleted their reply
VALARYUZ WTFF
VALARYUZ WTFF
VALARYUZ WTFF19 days ago
VALARYUZ WTFF19 days ago

any news abt this issue please ? :'(

Bryan de Caxias
Bryan de Caxias
Bryan de Caxias18 days ago
Bryan de Caxias18 days ago

o meu ainda não voltou a funcionar.

karv
karv
karv18 days ago
karv18 days ago

estou com o mesmo problema

Want to participate?
Sign in to leave a reply