Battlefront 2 Mouse Not Working | Fixes That Stick

When your crosshair won’t move, the menus ignore clicks, or the camera snaps as soon as you spawn, it’s maddening. Most mouse issues in Battlefront II come from a small set of conflicts: the game losing focus, an overlay grabbing input, a driver layer filtering raw movement, or a controller profile taking priority.

This walkthrough keeps the steps tight and practical. Start with the fast checks that rule out the common traps. Then move into Windows settings, overlays, and game files.

Battlefront 2 Mouse Not Working On PC After Updates

If the mouse worked last week and now it’s dead or half-dead, treat it like an input conflict until proven otherwise. Updates to the EA app, Steam, graphics drivers, Discord, GeForce Experience, Windows Game Bar, or a mouse utility can change how input is captured.

Before you change a bunch of settings, pin down what “not working” means. That detail points to the right fix.

• Menu clicks fail — The game may be unfocused, an overlay may be on top, or Windows scaling can mis-map the cursor.
• Camera won’t move — Raw movement is getting blocked, the game is reading a controller, or a background app is taking the mouse hook.
• Mouse moves in menus, not in matches — A profile, overlay, or input mode is switching when the match loads.
• Mouse works until Alt+Tab — Focus or fullscreen behavior is the main suspect.

Do one sanity check. Close the game, unplug any controllers, wheels, HOTAS gear, or Bluetooth pads, then launch again. If the mouse wakes up, you’ve found the cause.

Confirm The Game Is Taking Mouse Input

Battlefront II can look “stuck” when it’s running, yet not actually receiving mouse input. This section is about getting a clean game window with no extra layers grabbing the cursor.

Start With A Clean Focus Test

Launch the game, then click once on an empty area of the desktop and click back into the game window. If the cursor starts responding, the issue is focus. Keep going so it stays fixed after you switch apps.

1. Run borderless first — Switch to Borderless Window in video settings, then restart the game to retest focus.
2. Disable mouse capture helpers — Turn off any “aim assist” style mouse tools, pointer enhancers, or macro layers while testing.
3. Turn off in-app overlays — Disable overlays one by one so you can spot the one that steals input.

Check For A Hidden Overlay Layer

Overlays can sit on top of the game even when they aren’t visible. They still hook input, so the game never sees raw movement.

• Disable EA overlay — In the EA app settings, toggle the in-game overlay off, then relaunch.
• Disable Steam overlay — Turn off the in-game overlay for Battlefront II, then test again.
• Disable Discord overlay — Disable it globally or just for the game, then retest camera movement.
• Disable GeForce overlay — Turn off the in-game overlay in GeForce Experience or the NVIDIA app.
• Disable Xbox Game Bar — Turn it off in Windows settings, then relaunch the game.

Make Sure A Controller Isn’t Taking Priority

Some setups load a controller profile even when the device is idle. That can mute mouse look inside a match. With the game closed, unplug controllers and disable controller remapping apps for one test run.

1. Exit Steam Input tools — Close Big Picture features and any controller mapping overlays.
2. Quit DS4Windows style apps — Close controller emulators so the game can’t latch onto a virtual pad.
3. Test with no Bluetooth pads — Disconnect paired controllers for a single launch, not just a sleep state.

Fix Windows Settings That Break Mouse Look

Once you’ve proven focus and overlays aren’t the whole story, shift to Windows input settings. The goal is a clean path from your mouse to the game without scaling glitches or USB power cutoffs.

Turn Off Pointer Features That Add Jitter Or Lag

Most games ignore Windows pointer acceleration, but driver utilities can still apply smoothing that feels like a dead mouse.

• Disable Enhance Pointer Precision — In Windows mouse settings, turn it off, then retest aim control.
• Set a steady DPI — Use one DPI step during testing so the aim feel stays consistent across restarts.
• Pause vendor suites — Exit Logitech G Hub, Razer Synapse, Corsair iCUE, or similar apps for the test.

Fix High DPI Scaling And Fullscreen Behavior

Cursor misalignment in menus often comes from scaling. If clicks land “next to” buttons, fix scaling first. You can also force Windows to handle scaling for the game.

1. Set scaling to 100% — In Display settings, set scaling to 100, restart, and test clicks again.
2. Override DPI scaling — In the game exe properties, enable “Override high DPI scaling behavior” and choose Application.
3. Try borderless window — Borderless often avoids capture issues that show up in exclusive fullscreen.

Stop USB Power Saving From Cutting Input

Random dropouts can be a power setting, not the mouse itself.

