Video summary

State of Unreal (Live in 4K - Wednesday) with Gears of War + More

Main summary

Key takeaways

Technology

Technological concepts & product/workflow features mentioned

Unreal Fest overview / roadmap context

  • Unreal Fest includes 100+ sessions and hands-on labs, plus an event app (QR code) and expo demos.
  • Epic stated there is no live stage tech demo this year because the team is focused on a major engine release:
    • Building the foundation of Unreal Engine 6 (details later in the program).
  • Unreal usage at scale was highlighted via several high-profile projects:
    • Claire Obscure Expedition 33 (San Fall Interactive)
      • Claimed breakout hit; later received 500+ awards.
    • Arc Raiders (Embark)
      • 14M+ copies sold (Oct–Feb).
      • Built a massive open world with UE5 + Epic Online Services voice chat.
      • Cited peak 960,000 concurrent users.
    • K-Pop Demon Hunters (Sony Pictures Animation / Imageworks)
      • Pipeline shifted to real-time previs/layout in Unreal.
      • Saved ~25% production time.
      • Enabled fast ecosystem work and a Fortnite collaboration plus UEFN developer tools launched in 2 months.
    • SAS enterprise digital twins
      • Unreal Engine digital twin simulations for manufacturing, safety, and life sciences to reduce operational risk before deployment.

UE5 “next release” focus (Unreal Engine 5.8)

Speakers framed 5.8 as:

  • Faster
  • More stable
  • More “headroom”
  • Fewer hitches
  • Reduced friction between ideas and shipping

Key UE5.8 features called out

  • Performance improvements (from UE 5.7)
    • Up to 25% GPU and 35% CPU performance gains for smoother frame rates.
  • Maturity / production readiness
    • Features previously experimental are now “production ready,” including:
      • Megalights (headline)
        • Thousands of dynamic shadow-casting lights at a fixed cost
        • Converts expensive lighting into a creative tool for better artist lighting without heavy budgeting
      • Live Link Hub
      • Movie Render Graph
      • Chaos Cloth authoring via dataflow
      • Wwise Audio Insights
      • Iris networking
  • Platform scaling improvements
    • Lumen Light (lightweight mode) reduces GPU cost while preserving visual impact
    • Positioned as making Lumen viable on Switch 2
    • Supports further Nanite optimization
  • Shader compile / hitch reduction (two-pronged)
    1. Shader compiler improvements
      • Deduplication and removal of redundant work
      • Fortnite cited a 68% reduction in shader count
      • Faster cooks/loads and less memory usage
    2. PSO (Pipeline State Object) pre-caching improvements
      • PSOs described as GPU draw bundles (shaders + render state)
      • Better pre-caching reduces runtime assembly that causes hitches
      • Also reduces “visible fallback rendering” while compiling
  • Advanced shader delivery (with Microsoft/hardware partners)
    • A DirectX 12 initiative to ship pre-compiled shaders to players
    • Shifts work out of player runtime (rollout ramping)
  • New experimental world-building feature: Mesh Terrain
    • Designed to overcome heightmap landscape limits (e.g., single-direction point movement and fixed grid resolution)
    • Capabilities:
      • Full 3D terrain manipulation (overhangs, tunnels, floating islands)
      • Triangle-level tessellation control
      • Material layer painting + additional attributes
      • Virtual texturing with automatic UV generation
      • Non-destructive modifiers and procedural tooling (layering/reordering/combining)
      • Works with World Partition streaming, uses Nanite when available
      • Supports PCG (Procedural Content Generation) and includes an expanded modeling toolkit
    • Fortnite optimization claims:
      • Smaller memory footprint
      • Faster than landscape
      • Enables “higher quality, lighter cost”

Animation / capture & rendering upgrades

  • Performance capture matured
    • Scaling from desk work to full mocap stages.
  • MetaHuman Animator markerless motion capture
    • New integration described as a Fab plugin
    • Uses regular video input (no suits/markers) to drive body, face, and hands
    • Positioned as a major animation workflow release—interactive and more tightly connected to the creative process
  • Cinematic rendering improvements
    • Offline depth of field upgraded to sample blur across multiple lens points
      • More physically accurate defocus, including translucency/thin geometry
    • Tiled mipmap video format
      • More efficient handling of ultra-high resolution media by avoiding processing unseen pixels

