State of Dev - Summer '26

Update 1.2 Context & New Features (Satisfactory)

The video thanks players for trying Summer 26 / update 1.2 and highlights several major additions:

• New weather events (including rain)
• A new “fluid truck”
• An updated vehicle pathing system (vehicle system reception discussed later)

Community Feedback Themes

What players liked

• New vehicle paths

What players wanted

• The ability to keep using the old vehicle system

Bugs and “cool new features”

The discussion acknowledges that update 1.2 included both “cool new features” and some accidental ones (bugs).

Performance Problems Reported in 1.2

Common criticisms after update 1.2 include:

• Decreased performance when entering new areas
• Micro stutters / frame drops
• Performance issues with large blueprints
• Other buggy behaviors introduced around or after 1.2

Studio response

The studio describes a workflow for handling reports:

• Collecting reports through a QA site (link referenced)
• Logging and tracking issues in Jira

Core Technical Cause: Unreal Engine Upgrade

A key technical point is that update 1.2 involved an engine upgrade:

• Unreal Engine upgraded from 5.3 to 5.6

This was not a small change—they effectively skipped multiple engine versions, moving from:

• 5.3 (Sep 2023) to 5.6 (Jun 2025)

Why that matters

UE updates can bring performance improvements, including:

• Better multi-threading support for modern multi-core CPUs

The intent is to allow more systems to run in a shared multi-threaded pipeline, improving FPS/scalability as factories grow.

The tradeoff

If a player’s hardware/CPU doesn’t benefit from multi-threading, they may see worse performance after the upgrade.

Additional engine feature usage (rain)

The team also mentions using more capable UE 5.6 features:

• Lightweight scene capture methods to constrain rain to the viewport
• Historical note: weather existed previously around update 6, but support was limited because techniques weren’t native; UE 5.6 improved feasibility.

Why Bugs Slipped Through

The studio frames large engine changes as creating “ripple effects” across the entire game, requiring extensive review.

• Team size mentioned: ~7 programmers (implying an engine-side vs. game-side split)
• They used an EXP branch and internal testing, but some issues still reached players.

Profiling / Benchmarking Approach

The video describes profiling as an automated performance workflow similar to 3DMark, including:

• Multiple save files
• Scripted camera paths
• Capturing:
  • CPU/GPU performance
  • FPS distribution
  • memory usage

It also notes that the game is not inherently memory-friendly, due to the freedom players have when building.

Multiplayer Issues

Reported multiplayer problems include:

• Disconnects in late-game saves
• FPS drops in new areas
• Performance issues on multiplayer servers

A suspected contributing factor tied to CPU/engine systems:

• Collision streaming complexity in multiplayer
• The system must track all players and determine which areas/objects have active collision

Studio action

Developers are described as actively investigating root causes, with multiplayer stability stated as a priority.

Horizontal Lifts Bug (Exploit Removed)

A bug allowed rotating conveyor lifts in “funky ways.”

Community reaction

Players were upset because it enabled creative/expressive builds (example: a “waterfall of items”), referencing a video by “Doug and Nova.”

Decision: not reverting

The studio chose not to revert the bug.

Technical reason

They explain the exploit:

• Breaks conveyor lift logic
• Causes items to render off-screen
• Creates unnecessary/unexpected rendering costs—especially costly for lower-end machines

They say they’ll remember the desire for future updates, but legacy behavior isn’t coming back (in this context).

Vehicle System: New vs. Legacy

Reception

Overall, reception is positive, including many players who hadn’t used vehicles before.

Disappointment mentioned

• Players can’t drive and set their own routes
• Players can’t rely on physics-based creation of wacky paths

Legacy system stance

The speaker states: “Legacy vehicle system is dead.”

Reason given:

• The legacy structure became harder to support after the UE4 → UE5 upgrade.

The new system is positioned as:

• More scalable and maintainable long-term

Keeping the legacy system would require continued support and would lead to unorganized/non-expandable code, conflicting with studio core values.

Post-1.2 Patches Already Released (Bug Fixes)

First follow-up patch (highlights)

• Memory leak fix related to multiple drone issues
• Conveyor belt ghosting fixes
• UI fixes, including:
  • Virtual keyboards not opening/closing correctly on consoles
  • A save issue for a new color preset due to pop-up dismissal

The video points to full patch notes (linked/shown).

Second patch (additional mentions)

• FS4 upgrade
• Many UI fixes
• Potential fixes for common console crashes

Main Speaker / Sources

• Speaker: Jason (Community Manager, Coffee Stain Studios)

Referenced sources/tools/communities:

• Epic Games (Unreal Engine)
• QA site
• Jira
• questions.satisfactory.com
• Discord
• “Doug and Nova” video about the horizontal lift exploit