Unity (Engine)

Unity Technologies’ (unity-technologies) cross-platform game engine and real-time-3D (“RT3D”) software, scripted in C#. A proprietary, subscription/seat-based product (free, Plus/Pro/Enterprise tiers) — the subscription end of this wiki’s landscape, contrast open o3de and godot-engine and royalty-based unreal-engine. Still the most-used engine overall, but losing some indie mindshare to open alternatives.

Unity AI (the ingested source)

The source page is Unity’s AI offering — positioning AI-assisted tooling as a core feature of the engine: AI tools for game development and RT3D content/code generation inside the editor. This is the clearest marker in the current cluster that AI tooling is the new competitive front among engines.

Stub: unity.com/features/ai returned HTTP 403 to the fetcher (2026-05-31). Recorded from the page title + known context per the hub fetch-fail rule; specific product names/pricing on the page were not captured. Refresh in place when a fetchable source arrives.

Unity 7 — the next generation (2026-07)

Announced at Unite Seoul (unity-7-roadmap, 2026-07-21): early beta Dec 2026, final release early 2027. The defining claim is continuity — Unity 7 keeps Unity 6’s underlying architecture, so the upgrade is pitched as zero rebuilding, projects and code carrying forward untouched. New in the release: an open collaborative ecosystem (a CLI + public API for validating assets, pushing builds, and browser-based Scene Preview without full Editor access — the Unity CLI shipping this is already available), faster workflows/graphics, and opt-in generative AI (AI-assisted graphics optimization, Unity Vector ads AI) — deliberately framed so AI-averse studios aren’t forced in. No pricing change announced. The “won’t break your build” messaging reads against the 2023 Runtime Fee trust damage.

visionOS — the renderer Unity doesn’t own

PolySpatial (2026-07-29) is Unity’s path onto Apple’s headset, and it is the one platform where Unity simulates but does not render: RealityKit draws the frame, because visionOS composites apps into a shared space. Current 2.0.x adds a Metal escape hatch to take the pipeline back for immersive apps, and gates the whole package behind Pro / Enterprise / Industry — Unity Personal cannot ship to visionOS.

Versus Godot (from the comparison source)

From a like-for-like build of the same game in both engines (unity-vs-godot-comparison):

• Comparable raw performance — both cleared a 60fps target.
• Heavier dev environment than Godot: Unity Hub ~21 GB vs Godot ~164 MB; C# script compile ~15.4 s vs Godot’s GDScript ~0.31 s; slower build/startup.
• Maturity: Unity is more mature/complete; godot-engine trades some of that for openness and a lighter, faster iteration loop.
• Notable defection: mega-crit moved from Unity to Godot for Slay the Spire 2.

Related

unity-technologies · unity-7-roadmap · unreal-engine · o3de · godot-engine · unity-vs-godot-comparison · mega-crit · synthesis