The highest-signal interpretation of recent Steam player feedback.
Space Engineers 2 is viewed as a highly promising but unfinished successor, with strong enthusiasm for shipbuilding, unified-grid construction, destruction, visuals, physics, and improved performance versus Space Engineers 1. The main barriers are missing multiplayer, alpha-level bugs, inconsistent performance and crashes—especially on some AMD hardware—plus contracts and survival progression that can block play. Players broadly recommend it to builders and existing fans who accept Early Access, while advising newcomers and players seeking a complete multiplayer survival game to wait.
Space Engineers 2 occupies a differentiated builder-engineering sandbox niche with strong appeal to creative players, simulation enthusiasts, and SE1 veterans. Its improved construction system and presentation create a credible upgrade path, but it currently competes more as an Early Access creative construction platform than as a complete multiplayer survival or space-exploration game. The best near-term audience is tolerant builders and existing franchise fans; newcomers seeking immediate structure, stable progression, or co-op should be targeted only after onboarding, stability, and multiplayer improve.
Recurring praise and friction patterns extracted from the review set.
Explore the market
99 reviews analyzed
Opportunity score 83
Read report99 reviews analyzed
Opportunity score 87
Read report100 reviews analyzed
Opportunity score 79
Read reportThe unified 25 cm grid, mixed grid sizes, improved placement precision, detailing blocks, and shipbuilding UI are repeatedly praised for enabling creative builds with less complexity than SE1.
Designing, testing, repairing, tuning, and flying ships is highly satisfying for the target audience. Players enjoy the depth of propulsion, power, gyros, dampeners, hinges, pistons, wheels, and other engineering systems.
Reviews frequently cite better graphics, more convincing physics, satisfying destruction, engine sounds, and a stronger sense of weight and immersion than the original.
Many positive reviewers believe the game could surpass SE1 and trust Keen to improve it, particularly when discussing the roadmap, updates, and responsiveness to feedback.
Players value community creations and the freedom to build unusual ships, vehicles, bases, and contraptions, even when survival content is limited.
Several players report smoother gameplay, fewer crashes, and major gains after performance and stability updates, including on mid-range or older systems and Linux through Proton.
The absence of multiplayer or co-op is the most consistent major complaint. Players also describe the current universe as empty, with NPCs, richer activity, and a more living space experience still missing.
Players report crashes on launch, save-loading failures, hard locks, broken solar panels, stuck interfaces, physics issues, and updates that temporarily make the game unplayable. Some AMD GPU users report disproportionately severe crashes and compatibility problems.
Performance is inconsistent across hardware. Complaints include frame drops, stuttering, low or effectively capped visual responsiveness, input lag, and poor performance on otherwise capable AMD systems. Other players report substantial improvements, indicating uneven rather than universally poor performance.
Bugged or non-completing contracts can prevent sector progression and blueprint unlocks. Players also object to unclear requirements, excessive resource demands, and having to use debug workarounds.
Veterans dislike changed building rotation and flight controls, highly sensitive mouse steering, powerful gyros, missing roll customization, and placement obstruction or collision issues. Some feel the redesign removes useful SE1 depth.
New players often feel thrown into the game without enough explanation, while others find the updated introduction helpful. Requests for a detailed manual and clearer explanations of advanced construction are recurring.
Criticism focuses on limited block availability, grindy early progression, small ore deposits, low inventory capacity, inefficient vehicle construction, and a resource system that can make refining and base logistics feel unrewarding.
The HUD and menus are frequently described as oversized, cluttered, awkward, or difficult to navigate. Players request UI scaling, fewer persistent control prompts, hideable GPS markers, better horizon indicators, and persistent camera settings.
Some players see the current experience as a polished building sandbox but lacking meaningful objectives, NPCs, water, pressurization, aerodynamics, broader block variety, and reasons to explore beyond self-directed projects.
Product requests and practical actions that can improve market fit.
The most repeated request; players want to build, survive, and explore with friends, with several references to planned four-player co-op.
Broken completion states and unclear or excessive requirements can halt progression, making this a high-priority usability and retention feature.
A cluster of negative reviews attributes crashes and launch failures to AMD GPUs, while other reports cite hard locks and save-loading problems.
Players want deeper resource processing, better progression balance, larger or more meaningful ore deposits, improved inventory capacity, and less tedious early construction.
NPCs, pirates, scavenging, colonization depth, water, pressurization, and more exploration incentives are requested to make the universe feel alive.
Players want SE1-style control options, mouse sensitivity curves, mouse-roll assignment, gyro sliders, thrust overrides, improved wheel control, and better vehicle handling.
Players request fewer false obstruction and collision failures, more forgiving edge placement, area welding, and faster survival construction.
UI scaling, hideable prompts and GPS markers, usable horizon indicators, camera-distance persistence, and zoom would improve readability and comfort.
Single-player users want saves to move seamlessly between desktop and laptop without repeatedly publishing saves to the Workshop.
At least one player specifically requests a colorblind filter, alongside broader demand for clearer interfaces and customization.
Track crashes by GPU, driver, world size, and grid complexity; prioritize AMD launch and large-grid failures, hard locks, save-loading regressions, and update rollback safeguards. Communicate known issues and fixes prominently in the store page and patch notes.
Preserve the depth valued by veterans while adding optional SE1 control presets, configurable flight handling, better placement feedback, and forgiving construction rules. Prototype area welding and clearer obstruction diagnostics.
Add automated end-to-end tests for every contract type, display requirements at acceptance, provide recovery or abandonment options, and prevent a single failed contract from blocking sector progression.
Expand the tutorial into short, searchable modules covering grid concepts, hinges, pistons, power, flight, survival production, and recovery from vehicle loss. Add an in-game manual and contextual explanations without removing the sandbox freedom.
Player language translated into credible positioning angles.
Move this report into your research workflow or share it with your team.
Copy the summary, export the full report as Markdown, or share this public intelligence page.
Deliver co-op with reliable save ownership, desync protection, and clear host/join flows. Coordinate the launch with a strong returning-player campaign aimed at SE1 groups and Workshop communities.
Set expectations explicitly around missing content, hardware requirements, known AMD risks, and roadmap uncertainty. Offer an accessible first-session path so the two-hour refund window demonstrates the core loop instead of exposing only confusion and setup friction.
Add repeatable contracts, NPC encounters, salvage, pirate threats, and exploration rewards that give builders reasons to leave their bases before water and other major systems arrive.