Locomotive Delete Crash in 1.2.2.0

Satisfactory 1.2.2.0 Build 488068: The Locomotive Delete Crash

Patch v1.2.2.0 (EXPERIMENTAL) Build 488068, released in late April 2026, introduced a new client-side crash that triggers when you delete a train locomotive from your factory. The patch otherwise fixed dozens of conveyor lift, splitter, and merger issues, so most groups want to stay on it rather than roll back. This guide covers what triggers the crash, the safe workaround, and how to keep your trains operating until Coffee Stain ships a fix.

What triggers the crash

The crash fires when:

1. You walk up to an existing train locomotive (either powered or unpowered).
2. You aim at it with the dismantle tool.
3. You confirm the dismantle.

The client process exits hard, usually with an EXCEPTION_ACCESS_VIOLATION in the crash log. The dedicated server itself does NOT crash. The locomotive may or may not actually be deleted depending on timing; on most reports, the locomotive stays in the world and the client just dies.

The workaround

Until a fix ships, do not dismantle locomotives directly. The two safe alternatives:

Option 1: Replace, don't delete

Need to move a locomotive? Build the replacement first at the new position, set up the routing, then remove the old locomotive by dismantling the track segment it's parked on. Removing the supporting track will dispatch the locomotive back to your inventory through the standard "no track found" handler, which uses a different code path than direct dismantle and doesn't trigger the crash.

Option 2: Use admin SCIM if you absolutely need it gone

If a locomotive is glitched and you need to remove it from the save entirely, do it server-side via SCIM (Satisfactory Calculator Interactive Map):

1. Stop your dedicated server.
2. Download the .sav file via FTP or the file manager.
3. Open the save in SCIM (saveeditor.satisfactory-calculator.com).
4. Locate the locomotive entity by its coordinates.
5. Delete the entity from the save tree.
6. Upload the modified save back to the server.
7. Restart the server.

See our SCIM guide for the detailed walkthrough.

Identifying if your save is at risk

Run this checklist before any train-related demolition session:

• What patch are you on? Check the server log: grep -i "build version" FactoryGame.log. If you see Build 488068 or anything labeled 1.2.2.0, you are exposed. Anything earlier (1.2.1.x or below) is safe. Anything newer should have the fix, but check the patch notes first.
• How many locomotives do you have? Run a SCIM scan or inventory grep on the save: grep -c "Build_Locomotive_C" save.dump. Higher counts = higher chance of accidental dismantle.
• Is there auto-dismantle in your habit? Some players bind dismantle to a hotkey near movement keys. If yes, you're at higher accidental-trigger risk; rebind for the duration of the patch.

Other notable issues in Build 488068

The same patch acknowledged a few smaller server-side issues worth knowing about:

• Fixed: Conveyor Lift Splitters/Mergers now use belt-style snapping (previously caused alignment crashes).
• Fixed: Logic for guideline snapping on lift attachments. This was a separate crash class than the locomotive one.
• New: Paintable train tracks. Cosmetic; no server-side impact.
• Open: Some clients report rare crashes on Conveyor Belt Manufacturer interactions, still being investigated.

Reporting it (if you hit a different variant)

Coffee Stain runs an authoritative QA site at questions.satisfactorygame.com. If your crash signature looks similar but isn't the locomotive dismantle path, file a bug report with:

• Your build number (from FactoryGame.log)
• The 30 seconds before the crash described as steps
• Your client crash log (typically FactoryGame/Saved/Logs/FactoryGame.log on the client machine, not the server)
• Whether you can reproduce on a fresh save

Patches typically land within 1-2 weeks of a confirmed bug report with a reproducer.

Should you roll back to 1.2.1?

Most groups should stay on 1.2.2.0 unless trains are central to your current factory and you have multiple locomotives you actively dismantle. The conveyor lift, splitter, and merger fixes in 1.2.2.0 are significant quality-of-life improvements. The locomotive crash is annoying but has a clear workaround.

If you decide to roll back, use Steam → Properties → Betas → select the earlier branch. Servers must roll back to the same version as clients or you'll get a "version mismatch" join error. See our server update guide for the bidirectional update procedure.

Related troubleshooting

• Patch 1.2.2 Experimental update notes
• EXCEPTION_ACCESS_VIOLATION crash diagnosis
• SCIM save editor guide
• Restore from backup

Supercraft Satisfactory hosting ships with hourly auto-backups and 14-day retention, so a bad patch interaction never costs you more than an hour of factory time. Plans from $7.99/mo.