AI-assisted creation / editor automation (UE 5.8 ecosystem)

A major portion focused on reducing “technical overhead” using AI and new Unreal integration.

MCP server + Cloud Code concept (experimental but shipping in 5.8)

  • Epic introduced an MCP (Model Context Protocol) server to bridge Unreal Engine and any model.
  • Demo behavior:
    • The system connects to a chosen model (example used Claude Code, but the concept supports Gemini, custom models, etc.).
  • Workflow philosophy:
    • Keep edits inside Unreal as editable real geometry and procedural graphs
    • Avoid “locked generated images” as the primary output
  • Demo outcomes:
    • Living room furnishing
      • Uses semantic search from an asset library plus manual placement
      • Produces editable geometry and procedural content that can be opened/modified
    • City generation
      • Prompt defines boundaries/districts
      • Highways/roads fill in
      • Buildings and forests generated via semantic search and procedural graphs
      • Collaboration concept: multiple developers can work in separate sessions while updates reconcile
    • Lighting “skill” orchestration
      • Lighting adjusted by describing intent (e.g., “purple dusk” vs “overcast”)
      • If the model misreads conditions (e.g., sky/cloud material wrong), users can correct via follow-up prompts
      • Supports geographic/sun knowledge (example: Bogotá at 9:30am) and image-based look matching (screenshots/Vancouver reference)
    • Interactive scene example (hazard zone)
      • Model reads existing materials/graphs and inserts new logic
      • Edits and connects:
        • Material instance editor
        • Niagara templates extended via parameters controlling multiple emitters
        • UMG HUD (status display/danger meter)
        • Blueprint logic tying proximity triggers to material + Niagara + HUD
      • Claim: would take months by hand, but pipeline produced it in days

Procedural content generation scaffolding

  • Mentions delivering:
    • MCP server
    • PCG primitive plugin
    • “Skills” developed as part of 5.8
  • Unreal provides 80+ PCG building blocks, including an example library and workflow-focused “skills.”
  • Stated limitation:
    • Early days—models can be unpredictable
    • Designed to keep Unreal scene editing possible

Linear content workflow (film-like creation path, early next year)

A second speaker described tools for AI pipeline image/video restyling and scene generation with stronger art-direction control.

  • Connects to image/video models (examples named: Nano Banana Pro, “GPT image,” Grok Imagine, Luma, SeaDance, etc.).
  • Approach: combine text prompts with Unreal scene setup + render passes.
  • Demonstrated process:
    1. Build a 3D layout in Unreal (Quixel environment customized)
    2. Render a style frame using depth conditioning + prompt text
      • Uses Movie Render Graph to produce a 4K image and associated pass data
      • Models are conditioned with Unreal-derived depth/layout information
    3. Use editor image segmentation tools to extract/mask elements (e.g., add a tire not available as an exact asset)
    4. Use the image model + tools (example: TripO 3.1) to repair/mesh extracted elements
    5. Reinsert repaired assets into Unreal and composite back into the image
    6. Generate video
      • Use the style frame as the first frame reference
      • Video model (example: SeedDance 2.0) generates camera-move-consistent output
  • Notes:
    • Video coherence limitations were discussed (e.g., camera can be controlled, but content behavior isn’t fully controllable)
  • Another “apartment” workflow:
    • Diffusion approach with a local Flex client
    • Lower temporal coherence (few frames/sec)
    • Interactive benefits:
      • prompt for lighting
      • return to UE viewport to move/adjust assets while diffusion restyles the scene
  • Availability:
    • Image/video tools described as early next year
    • MCP server ships earlier as part of 5.8

Distribution / ecosystem updates (Epic Games Store, Fortnite/UEFN)

Epic Games Store business metrics + incentives

  • 2025 growth / early 2026 results
    • 78M monthly active users (Dec record)
    • $1.16B player spend
    • 6,000+ games from 3,000+ partners
  • Incentives:
    • 100% of first $1M net revenue per product per year (then 88/12 rev split)
    • Epic First Run: 100% net revenue for first 6 months
    • Launch Everywhere with Epic: UE dev engine royalty reduction to 3.5% from 5%
    • Epic Rewards: 5% back to players on third-party purchases processed by Epic
  • Store performance improvements in progress:
    • Rebuilding launcher to reduce cold start times and improve browsing
    • Re-architecting backend for faster shipping of new features
    • Search/discovery enhancements and community features

