Satisfactory update 0.5.1.12 is now rolling out on PC (Steam). According to the official Satisfactory patch notes, the latest update 0.5.1.12 added quality of life improvements and gameplay optimizations.
Since the last patch, players are facing a number of problems with the game. Today’s Satisfactory patch 0.5.1.12 will fix a few of these issues.
Check out more details below.
Satisfactory Patch 0.5.1.12 Notes
NEW
- Epic Online Services (EOS) account link status resetting is now possible by going to Options > Online > Reset Account Linking
BUG FIXES
- Fixed a crash that could happen if there’s a deadlock near a non-automated vehicle
- Decreased the collision-avoidance distance for automated vehicles
- Fixed a crash for client related to vehicle paths
- Fixed an issue with vehicle path recording inside factories sometimes recording docking to stations on floors above the vehicle
- Fixed issues with the Factory Card having difficulties finishing path recording
- Fixed a crash related to the vehicle representation on the map
LOCALISATION
- Fixed Esperanto not working properly
- Updated all languages with the latest translations
- Updated language completion rates
- Updated community translators in the credits
KNOWN ISSUES
- A reminder for people who have been having issues with unexpected crashes on startup or weird behaviour with the game, in that case please try to verify your game files.
You can do this on Steam by Right Clicking the game in your Library > Properties > Local Files > Verify integrity of game files…
And on Epic by clicking on the three dots (“…”) next to the title or at the right side, depending on your selected library view > Verify
This may or may not redownload a large amount of files which might take a while depending on your internet connection or hard drive speeds so be wary of that.
If you are using mods, they might need to be updated or uninstalled after updating so please keep this in mind too.
- If you are experiencing issues launching the game or loading a save and you have already verified your files, you might have some incompatibility with DX12 as the default renderer, you can try the following launch options to try to force DX11, DX12 or Vulkan to run respectively.
- d3d11
- DX11
- d3d12
- DX12
- vulkan
- Dedicated Server Crash reports, Currently Crashes that happen on a Dedicated Server are automatically sent to us, this is enabled by default, we plan on including a toggle for this in GUI but for the moment, if you want to disable automatically sending crash logs you can do this:
- Go to the Server Install folder
- Open “Engine.ini”
- Add the following:
- [CrashReportClient]
- bImplicitSend=False
- Save changes and restart the Server
- Packet routing is incompatible with multihome, so we’re automatically disabling the former when the latter is enabled