Choose an ultrawide fix by symptom, not monitor label: confirm aspect ratio and display mode, compare DLSS, and use the documented Screen.ini reset only for the matching configuration case.
Record the display case first
The supplied developer and player evidence supports 21:9, while reports above 21:9 are mixed. At 32:9, players have described both usable output and blur or UI stretching. A separate 5120×2160 case improved after DLSS was disabled.
Before changing files, record desktop resolution, game resolution, aspect ratio, full-screen or borderless mode, DLSS state, whether the issue existed on first launch, and whether switching to 16:9 changes it. This separates resolution selection from scaling, rendering, and interface layout.
Classify blur, stretch, crop, and dead controls
These symptoms need different evidence:
- blur: compare native resolution with DLSS off in the same scene;
- stretch: compare the interface at the current ratio and at 16:9;
- crop: record which edge or element is missing rather than calling it general blur; and
- unclickable control: test display mode and whether the pointer aligns after a configuration reset.
Do not claim that one setting fixes all four. A 21:9 success does not prove full 32:9 or 5K interface adaptation.
Compare DLSS for scaling problems
For blur or incorrect scaling, disable DLSS and repeat the same resolution and display mode. One 5120×2160 community case reports that this resolved the scaling problem, but that is a specific sample rather than a universal ultrawide cure.
If disabling DLSS changes general performance instead of the geometry or clarity symptom, move to the performance guide and retain the official verify-files, DLSS, and Frame Generation order.
Reset Screen.ini only for the matching case
Historical official troubleshooting for stretched or unclickable UI directed players to exit the game, open %appdata%/../locallow/Multiverse/Pax Autocratica, remove Screen.ini, and restart so the display configuration could be rebuilt. Back up Screen.ini first so the previous settings remain recoverable.
This resets display configuration. It is not a guarantee that every 32:9 or 5K interface is fully adapted, and it must not be expanded into deleting the entire LocalLow directory. The Save folder contains campaign data and is a different target.
Try display-mode checks without overclaiming
Developer or moderator replies in the supplied discussions also mention Alt+Enter, a temporary desktop-resolution change, and checking Screen.ini for particular high-resolution cases. Apply one change at a time, return to the original value if it does not match the symptom, and record the result.
Keep Windows and Linux branches distinct
The Screen.ini path and official replies above concern the Windows LocalLow workflow. A Linux, Bazzite, AMD, Proton, or Mesa workaround from a specific environment is not part of this official Windows branch and cannot be assumed to transfer.
Report what remains after each branch
If the symptom survives, submit the build, GPU and driver, desktop and game resolution, aspect ratio, display mode, DLSS and Frame Generation state, screenshots, and whether 16:9 restores normal behavior. That report is more actionable than “ultrawide is broken” because it identifies the failing layer.
Before touching save data, use the save-location guide to keep Screen.ini and the Save directory separate.