Did the camera suddenly become slow during a session?
If it changed abruptly after entering a dungeon, opening the in-game shop or recording, treat it separately from your normal sensitivity preference. Players report similar symptoms, with different triggers. That is evidence of a recurring complaint, not a confirmed diagnosis for your machine.
A short recovery path
- Move to safety and tell your group before troubleshooting. Close chat and menus; check whether the menu cursor still moves normally.
- Keep the original camera values and DPI recorded. If neither changed, repeatedly raising them can leave the camera too fast when the symptom clears.
- When safe to leave the session, restart the game and compare the same movement. Several players report temporary recovery this way; it is not a guaranteed fix. Avoid exiting during a run or purchase without checking its consequences.
- If it returns, record the launcher, control mode, client version and the preceding action. Check current official notices and attach those reproduction steps to support.
Evidence status · checked November 1, 2026: the linked player thread reports dungeon and shop triggers and restart recovery. Disabling the Steam overlay is only an unconfirmed suggestion in that discussion. The official announcement feed reviewed today did not establish a confirmed fix for this particular symptom.
Player reports and replies · Official announcements · Official support
Previously changed Input.ini for inversion?
A community workaround author later reported that their custom lines override the in-game sliders. If you used that workaround, preserve a copy and compare your file with the exact changes you made before troubleshooting persistence. Do not replace the whole file with someone else’s configuration. This report is not an independently tested fix.
Original workaround and author’s update · Source-qualified inversion update
Camera sensitivity or menu cursor: which should you change?
If camera turning feels wrong but menu movement feels normal, test the in-game camera speed first. If only the menu cursor feels wrong, a camera-speed change may not help.
| What happens? | Try this first | Check the result |
|---|---|---|
| Camera turns too fast or too slowly | Find the published horizontal / vertical camera-speed labels; record your current value and change one axis. | Use the same landmark and hand movement, keeping mouse DPI unchanged. |
| Menu cursor feels too fast or slow | Record the original pointer and DPI settings before testing a single change. | Compare menu movement and camera turning separately; restore if the other becomes uncomfortable. |
| The changed value resets | Apply using the control actually shown, then close and reopen Settings. | Check the active profile and repeat after relaunch. Record the client version if it reverts. |
| The camera jumps or stutters | Use the camera symptom checks before changing several sliders. | Distinguish uneven frame delivery from consistently fast or slow turning. |
The paths and screenshot below retain their original source dates and verification limits. Record, apply and restore one change →
What do you want to change?
Record your original settings and change one camera setting or key assignment at a time. Use the same safe-area test before and after each change.
This guide provides tuning methods and suggested bindings. The camera menu path above is community-documented, while exact release-client labels, default shortcuts and slider ranges still need independent verification.
Find a test for your settings problem
Choose what feels wrong. Follow one test, record the original value, then keep or restore the change.
Menu paths remain source-qualified. Use the controls shown in your current client; the website does not change game settings.
How to change mouse sensitivity in AION 2?
Look for the horizontal and vertical camera movement speed controls under Settings → Graphics → Camera / Direction, as documented by a Global-client community guide. Record the original values, change one slider by a small step, apply using the controls shown, and test in a safe area. Keep your mouse DPI unchanged so you can tell what the in-game adjustment changed.
Cannot find a mouse sensitivity slider?
- Check the camera section for horizontal and vertical speed controls rather than searching only for “Mouse Sensitivity”. Record your region, client version and control mode.
- If those controls are absent, do not assume a hidden setting exists. Keep your original settings and use the symptom checks below.
- If you choose to test mouse DPI instead, record the original DPI, change only that value and check both camera turning and menu cursor movement. Restore it if other controls become uncomfortable.
Check a camera symptom · Record the labels your client actually shows. The guide does not verify a configuration-file workaround. For the announced Y-axis inversion option, see the official settings update.
Mouse DPI is not the same as camera sensitivity
Mouse DPI is a hardware setting; in-game camera sensitivity changes how your input turns the view. Cursor speed in menus is a separate symptom: do not assume a camera adjustment will also change inventory or interface cursor movement. If turning feels wrong but menu movement feels comfortable, test the game's camera control first rather than changing every input setting.
What is the best sensitivity?
There is no verified universal AION 2 value to recommend here. Your mouse, desk space and comfortable hand movement matter. Aim for a setting that lets you turn to a target behind you without running out of mouse space, then make small corrections without repeatedly overshooting. Do not copy a number from a different regional client or input device as though its scale were identical.
What the published camera settings screenshot shows
A community article published October 6 includes a settings image showing Camera Horizontal Move Speed and Camera Vertical Move Speed under Graphics. These are the shorter labels visible in that image; other menu views may use “Movement Speed”.
View the published settings screenshot ↗ Read the source and image credit ↗
Image credit reported by the source: NC via YouTube/@Grobs. The image’s exact client build is not supplied. We inspected the visible labels on October 11; this is not an Aion2Pilot live-client test or proof of the controls in every version. Compare the labels with your own client before following the camera test.
A two-minute camera sensitivity test
- Save a baseline. Note your current DPI, sensitivity value and control mode, where these are available. Keep them fixed except for the one setting you are testing.
- Turn and stop. Pick a stationary landmark in a safe area. Turn away, then turn back and stop on it. Repeated overshooting suggests trying a lower sensitivity; repeatedly running out of mouse space suggests trying a higher one.
- Track while moving. Walk around the landmark while keeping it in view. Check that small corrections remain comfortable and that your movement keys still work.
- Test your combat inputs. Where safe, use a familiar action and defensive response while moving the camera. A missed key or changed target may be a binding or targeting issue, not sensitivity.
- Retest one small change. Repeat the same route after adjusting a single setting. Keep the version that is easier to control; restore your baseline if the result is worse.
Use the same test before group content. A setting that feels fast while standing still may be difficult to control while tracking an enemy or reading ground effects.
Save your sensitivity test
Record the exact labels and values from your client before changing them. If the interactive form is unavailable, keep your own before-and-after note and screenshot.
Can you invert the Y-axis in AION 2?
NC’s October 13 PDT / October 14 CEST patch notes announce a Y-axis inversion option in Settings. The notice does not give its exact sub-tab or translated label. Check the updated client’s Settings menu; this is an announced feature, not our live-client test.
The same patch announces reduced Abyss battle stuttering, a fix for graphics configuration on PCs with two graphics cards, and removal of graphics settings from Steam Cloud. These do not establish a universal fix for every camera or performance symptom.
Official October 14 patch notes → · Source reviewed October 14, 2026.
After updating, record the settings actually shown on each device. A Y-axis direction change and camera movement speed are different controls; test them separately.
Movement Controls duplicate-entry fix
The October 7 patch announces a fix for repeated Movement Controls entries under Settings → Key Settings → General. This is separate from the earlier duplicate Content-entry fix in Menu. It does not establish a camera sensitivity slider path.
Official October 7 patch notes · Reviewed October 7, 2026 · Global. Patch-announced changes; individual client behavior has not been independently tested.
AION 2 keybind example: build a comfortable layout
Use this as a starting point for actions available to your character. These are suggested keys, not AION 2 defaults. Check existing assignments first, especially movement keys and mouse buttons.
| Action group | Example placement | Check before keeping it |
|---|---|---|
| Movement | Keep your current movement keys | You can move while pressing combat keys. |
| Frequent attacks | 1–4, if comfortable and available | You can reach them without looking down. |
| Emergency defense or movement | One free nearby key or mouse side button | It does not replace a movement or camera action. |
| Frequent utility | Q, E or R only if unassigned | The action still works while moving. |
| Menus and occasional actions | Keep existing keys initially | You can open and close menus without accidental combat inputs. |
What are the best keybinds? Keep the layout you can use reliably while moving. A copied layout that forces awkward reaches or conflicting modifiers is a poor fit. Test your frequent action and emergency response first, then add less-used actions.
Keybind priority
| Closest keys | Place here |
|---|---|
| Primary | Dodge, core attacks, interrupt, emergency defense |
| Secondary | Movement skills, control, frequent utility |
| Reach keys | Long cooldowns, mounts, menus, rare consumables |
Keep similar functions in similar positions across characters. Avoid modifier combinations that interfere with movement.
How to test your AION 2 keybinds
- Record the original assignment before changing one binding.
- Check whether the new key conflicts with another action, then save or apply using the controls actually shown in your client.
- In a safe area, test moving while using your most frequent action and your defensive response.
- Confirm target changes, camera movement and menu access still work.
- If an input fails, check focus, conflicting assignments and modifier keys. Restore that single assignment before changing more settings.
The menu-binding path above is named in the official notice. Combat-binding tabs, default keys and reset controls still require Global-client verification.
Camera feels too fast, too slow, or stops moving?
| Symptom | First check | What to avoid |
|---|---|---|
| View turns too fast or slowly | Compare mouse DPI and the available camera setting with your baseline. | Changing both at once. |
| Menu cursor feels wrong, camera feels fine | Check your mouse profile and cursor behavior separately. | Assuming a camera control changes menu cursor speed. |
| Camera stops responding | Check whether chat or a menu has focus. | Resetting every binding immediately. |
| View stutters or skips | Check frame-rate stability with the PC performance guide. | Increasing sensitivity to hide frame drops. |
If behavior changes after switching control modes, review that mode's displayed descriptions and bindings. Camera movement and target selection may differ. For stuttering, use the PC performance guide rather than changing sensitivity.
If a problem returns without a setting change, record the client version, control mode and steps that reproduce it for official support.
Before resetting all controls, record your custom bindings. Restore only the changed option when possible so you do not lose a working keybind layout.
Targeting setup
If the client offers bindings for target cycling, nearest hostile, party members or self-targeting, choose the ones your role needs. Tanks and healers should practice switching targets before entering difficult group content.
Combat readability
Keep enemy telegraphs and important party effects visible. Reduce decorative effect density before removing information needed for mechanics.
Inventory sorting: what is safe to do now?
For players searching how to sort inventory: this guide does not yet verify the Global client's sort-button location, shortcut or automatic-sort behavior. Use the labels and tooltips shown in your client rather than a guessed hotkey.
- Check each item's purpose, binding and expiry before reorganizing it.
- If your client offers an item lock or protection control, use it for valuable equipment before dismantling or selling.
- Distinguish rearranging slots from deleting, selling or dismantling. Read the confirmation before any destructive action.
- Keep reward mail and purchase references until delivery is confirmed.
Change, test and restore your controls
Use this worksheet before changing a setting. The key-setting paths below are named in official notices; the camera path above is community-documented. This diagram is not a game screenshot.
1. Record the baseline
Take a screenshot in your own client. Record mouse DPI, the exact camera-control label and value, any modifier, and the existing key for the action you want to change. Keep DPI unchanged during the comparison.
2. Change one control
For sensitivity, check the reported Settings → Graphics → Camera / Direction path against your live client and note the exact control label. Adjust one step, then use the same landmark and movement in the two-minute sensitivity test. For keys, review conflicts before changing one assignment.
3. Apply and verify persistence
Use the save or apply control actually shown. Close and reopen settings to check the value, then leave and re-enter the game when convenient. If it changed back, inspect the active profile and record what happened before making another edit.
4. Restore the single change
Re-enter the original value or key from your screenshot and apply it. Repeat the same test. A full reset can remove other custom bindings, so restore the recorded control first.
| Record | Before | After / decision |
|---|---|---|
| DPI and camera label | Your original values | One changed value; same DPI |
| Action and key | Original key and modifier | New key; conflict check |
| Result | Same landmark, target and movement | Overshoot, tracking, simultaneous movement; keep or restore |
Keep this record with your own screenshots or build notes. Website cloud sync covers saved website tools; it does not change or sync game-client settings.