Fortnite ecosystem / UEFN creator tools

  • UEFN creator output described as a major driver:
    • 75M+ monthly active users (Fortnite overall)
    • UEFN games capturing a growing share of playtime (example: 47% of player hours, up from 38% the year prior)
    • $1B+ paid out to developers since UEFN launch
    • Increasing share of UEFN revenue shifting to in-island transactions
  • Iteration and stability improvements (quality-of-life for creators):
    • Reduce change push times by ~40% on average; larger projects up to ~70%
    • Expanded Live Edit
      • edits applied directly in-game mode
      • “edit list” UI
      • consolidated UI adds detach camera + pause
  • Gameplay authoring expansion:
    • Scene Graph maturing (positioned as foundation for UE6)
    • New workflows mentioned: custom weapons/animations via Scene Graph
    • Plans/updates: gameplay attributes/abilities + Scene Graph UI
    • Engine systems emerging as first-scriptable components for UEFN
  • Monetization expansion:
    • IP partner program enabling licensed templates/characters/worlds (examples: LEGO, Star Wars, Squid Game)
    • Example creator: Future Trash’s “Droid Tycoon”
      • Most played UEFN game by hours
      • Concurrent player record
      • Star Wars IP
  • Mobile:
    • UEFN mobile play time doubled
    • Native gestures/support and touchscreen HUD customization
    • Some features exited experimental mode in August

IP partnerships & examples (Fortnite)

  • Disney/Fortnite partnership highlights:
    • Star Wars UEFN IP program results: multiple large island launches with millions of plays in short windows
    • Mandalorian/Grogu watch party island timing
    • Simpsons joining IP partner program later this year (Springfield “UEFN ready”)
    • Additional Disney/Pixar/Lucasfilm/Marvel/20th Century Alpha collabs described as popular

Unreal Engine 6 direction (core platform architecture + open ecosystem)

A major segment presented UE6’s vision/architecture: unifying UE5 and UEFN capabilities and enabling interop at scale.

UE6 unification strategy

  • Tim Sweeney framed the move:
    • Today: two paths—UE5 standalone games vs UEFN Fortnite-based toolchain
    • UE6 initiative: “UE5 + UEFN = UE6”
  • Goal: build once and deploy broadly:
    • ship to consoles/PC/mobile stores
    • ship into the Fortnite ecosystem
    • extend via other UE6 ecosystems

Verse as the gameplay programming foundation

  • Gameplay coding shifts toward Verse alongside low-level C++ engine.
  • Motivations:
    • massive scale code/content interoperability
    • transactional concurrency model (handled by runtime)
    • persistent worlds and global state correctness

Open standards and interoperability

  • Push for an “open ecosystem like the web”:
    • interoperable servers
    • shared content
    • travel between games
  • Mentioned interest/adoption of standards:
    • USD (Pixar USD)
    • glTF
    • open specifications when no standard exists
  • Stakes:
    • avoid an “overlord” model
    • Epic wants to be a peer partner

Unlocking portable player value

  • Fortnite cosmetics as first proof point:
    • base system modularized into an open module usable across games
    • player-entitled Fortnite outfits usable in other games
    • tools for creators to build outfits
  • Announced MetaHuman Dev Kit
    • rig logic + MetaHuman DNA tool sets open under MIT license
    • enables MetaHumans in “any game/engine/platform”

Gameplay architecture details (Curtis + Verse)

  • Verse technical ideas:
    • Software Transactional Memory (STM)
      • functions run as atomic transactions
      • can roll back/resimulate if spatial queries collide
    • distributed scaling approach
      • distribute “single-threaded style” code across servers
      • runtime migrates objects and reruns transactions to preserve consistency
    • simplified saving
      • global state synchronization and saving from Verse runtime
  • Adds Verse scene graph
    • modern component framework with prefab-style workflows and runtime composition
  • Engine exposure:
    • core systems become statically validatable Verse objects/types
    • compiler validation and parameter consistency across code/data

