Satisfactory 1.2 just received its first follow-up fix patch, and this one is worth installing quickly if your factory uses drones, multiplayer photo mode, controllers, Steam Deck, console keyboard input, or a dedicated server.
Coffee Stain’s official Satisfactory Q&A patch note entry lists the update as Patch Notes: v1.2.3.0 – Build 493833, with version number 1.2: 493833. The matching Steam announcement is titled 1.2 Update Fixes v1.2.3.0. Coffee Stain also noted that this is the first 1.2 patch where the build number and patch contents match across PC, PlayStation 5, Xbox Series S, and Xbox Series X, so the notes below apply broadly instead of being a PC-only hotfix.
For most players, the short version is simple: update the game, restart it cleanly, and make sure everyone joining a multiplayer session or dedicated server is on the same build. For server owners, treat it like a small maintenance window: save, back up, stop the server, update, restart, and verify before inviting players back in.
What Changed In Satisfactory v1.2.3.0 Build 493833?
This patch is mostly stability and quality-of-life repair work after the larger 1.2 release. There are no new headline factory systems here; the important news is that several crash, input, UI, and multiplayer rough edges were addressed.
Drone Memory Leak Fixes
The biggest PC and server-adjacent fix is the drone-related memory leak. Coffee Stain says the patch fixed a memory leak caused by multiple drone issues. If your save has a large drone network, long play sessions, or a dedicated server that seemed to become unstable over time after 1.2, this is the first fix I would want installed.
Practical advice: after updating, restart the whole game or server process instead of only relying on a live reload. Memory leak fixes help after the fixed build is running cleanly; they do not magically clean up an already-bloated old process.
PS5 Crash Fix
The patch includes a PlayStation 5 crash fix related to UFGBluperintFunctionLibrary, as written in the official notes. If someone in your household or group is playing on PS5 and crashing after the 1.2 release, make sure they are on Build 493833 before chasing more complicated troubleshooting.
Lizard Doggo Inventory Lock Fix
One of the more annoying gameplay fixes is for an issue where the inventory could become unusable after interacting with a Lizard Doggo. That is exactly the kind of bug that can make players think their save, UI, or input profile is broken. If this happened to you, update first, fully restart, and try the interaction again before changing your settings.
Controller, Steam Deck, And Join Game Fixes
Build 493833 includes several controller and handheld improvements:
- Tooltips in the MAM can now be opened when using a controller.
- Confirm now works on the Join Game menu when using a controller.
- Several incorrect default settings on Steam Deck were fixed.
- The To-Do List text size on Steam Deck was corrected.
If you play from a couch setup, Steam Deck, or controller-first PC, check your settings after the update. If the game still feels off, reset only the affected input/display settings instead of wiping your whole config.
Console Keyboard Fixes
Coffee Stain also fixed console keyboard behavior in text fields. Virtual keyboards should open and close more correctly when a physical keyboard is plugged in on consoles, and multi-line text fields should now block gameplay actions while typing with a keyboard. That matters for players naming things, editing notes, or using text fields without accidentally triggering in-game actions.
Photo Mode And Multiplayer Camera Fixes
Photo Mode got several repairs, especially around multiplayer and decoupled camera behavior:
- Camera settings now reset properly after leaving Photo Mode with decoupled camera in multiplayer.
- Player visibility issues when switching camera modes in Photo Mode were fixed.
- Pioneers should no longer always go into the offline pose when using decoupled camera mode in multiplayer.
If you take build screenshots with friends, this patch should make Photo Mode less weird after switching views or leaving the camera.
Other Gameplay And UI Fixes
The official patch notes also list these fixes:
- Saving a new color preset should no longer get stuck behind a name-already-in-use popup that cannot be dismissed.
- Milestone progression icons now refresh correctly when toggling the small game progression slot size in the HUD.
- The recipe cost multiplier at x1.75 no longer sets all liquid recipe costs to 0.
That liquid recipe cost multiplier fix is especially important for players using adjusted game rules. If you used x1.75 and saw liquids behaving strangely, re-check those recipes after updating.
Localization Updates
The localization section is straightforward: all languages were updated with the latest translations, language completion rates were updated, and the credits were updated.
What Players Should Do Before Launching The Patch
Satisfactory saves are valuable because they represent hundreds of small design decisions. Before updating a large 1.2 save, take five minutes and do the boring safe thing:
- Back up your save. Copy your current save folder or export the save before opening it in the new build.
- Update the game client. Let Steam, Epic, PlayStation, or Xbox finish the update completely.
- Restart the game. Do a clean launch after the patch, especially if you had the game suspended or idle.
- Check the build number. The target patch is v1.2.3.0 Build 493833.
- Make sure multiplayer friends match. Mixed client builds are a common source of join/session weirdness.
Dedicated Server Admins: Update The Server Too
If you run a Satisfactory dedicated server, update the server before players pile back in. The client and server should be on the same current build, and this patch includes a drone memory leak fix that could matter a lot for long-running servers.
We already have a step-by-step guide for the bigger 1.1 to 1.2 server upgrade here: How To Update A Satisfactory Dedicated Server From 1.1 To 1.2. You can use that same basic maintenance pattern for this smaller patch:
- Tell players the server is going down for a short update window.
- Save the game from the server or admin tools.
- Back up the save/config folder before changing anything.
- Stop the dedicated server process cleanly.
- Run your normal SteamCMD or host-panel update.
- Start the server again and confirm it reports the new build.
- Have one player join and test drones, inventory, and basic interaction before opening it back up to everyone.
If your server was struggling after the 1.2 release, do not skip the full process restart. A patched binary only helps once the old server process is gone.
Still Having Problems? Report Them In The Right Place
Coffee Stain specifically asked players to report issues on the official Satisfactory Q&A site, and said they read posts there every day. If Build 493833 does not fix your issue, report it at questions.satisfactorygame.com.
Good bug reports save everyone time. Include:
- Your platform: Steam, Epic, PS5, Xbox Series S/X, or dedicated server.
- Your exact build number: v1.2.3.0 Build 493833 if fully updated.
- Whether the issue happens in single-player, multiplayer, or dedicated server play.
- What you were doing right before the problem happened.
- Whether mods are installed, if you are on PC.
- Crash logs, screenshots, or save details if they are relevant.
For local players and small server groups, my recommended order is: update everything, restart everything, verify the build, test without mods if you use them, then report the bug if it still happens.