Wild West Pioneers crashing? What is fixed and what to try
Crashes are the problem players report most, and three hotfixes have targeted several of them. If the game still crashes after the first hotfix, the publisher’s first advice is to switch VSync off in the graphics settings. After that, send a report from the pause menu, and if the crashes keep coming, send your crash logs or a dxdiag log through the publisher’s support site.
Try these, in this order
Get the latest hotfix Restart Steam so it downloads the current version. The version number sits in the top right corner of the screen, so you can check which one you are on: the third hotfix is version 0.1.0 19530, and anything higher is newer.
Turn VSync offOptions, then Graphics. VSync is the fifth line, between Resolution and FPS Limit.The publisher’s pinned advice: “If the hotfix does not help you, please try disabling V-sync in the video settings.” An official forum account gave the same advice to a player whose game crashed while still loading.
Let Steam verify the files Right-click the game in your Steam library, then Properties, Installed Files, Verify integrity. The publisher suggested it to a player whose save button stopped working after the hotfix: “Please let Steam verify the installation. This checks for missing and damaged gamefiles and replaces them if needed.” It is also the first thing to try when the game will not start and shows “Failed to load il2.cpp”. If verifying does not clear it, uninstall and reinstall the game: one player who hit that error got past it by reinstalling.
Report it from inside the game The welcome letter on the title screen asked for exactly this: “Please use the feedback form in the in-game pause menu to submit issues and suggestions”. An official forum account added that the team is chasing the random crashes: “We're aware of the random crashes and the team is working on a fix.” The publisher also points to its support site and Discord for crashes that keep coming back.
When the publisher asks for crash logs, this is the folder it points to:
Paste it into the File Explorer address bar as it is; Windows fills in your user name for %USERNAME%. Send the newest crash from that folder along with your report.
What each hotfix changed
Version
Which one
What it fixed
0.1.0 19409
Launch version
Nothing yet; this is the version Early Access opened with.
0.1.0 19478
First hotfix
Crashes tied to residents moving around, graphics crashes in long sessions, memory that kept growing after resolution changes or switching windows, a clock that could stop for good, and controls that stopped answering after a return to the main menu.
0.1.0 19496
Second hotfix
A wider Barber Shop range, workshops that looked stopped, Food Store upgrades dropping connections, scouts stuck on their way home, missing Moonshine Boxes in the priest questline, and a freeze when the bandit cutscene started while you were away from the settlement.
0.1.0 19530
Third hotfix
A crash from fireplace and light effects as day turns to night, a Saloon problem that stopped some late-game saves loading, residents spinning in place or getting stuck, a see-through interface after changing window mode or resolution, and residents riding invisible horses. The Load Game menu now shows longer save names, newest first.
Not given
Fourth hotfix
Caravans cut from 20 to 5 canned food, the Cattle for the natives quest counting cattle you already own, the new-settler timer climbing above 50 hours, and Jamie not responding after a save is loaded, which blocked his questline.
The first hotfix led with “Fixed several crashes related to residents movement.” and also lists “Fixed memory usage increasing over time, especially after changing resolution, opening certain UI elements, or switching between applications.” If you alt-tab a lot, that second line is the one that applies to you. If the crash always came at dusk or dawn, the third hotfix is the one for you: “Fixed fireplace and light effects that could cause crashes during the transition between day and night.” All the patch notes are in the update log.
When the game looks frozen but is not crashing
What you see
Status
In the meantime
A workshop stops producing
Fixed in the second hotfix: “Workshops now wait until all required resources are in storage before collecting them and starting production.” It also stopped production halting when you change a recipe at night.
Change recipes during the day, and check the warehouse actually holds a full cycle’s worth of input.
Buildings drop off the Food Store
Fixed in the second hotfix: “Fixed an issue where upgrading the Food Store could disconnect some of the buildings linked to it.”
If links still go missing, open the Food Store after upgrading it and check its connections.
Scouts never come back
One version was fixed: “Fixed scouts getting stuck after being sent back to the settlement from the popup.”
Check the clock first. One player’s scouts were fine: “The game had been paused somehow. Had to press play in the top left.”
Residents spin in place or stand stuck
Improved in the third hotfix: “Added several fixes to reduce residents spinning in place or becoming stuck.” It reduces the problem rather than promising it is gone.
Check the clock is running and the resident has somewhere to go: a free job, a home, a path that is not blocked.
A save never finishes loading: black screen, spinning horseshoes
One cause was fixed in the third hotfix: “Fixed an issue involving the Saloon that could prevent some late-game save files from loading.”
Update, then let Steam verify the files. The publisher’s advice: “Since it started with the last patch, please let Steam verify the integrity of the gamefiles.” Keep a second manual save under another name so one bad file cannot cost you the town.
Settlers stop arriving when the migration counter hits zero
A known bug the team is looking into, an official forum account says. There is also a hard limit: “settlements are capped at 250 residents right now”, so a town close to 250 gets nobody new. A related timer fault is fixed: the fourth hotfix stops the new-settler timer sometimes climbing above 50 hours.
Save and restart: “Restarting the game usually gets settlers arriving again for a while.” Other reasons nobody turns up, such as satisfaction not being above 60, are on the population page.
A building loses its warehouse link
Not listed in any hotfix so far.
Players’ fix: “go to the nearest Warehouse, remove a Worker, add it back and it works (for me)”.
Food or moonshine disappears, and shops show another building’s name
Other players report it too. The publisher: “We have several reports on this, so you aren't alone.”
Send it in with the report form in the pause menu, and keep a manual save from before it started.
A caravan vanishes after you change its cargo
A bug, an official forum account says: “that's not supposed to happen, it sounds like a bug.”
Leave a running caravan’s cargo alone. One player says a caravan set to run once or three times disappears when its trips are done; set it to nonstop to keep it.
A potato farm stops mid-harvest
“The potato farm stopping mid-harvest is a known issue the team is working on right now.”
You cannot move it or tear it down once its fields are in, so it keeps its spot until a patch. Moving and demolishing covers what can and cannot be moved.
The interface turns see-through
Fixed in the third hotfix: “Fixed the interface becoming transparent after changing the window mode or resolution.”
Update to the third hotfix, then change the window mode or resolution again if the interface is still see-through.
Wagons spin on the spot
Not listed in any hotfix so far.
A player’s workaround: “It sometimes helps to switch speed to make them stop spinning.”
The in-game clock stops for good
Fixed in the first hotfix: “Fixed an issue that could cause the in-game clock to stop permanently.”
Make sure you are on version 0.1.0 19478 or later; the version number is in the corner of the screen.
Keys and clicks stop working after a new game
Fixed in the first hotfix: “Fixed controls no longer responding after returning to the main menu and starting a new session.”
If it still happens, restarting the game is simpler than starting a second session from the menu.
For production that never reaches the warehouse, an official forum account asked players to use the in-game report form: “you can submit a bug report straight from the pause menu in the game.” Quest objects that fail to appear are covered on the Moonshine Scandal page, where players have run into them.
The letter on the title screen, signed by the EmpireCraft Team, asking players to use the feedback form in the pause menu.
Keep a crash from costing you a day
The game autosaves when a new in-game day begins, so a crash can cost you most of a day (this may have changed in later updates). Saving by hand is in the pause menu, as one player put it: “Escape - Save Game”. Do it before a long building spree. Where the save and log files live, and how autosave works, is on cheats, trainers and saves.
If your PC is near the bottom of the requirements, the system requirements page covers what the store lists and how the game runs on a Steam Deck.