Players are reporting a frustrating Battlefield 6 Rush bug where the game won’t show the prompt to arm or disarm M-COM objectives. This issue stops you from interacting no matter where you stand, making the entire Rush mode feel broken and impossible to play. Many users say the interaction prompt doesn’t appear whether they’re attacking or defending, creating confusion and costing matches.
This problem often comes from input conflicts, controller settings, broken prompts, or objective hitbox bugs inside Battlefield 6. When the M-COM can’t be interacted with, it disrupts gameplay flow, progression, and even XP gain. Let’s break down the causes and fixes with strong keywords to help players searching for Battlefield 6 Rush bug or M-COM interaction not working.
Quick Fix
Reset your keybinds or controller layout, then reload into a new Rush match — this instantly restores the M-COM interaction prompt for many Battlefield 6 players.
Fix 1 – Reset All Controller or Keyboard Bindings
Sometimes the M-COM interaction bug in Battlefield 6 happens because your interact key is unassigned or overridden. Resetting all bindings forces the game to refresh the default button mapping, bringing back the interaction prompt.
- Go to Settings → Controls → Reset to Default
- Reapply sensitivity and aim settings afterward
- Restart the game before testing Rush again
How this helps: It restores the missing “interact” command so the objective prompt appears properly.
Fix 2 – Rebind Your Interact Button Manually
If resetting doesn’t work, your interact key/button might be overlapping with other actions. Manually setting it removes conflicts that stop the interaction prompt from appearing.
- Bind “Interact” to a single, unused key or button
- Avoid double-mapping it with revive or pickup keys
- Apply changes and reboot the match
How this helps: Ensures a clean, dedicated button to arm and disarm the Rush M-COM.
Fix 3 – Move to the Correct Hitbox Area
In Battlefield 6, the M-COM hitbox can glitch, especially on uneven terrain or damaged structures. Standing slightly off-center often prevents the prompt from showing.
- Approach the M-COM from multiple angles
- Try crouching or moving to its right-hand side
- Avoid standing directly on rubble or debris
How this helps: You find the working interaction spot when the hitbox is misaligned.
Fix 4 – Turn Off Custom HUD Settings
Custom HUD scaling or hidden UI elements might remove the interaction prompt entirely. If your HUD is modified, Rush interaction boxes may disappear.
- Reset your HUD to default
- Disable “Minimal HUD” modes
- Set UI scaling back to 100%
How this helps: Restores the on-screen interact prompt that may have been hidden.
Fix 5 – Switch From Controller to Mouse/Keyboard (or Vice Versa)
Input devices can bug out in Battlefield 6, causing the game to ignore interaction commands. Switching devices temporarily refreshes the input pipeline.
- Unplug controller and use keyboard
- Or switch back to controller after restarting
- Rejoin a Rush match after changing input
How this helps: Forces the game to detect your active input correctly.
Fix 6 – Leave the Match and Rejoin a Fresh Lobby
Some Rush rounds load with broken objective logic. Even if your settings are fine, the M-COM itself may spawn in a bugged state.
- Exit the current match
- Queue into a new Rush map
- Avoid servers with extremely high ping
How this helps: Loads a fresh objective instance so interaction works again.
Fix 7 – Disable Crossplay Temporarily
Crossplay can cause sync differences in objective states between platforms. Sometimes this stops the interaction prompt from appearing.
- Turn off Crossplay in Settings
- Restart Battlefield 6
- Try Rush again
How this helps: Removes cross-platform sync issues that affect objective prompts.
Fix 8 – Disable In-Game Overlays
Overlays like Discord, Nvidia, Steam, or Xbox overlays may intercept the interact button. This prevents M-COM actions from triggering.
- Disable Discord overlay
- Disable GeForce overlay
- Disable Steam Input overlay
How this helps: Frees the interact command so Battlefield 6 receives it properly.
Fix 9 – Check for Corrupted Game Files
Corrupted installation files often break M-COM objective prompts in Rush mode. A verification scan repairs them automatically.
- On Steam/Epic, run “Verify Game Files”
- On console, reinstall the game cache
- Restart your device afterward
How this helps: Replaces broken interaction scripts and restores objective behavior.
Fix 10 – Update or Reinstall Battlefield 6
If none of the fixes work, your Battlefield 6 build may be outdated or fully corrupted. A clean install solves deep-rooted interaction glitches.
- Update to the newest patch
- Fully reinstall if needed
- Restore your settings afterward
How this helps: Ensures the M-COM bug disappears with the latest stability fixes.
Fix 11 – Clear Your Battlefield 6 Cached Data
Sometimes the cached game data conflicts with objective scripts, causing the Rush M-COM not interacting bug. Clearing cache removes outdated temporary files that interfere with prompts.
- On console: fully power off → hold power button → clear cache
- On PC: delete the Battlefield 6 cache folder in Documents
- Restart the game afterward
How this helps: Removes corrupted cached data that blocks the M-COM interaction system.
Fix 12 – Change Your Soldier Interaction Behavior Setting
Battlefield 6 includes toggles for hold/tap interactions. If this setting breaks, the prompt might appear but won’t respond when pressed.
- Go to Settings → Gameplay → Interaction Behavior
- Switch from “Hold” to “Press” or vice-versa
- Apply changes and reload Rush
How this helps: Fixes broken interaction timing that prevents arming/disarming.
Fix 13 – Switch to a Different Soldier Class
Certain class loadouts bug the interaction logic, especially when running gadgets that override interact inputs (like repair tool or defib).
- Change to Support or Recon
- Avoid interacting while holding gadgets
- Try again next match
How this helps: Removes class-specific gadget conflicts with M-COM prompts.
Fix 14 – Drop Equipment Away From the M-COM
Deployables like ammo crates, med crates, shields, or turrets sometimes overlap with the M-COM hitbox. This blocks interaction completely.
- Move 2–3 meters away before placing gear
- Avoid placing equipment right on the objective
- Clear clutter if teammates stack gear
How this helps: Ensures nothing overlaps or obstructs the interaction zone.
Fix 15 – Lower Your Ping and Stabilize Network Settings
High latency can cause the Battlefield 6 Rush objective bug where the server doesn’t register your interact attempt.
- Switch to a nearer server
- Use wired Ethernet
- Disable background downloads
How this helps: Lets the M-COM register interaction commands instantly.
Fix 16 – Disable Controller Vibration or Adaptive Triggers
Some users report that PlayStation adaptive triggers block certain input actions during objective interactions.
- Turn off vibration
- Turn off adaptive triggers
- Relaunch the game
How this helps: Eliminates hardware feedback interference with the interact button.
Fix 17 – Lower Graphics Settings to Improve Input Responsiveness
Heavier graphics loads sometimes delay button inputs, making the M-COM arm/disarm prompt disappear or fail to register.
- Set textures to Medium
- Turn off motion blur
- Reduce post-processing
How this helps: Smoother input polling makes interactions trigger instantly.
Fix 18 – Avoid Sliding or Sprinting Into the Objective
Movement animations can cancel or hide interaction prompts. Sliding into the M-COM often prevents the button from appearing.
- Stop sprinting before you reach the objective
- Stand still for 1–2 seconds
- Try crouching gently toward the device
How this helps: Lets the game properly activate the M-COM interaction animation.
Fix 19 – Disable Third-Party Key Mapping Software
Programs like Xpadder, reWASD, and Razer Synapse can override the “Interact” key without you noticing.
- Close all remapping software
- Restart Battlefield 6
- Test the M-COM again
How this helps: Removes competing keybind layers that stop the prompt.
Fix 20 – Switch to a Different Server Region
Some servers have broken Rush objective scripts. Changing regions loads a fresh server with working logic.
- Pick a new region in server browser
- Avoid community servers with mods
- Join an official Rush playlist
How this helps: Ensures the M-COM spawns with correct interaction functionality.
Why can’t I interact with objectives in Rush mode in Battlefield 6?
If you can’t interact with objectives in Rush mode in Battlefield 6, the game is failing to activate the interaction layer that controls arming, disarming, and using M-COM stations.
This usually happens when your soldier loads into the match with a broken interaction script or incorrect input state.
Common triggers include:
- Spawning during a countdown
- Switching classes right as the round starts
- Input conflicts between controller and keyboard
- A soft-lock after dying or reviving
When this happens, the game never shows the “Interact” UI even when you stand next to the M-COM.
Redeploying, resetting keybinds, or restarting the match usually restores the missing Battlefield 6 M-COM interaction.
Why is the arm/disarm prompt missing in Battlefield 6 Rush?
The arm/disarm prompt missing in Battlefield 6 Rush means the game is not detecting your character as eligible to interact with the M-COM.
This can happen when the objective’s interaction radius fails to load or when the server desyncs your player state.
Reasons include:
- Cache corruption after long play sessions
- Controller input being overridden by another device
- Server latency delaying the objective state
- M-COM interaction bubble spawning in the wrong place
Because the objective prompt is tied to server-side logic, even minor desyncs can remove the prompt entirely.
Most players fix the issue by redeploying, switching loadouts, unplugging extra devices, or resetting controls.
Is Rush broken in Battlefield 6 — can’t arm M-COM stations?
Rush isn’t fully broken, but a large number of players are reporting the Battlefield 6 Rush M-COM bug where arming stations doesn’t work.
This occurs when either the M-COM logic fails to initialize or the map loads without proper objective scripting.
This results in:
- No arm/disarm prompt
- No interaction bubble around the bomb
- Players walking around the M-COM with no UI response
- Arming progress never starting
These issues appear most often on:
- Portal Rush playlists
- RedSec → Rush conversions
- Seasonal event Rush variants
If the server fails to load objective logic, no one in the match can arm the bomb, and switching servers is the only fix.
Did Battlefield 6 remove the ability to disarm objectives in Rush?
No — Battlefield 6 did not remove disarming.
If you can’t disarm objectives in Rush, it is almost always a bug in the interaction system rather than a feature change.
The disarm action disappears when:
- The M-COM interaction trigger breaks
- The player loads stuck in a restricted animation
- The server registers the objective in the wrong state
- The input layer responsible for “Use/Interact” doesn’t load
You still have the ability to arm and disarm, but the game temporarily fails to give you access to that function.
Resetting keybinds to default, switching classes, or redeploying restores the disarm prompt for most players.
Is this a known Battlefield 6 Rush bug or a control issue?
This is a known Battlefield 6 Rush bug, but it can sometimes appear as a control issue depending on the cause.
If your keybinds are conflicting or a controller is connected in the background, the game may ignore your interact input — making it seem like a control problem.
However, the majority of reports point to:
- Broken interaction scripts
- M-COM logic failing to load
- Server desync in Rush
- Missing objective activation bubble
Because the bug affects both attackers and defenders, it is not user error; it is a Rush mode objective glitch.
Players typically resolve it by redeploying, resetting keybinds, or switching servers if the entire map is affected.
Is the Rush interaction bug caused by broken objective collision zones?
Yes — one major cause of the Battlefield 6 Rush interaction bug is broken or misaligned objective collision zones around the M-COM.
Each M-COM has a hidden “interaction bubble” that must load correctly for the arm/disarm prompt to appear. When this bubble spawns at the wrong height, clips into terrain, or loads offset from the device, players can walk directly into the M-COM but never enter the interaction zone.
Broken collision zones are usually caused by:
- Terrain height mismatches
- Poorly loaded map segments
- Portal Rush variations with modified geometry
- Server-side issues failing to sync objective colliders
In these cases, no amount of button pressing will work because the interaction trigger physically isn’t where it should be.
Switching servers or redeploying often fixes malformed collision zones.
Does the M-COM interaction depend on faction or map spawn setup?
Faction does not directly limit interaction, but spawn setup and round transitions absolutely affect M-COM accessibility.
If you spawn during a round transition, join mid-match, or load into the wrong interaction state, the game may not register that your soldier is allowed to arm or disarm objectives.
Common triggers include:
- Switching sides after a round win/loss
- Late joining during an objective transition
- Spawning at a squad beacon too close to the M-COM
- Using a broken deployment zone
This can cause the interaction layer to fail to initialize for your faction’s current state.
Because Rush must dynamically enable or disable objectives based on which sector you’re in, any misalignment during spawn transitions can break the Battlefield 6 arm/disarm prompt.
A redeploy or full respawn often resets the correct state.
Is this bug linked to network desync or input lag in Battlefield 6?
Yes — network desync is one of the biggest root causes of missing M-COM prompts in Battlefield 6.
Rush relies heavily on server-side validation to determine whether you are close enough to interact. If your client becomes desynced from the server, it may show the correct visuals but not the correct interaction state.
Network-related causes include:
- High ping spikes
- Packet loss
- Server tickrate drops
- Latency between interaction request and server reply
When this happens, the server may think you are:
- Not close enough to the bomb
- Not in the correct angle
- Not eligible for the current objective state
Input lag can make this problem worse, but desync is the main issue.
Switching servers or restarting the match usually resolves Battlefield 6 Rush desync bugs.
Can the lack of prompt be tied to UI scaling or controller mapping errors?
Yes — UI scaling and controller mapping problems can both hide or block the Battlefield 6 interact prompt.
If your UI scale is set too low or if your HUD is partially off-screen, the arm/disarm prompt may never appear even though the interaction itself is active.
More commonly, controller mapping errors cause conflicts where two inputs bind to the same action. This breaks the “Use / Interact” action required for M-COM arming.
Typical causes:
- Duplicate binds
- Controller + keyboard both active
- Remapped interact button
- Hidden accessibility overrides
Resetting your settings to default often restores the interaction key and brings back the missing UI prompt.
This makes the Battlefield 6 Rush interaction bug look like a hardware problem when it’s actually a mapping conflict.
Does switching from controller to keyboard fix the issue in Rush mode?
Yes — switching from controller to keyboard (or vice versa) can temporarily fix the Rush objective bug because it forces the game to reload the interaction profile.
Battlefield 6 stores interaction actions separately for controller and M+K, so swapping inputs refreshes the underlying logic.
This switch helps when the game:
- Loads incorrect controller states
- Loses track of the interact button
- Misreads analog inputs
- Assigns interact to a dead keybind
- Fails to initialize the controller layer at match start
Many players report that simply unplugging their controller or tapping the keyboard once causes the arm/disarm prompt to appear again.
This indicates the issue is partially tied to input recognition errors, not just objective scripting.
Final Thought
The Battlefield 6 M-COM interaction bug in Rush mode is annoying, but most players can fix it with simple input resets, HUD adjustments, or a fresh match. As more users report the issue, DICE will likely address it in upcoming patches. Until then, these fixes help restore the interaction prompt and make Rush playable again. Stay updated on Battlefield 6 bug solutions to avoid losing matches to objective glitches.