To zoom out in Azeroth Survivors, check Key Bindings → CAMERA: the observed v0.135.1 menu assigns CAMERAZOOMOUT to mouse-wheel down and PREVVIEW/NEXTVIEW to Home/End. For automatic following, open Options → Controls and compare Camera Following Style after recording your current value. These are menu observations, not an input or comfort test.
On this page
| Task | Observed control | What the evidence establishes |
|---|---|---|
| Compare camera distance | Mouse wheel up/down | Zoom command assignments; no measured maximum |
| Choose another view | Home / End | Previous / next view, not a FOV value |
| Investigate automatic following | Smart / Always / Never | Three menu choices; effect needs a controlled comparison |
| Compare terrain or bobbing | Follow Terrain / Head Bob | Independent toggles, not a proven combined fix |
| Adjust mouse response | Invert Mouse / Mouse Sensitivity | Separate direction and sensitivity entries |
| Adjust controller response | Invert Camera X/Y; Camera Speed; Zoom Speed | Independent gamepad entries, menu support only |
| When changes apply | Controls / Gamepad footers | Next run / at once, respectively |
Name the movement before changing settings
A turning view, automatic recentering and a close camera are different problems. First note what happens without changing anything: does the scene turn while you hold A or D, return after you stop, move with terrain, or simply show less of the surroundings than you want? A useful report describes the input and the moment the movement begins, rather than calling every case a field-of-view problem.
In the observed v0.135.1 Key Bindings → MOVEMENT menu, MOVEFORWARD is W/UP, MOVEBACKWARD is S/DOWN, TURNLEFT is A/LEFT, TURNRIGHT is D/RIGHT, STRAFELEFT is Q and STRAFERIGHT is E. These are separate turning and strafing bindings. Automatic camera follow is a different Controls setting; this menu snapshot is not an input test or a recommendation to remap your keys.
A Chinese player discussion includes a report of the view turning with A/D and a reply about holding the mouse to maintain a view. That is a small community exchange, not a confirmed universal fix. It does not identify a mouse button clearly enough for us to prescribe one. The menu evidence below is the firmer starting point.
Find Controls and preserve your starting point
Open the original game’s Options menu and choose Controls. The inspected panel contains Camera Following Style, Follow Terrain, Head Bob, Auto-Follow Speed, Invert Mouse and Mouse Sensitivity. Record the values or take your own screenshot before touching them. Include whether you are using the browser game, another client version, a mouse or a controller.
The Controls footer says changes are saved immediately and apply to the next run. Therefore, closing the panel and seeing no difference in an already running session is not a reliable failed test. Keep a baseline you can restore, and make the comparison in a subsequent run instead of changing several controls repeatedly.
Separate automatic following from terrain and bobbing
Camera Following Style shows three choices: Smart, Always and Never. If your main concern is a view that returns or follows when you do not want it to, trying Never is a reversible way to isolate that setting. It is an editorial test suggestion, not an observed fix for every rotation report. Restore your previous choice if the comparison is unhelpful.
Treat Follow Terrain and Head Bob as separate toggles. If one is enabled in your own setup, try disabling only that one before the next comparison. Keep the other controls unchanged. Auto-Follow Speed showed 180 in the inspected menu, but this is one displayed sample, not a default or recommended optimum. We have not measured its range or response in a run.
Use the verified zoom and view bindings
Under Key Bindings, expand CAMERA. The observed assignments are CAMERAZOOMIN → MOUSEWHEELUP, CAMERAZOOMOUT → MOUSEWHEELDOWN, NEXTVIEW → END and PREVVIEW → HOME. Check your own bindings first if a key behaves differently. A reassigned command or a browser page receiving the input can look like an unavailable camera feature.
Zoom and switching views are distinct actions. Try the wheel when you want to compare distance, and Home or End when you want to compare the available views. These four assignments do not establish a free-rotation mouse gesture, a numerical maximum distance, or a field-of-view slider. We do not provide an unverified console command to overcome an unknown limit.
Mouse inversion is not a speed adjustment
Invert Mouse and Mouse Sensitivity are separate entries in Controls. Keep inversion unchanged while comparing sensitivity, then restore the recorded value before testing direction. This avoids mistaking a reversed movement for excessive speed. If the wheel or Home/End affects the surrounding web page instead, check that the running game is receiving input before drawing conclusions about its camera. No specific laptop key combination or mouse-button rotation gesture is established by the inspected CAMERA list.
Gamepad has independent camera controls
The Gamepad panel separately exposes Invert Camera X, Invert Camera Y, Camera Speed, Zoom Speed and Stick Dead Zone. Its help text assigns movement to the left stick, turning the view to the right stick and zoom to bumpers and triggers. These are observed menu instructions; we have not tested a physical controller or a Steam Deck.
Keep direction, turning speed and zoom speed separate when comparing a controller setup. The inspected values were Camera Speed 100%, Zoom Speed 100% and Stick Dead Zone 25%; none is presented as a best setting. Unlike Controls, the Gamepad footer says changes apply at once. Do not carry the next-run instruction from the mouse panel over to this panel.
Compare one variable, then keep or restore it
Choose a short, repeatable check: the same input device, the same movement and one changed setting. Note whether the unwanted motion changes, whether ordinary turning remains usable, and whether the camera still shows enough of the scene. If nothing improves, restore the previous value before trying another option. Avoid using Defaults as a first diagnostic step, because it removes the clean comparison you just recorded.
This is a way to organize observations, not a promise of comfort or a medical remedy. If the motion is unpleasant, stop the comparison rather than continuing a run to complete a checklist. There is no verified universal combination of Never, terrain, bobbing and sensitivity in the evidence used for this page.
When the menu or problem does not match
The original menu inspected on November 1 displayed v0.135.1, build 90898d5e3. If your labels or bindings differ, record the version and the exact missing field. Explain whether this is unwanted motion, an unresponsive command or a game that never reaches the menu. A launch failure belongs in the troubleshooting guide, not in a camera adjustment sequence.
Do not delete your save to test a view setting. Keep the settings baseline and any normal backup separate from the experiment. These new menu observations also do not upgrade the companion planner’s independently documented 0.131.0 rules; menu guidance and calculator data have different verified scopes.