The Legacy Edition Steam page does not publish an ultrawide support promise or aspect-ratio matrix. Treat 21:9, 32:9, and other non-16:9 behavior as something to verify in the current public build. Start with an unmodified native-resolution launch, compare gameplay, menus, HUD, cutscenes, and split screen, and keep a reversible 16:9 fallback.
Native test
Select the panel's native resolution in-game and restart once before judging the applied aspect ratio.
Gameplay view
Check whether the sides expand, the top and bottom crop, or the image stretches around known round shapes.
Interface view
Inspect health, prompts, subtitles, merchant panels, and inventory edges for clipping or excessive distance.
Safe fallback
Use a centered 16:9 resolution with pillarboxing when native output hides information or distorts composition.
Establish a clean 16:9 reference
Before changing aspect ratio, capture a normal 1920×1080 or equivalent 16:9 scene in Bree. Include the hero, a circular UI element, subtitle area, and a fixed landmark near each side. This provides a reference for expansion, crop, and stretch.
Record graphics settings, display mode, and resolution. Close overlays that alter scaling. Do not install an original-release community patch before testing AppID 2523770; a fix written for AppID 32800 may target different files or behavior.
Exit normally after the reference so display configuration and campaign state are not changed during a crash recovery.
Classify the native ultrawide result
Select the native 21:9 or 32:9 resolution, apply, and restart if the menu requires it. Return to the same Bree landmark. If extra world appears on the left and right while vertical composition remains, the view is horizontally expanded. If top and bottom content disappear, it is cropped. If round shapes become ovals, the output is stretched.
Check aiming, target lock, and camera distance during combat. A wider view can still be unusable if target indicators or attacks leave the visible safe area. Test a crowded encounter rather than judging only an empty town.
Write the exact resolution and display mode with the observation. “Ultrawide works” is too broad when fullscreen and borderless can behave differently.
Inspect HUD, menus, and cutscenes separately
Open inventory, skill tree, merchant, quest log, map or travel interface, and pause menu. Check every edge for clipped labels or inaccessible controls. Trigger subtitles and verify they remain readable rather than stretching across the full panel.
Watch a normal dialogue and a pre-rendered or scripted cutscene. Pillarboxing in a fixed-aspect cutscene may be intentional even when gameplay expands. Do not apply a crop solely to remove black bars if it cuts faces or captions.
For split screen, repeat the readability check because each player’s view uses a different composition. A configuration acceptable in single-player may make local co-op HUD elements too small.
Prefer reversible display corrections
If native ultrawide stretches or crops, use a 16:9 resolution and configure GPU or monitor scaling to preserve aspect ratio with centered pillarboxes. Confirm that the desktop and other games are not globally forced into the same override unless intended.
Change FOV only through a current supported setting. No official Legacy Edition FOV or ultrawide configuration method is documented here. Avoid binary patches, memory editors, or old executables in the completion save environment.
If a community fix later becomes necessary, verify that it explicitly targets AppID 2523770 and the current release date, scan its provenance, preserve original files, and test offline before joining co-op.
Report a reproducible presentation fault
Capture paired 16:9 and native-ultrawide screenshots from the same location. Include resolution, display mode, GPU scaling setting, monitor model, public branch, and whether the issue affects gameplay, HUD, menus, or only cutscenes.
Submit that evidence to Aspyr support. Recheck official updates before retaining a workaround because a public build change can make an older fix harmful.
Use System Requirements for the official PC baseline and Controller Setup when the issue is input rather than composition.