• Disable USB selective suspend — In Power Options advanced settings, turn it off and reboot.
• Disable hub power saving — In Device Manager, uncheck “Allow the computer to turn off this device” for USB hubs.
• Plug into a different port — Use a rear motherboard port, not a front panel hub, then test again.

Repair Battlefront II Files And Input Config

When settings get corrupted, you can end up with odd behavior like a working cursor in menus but no camera look in a match. This section resets the game’s local config without deleting your whole library.

Reset Local Settings Safely

Battlefront II stores settings and cached profiles in your Documents folder. Renaming the folder forces the game to rebuild clean config on next launch. This is a fast, reversible test.

1. Close the game fully — Exit to desktop, then make sure the process is gone in Task Manager.
2. Rename the settings folder — In Documents, rename the Star Wars Battlefront II folder so the game recreates it.
3. Launch and retest — Start the game and check mouse look in Arcade or Instant Action first.

Verify Or Repair The Install

A damaged input file or a mismatched overlay component can ride along after a patch.

• Verify on Steam — Use the game’s Properties, Installed Files, then Verify integrity.
• Repair in the EA app — Use Manage, then Repair to recheck core files.
• Clear EA app cache — Use the app’s recovery or cache clear option, then launch again.

Reset Keybinds And Input Toggles

If you’ve changed bindings or imported configs, a toggle can be stuck. A full reset inside the game is worth a quick pass after the folder rebuild.

1. Reset controls to default — In the Controls menu, reset to default, apply, then restart the game.
2. Rebind mouse buttons — Bind primary fire and aim to default mouse buttons, then test in a match.
3. Remove raw input tweaks — If you used third-party tweaks, remove them for this test.

Handle Overlay, Hook, And Frame Tools

Anything that draws on top of the game can hook input. Some tools do it for FPS counters, some for streaming, some for RGB or audio. If your mouse dies only when you spawn, the hook might attach at match load.

Temporarily Remove Frame And Monitoring Tools

Monitoring tools can inject into the game process. Some combinations block mouse capture or add stutter that feels like input loss.

• Exit MSI Afterburner — Close Afterburner and RivaTuner Statistics Server, then retest.
• Turn off ReShade — Disable reshade injectors for one test run.
• Pause capture apps — Close OBS hooks or streaming overlays, then test camera control.

Check For Conflicts With Mouse Software And Macros

Macro layers can grab the mouse for profiles. If the mouse works in Windows but not in matches, test without the vendor app running.

1. Stop per-game profiles — Disable auto profile switching inside your mouse suite, then retest.
2. Remove on-the-fly scripts — Disable scripts, rapid-fire, or recoil macros during troubleshooting.
3. Reboot after uninstall — If you uninstall a driver layer, reboot so Windows loads the plain HID stack.

Use A Straight Test Plan When Nothing Works

At this point you’ve ruled out the usual culprits. The fastest way forward is to isolate the problem with controlled tests: clean boot, alternate mouse, alternate port, and a fresh Windows user profile.

Run A Clean Boot Test

A clean boot starts Windows with only core services plus your drivers. That strips out overlay hooks and background utilities, without a full reinstall.

1. Disable non-Microsoft services — Use System Configuration, hide Microsoft services, then disable the rest.
2. Disable startup apps — In Task Manager Startup, disable non-needed items, then reboot.
3. Launch the game first — Start Battlefront II before opening chat, browsers, RGB tools, or capture apps.

Compare Results With This Quick Table

Finish With A No-Guesswork Checklist

If you want a clean “done” moment, run this list in order. Stop when the mouse works and leave the last change in place.

• Unplug controllers — Test the game with no pads or virtual controllers attached.
• Disable overlays — Turn off EA, Steam, Discord, GeForce, and Game Bar overlays for one launch.
• Switch to borderless — Use Borderless Window, restart, and test aim in a match.
• Clear local settings — Rename the Documents settings folder so the game rebuilds clean config.
• Verify the install — Run a verify or repair pass in your launcher.
• Cut monitoring tools — Exit RTSS, Afterburner, ReShade, and capture hooks for the test.
• Fix power saving — Disable USB selective suspend and hub power saving, then reboot.
• Run a clean boot — Launch the game before any background utilities start.

If battlefront 2 mouse not working still shows up after these steps, use the clean boot result as your compass. If clean boot fixes it, the fix is a conflict you can remove. If clean boot doesn’t fix it, focus on drivers, USB power, and the game’s config reset steps.

Most players get a full fix without reinstalling Windows. Keep changes small, test once, and you’ll land on the switch blocking your aim.

Send us your feedbackTell us what you thought about this post

Name * Email *

Your comment *

Quick check — what is …? *

Send feedback