Back to Blog
    Last Week in Unreal

    Last Week in Unreal: 5.9 Preview 1 Is Out, and ue6-main Removes Legacy Ray Traced AO (November 9 to November 15, 2026)

    Venkat S27 min read
    Terminal-style commit analysis card on a dark navy background, showing 1,271 commits on the ue6-main branch and 351 on the public 5.9 branch for the week of November 9 to November 15, 2026, under the headline Last Week in Unreal.

    Week of November 9 to November 15, 2026 | 1,271 commits on ue6-main, 351 on the public 5.9 branch, 801 more on ue5-main, none on 5.8 | Branch: ue6-main

    Overview

    The week’s news is 5.9 Preview 1. Epic tagged 5.9.0-preview-1 on November 9, a week after it said the Preview was coming. It is a Preview, and everything we say about 5.9 below should be read that way.

    All 351 of this week’s commits on the public 5.9 branch landed after the tag, and the branch head already differs from the Preview. Content-only projects package for the web there (Preview 1 still refuses them), AllToolsets is on by default, and Preview 1 bugs are getting fixed, including C++ web games built with the launcher engine losing their saves on reload and UnrealPak failing on paths with parentheses.

    If you ship on 5.8, the 5.8 branch took no commits and there is still no 5.8.5 tag. The 5.8 section lists the ue5-main fixes that match the 5.8.4 source, including a crash when r.ShadowQuality drops to 0 mid-frame, the same UnrealPak fix, and metal and mirror surfaces reflecting black near mobile reflection captures.

    On ue6-main, the second attempt to remove ray traced AO held, the cook version changed twice (each change invalidates every incremental cook), materials and Blueprints each take a one-time recook, the Linux toolchain build moved to EpicClang, and Model Context Protocol and AllToolsets are now on by default to match 5.9.

    At 1,271 commits, ue6-main came in below last week’s 1,476. Among named subsystems, build leads at 165, followed by editor at 94, rendering at 72, core at 36, and platform at 35.


    Legacy ray tracing went from opt-in to deleted across three weeks

    Pattern: this is the third week in a row with a legacy ray tracing step on ue6-main. In the week of October 26, ray traced AO, translucency, and sky light were put behind .Supported startup variables. Last week sky light was removed, and the AO removal was backed out the same day. This week AO was removed again under the same title, and this time it stayed (a5aad229). The same week removed D3D12 work graphs, the Lumen hit lighting direct lighting toggle, and r.RayTracing.Compaction.Explicit, a rollback switch added only last week.

    Interpretation: the pattern looks like gate it, wait about a week, then delete it. The rollback switches are not lasting much longer than the features they guard. Rendering commit volume does not show this. It went 66, 101, 91, then 72 over the last four weeks. Translucency is the one gated legacy feature from October 26 that has not been removed yet, so watch it next.

    Who cares: rendering leads and technical artists with ray traced projects tracking ue6-main.

    Signal strength: Strong.

    Build infrastructure had its biggest week since we began tracking ue6-main

    Pattern: 165 build commits this week, the highest weekly count since we began tracking ue6-main in June. Across the last eight weeks: 121, 104, 99, 123, 139, 116, 129, 165. The week includes EpicClang for the Linux toolchain build, OpenSSL 3.5.9 on Win64, the removal of long-obsolete RunUBT overloads, and two CookIncrementalVersion bumps, after four, zero, and three bumps in the previous three weeks.

    Interpretation: this continues the toolchain-floor and CI-script changes we have reported since mid-October (VS2026, the Linux Clang full rebuild, UAT and UBT changes). Read 165 as volume. A large share is UBA work, much of it bounds checks and POSIX, Linux, and Go error handling.

    Who cares: build engineers and anyone maintaining custom C# automation against UAT or UBT.

    Signal strength: Strong.

    Agent tooling volume fell back, and ue6-main now matches 5.9’s defaults

    Pattern: counted by commit path as before, the agent tooling cluster came to roughly 55 to 60 commits this week, depending on how noise is counted, against 55, 60, and 91 over the prior three weeks. Last week’s post said ue6-main kept Model Context Protocol disabled while 5.9 turned it on. This week 58fcabbf sets EnabledByDefault to true for ModelContextProtocol and AllToolsets, to “Match the 5.9 defaults.” Both plugins are still marked experimental.

    Interpretation: the agent stack now has the same defaults on both branches. A fresh ue6-main editor loads these plugins unless a project turns them off.

    Who cares: tools programmers, teams with editor automation, and anyone who audits which plugins their editor loads.

    Signal strength: Medium.


    TL;DR

    • 5.9 Preview 1 is out. Tag 5.9.0-preview-1, published November 9. Since the tag, the branch packages content-only projects for the web (Preview 1 itself still refuses them), turns AllToolsets on by default, and fixes Preview 1 bugs, including launcher-build C++ web games losing saves on reload and UnrealPak failing on paths with parentheses.
    • If you ship on 5.8: no commits on 5.8 and no 5.8.5 tag. Worth cherry-picking from ue5-main: the shadow quality crash, the UnrealPak parentheses fix, black reflections near mobile reflection captures, and null widget animation references after undo. They should apply, not that they compile.
    • ue6-main removed legacy ray traced AO, and this time it stuck. The FPostProcessSettings RTAO fields are deprecated (a5aad229). D3D12 work graphs are gone (6e861cfc), and so is the explicit compaction rollback switch added last week (c01a3896).
    • Plan for recooks. CookIncrementalVersion changed twice, and each change invalidates every incremental cook (09690137, a5fa71a4). Every material and material instance recooks once (dae20a62), and Blueprints take a one-time full recook (20b0e9e0). Multi-platform multithreaded saves could save platforms twice or skip them (c576ee61).
    • Toolchains moved. The Linux toolchain build now produces EpicClang instead of vanilla LLVM (def40d87). Win64 is on OpenSSL 3.5.9, other platforms are not (9fa0b5f2). The Android code removal was backed out and did not ship (89f3c8cf).
    • Defaults moved. MCP and AllToolsets are on by default (58fcabbf), UMG.ReregisterQueuedAnimationsOnTick is on (40aa9104), and Vulkan SM6 gets shader bundle dispatch on Linux and Windows (309d3020).

    Highlights

    Legacy ray traced AO is gone, along with work graphs and the compaction switch

    AO, this time for real. “[HWRT] Remove legacy RT Ambient Occlusion,” which the commit says was “deprecated by Lumen and has not been enabled by default for a while” (a5aad229). The diff removes r.RayTracing.AmbientOcclusion, .Supported, .SamplesPerPixel, .EnableTwoSidedGeometry, and .EnableMaterials, along with the r.AmbientOcclusion.Denoiser.* family. In FPostProcessSettings, RayTracingAO, RayTracingAOSamplesPerPixel, RayTracingAOIntensity, and RayTracingAORadius lose their editor and Blueprint exposure (they were EditAnywhere, BlueprintReadWrite) and are renamed with a _DEPRECATED suffix, along with their bOverride_ toggles. The r.RayTracing.AmbientOcclusion=0 line in BaseDeviceProfiles.ini is gone too, along with the r.RayTracing.GlobalIllumination=0 line next to it.

    D3D12 work graphs. “Remove D3D12 work graphs.” The commit says the feature was experimental, that “Support is discontinued by Microsoft in future versions of D3D12,” and that it was “Only used by Nanite with r.Nanite.AllowWorkGraphMaterials (off by default)” (6e861cfc). The diff deletes r.Nanite.AllowWorkGraphMaterials and r.ShaderBundle.MaxSize, and removes bSupportsWorkGraphs=true from the Windows DataDrivenPlatformInfo.ini.

    Compaction. “FRayTracingGeometryManager now always manages compaction” (c01a3896). The diff removes r.RayTracing.Compaction.Explicit, the rollback switch added last week, along with the per-RHI MaxBatchedCompaction variables for D3D12, Metal, and Vulkan.

    Smaller removals. r.Lumen.HardwareRayTracing.HitLighting.DirectLighting is gone: “Hit lighting now always calculates direct lighting” (30934c36).

    Why it matters. Blueprints or C++ that set the RTAO post process fields can stop compiling or stop applying, and any config or device profile that still sets the RTAO variables now sets nothing. If you set r.RayTracing.Compaction.Explicit=0 last week to roll back compaction, that option no longer exists. Nanite work graph materials were off by default, so few projects should notice that removal.

    Urgency: act now if your post process volumes, Blueprints, or configs reference ray traced AO.


    Cook and shader cache correctness

    Two cook version bumps. “Bump CookIncrementalVersion. Gameplay tags not picked up” (09690137). The engine says a new CookIncrementalVersion means “all packages in all platforms in all projects need to be invalidated in the next incremental cook,” and the second bump changes the same value. It comes with a fix that stops DLC cooks on a cooked base game from writing “invalid oplog entries for basegame packages that they loaded from cooked packages.” The commit warns it “will cause all DLC cooks to recook all of their packages that have transitive build dependencies on basegame content,” unless the DLC cook has the base game oplog available (a5fa71a4).

    Material and Blueprint recooks. The stale shader map fix below also bumps the material incremental cook version: “Every material and material instance recooks once in each existing incremental cook store” (dae20a62). A separate change accepts “every native class hash changing once and a one-time full Blueprint recook” (20b0e9e0).

    Multi-platform multithreaded save. With Cook.AllowMultithreadedSave, the save context held a view of a reused array, so with more than one target platform “platforms were saved twice or skipped,” producing “FZenStoreWriter commiting the same package twice” errors and fatals. “Single-platform cooks were unaffected” (c576ee61).

    Stale material instance shader maps. Material instances with static permutations now declare their shader map inputs as cook dependencies. Before, an incremental cook could keep a stale map, which, after a parameter collection layout change, ended in a runtime fatal, “Failed to find parameter collection buffer” (dae20a62).

    ShaderCompileWorker source checks. UBT now writes source hashes, and ShaderCompileWorker rejects batches when its source differs from the editor’s, “instead of compiling output that gets cached under the editor’s keys” (6346fd62, with 49de21da). The commit says the existing local-worker version check “never ran,” because names were dropped in serialization. The diff adds +EditorModuleSourceHashTargets=ShaderCompileWorker to BaseEngine.ini.

    Editor-only shaders stripped from Windows client cooks. Hit proxy, Nanite raster VISUALIZE, and landscape physical material permutations “are no longer cooked for every PC material” (0b24b9ae). The diff adds r.Shaders.CookEditorPermutations, default 0, and the message says it “is part of the shader DDC key, so changing it recompiles.” One caution: the message describes a Windows config override that keeps the engine’s fallback materials complete, but that override is not in the commit’s diff, and no other commit this week adds it. Check the value your Windows cooks actually resolve before you assume the fallback materials keep their editor permutations.

    Why it matters. Syncing past this week means a full recook, and DLC cooks on a cooked base game recook their base game dependents on top of that. The multi-platform save fix matters if you cook two or more platforms in one process with multithreaded save on. The ShaderCompileWorker change can surface as new rejected batches on machines with stale workers.

    Urgency: act now on recook capacity. Track the rest.


    Build toolchain: EpicClang for Linux toolchains, OpenSSL 3.5 on Win64, and AutomationTool removals

    Linux toolchain. “New Linux toolchains. Vanilla LLVM replaced with EpicClang” (def40d87). The commit changes how the Linux toolchains are built and packaged: they are now stored packed, and it adds AutoSDK setup and unsetup scripts. Linux_SDK.json on ue6-main still pins v26_clang-20.1.8-rockylinux8, so the toolchain version the engine asks for has not changed.

    OpenSSL 3.5.9 on Win64 only. “OpenSSL 3.5 upgrade (3/3): build rules, scripts and call sites” moves “Win64 onto OpenSSL 3.5.9 … Every other platform stays on 1.1.1t for now” (9fa0b5f2). The diff limits it to Win64 when the architecture is not Arm64. Parts one and two add the 3.5.9 binaries alongside 1.1.1t and rebuild WebRTC against 3.5.9 (125fc673, 6757dfbc). The commit lists what broke along the way, including windows.h leaking max() and GetObject() “into whatever is compiled next in the same unity blob” and renamed imports such as SSL_get_peer_certificate. Win64 code that includes <openssl/ssl.h> or links its own OpenSSL-dependent libraries can hit the same issues.

    Installed engine, monolithic games. Shared monolithic games built against an installed engine now compile the engine’s per-target code from source, so they “can then use … EnablePlugins and DisablePlugins” (95f7c9a8). When that source is not installed, UBT keeps the precompiled libraries and refuses a target that sets either list (cb8048f8).

    AutomationTool API removals. RunUBT overloads that take a UBT executable path are removed, “obsolete since 5.1” (c637bbe2). BuildCommand is removed from CodeSign.SignMultipleIfEXEOrDLL (99a2b1fb). More than a dozen “Remove unused code” commits went through Apple, Microsoft, BuildGraph, Turnkey, Gauntlet, and other code. The Android one was backed out with no reland, so it did not ship (987038a8, 89f3c8cf).

    Android SDK setup. The setup scripts now use the new Android CLI instead of sdkmanager, because “cmdline-tools 23.0 replaced the Java sdkmanager with a shim over Google’s self-updating Android CLI.” They fall back to sdkmanager if the CLI is missing, but “The legacy tools/bin location (SDK Tools 26.1.1…) is no longer searched” (5db64414).

    Horde leases. “Completed leases kept job bearer tokens, compute keys and workspace credentials in their stored payload with no expiry.” They are now blanked when a lease completes, but “Leases that completed before this change are not changed” (e7aa4b54).

    Why it matters. Custom C# automation that calls the removed overloads can fail to compile. Win64 plugins with their own OpenSSL dependency should be rebuilt and tested against 3.5.9. Android build machines that rely on the old tools/bin layout need the newer command-line tools. If you run Horde, the lease fix covers new leases only, so stored payloads from older completed leases still hold those credentials.

    Urgency: act now for custom AutomationTool code, Win64 OpenSSL consumers, and Horde administrators. Track the Linux toolchain if you build Epic’s toolchains yourself.


    Defaults that moved

    • MCP and AllToolsets on by default, as covered under Trends. The same commit restricts the Interchange references in EditorToolset.uplugin to editor targets, because they “fail UnrealGame builds on other platforms” (58fcabbf). Separately, the deprecated MCP Tool Library classes were removed, including UModelContextProtocolToolLibrary (43252bb3).
    • UMG animation re-registration. UMG.ReregisterQueuedAnimationsOnTick now defaults to true, so ticking widgets with queued animation transitions re-register with the animation tick manager after being dropped (40aa9104). The 5.8 section covers its mention of 5.8.5.
    • Material translator. The code default of r.Material.Translator.EnableNewUI goes from 0 to 1, and r.Material.Translator.DefaultProfile=1 is removed from the engine’s ConsoleVariables.ini (0670af7e). Another commit replaces the r.Material.Translator.EnableNew toggle with “a Standard/Compatibility/Legacy material translator profile” and renames r.Material.Translator.EnableLegacyValidation to EnforceLegacySupport (01a83ac7).
    • Vulkan shader bundles. “VulkanRHI: Enable shader bundles on Linux” (309d3020). The diff sets bSupportsShaderBundleDispatch=true in the Linux DataDrivenPlatformInfo.ini and r.Nanite.Bundle.Shading=1 in LinuxEngine.ini. It also sets bSupportsShaderBundleDispatch=true for the Vulkan SM6 shader platform in the Windows DataDrivenPlatformInfo.ini, which the message does not mention.
    • Linux drivers. The suggested NVIDIA driver goes from 595.71 to 620.70.06 in BaseHardware.ini. The config comment says it is “the first version to include a performance fix for ShaderObject binding” (164b1e1c). The same commit raises the suggested AMD RADV driver from 26.0.0 to 26.2.6 and deny-lists RADV versions below 26.2.0, up from below 25.0.0.
    • Agility SDK. The default version goes from 1.620.1 to 1.620.2 (71f06aa5), which was added “with the explicit PSDB lookup fix” (9895c412).

    Why it matters. Configs that set EnableLegacyValidation or EnableNew now set nothing. The shader bundle commit also changes a Windows platform flag for Vulkan SM6, so teams running Vulkan on Windows should know it is there. Linux machines on RADV 25.x through 26.1 now fall under the deny list.

    Urgency: act now on configs that set EnableLegacyValidation or EnableNew, and on Linux RADV drivers. Track the rest.


    “Final” material instances

    A new opt-in for material instances and material function instances. “A Final asset only lets its descendants change values that do not change shader code” (7a84509a). The diff adds bFinal, default false.

    • Overrides are set aside. A day later the design changed: “overrides a final ancestor does not allow are set aside, not ignored in place” (60af5774). They move to editor-only storage and come back if Final is cleared.
    • It holds in cooked builds. bFinal “is runtime data on both classes so cooked parents keep the rule, including in cooked editors” (7a84509a).
    • Still settling. Validation tools followed (bbe33839), behavior and storage were reworked (60af5774), and the two clear functions in UMaterialEditingLibrary were renamed twice, with “No redirects” (60af5774, 4401aad7).

    Why it matters. It is an opt-in, per-asset way to cap permutations at the parent, on top of the existing override locks. Marking an existing parent Final can change how its descendants render, with no edit to the descendants. The clear functions were renamed twice within a day of landing, so wait before you script against them.

    Urgency: track. Try it on a test material tree before you mark a widely used parent Final.


    Worth Tracking

    Lore source control plumbing. About 25 commits mention Lore. “UGS Lore mode (syncs from Lore; Perforce stays the system of record for checkouts, shelves and submits)” (427d2098). A Horde Lore driver gained an opt-in virtual filesystem, “Off by default,” which the message says “falls back to a normal clone in the same lease” on failure (4bc4dfb9).

    Mobile and HDR wins, off by default. r.ShadowProjection.UseHardwarePCF3x3 defaults to false and is mobile renderer only. On a Galaxy S25 the commit measures shadow projection going from 0.54 ms to 0.40 ms, and from 1.57 ms to 1.01 ms with the depth bounds test off, “the path Mali uses” (617d6bd1). The light function atlas comes to the mobile deferred renderer’s light passes, for default materials only (99dbce9b). “Overly bright after-tonemap materials with HDR output” are fixed behind r.HDR.SDRReferredAfterTonemapMaterials, default 0 (62e07276).

    Security fixes. Iris validates the size read in the RPC header (a7535e75), remote Chromium devtools are off in shipping builds (ba8670c6), and nDisplay Quick Launch binds the message bus to loopback by default (2c41b863).

    Follow-ups on earlier posts. Beyond the AO removal and the compaction switch, we found no follow-ups to last week’s removal of cooking in the editor process or of ray traced sky light.


    What We Ignored

    Most of the 1,271 ue6-main commits: Toolsets and MCP agent tooling churn, Verse and UEFN internals, Navigation and Detour bug fixes, DDC legacy API migrations, new material translator work on loops and tuples, Horde logging and audit changes, a run of UBA hardening commits, Gauntlet and PGO work, and single crash fixes in tools. There were 16 commits tagged [Backout] among the 1,246 we analyzed (18 in the full 1,271). Among the backouts that did not reland, besides the Android removal, are a UBA fstatat change (cf88f64c, backed out by 7e1e2e74), a port that runs a UAF (animation framework) graph inside the ChaosMover step protocol (f1103071, backed out by a1ceacf5), and the removal of Mutable Int redirects (8191117b, backed out by 4682ee50), so those redirects stay.


    For teams shipping on 5.8

    Nothing moved on 5.8. The public 5.8 branch took zero commits this week. Build.version still reads 5.8.4, and there is no 5.8.5 tag. The fixes we recommended in earlier editions are still cherry-pick material.

    Where the fixes are now. Fixes land on ue5-main and on 5.9, many of them twice, once as a Dev-5.9 copy. Of the 801 ue5-main commits whose SHA is not on 5.9, most are the same changes landing on 5.9 under another SHA. The rest are mostly Unreal Canvas, UAF and AnimNext, and similar work with nothing for 5.8.4. The ones below matter to 5.8 users. For each one we pulled the diff, fetched every patched file at the 5.8.4-release tag, and searched for each hunk’s context and removed lines as a contiguous block. “Matches 5.8.4” means every non-test hunk was found. That means it should apply, not that it compiles, so build and test it. No backout this week touches any of these.

    Worth cherry-picking onto 5.8.4

    • Shadow quality crash. “Fix crash in shadow projection when r.ShadowQuality drops to 0 while shadow projection passes are in flight.” The commit: “If r.ShadowQuality=0 is propagated between the shadow pass being enqueued, and the pass being executed, the check will crash.” The fix reads the value on the render thread and captures it by value (4a89ad4e). Matches 5.8.4. Take it if your settings menu or scalability code can drop shadow quality to 0 at runtime.
    • UnrealPak paths with parentheses. “UnrealPak cut -cryptokeys and other path switches at the first ‘)’ or ‘,’ (e.g. D:\UE\Release5.9(launcher)...), so loading the keychain asserted and packaging failed” (11a6a7b0). Matches 5.8.4. The commit says it was “Not run through UAT on Windows or with -iostore end to end,” so test your packaging path after you take it.
    • Black reflections near mobile reflection captures. “On the mobile shading path, metal and mirror surfaces near a built reflection capture reflect black.” The commit traces it to “CL 49645640 (5.8, a race on creating the encoded HDR texture),” and says “Natively nothing recreates it in a cooked game” (1685f000). Matches 5.8.4. The diff adds r.ReflectionCapture.UpdateProxyOnEncodedAllocate, default 1; setting it to 0 restores 5.8 behavior, apart from a new empty-data check that stays on. It applies to mobile forward shading and to forward-shaded translucency on mobile deferred, whenever clustered reflections are off (the default). Streamed sublevels and Level Instances can still render black, which the commit leaves open.
    • Widget animation null references. “Widget animation copies killed by undo were saved as null references, crashing compile-on-load in PurgeClass.” It happens when undoing a compile inside a transaction, such as Reparent Blueprint (64e84d24). Matches 5.8.4.
    • Animation DDC softlock. “Fix for softlock when building anim ddc.” On a DDC miss, the worker “must take that same lock … and nothing cancels it.” The commit says “a.SkipDDC=1 should help repro” (0a6a1e8c). Matches 5.8.4.

    Take if you hit them

    • Xcode to LLVM mapping. “Every x.y Xcode that equals a key got the previous row’s LLVM version (16.3 -> 17.0.6 instead of 19.1.4, 26.4 -> 19.1.5 instead of 21.1.6)” (f6956ffd). Matches 5.8.4, whose Apple_SDK.json has those rows. The commit describes a wrong mapping, not a build break, and says it was “Not tested on a Mac with a real Xcode install.”
    • More black mobile reflections. Mobile captures that were never built, or edited without a rebuild, bind a black cube, so nearby metal and mirror surfaces reflect black (de087845). Matches 5.8.4.
    • Crashes. SViewport::OnPaint “called ISlateViewport::GetViewportRenderTargetTexture() twice and null-checked only the first result” (1a5460f1). Generating box, sphere, or capsule collision on a mesh with no mesh description (f5fda880). “LiveLinkHub crashing when ingest scans a folder containing a re-muxed mp4” (7129040d). All match 5.8.4.

    Looks like a fix, but is not one for 5.8.4

    • An Interchange FBX dense-mesh slowdown fix (6a9bd112) measures 5.8.4 at “19.8 s” and Main before the fix at “52.7 s”. The regression came after 5.8, so there is nothing to take.
    • A UBA link.exe hang, “deadlocked in UBA’s detour DLL, which called GetProcAddress in AttachLazyDetours while holding the loader lock” (cb19fb57). 5.8.4 has no AttachLazyDetours, so the patch does not apply. We have not verified whether 5.8.4 has the hang in another form.

    The one 5.8.5 mention. A ue5-main commit turns on UMG.ReregisterQueuedAnimationsOnTick and says “This was submitted to 5.8.5 at 59825078 but disabled” (4fb13b79). That variable does not exist in 5.8.4’s UserWidget.cpp, it is not on the public 5.8 branch, and CL 59825078 is not public. It is the only change this week that mentions 5.8.5 (the same change also landed on ue6-main), and it says nothing about when 5.8.5 might ship.


    UE 5.9: Preview 1 and what changed since

    Where it stands. Epic published “Unreal Engine 5.9.0 Preview 1” as a GitHub release on November 9, with the tag 5.9.0-preview-1 and the body “Unreal Engine source code for version 5.9.0 Preview 1 (changelist 60351404).” All 351 commits on the public 5.9 branch this week came after that tag, most of them in one batch on November 13. The branch head is 433 commits ahead of the Preview 1 tag, so 82 more predate this week. Several commits mention “Preview 2” (2235c93a, 06b36c45), but there is no Preview 2 tag or release. Treat those as labels on work aimed at the next Preview.

    What changed since last week’s post. Two of last week’s points have moved, and one more default changed.

    • Web no longer needs a C++ project on the branch. “content-only (Blueprint-only) projects package for the web, running the engine’s UnrealGame” (6e09f48b). Before it, “UAT stopped every content-only project with exit 19 (‘Web (Wasm) … needs a C++ project’), and the editor greyed out the platform for it.” The docs drop “Preview 1’s web needs a C++ project” and now require “emscripten 6.0.10, exactly, for every project, content-only projects included,” and a content-only project’s BuildCookRun that builds or cooks without emsdk now stops at the start with exit 10. Preview 1 itself is unchanged: another commit says “5.9 Preview 1’s packaging refuses content-only projects for the web” (ac68d81f). A related fix enables GameplayStateTree by default, because without it the Blueprint templates were “treated as a code-based project” (7f07d64a).
    • AllToolsets is on by default. The diff flips EnabledByDefault from false to true in AllToolsets.uplugin (e9ec048d). It was false at the 5.9.0-preview-1 tag and is true at the branch head, and it is still marked experimental. The reason given: without it, “Agents had no actor, level, asset, Blueprint, console or Live Coding tools, and nothing told them the plugins were disabled.” A follow-up says “AllToolsets is enabled by default on Release-5.9 … this change is for Release-5.9 only” (d7d553a5). ModelContextProtocol is also still on by default.
    • UBA Cloud is labeled Experimental. Last week it was Alpha. Its README and docs now say “This feature is Experimental. You can use it, but it may change or be removed in a future release” (753bdfe1). It ships as source under Engine/Extras/UBACloud, and it is not in the installed-build file lists.

    The docs lag the default. The 5.9 getting-started docs at the branch head still describe AllToolsets as off by default, and so does a troubleshooting entry added this week (4b3914d0). That entry scopes the GameFeatureData cook failure to a project that turns AllToolsets on, and says “a fresh project cooks as made.” The web skill notes say a build with “the QFE default with AllToolsets on” cooked for Wasm, while a project “whose .uproject turns AllToolsets on stopped the cook” (03558cfe). We have not tested it. If you see “Asset manager settings do not include a rule for assets of type GameFeatureData” on a web cook, check whether your .uproject enables AllToolsets.

    Preview 1 bugs fixed on the branch

    • Web saves lost on reload. “every C++ web game packaged with the 5.9 Preview 1 launcher build loses its saves, settings and log on every reload.” Source builds are not affected, because “A source build compiles Core per project” (ac68d81f).
    • UnrealPak and parentheses. The same fix as in the 5.8 section, for launcher paths like Release5.9(launcher) (625a5341).
    • Mac and Linux installed builds. Agent tools were “listed only in CopyEditorFilterWin64, so the Mac and Linux installed builds shipped without it” (c07d6b69). Those builds also lacked the web libraries, templates, and docs (cc7d02be).
    • Web memory above 2 GB. A signed shift in the JavaScript glue meant “At an address of 2 GB or more the index is negative: a read gives undefined and a write is dropped” (4f84f35f).
    • iOS. An extra audio-thread worker on iOS 26 meant “a stock Third Person template Development build was killed” on an iPhone 15 Pro Max (f5e719ef).
    • Editor. Issues “Originally raised in 5.9 preview 1,” including “multiple sources could be added for the same Actor during PIE” and “Crash when undoing applying a Take Preset” (d45ef65e), plus a fix for an “editor crash when deleting a stale Blueprint subobject handle after replacing the scene root” (91e3a3cd).

    Web follow-ups

    • Linux browsers no longer run the desktop tier. A revert of web dispatch workarounds removes r.Lumen.WebDirectDispatch=1 from BaseWasmEngine.ini after the commit measured “Linux Chrome on an NVIDIA L4 … -51 % (24.4 to 12.0 fps), about 1.3 ms per indirect dispatch” (02276673). The docs say the desktop tier “is experimental and not part of Preview 1.”
    • Localization. ICU on the web is behind WasmTargetRules.bICU, default false according to the message. Without it, -culture= and the browser language “change nothing, no translation applies,” and “CJK text does not wrap” (3e60363b).

    AI and MCP. The deprecated MCP Tool Library classes, including UModelContextProtocolToolLibrary, are removed, which the commit says were deprecated for UToolsetDefinition (cd6973d2). That is an API break on a release branch: plugins built on those classes against Preview 1 can fail to compile against the branch head. AI Assistant fixes include “give an external agent the editor’s MCP server only while that server runs” and “restrict the assistant web API to pages under main_url” (14025b4d).

    Rendering defaults

    • Stochastic PCSS for virtual shadow maps at lower quality. Directional VSM optimizations and Stochastic PCSS came over from Main (db7dcc6a). The diff adds r.Shadow.Virtual.ProjectionMethodDirectional with a code default of 0 (SMRT), but BaseScalability.ini sets it to 1, Stochastic PCSS, described as “lower quality, faster,” at shadow quality 0 and 1, and to 0 at 2, 3, and Cinematic. A follow-up disables the projection data uniform buffer to fix a VULKAN_SM6 shader compile error, and the commit says “This gives up part of the GPU time saving” (5eb57f15).
    • Linux SM6. The diff adds +TargetedRHIs=SF_VULKAN_SM6 for Linux in BaseEngine.ini (d73c02c8).

    What did not ship. A wrap for Lumen light tile dispatches past 65,535 groups (f7b86bae) was backed out: “back out the light tile slot dispatch wrap (60351041)” (27155261). The backout says there was “no report of it,” that it “was tested only with the limit lowered,” and that it costs “a buffer read per group on every platform.” There is no reland. The separate compacted-trace wrap stays (67cd369c).

    Toolchain. bNoStaticDestructors now needs Clang based on LLVM 20.1 or later, and UBT refuses that option on older Clang or MSVC (eef6b606). This is a floor for that option only.


    Closing

    Evaluating 5.9? Read the branch head for web, since content-only packaging is not in Preview 1. The launcher save and UnrealPak fixes are on the branch only. Move MCP Tool Library plugins to UToolsetDefinition. On 5.8, take the shadow quality and UnrealPak fixes, plus the mobile reflection fix if you ship on mobile. On ue6-main, clear RTAO references from your post process settings, plan for a full recook, and rebuild Win64 OpenSSL consumers.

    Commit SHAs are cited inline, in parentheses, next to each claim. They reference the ue6-main branch of EpicGames/UnrealEngine, except in the 5.8 and 5.9 sections, where they reference commits on ue5-main and the public 5.9 branch.

    Share this article