Skip to content
AssetLoom

AI & industry

Unreal Engine 5.9 Preview puts AI agents in the editor: what game developers should know

Epic's Unreal Engine 5.9 MegaJam Preview adds editor AI agents, Unreal Canvas for generated meshes and AI animation. What shipped and what to check.

By AssetLoom Team, published , 6 min read

0 likes
Small clay-like 3D objects (a rock, a crate, a lamp post and a wooden mannequin) on floating glass panels, linked by warm orange light threads, suggesting AI agents assembling a game scene.

On 9 November 2026 Epic Games released an early preview of Unreal Engine 5.9, timed for its Epic AI MegaJam (12 to 15 November). Most of what is new is about AI: agents that can work inside the editor, an experimental workspace that generates images, meshes and video with your own API keys, and AI-driven animation generation. It is a preview, built fast and tested lightly, so the useful question is not "should I upgrade?" but "what should I try on a copy, and what still needs a human check?" This post walks through what Epic actually shipped, using its own announcement and release notes, and what it means if you make games or game assets.

What Epic released, and why it is unusual

Epic's announcement on its developer forum (opens in a new tab) calls this the "MegaJam Preview" and says it is not a typical preview. Epic had been collecting rendering and animation changes for a full 5.9 release next year, then decided about a week before the post to put out a preview in time for the jam.

Epic describes it as the first Unreal Engine release built primarily with agentic workflows: a small team directed AI agents that ported AI tooling from the Unreal Engine 6 development branch and added the web as a target platform, while engineers directed, reviewed and tested the work. The post is open that it had about a week of development and a shorter QA pass than usual, and that agent-written code is still being cleaned up.

A preview, not a release

Epic says preview builds are not fully quality-tested and should be treated as unstable until the final release. It recommends testing on a copy of your project rather than converting your project. The full 5.9 release is planned for next year, with no date given.

AI agents inside the editor

The biggest change is how much of the editor an outside AI agent can now reach. According to the forum post and the 5.9 Preview release notes (opens in a new tab):

  • Unreal MCP (experimental) now starts with the editor and connects more reliably. MCP is the Model Context Protocol, a common way for AI agents to call tools. The toolsets cover rendering, source control, profiling, debugging, gameplay testing, geometry, audio, UI and level creation, plus a Fab toolset for searching, browsing and installing assets.
  • Unreal Assistant (experimental) is an in-editor panel for working with external coding agents connected to Unreal MCP. A tool-access setting with five levels (Ask, Read, Edit, Auto and Full) controls how much it may do on its own.
  • A Toolset Registry decides which toolsets agents may use, and new project settings control the MCP server's port and allowed origins.
  • Wider Python scripting, with APIs for audio, MetaSounds, modeling, physics, Niagara, materials, PCG, networking and UI, and new libraries that let scripts create and edit Blueprints, graphs, nodes and variables.

One practical detail from Epic's known-issues list: in new projects the level-editing toolsets for agents are off by default, so an agent cannot edit levels until you enable all toolsets and restart the editor.

Unreal Canvas: generating images, meshes and video

Unreal Canvas is a new experimental feature that the release notes describe as a shared workspace where people and agents create and refine content. The forum post says it runs as a web app and inside the editor, and generates concept art, images, 3D meshes and video using your own API keys for the models you choose. The release notes list the generation services it connects to, including Fab image and mesh generation, chat completion, voice, and third-party AI models.

Two companion plugins tie Canvas to your scene: one exposes Movie Render Graph rendering to Canvas as MCP tools, and one places annotations in the 3D scene and captures it for Canvas. The release notes also mention a live AI-processed viewport preview.

What the release notes do not cover is just as important for creators: they say nothing about what generation costs, how ownership or commercial-use rights work for generated assets, or how your data is handled. Because Canvas uses your own keys, those answers come from each service you connect, not from Epic's notes.

AI-driven animation

The Unreal Animation Framework (UAF) gets a large update, and part of it is generative. The release notes list a UAF AnimGen plugin that brings AI-driven animation generation into UAF, an AnimGenOffline plugin that places generated animation straight into Sequencer, and an NVIDIA plugin called Kimodo for making characters follow trajectories, setting key poses and producing animation from text descriptions.

Not everything is generative. The IK Retargeter gains Proximity IK, Pelvis Volume and Limb Twist, UAF adds a notify system with built-in sound and Niagara handlers, and StateTree gets new conditions such as Animation Is Looping and Animation Time Remaining. Those are the kind of changes that help any animation, generated or hand-made, sit better on your characters.

The rest of the preview

  • Web as a target (experimental): projects can run in a browser through WebAssembly and WebGPU with the mobile renderer. It needs a source build and a C++ project, and Epic's known issues include crashes above 2 GB of WebAssembly memory and missing support files in the premade Mac and Linux builds.
  • Lumen World Cache: a lighting cache built at runtime by path tracing, so it needs no mesh cards. It requires hardware ray tracing and is switched on per project.
  • Nanite culling: applied automatically with no content changes, with larger gains in larger scenes.
  • Forge: described only as a collection of web-based designer tools inside the editor.

Reaction in the forum thread is mixed. Some replies welcome the direction; others object to AI-written code and documentation, or would rather see long-standing bugs fixed first.

What this means for you

If you make games or game assets, here is how we would approach the preview.

A grey 3D rock on a turntable beside a ruler, a magnifying glass, a glowing orange wireframe cube and a checker-pattern sheet, standing for the checks a generated mesh needs.
Generated or hand-made, every mesh needs the same checks before it goes into a level.
  • Try it on a copy. Epic says so itself. Keep your main project on your current release, and treat anything built in the preview as an experiment until the full release.
  • Decide what an agent may touch. The Assistant's access levels and the Toolset Registry are there for a reason. Start with read-only or ask-first access, keep the project under source control, and review what an agent changed before you commit it.
  • Check every generated mesh like any other import. Look at scale and pivot, topology and UVs, materials, collision and LODs before a generated mesh goes into a level. A model that looks right in a preview can still be heavy, open or badly unwrapped. Our post on what AI 3D generation can and cannot do yet covers what to look for.
  • Check generated animation on your own rig. Watch feet and hands for sliding, check loops at the seam, and decide early between root motion and in-place clips. Our guides on retargeting in Unreal and root motion versus in-place help here.
  • Read the terms of every service you connect. With your own keys, costs, ownership and commercial-use rights come from each provider. The same goes for assets you install through an agent: check each one's licence, as our guide to using assets commercially without licence surprises explains.
  • Keep a record of what was generated. Stores may ask. Steam's content survey asks developers about AI-generated content, which we covered in our post on Steam's AI disclosures. Noting which assets, clips and voices came from which tool is much easier as you go than at launch.

Whatever mix of generated and hand-made assets you use, the import basics do not change. Our guide to importing an FBX character into Unreal Engine 5 covers skeletons, scale and animations, and AssetLoom Studio exports what you build as FBX or GLB for Unreal. The Loom Avatars Starters are free to build with.

Sources

  1. Unreal Engine 5.9 MegaJam Preview (opens in a new tab), Epic Games (Epic Developer Community Forums),
  2. Unreal Engine 5.9 Release Notes (opens in a new tab), Epic Games,

Spotted a mistake or have a question? Email support@assetloom.io.

All posts