Separate four different symptoms

An ultrawide display problem can mean the native resolution is missing, gameplay looks cropped, HUD elements sit too far apart, or a cinematic has bars. Changing one assumed Engine.ini value is not evidence that all four are fixed.

This page gives a reversible comparison sequence. We have not verified a universal BL4 21:9 or 32:9 configuration override, so it does not publish one as a working fix.

1. Confirm the display mode and native resolution

Record the monitor’s native pixel dimensions and Windows’ active display resolution. In the game’s available display options, compare fullscreen and borderless modes if both are offered. Capture the selected resolution and the result after applying it.

If a native resolution is not offered, check the display connection and GPU driver first. Do not assume a UI label or aspect-ratio control exists in every build; report the choices actually shown by your installation.

2. Compare gameplay and cinematics separately

Use a fixed position in normal gameplay and capture a screenshot. Then capture the cinematic or menu that looks wrong. Include the resolution and aspect ratio in both filenames.

A cinematic with bars does not by itself prove that gameplay is being cropped. Likewise, stretching a 16:9 image to fill the monitor is not the same as rendering a wider field of view. Keep those observations distinct in your report.

3. Adjust only the in-game FOV controls you can see

If your build offers a field-of-view control, record its current value, adjust it gradually, and compare the same scene. Choose a comfortable setting rather than copying a purported Samsung G9 test value from another machine.

We do not claim an exact slider maximum, hidden vehicle-FOV setting or universal 95–105 range. Those details need confirmation in the actual version and menu you are using.

4. Treat HUD placement as its own issue

Check the current interface/accessibility options for HUD and text controls. Record which controls exist and their values before changing them. If no appropriate control is offered, include a screenshot showing the affected HUD element and monitor resolution in your support report.

Do not add guessed HUDSafeAreaScale, HUDScale or old Oak2 keys to a file and describe them as supported BL4 options. For any experiment with a documented mod, back up the actual game-data folder first and use the author’s version-specific instructions; see the backup guide.

5. If the wider resolution causes low FPS

Higher pixel counts can change rendering load. Keep the same gameplay scene and compare the game’s supported upscaling methods under Options → Visuals → Advanced → Resolution Scaling. Then use the low-FPS comparison routine. Resolution scaling is a performance comparison, not a repair for incorrectly framed cinematics.

What to include in an ultrawide report

  • Monitor model, native resolution, active Windows resolution and connection type.
  • GPU, driver and game version.
  • Fullscreen/borderless setting and selected game resolution.
  • Screenshots of normal gameplay, the affected cinematic/menu, and the available FOV/HUD controls.
  • Whether the problem reproduces at a standard 16:9 resolution.

The official PC guide is a driver/performance baseline; it does not establish a universal ultrawide configuration hack. Current update notes are the right place to check for a documented display change.

FAQ

Can I guarantee a 32:9 fix from an Engine.ini line? No universal BL4 line has been verified for this guide. Use the stock settings and comparisons above before considering a version-specific mod.

Will a mod be safe in online play? A display-mod label is not a compatibility or account-safety guarantee. Check the actual author’s requirements and test separately from a main save.

Source and reporting a remaining problem

This checklist follows the official PC troubleshooting guide, checked October 18, 2026. It is a diagnostic sequence, not a promise that one step fixes every PC. Record your CPU, GPU, driver, resolution, game version, exact error and the result of each test. Send those details with DxDiag and MSinfo to Borderlands Support if the problem remains.