Update first, then isolate display and compatibility settings
Start by updating Lootbound through Steam and launching version 1.1.7 with the August 21 fixes. That update addressed different screen resolutions, so old launch advice should not be the first step. Restart Steam once, verify the installed files, and test with overlays and custom launch options temporarily disabled.
If the first loading screen still does not advance, use the platform path below. On Linux and Steam Deck, test a supported recent Proton option or a 60 Hz gamescope launch. On Windows, gather the log before changing save files. Do not delete progression as an opening fix; the reported startup failures are more closely tied to display and compatibility initialization.
Fix Linux loading with refresh rate or Proton
A native Linux startup failure can occur when the desktop is not running at 60 Hz. Test the game at 60 Hz first. With gamescope installed, a working pattern is to set the output width and height for the display, add a 60 Hz refresh limit, use fullscreen, and pass the Steam command afterward. Replace the sample resolution with the monitor's actual resolution.
If the native build remains stuck, open Steam Properties, choose Compatibility, and test Proton Experimental or another recent compatible Proton release. Remove older forced compatibility selections that crash or stall. Change one variable at a time, launch, and note the result so the working combination remains reproducible.
| Step | Action | What it isolates |
|---|---|---|
| 1 | Set the display to 60 Hz | Native refresh-rate initialization |
| 2 | Use gamescope at the monitor resolution and 60 Hz | Controlled display mode |
| 3 | Try Proton Experimental | Native-build-specific failure |
| 4 | Remove older forced Proton versions | Outdated compatibility layer |
Use a clean Windows startup test
On Windows, close the game and Steam completely, reopen Steam, and verify Lootbound's installed files. Remove temporary launch options and disable third-party overlays for one test. If an ultrawide or unusual refresh configuration is active, switch Windows to a standard 16:9 resolution and 60 Hz long enough to determine whether display initialization is the blocker.
Do not reinstall repeatedly before collecting useful evidence. A reinstall may leave the same configuration and save folders in place, producing the same result. If the clean display test works, launch the game, choose a supported in-game resolution, exit normally, and restore the desktop setting. If it does not work, capture the current log next.
- Update the game and restart Steam.
- Verify installed files.
- Remove custom launch options and disable overlays for one test.
- Temporarily test a standard resolution at 60 Hz.
- Collect Player.log immediately after the next failed launch.
Collect the log without exposing personal files
On Windows, open the LocalLow LootBound folder through the current user's AppData location and locate Player.log. Capture it immediately after forcing the stuck process to close so the relevant startup sequence remains near the end. On Linux, inspect the corresponding Unity player log for resolution or settings initialization errors.
Keep the original log with the date, operating system, GPU, monitor resolution, refresh rate, and compatibility option used. Remove personal account paths before sharing excerpts. A precise report makes it possible to distinguish a resolution exception from a damaged install or unrelated driver problem.
- Record operating system and version.
- Record GPU, resolution, and refresh rate.
- Record native Linux or exact Proton choice.
- Attach the newest Player.log after removing personal path details.
Protect saves and stop after the first working launch
Back up the full-release save before resetting configuration folders or testing a different machine. Do not copy demo files into the release profile and do not disable Steam Cloud permanently. Once one combination reaches the menu, keep that configuration, enter the Hub, exit normally, and let Steam synchronize.
Restore optional overlays, higher refresh rates, and custom launch parameters one at a time. If the problem returns, the last change identifies the trigger. This controlled order prevents a working fix from being lost inside several simultaneous changes and keeps progress separate from display troubleshooting.