Big Ambitions Crashes: Startup and Shader Fixes

Identify when the crash happens

Write down whether the game closes before the menu, waits at Compiling Shaders, crashes when loading one save, or fails during an action inside the city. Include any error text and the game build. These are different symptoms, so a fix for one should not be presented as a diagnosis for all of them.

Start with a computer restart, the current game update, and a comparison with Steam's published hardware requirements. On Windows, check operating-system updates and graphics drivers from the hardware maker. On macOS, use the supported system update route. Retest after each change.

Verify the installed game files in Steam

Steam can check the installation and repair missing or damaged game files. Let the process finish before launching again. Valve notes that some local configuration files may not verify, so that message alone does not prove the whole installation is broken.

• Open your Steam Library and right-click Big Ambitions.
• Choose Properties, then Installed Files.
• Select Verify integrity of game files and wait for completion.
• Launch once more and record whether the same symptom returns.

If it stalls while compiling shaders

In a December 20, 2024 reply, the developer advised allowing several minutes without clicking through the shader screen. A slower machine may exceed the time shown on that screen. If the game actually exits, treat that as a crash; repeated long waits are a reason to collect logs.

For startup failures or a flickering or solid-color screen, the developer's pinned help post, last edited March 21, 2025, offers this temporary launch setting: -screen-quality Low -screen-fullscreen 0 -screen-width 1024 -screen-height 768

To try it, open Steam Properties, select General, and use Launch Options. Keep a copy of any options already there. This lowers quality and uses a small window; it is a workaround, not a guaranteed 1.0 repair. Remove the added text to undo the test, and check your graphics settings afterward.

Separate a mod problem from a save problem

If you use mods, record which ones are active and use their supported controls to disable them temporarily. Try a separate new game, without overwriting your existing saves. A modded save may rely on content that is absent when its mods are disabled.

If a new unmodded game works but one existing save does not, that narrows the report to a save or mod dependency; it does not establish corruption. Keep the original file for support. Change one factor at a time so you can explain which test affected the result.

Crash FAQ and what to send support

Where are Windows logs? The developer's December 2024 instructions point to %USERPROFILE%\AppData\LocalLow\Hovgaard Games\Big Ambitions. Copy Player.log and Player-prev.log if present after the failed attempt; the same reply gives support@hovgaard.com as the support address.

What else should I include? Add your game build, operating system, processor, graphics card, memory, active mods, error screenshot, and the action that triggers the crash. Mention whether a separate new game loads.

Can I report it in-game? Use F2 if the game remains accessible. The developer's pinned reporting instructions say that players wanting a reply should include a link to their Steam discussion in the report.

Should I delete saves or turn off security software? Neither is part of this checklist. Keep your original saves and seek a specific diagnosis if the reversible checks do not help.