UI Fixes Guide — Camera Focus, Resolution & Controls

A Reddit player recently asked the question that haunts every Going Medieval session: "How do I fix that wrong focusing?" The camera in Going Medieval has a mind of its own. It snaps to random corners, locks onto the wrong settler, resets resolution on every launch, and sometimes zoom stops working entirely after an alt-tab. This guide covers every known UI and camera bug, their root causes, and the exact steps to fix them.

The "Wrong Focus" Problem — Why the Camera Misbehaves

The most common camera complaint is that selecting a settler causes the camera to jump to the wrong tile or lock into a follow mode that cannot be escaped. This happens because Going Medieval has two focus modes that can conflict: selection focus (camera recenters on whatever you click) and follow focus (camera continuously tracks a selected settler). When both are active, the camera fights itself.

To diagnose which mode is causing the problem, select a settler and watch the camera behavior. If the camera jumps once and then stays still, selection focus is the issue. If the camera continuously tracks the settler as they walk, follow focus is engaged. The follow mode toggle is the tilde key (`) by default, which many players press accidentally while reaching for the number row. Press tilde once to toggle it off, and the camera will stop following.

A deeper cause of wrong focus is the settler portrait click. Right-clicking a settler portrait recenters the camera on that settler without locking follow mode. Left-clicking a portrait selects the settler but does not move the camera. If you are accidentally right-clicking portraits while trying to assign jobs, the camera will appear to jump randomly. Train yourself to left-click portraits for selection and use the Home key (or your remapped focus key) when you actually want to jump to a settler.

Display and Resolution Fixes

Display problems in Going Medieval fall into three categories: resolution resets, UI scale issues, and window mode bugs. The table below covers every known display bug, its root cause, and the fix. Most of these require editing config files because the in-game settings menu does not always save correctly.

Camera Controls — Zoom, Pan, and Edge Pan

The Going Medieval camera has three movement modes: zoom (scroll wheel), keyboard pan (WASD or arrow keys), and edge pan (moving the mouse to the screen edge). All three can be active simultaneously, which is the source of most camera chaos. If the camera drifts on its own, edge pan is usually the culprit — a mouse resting near the screen edge triggers continuous panning even when you are not touching the keyboard.

To disable edge pan entirely, open Settings, then Controls, then Camera, and set Edge Pan Speed to zero. This forces all camera movement through the keyboard and scroll wheel, which is far more precise. Many veteran players disable edge pan permanently because the keyboard pan (WASD) is already fast enough and does not cause accidental drift.

Zoom range is fixed by the game but can feel limited on large maps. The maximum zoom-out shows roughly a 40x40 tile area. If you need to see more, use the overview overlay (F9) which renders the entire map as a top-down minimap. Click any tile in the overlay to jump the camera there instantly — this is the fastest way to navigate a large castle.

Keybind Recommendations for Better Camera Control

The default keybinds in Going Medieval are functional but not optimal. Several camera keys are placed awkwardly far from the WASD cluster, forcing you to take your hand off the mouse or move your fingers across the keyboard. The table below lists the default keys, recommended remaps, and the reasoning behind each change.

Common Display Bugs and Their Workarounds

• Black screen on launch. This is usually a fullscreen exclusive mode conflict with a multi-monitor setup. Fix: press Alt+Enter to switch to windowed mode, then change the display mode to Borderless Window in Settings. Borderless window is more stable than exclusive fullscreen on multi-monitor rigs.
• Flickering textures on walls and floors. This is a known z-fighting issue when two floor tiles overlap at the same height. Fix: remove the duplicate floor tile. If it persists, save and reload — the game rebuilds the render layer on load and the flickering usually disappears.
• Settler names and health bars disappear. This happens when the UI scale is set too low (below 80%) on high-resolution monitors. Fix: raise UI scale to at least 90% in Settings. If names are still missing, toggle the settler label hotkey (default: N) to force them to re-render.
• Build menu overlaps with the sidebar. This occurs at very low resolutions (below 1280x720) or when the UI scale is above 110%. Fix: lower the UI scale or increase the resolution. The build menu requires at least 1280x720 to display without overlap.
• Camera gets stuck inside a wall. The camera collision system can trap the view inside a multi-story building. Fix: press the Home key or your remapped focus key to snap the camera to the currently selected settler. If no settler is selected, press Tab to select one and then Home to focus on them.
• Scroll wheel zoom stops working after alt-tab. This is a window focus bug where the game loses scroll wheel input after losing focus. Fix: click once anywhere on the game window to restore input capture. If that fails, toggle fullscreen with Alt+Enter twice to force a window reset.

FAQ

Last updated: July 5, 2026