Version control for massive assets (Lore)

  • Matias presented Lore, Epic’s version control / data storage system.
  • Open-source announcement: MIT license
  • Designed for:
    • huge binary data sets
    • scalability globally
    • secure multi-tenant isolation
    • deduplication via content-addressed storage
  • Features:
    • free branching model
    • sparse binary-first storage (fetches only needed revisions/branches)
    • fragmenting large binaries for partial deduplication and efficient transfer
  • Tooling:
    • API-first design + CLI + desktop app + near-future Unreal Editor integration
  • Current usage:
    • Lore already powers UEFN under a prior name (“Unreal Revision Control”)
    • Epic plans full use by UE6 launch

AI and engineering use in UE6

  • Claims about AI-assisted creation:
    • not replacing engines with promptable world models
    • more about tightening iteration loops and reducing manual setup work (levels, rigs, particle systems, lighting)
  • Mentions internal usage success:
    • code indexing, incident response analysis, root-cause analysis
    • automated test generation
    • backend engineering wins
  • UE6 includes battle-tested AI workflows across internal + UEFN contexts

Timeline / transition from UE5 to UE6

  • UE5 and UEFN merge into one editor concept for UE6.
  • Actors/Blueprints appear early but eventually deprecated as the framework matures.
  • Public UE6 main stream visibility on GitHub later “today.”
  • Release plan:
    • early access around end of 2027
    • UE6 6.0 released 12–18 months after early access
    • keep most UE5 tech; Cascade is explicitly called out as being killed (move to Niagara)

Key tutorials/review-style takeaways (what was “shown” as effective)

  • UE5.8 performance/hitch reduction
    • shader dedup + PSO pre-caching + shader delivery initiative
  • Mesh Terrain
    • practical alternative to heightmaps
    • enables new geometry types while staying compatible with Nanite/World Partition/PCG
  • MCP + AI in-engine workflows
    • outputs remain editable Unreal scenes/procedural graphs (not static images), enabling rapid iteration
  • Linear content pipeline direction (early next year)
    • use Unreal depth/layout passes to condition image/video models
    • use segmentation to bridge missing assets into a consistent Unreal scene and compositing workflow
  • UE6 strategy
    • unify UE5 + UEFN tooling
    • use Verse + scene graph + STM for persistent and scalable worlds
    • add open standards/interoperability (plus open-source Lore and MetaHuman Dev Kit)

Main speakers / sources (as stated or implied)

  • Bill (host)
    • opening Unreal Fest remarks; references UE5.8 and project shout-outs
  • Mona me, Simon, and Jordan Rowe
    • introduced as presenters for UE5.8; Simon leads multiple sections
  • Michael
    • demoing MCP + Cloud Code + MCP server/PCG skills integration
  • Pat Kiernan
    • linear content creation tools; image/video restyling workflows
  • Jason and John
    • mentioned as giving deeper shader/cooking talk tomorrow
  • Kate Rayner (The Coalition)
    • Gears of War: E-Day showcase
  • Gina (Riot Games)
    • TFT migration and Unreal engine performance/system changes
  • Thor Freek (Neon Giant)
    • No Law presentation
  • Hannah
    • Fortnite developer relations; UEFN ecosystem/tools/Discover updates/IP program framing
  • Kevin Martineau
    • Future Trash; Droid Tycoon story
  • Tim
    • Tim Sweeney; UE6 vision/unification/interoperability direction + game business outlook
  • Marcus Wassmer
    • UE6 architecture overview; platform/ecosystem philosophy
  • Curtis
    • UE6 gameplay architecture; Verse + STM/distributed approach
  • Matias Jonsson
    • Lore version control; open-source release details
  • Curtis Schmidt
    • mentioned in UE6 distributed scaling/STM context (referenced as future talk)

Rate this summary

Your feedback will help improve summaries.

Improve this summary

Reprocess with a stronger model when the summary feels incomplete or inaccurate.

Pro

Translate summary in another language

Pro

Ask questions to this video

Chat for follow-up questions, clarifications, and source-backed answers.

Coming soon

Share this summary

Share on X/Twitter Share on LinkedIn Share on Reddit

Original video