Status: 2026-10-18. Measured on PC 1 (RTX 5090, Ryzen 9 7950X3D, Epic) on Death Island, the heaviest remastered map: 535,000 grass clumps in 245 instanced meshes, 7,700 cliff-cladding rocks, 790 decor pieces. Most runs were at 1710x1073 (a borderless window over Remote Desktop; the 200% runs render 3420x2146), and the last at 3840x2160. On 2026-10-18 the campaign (B30) was measured against Blood Gulch and Death Island at the same settings (Campaign against our maps).
Update 2026-10-21: the mod changes on this page have shipped:
mjolnir_bench, /bench, the cull, low-foliage wind and dry zones fixes in
mods-v0.28.0 (PR #201), the frame split in mods-v0.29.0 (PR #202), the Lua
collector changes in mods-v0.30.0 (PR #206), the loader's side of baked
foliage and the faster asset lookup in mods-v0.31.0 (PR #208), and the bench
camera fix in mods-v0.31.1 (PR #204).
Players report that the remastered maps play fine without grass and rocks and slow down with them. This page covers the tools for seeing where frame time goes, what was measured, what was changed, and what is left.
Tools
| Tool | What it tells you | Where |
|---|---|---|
stat unit | Frame, Game, Draw (render thread), RHIT, GPU Time, Draws, Prims. Works in this Shipping build. | console |
/bench (match chat) | The foliage bench below, its result in your chat, and sent to the hub with its settings; admins read them on the moderation page's Benchmarks tab. For players. | MJOLNIRHud Scripts/bench.lua, hub POST /benches |
mjolnir_bench | The cost of the loader's foliage, its shadows and its wind, as an A/B at a held camera. mjolnir_bench send also sends it, as /bench does. | MJOLNIRHud Scripts/bench.lua, bench.log |
mjolnir_bench <cvar> <value> | The same A/B for any console variable against its current value. | same |
mjolnir_hitches | Per-map median, p95, p99 and worst frame, every hitch with where the camera was and which of our Lua loops ran. Each map's heading in hitches.log now carries the settings line. | MJOLNIRHud Scripts/hitches.lua, hitches.log |
mjolnir_level_status | Also the loader's live Lua heap (after two full collections) and how many actor handles it holds. | MJOLNIRLevelLoader |
r.ScreenPercentage 200 | Makes a fast GPU the bottleneck, so GPU costs show in frame time. | console |
These were tried and do not work in Shipping: stat gpu, stat scenerendering
(compiled out with STATS), csvprofile, startfpschart. HighResShot does
nothing.
Reading the numbers
- Warm-up. The first minutes after a map loads run slow while shaders,
pipeline states and textures arrive: Death Island read 12.6 ms a frame
right after loading and 8.1 ms steady. Never take a baseline in the first
3 minutes.
mjolnir_benchwarns when it is started earlier. - Game includes the GPU wait. At 50% resolution the Game figure fell from 8.4 to 5.2 ms with nothing else changed. In this build, stat unit's Game time includes the game thread waiting for the GPU, so it is not a pure CPU measure. Read GPU Time and Draw for where the work is.
- A fast GPU hides GPU costs. At 100% on PC 1 the frame is close to
CPU-bound, so a GPU saving barely moves it. Bench GPU work at
r.ScreenPercentage 200. - Draws and Prims miss instanced geometry. Hiding all 535,000 grass clumps changed Draws by about 140 and Prims not at all. Use frame time.
- PC 1's game thread runs at one of two speeds. PC 1 is a Ryzen 9
7950X3D. Coagulation at a held view read 9.1-9.5 ms in some sessions and
7.4-7.8 ms in others (2026-11-11), all of it the Game figure, GPU
unchanged. Pinning the running game to the V-Cache cores (0-15) read
9.48 ms; to the other cores (16-31), 7.61 ms. Windows picks per session
and can move the thread mid-session, so a comparison across sessions is
only valid on the same cores. Compare within one session (
mjolnir_benchdoes), or pin the game first:(Get-Process HaloCampaignEvolved) .ProcessorAffinity = [IntPtr][int64]4294901760for cores 16-31. - Alternate conditions with the baseline. Single
stat unitsnapshots vary by about ±0.5 ms.mjolnir_benchalternates base / condition / base over 6-second windows, and its baselines repeat within ±0.1 ms.
mjolnir_bench
Stand where you want to measure and type mjolnir_bench in the console. The
camera is held for about a minute while it takes turns (2.5 s to settle,
6 s timed):
bench on DTI: base 7.94 ms (126 fps), 4 runs from 7.91 to 7.96
bench on DTI: no foliage 6.42 ms -1.52 ms -19.2%
bench on DTI: no foliage shadows 7.29 ms -0.65 ms -8.2%
bench on DTI: no foliage wind 7.04 ms -0.90 ms -11.4%
(Death Island's beach camera, after the cull fix, 2026-10-17.)
Above each table, bench.log records the size actually drawn (the viewport,
not the saved resolution, which borderless ignores), window mode, vsync, every
sg.* quality level, r.ScreenPercentage, the GPU's name and score (from the
game's own Saved/GpuBenchmark.json) and the CPU. A player can send that
file, and the numbers can be compared with ours.
The bench runs on the HUD's frame hook. mjolnir_hitches off pauses that
hook, and the bench with it.
Where a frame goes
Each row also carries stat unit's split for its turns, averaged over every
timed frame, and bench.log records the held camera (view:):
bench on BGL: base 7.93 ms (126 fps), 4 runs from 7.20 to 9.86 [game 7.36, draw 2.97, rhit 4.48, gpu 5.70]
bench on BGL: no foliage 6.50 ms -1.43 ms -18.0% [game 5.97, draw 2.70, rhit 3.94, gpu 4.87]
(Blood Gulch at 1280x720 on PC 1 seconds after loading, 2026-10-18: a CPU-bound frame, GPU 5.7 ms of 7.9.)
A frame is as slow as the slowest of the game thread, the render thread (Draw)
and the GPU, so a cost that lands on the GPU saves nothing while the game
thread is the slow one. Game includes the game thread's wait for the GPU (see
above); the report also carries game_cp and draw_cp, the critical paths
without waits, and RHIT.
Nothing reflected holds these numbers, so MJOLNIRHud reads them through
native\mjolnir_frame_times.dll (native/frame_times, built in CI like the
other native halves). It finds FStatUnitData::DrawStat in the exe by a byte
pattern and decodes the engine globals that function reads
(GGameThreadTime, GRenderThreadTime, GRHIThreadTime, their critical
paths, and GDynamicRHI->RHIGetGPUFrameCycles(0)) from its RIP-relative loads.
They update every frame with stat unit off. After a game update that
changes DrawStat the pattern stops matching: the bench still runs, its rows
have no split, and bench.log says no frame times. After each game update
run python tools/pe/statunit_pattern.py "<Win64>/HaloCampaignEvolved.exe":
it says whether the pattern still matches once and, if not, prints a new one.
/bench and the hub
A player types /bench in match chat. It refuses in the first two minutes on
a map, then runs the same foliage bench at the player's own camera, prints
the result in their chat, and writes bench_<id>.json beside MJOLNIRHud,
named in the match_outbox.txt MJOLNIRLobby sends match records from:
Bench on DTI at 3840x2160: 64 fps (15.5 ms a frame).
Foliage costs 2.5 ms (16%): its shadows 0.5, its wind 1.3.
Sending it to the MJOLNIR team. Thanks!
From MJOLNIRHud 0.11.0 (PR #202), when mjolnir_frame_times.dll returned
the frame times, a line before the last gives the base's split:
Game thread <ms> ms, render thread <ms>, GPU <ms>.
MJOLNIRLobby posts it to POST /api/v1/benches with the launcher's key
(scope lobbies:write, as match reports), so any player signed in to the hub
through the launcher can send one. A hub that does not have the route yet
answers 404, which keeps the file for a later try. The hub stores the settings
line's fields with the sender's account (migrations/0021), and from MJOLNIRHud
0.11.0 the held camera and each condition's frame split (migrations/0022).
Only admins read them: the moderation page's Benchmarks tab
(/moderation#benchmarks) averages foliage runs by GPU, map, height drawn and
foliage quality, and lists recent runs with who sent each, which of game,
draw and GPU bound the frame, and where the camera stood; GET /admin/benches and
GET /admin/benches/summary serve the same data. A run taken in the first two
minutes on a map is kept but left out of the averages.
What was measured (Death Island)
At 3840x2160, Epic, by mjolnir_bench:
| View | Base | No foliage | Foliage shadows | Foliage wind |
|---|---|---|---|---|
| Beach camera | 14.5 ms (69 fps) | -2.54 ms (-17.5%) | -0.58 ms | -1.28 ms |
| Island overview | 14.8 ms (68 fps) | -2.69 ms (-18.1%) | -0.25 ms | -1.29 ms |
A 5090 holds under 70 fps at 4K on Death Island. By the ratio of GPU
throughput, a mid-range card at 1440p should be well below 60 with the foliage
on; players' /bench runs are where that gets measured rather than estimated.
The tables below are from the 1710x1073 runs.
ABAB, 6 s windows, after warm-up. "Grass" in these tables is every instanced mesh the loader scatters (grass, tufts, pebbles, shells, driftwood, tree leaves); grass and tufts are about 97% of the 535,000 instances.
Beach view (the DTI test camera), 100%:
| Condition | Frame | vs base |
|---|---|---|
| base | 8.1 ms | |
| no grass | 6.6 ms | -1.5 ms (-18%) |
| grass, no shadows | 7.4 ms | -0.7 ms |
| grass, no wind | 7.15 ms | -0.9 ms |
| 7,700 cladding rocks hidden | 7.8 ms | -0.3 ms |
Island overview, r.ScreenPercentage 200 (GPU-bound):
| Condition | Frame | vs base |
|---|---|---|
| base | 13.3 ms | |
| no grass | 10.8 ms | -2.5 ms (-19%) |
| grass, no wind | 12.0 ms | -1.25 ms |
| grass, no shadows | 13.15 ms | -0.15 ms |
| cull fix (below) | 13.2 ms | -0.1 ms |
wind only within 20 m (WorldPositionOffsetDisableDistance) | 13.26 ms | none |
What this says:
- Grass is a fifth of the frame, and almost all of it is GPU work. The render thread and RHI barely change without it (Draw 3.2 → 3.0 ms, RHIT 4.3 → 4.0 ms), so the number of components and draw calls is not the problem.
- The cost is geometry, not pixels. It stays about the same from 100% to 200% resolution. The meshes are Megascans grass at 570–1,650 triangles per clump (LOD0), with two LODs and no Nanite. A GPU with a fifth of a 5090's throughput pays roughly five times as much: 7–12 ms, which matches "slows down with the grass".
- Wind is half of the grass cost. World position offset makes every
clump go through the velocity pass and keeps shadow pages invalid. The
loader sets the "Rigid" shadow-cache mode, but swaying grass still costs.
WorldPositionOffsetDisableDistance(sway near the camera only) has no effect in this build. - The rocks are effectively free (-0.3 ms): the Uluwatu cliff meshes are Nanite.
- Keep virtual shadow maps.
mjolnir_bench r.Shadow.Virtual.Enable 0read +1.76 ms (+22%) at the beach view: the fallback shadow maps cost more.
Campaign against our maps (2026-10-18)
A player (RX 9060 XT, 2560x1440 at 58.8% screen percentage, Epic) reported
up to 240 fps in the campaign and about 51-58 fps on our maps, choppy. Their
/bench on Blood Gulch read 19.6 ms base, foliage 5.5 ms, of which wind was
5.2 ms. This section measures the campaign and both maps on PC 1 at one
set of settings, to see where that gap comes from.
Settings, every run: 1710x1073 borderless (Remote Desktop's display;
the bench camera letterboxed it to 1710x962, since fixed, see below), every sg.* at 3
(Epic), r.ScreenPercentage 100, vsync off, no fps limit, MJOLNIRHud
0.11.0 (stat unit split from mjolnir_frame_times.dll). The game's own
Frame Generation setting was on (bFrameGeneration=True), which does not
touch these numbers: the bench and stat unit read engine frame times, not
presented frames. Each map had more than 3 minutes to warm up first.
- Campaign: The Silent Cartographer (B30) at the user's checkpoint (Resume Solo Game), the beach beside the Warthog at (18930, -16518, 810).
- Blood Gulch:
mjolnir_auto host BGL slayer private, the spawn view at (9313, 27259, 226), grass and a tree in view. - Death Island:
mjolnir_auto host DTI slayer private. The spawn is indoors, so a CameraActor was set as the view target at the beach test camera (2323, -13154, 2784), which the bench then holds.
The table
From bench.log (each base is 4 alternated 6 s windows; the three bases per
map agree within 0.08 ms):
| Campaign (B30) | Blood Gulch | Death Island | |
|---|---|---|---|
| Base frame | 8.29-8.34 ms (120 fps) | 8.09-8.17 ms (123 fps) | 8.02-8.04 ms (124 fps) |
| Game / Draw / RHIT / GPU | 5.0 / 4.2 / 6.3 / 5.95 | 8.0 / 2.8 / 3.7 / 6.7 | 7.9 / 3.0 / 4.1 / 6.5 |
| Bound by | RHI thread | GPU (Game is waiting on it) | GPU |
r.ScreenPercentage 200 | 13.47 ms, GPU 11.65 | 12.87 ms, GPU 11.48 | 12.51 ms, GPU 10.99 |
r.ScreenPercentage 50 | 8.22 ms, GPU 4.31 | 6.86 ms, GPU 5.43 | 6.87 ms, GPU 5.38 |
| GPU: fixed + per megapixel | 3.8 ms + 1.19 ms/MP | 5.0 ms + 0.98 ms/MP | 5.0 ms + 0.91 ms/MP |
| GPU at the player's 1.27 MP | 5.3 ms | 6.3 ms | 6.2 ms |
stat unit Draws / Prims | 964 / 123K | 859 / 278K | 1,090 / 501K |
| Hitches, 3 min standing | 2, worst 22 ms, no Lua | 1, 78 ms: LevelLoader footprints 70 ms | 2, worst 158 ms: LevelLoader pulses 150 ms |
The fixed and per-megapixel GPU figures are a straight line through the 50% and 200% points (0.41 and 6.58 MP drawn); it predicts the 100% GPU time within 0.2 ms on all three.
What this says:
- At the same settings the campaign is not lighter. On PC 1 the three run within 0.3 ms of each other, and at 200% our maps cost slightly less GPU time than the campaign's beach. B30 is held back by its RHI thread (6.3 ms), ours by the GPU.
- Ours carry about 1.1 ms more GPU work that does not shrink with resolution (5.4 against 4.3 ms at 50%). That is the foliage: removing it saves 1.40 ms on Blood Gulch and 1.56 ms on Death Island, mostly GPU (6.7 → 5.1 ms on BGL).
- At the player's internal resolution our maps should cost about 17% more GPU time than the campaign, not 4 times. Their GPU reads 12.2-16.5 ms on Blood Gulch where PC 1's fit gives 6.3 ms at that resolution, so their card is about 2-2.6x slower here. B30's beach would then read about 10-14 ms, 70-100 fps of engine frames.
- So the 240 fps is most likely presented frames, not engine frames.
58.8% is an upscaler's Balanced preset, and the game has a Frame Generation
option (on, on this box). FSR frame generation doubles what an overlay
counts (140-200 fps from the estimate above);
/benchcounts engine frames. A lighter view (interiors) would add to it. This was not measured here: there is no presented-frame counter on PC 1, and the FSR path cannot run on an NVIDIA card. The DLSS one (r.Streamline.DLSSG.Enable 1) stays on in our maps.
The player's own benches
The player sent five Blood Gulch benches through /bench on 2026-10-18
(2560x1440 borderless at 58.824%, Epic, vsync off, no fps limit, RX 9060 XT,
gpuScore 521 against the 5090's 2060). The last two came from MJOLNIRHud
0.11.0, so they carry the held camera and the frame split:
| Sent (UTC) | Time in world | View | Base | Game / Draw / RHIT / GPU | No foliage | No foliage shadows | No foliage wind |
|---|---|---|---|---|---|---|---|
| 07:55 | 185 s | (22101, 38552, 554) yaw -36 | 17.72 ms (56 fps) | 1.5 / 1.7 / 1.8 / 16.5 | -4.16 ms | -2.67 ms | -3.67 ms |
| 08:02 | 569 s | (12199, 23602, 708) yaw 89 | 13.48 ms (74 fps) | 1.6 / 1.6 / 1.8 / 12.2 | -1.68 ms | -0.24 ms | -1.08 ms |
The three earlier runs (MJOLNIRHud 0.10.0, no split or camera) read 19.64, 8.19 and 17.27 ms bases, the first of them at 123 s in.
- Their frame is the GPU and nothing else. Game, Draw and RHIT are all
under 2 ms; the render thread's critical path (
draw_cp12.5 and 16.8 ms) is the GPU wait. On their PC the wait lands on the render thread, where on PC 1 it lands on Game. Any GPU saving shows in full in their frame time. - Foliage costs them 1.7-4.2 ms depending on where they stand, against 1.4-1.6 ms on PC 1. That is in line with a slower card, view by view.
- Wind is not out of proportion after all. Across their five runs, wind is 41-94% of the foliage cost (1.1 ms of 1.7 at the 08:02 view, 64%, close to PC 1's 60%). The first run's 95% (5.2 of 5.5 ms) was 123 s after loading, inside the warm-up. Their two 0.11.0 runs are 3-4 ms of wind at a grassy view and 1 ms at a plainer one: a large share of their frame, but not an AMD-only cost. Shadows vary as much, from 0.24 to 2.67 ms.
What costs what on our maps (PC 1, 1710x962)
| Rank | Cost | Saving when removed | How measured |
|---|---|---|---|
| 1 | Foliage (grass, tufts, leaves) | -1.40 ms BGL, -1.56 ms DTI (17-19%) | mjolnir_bench |
| of which wind | -0.95 ms on both | same | |
| of which shadows | -0.53 ms BGL, -0.71 ms DTI | same | |
| 2 | CE placed lights' shadows (DTI, outside a base, 6 lights at 12-37 m) | -0.75 ms all 20 shadows off; -0.25 ms at the engine's 25 m shadow distance instead of our 80 m | held camera, two bases 1 min apart; mjolnir_bench r.LightMaxShadowDistanceScale 0.3125 |
| 3 | Fluid Flux coast (DTI beach) | at most -0.38 ms (GPU 6.48 → 6.16) | held camera, two bases 1 min apart, the sea not drawn at all, so an upper bound |
- The lights cost nothing at the beach, 90-190 m from any of them
(
r.LightMaxShadowDistanceScale 0.3125read +0.02 ms there): only views near a base pay. - Keep virtual shadow maps:
r.Shadow.Virtual.Enable 0read +3.04 ms (+37%) on Blood Gulch, as it did on Death Island (+1.76 ms). - Rows 2 and 3 are two bases taken a minute apart with the light shadows or the Flux actors (domain, surface, wave) switched by Lua between them, not the bench's alternated turns; the baselines repeat within 0.1 ms, so the sign and size hold, the second decimal does not.
Choppy: what the hitches show
Hitch counts come from mjolnir_hitches reset windows with nothing else
running. A bench makes its own hitches (a 200 ms frame each time it switches
a condition, on every map, the campaign included), so its minutes are left
out.
- Standing still, the worst frames on our maps are our own Lua. The
campaign's worst in 3 minutes was 22 ms. Blood Gulch's one hitch was
LevelLoader footprintsat 70 ms and Death Island's worst wasLevelLoader pulsesat 150 ms. The same session's log also hasLevelLoader weatherat 53 ms and footprints at 82 and 91 ms. Acrosshitches.log(all sessions since the logger shipped),Hud tickreached 95 ms. Most hitches name none of our loops, but every 50-150 ms frame in today's quiet windows does. - No first-sight stalls on a warm cache. Two passes of a teleport tour over eight Death Island views (bases, the overview, both shores) read 15 hitches, worst 26 ms, then 9, worst 27 ms. The same teleports hitched on both passes, so they are camera cuts, not new pipeline states. PC 1 has played these maps many times, so its driver shader cache is warm. A first run on a new PC, or after a driver update, is untested, so runtime PSO compiles of our cooked materials (chunks 983/990) are neither confirmed nor ruled out.
Recommended fixes (none made in this session)
| Fix | Expected saving |
|---|---|
Wind off at High/Epic on slower GPUs (by gpuScore) | 0.95 ms here (12%); 1.1-3.7 ms of the player's 13.5-17.7 ms (8-21%) |
Lua spike budgets: split pulses, footprints, weather and the Hud tick so no run takes more than a few ms | removes the 50-150 ms frames, the only large hitches standing still |
| A foliage density and cull pass on Epic | part of the remaining 0.45-0.6 ms of foliage outside wind; more on slower GPUs |
Placed lights: shadow_distance back toward 2500-4000, or no shadows on small fill lights | 0.25-0.75 ms near bases |
Flux coast: lower res or update rate | under 0.38 ms; last |
Update 2026-10-21: the Lua row is superseded. The long runs were the Lua collector finishing a cycle, not the loops' own work, and the generational collector, one shared hit-result table and garbage-free pulses removed them (MJOLNIRLevelLoader 0.7.3, MJOLNIRHud 0.11.1, mods-v0.30.0, PR #206): see "Lua garbage collection hitches" below.
For the tools:
- Fixed in MJOLNIRHud 0.11.3 (mods-v0.31.1): the bench camera letterboxed non-16:9
windows.
lockViewspawned a CameraActor withbConstrainAspectRatioon, so on 1710x1073 every bench drew 1710x962. Comparisons on one PC hold; a 16:10 player's absolute numbers read about 10% light. The held camera now turns the constraint off and takes the player camera's FOV (checked at 1280x800 on Blood Gulch, 2026-10-18: full frame, FOV 85 on both). - Ask the player whether Frame Generation is on, and what their overlay
counts. A campaign-side bench players can run (
/benchlives in match chat) would let the hub compare their campaign and our maps directly. - A cold-cache run (a new PC, or after clearing the driver's shader
cache) with
mjolnir_hitcheswhile walking, to settle the PSO question.
Changes from this investigation
- Grass that never culled (MJOLNIRLevelLoader). UE4SS passes a
fractional Lua number to an
int32parameter as 0, and an end cull distance of 0 means never cull. Foliage bands whose distance worked out to a fraction (5000 + 7000 × 1/3 = 7333.3) were drawn across the whole map: 26 of Death Island's 245 grass components, 51,000 clumps, mostly the 1,657-triangle groundcover. The lower foliage qualities multiply distances by 0.45–0.8, which made more bands fractional, so the setting meant to help weak PCs made this worse. Distances are now whole centimetres. After the fix, 0 of 245 components are uncullable. - No wind at Low and Medium foliage quality (
Foliage.QUALITY.still): -9% of GPU frame time on the overview. High and Epic are unchanged. It covers every foliage group, trees' leaf clusters included. At Medium, the beach bench now reads base 6.86 ms, no foliage -0.38 ms, no foliage wind +0.03 ms. The loader'sfoliage:log line saysstillwhen it applies. - Dry zones loop (MJOLNIRLevelLoader): looked up the GameplayStatics CDO and built a name string every 100 ms, 12–13 ms of game thread per second. It now reads the camera through the cached controller and compares by address.
- Tooling:
mjolnir_bench, and the settings line inhitches.log.
Questions this answers
Would baking the grass and walls into the paks help? Not the frame
rate. An instance renders the same whether it comes from a cooked level or
from AddInstance at load. Baking would save the 6 s foliage spawn and part
of the 14–16 s dressing, at the cost of a per-map cook pipeline, which has been
fragile for this fork (ue_mesh_write.md: stock-UE cooks
do not load). It is worth doing for load time, not for "slow with grass".
Done for Death Island on 2026-10-18 (see "Baked foliage" below): the load
frame went from 15.5 s to 9.1 s, the frame rate is unchanged. With the
scenery baked and a faster asset lookup it is 0.9 s.
Nanite? The rocks already are, and they cost almost nothing. The grass is not, and we cannot rebuild the game's meshes as Nanite. Nanite foliage with world position offset is expensive in UE 5.5 anyway. The grass levers are fewer clumps, shorter cull distances, and wind.
Is our Lua slow? Mostly no. The hitch log names every loop that reads 1 ms or more. Apart from the dry zones loop above and the lobby's main-menu watch (10–21 ms every 1.5 s at the menu only), long frames show "none of our timed loops". The frame budget is in the GPU. The occasional 50–200 ms Lua run was the garbage collector, not any loop: see below.
Lua garbage collection hitches (2026-10-18)
A player said our maps feel choppy. With the player standing still on Death
Island, the only 50–150 ms frames that the campaign does not have came from
our Lua, per the hitch log: LevelLoader pulses 150 ms, LevelLoader footprints 70–91 ms, LevelLoader weather 53 ms, and Hud tick 7–9 ms
every few seconds. None of those loops does that much work. Death Island
has no weather, so the weather loop returns in its first lines there, and
the pulses loop sets 25 material parameters. Each long run was the Lua
collector finishing a cycle inside whichever loop allocated next.
How that was found (a temporary PROF log of each slow run with the Lua
heap before and after, and probes run inside the mod's own Lua state):
- Every long run shrank the heap.
footprints 55 ms, heap 95.8 → 94.0 MB;pulses 29 ms, heap 108 → 93 MB. The HUD's 4–6 ms ticks came every ~15 s, each halving its heap (10 → 5 MB). - LevelLoader made ~240 KB of garbage a second, ~200 KB of it the 25 Hz
pulses: a
getWorld()(~1.5 KB of object handles) and aSetScalarParameterValuemethod lookup per flare (~250 bytes each, 25 flares). The HUD made ~350 KB a second on a live set of 0.5 MB. - UE4SS keeps every out-parameter table.
K2_SetActorTransform(t, false, {}, true)hands UE4SS a fresh{}for the sweep hit result, and UE4SS keeps a registry reference to it for good: 7,733FHitResulttables (8 tables and 5 userdata each, 62,000 tables in all) were live after Death Island loaded, most from the cladding rocks. That was most of the loader's live set, marked again on every cycle. Passingnilor leaving the argument out is an error. - A full collection of the loader's state took 112–183 ms, scaling with the garbage swept and the finalizers of the dead handles run. A cycle with no garbage, stepped one increment at a time, cost 33 ms in all with a 10 ms worst step.
- A smaller incremental step size did not help. At 1 KB (from 8 KB) the heap ran to 231 MB and one step then freed 62 MB in 205 ms.
The changes (MJOLNIRLevelLoader 0.7.3, MJOLNIRHud 0.11.1):
- Both mods run the collector in generational mode (UE4SS ships Lua 5.4.7). The loader takes young collections at 5% of the heap: at the default 20% each one was an 11 ms run every ~97 s.
- Every hit-result out parameter in the loader gets one shared table
(
Current.hit); the footprint canvas draws reuse their three. - The pulses keep each instance's setter (UE4SS returns a function bound
to the object it was read from) and the world the level was furnished in
(
Current.world): no garbage per flare. - Moving sounds read the time through the library the pulses keep, not a
GameplayStaticsStaticFindObject (~1 ms) every 100 ms, and move a part only when it moved. Weather copies follow the camera once it has moved half a metre.
Before and after, Death Island, standing still, PC 1, 1280x720 windowed,
mjolnir_auto host DTI slayer private, mjolnir_hitches reset, then
3–6 minutes (the "Lua on DTI so far" line). "After" is two windows, 6:16 and
3:18, with the final code:
| Loop | Before (worst) | After (worst) |
|---|---|---|
| LevelLoader pulses | 39 ms (150 ms earlier the same day) | 1–2 ms |
| LevelLoader footprints | 55 ms (70–91 ms earlier) | 2–3 ms |
| LevelLoader weather | 53 ms earlier | 1 ms |
| LevelLoader dry zones | 5 ms | 2 ms |
| Hud tick | 6 ms (7–9 ms earlier) | 1–2 ms |
| Worst frame in the window | 54 ms | 17 ms, no hitches |
The loader now makes ~36 KB of garbage a second. The other frames over 50 ms on Death Island name none of our loops: the first seconds after the map loads, and GPU work.
Baked foliage (2026-10-18)
Death Island's grass, ground cover, pebbles, shells, driftwood, the swapped trees' leaf clusters (534,835 clumps) and its 7,696 cliff cladding rocks, all 75 foliage groups, are now cooked into its landscape world instead of spawned by the loader.
How it works:
bake_foliage: trueon a map intools/level/ce_upgrade_maps.json. The editor stage runstools/level/foliage_bake.py, which writes the spec: the foliage file with the leaf clusters appended (as assemble appends them, so group numbers match the level file), each group's mesh, bands, cull and flags, and a stand-in per game mesh.- Stand-ins. The world names the game's own meshes (
/Game/Env/...,/Game/Megascans/...). Each gets an editor-only box of the game mesh's bounds with its slots (read withmjolnir ue get), never cooked (DirectoriesToNeverCook). The cook builds each component's cluster tree and cached bounds from the mesh's bounds, so the box has to match. In game the reference resolves to the game's mesh, the same trick as the deformation MPC. Scripts/build_ce_landscape.pycallsMjolnirUIBuilderLibrary.BakeFoliage(C++), which reads foliage.bin and places the clumps exactly asFoliage.spawndoes: same rotation, the same deal into bands, the same whole-centimetre cull distances, Rigid shadow caching, no collision. It takes half a second in the editor.- Foliage quality. Grassy groups are dealt once more into four tiers (3,
1, 2 and 6 clumps in 12). The loader hides the tiers above the quality:
tier 0 at Low, 0–1 at Medium, 0–2 at High. That is the old keep-1-in-4/3/2.
The engine's own density scaling would not do: the game's scalability sets
foliage.DensityScale0 at Low, which clears every instance at load. - The loader (MJOLNIRLevelLoader 0.7.5; it first shipped as 0.7.6, in
mods-v0.31.0): assemble marks the level file's
foliage
bakedand writescentre, the clumps' mean position for the wind flowmap.Foliage.spawnthen skips the baked groups andFoliage.dressBakeddoes one pass over theMJFol_<group>_<band>_<tier>components: tints and material overrides (the same dynamic instances as before), cull scaled by quality, wind off whenstill, tiers hidden.mjolnir_foliage offhides them. The pass resets each mesh to its own materials first, or a reload tinted the last load's tinted instances and the grass went dark grey. - Cladding rocks are mesh actors,
MJClad_<group>_<rock>, not instances: our cliff materials drew black on instanced meshes in this game. Each carries whatFoliage.spawnCladdinggave it: the CE light under it as custom primitive data 0-2, no collision, out of Lumen's bounce. Since 2026-11-16 each light group's material is cooked too (tools/level/clad_materials.py): one MaterialInstanceConstant a group, made by the editor stage with the valuesLand.cliffsused to set, set on the group's rocks when the world bakes them, and cooked into the landscape's chunk; the game's Megascans textures it names are never-cooked stand-ins at their paths. Assemble recomputes the values from the finished level and stops the build when they differ. The loader leaves a group as baked when its first rock wears the material the level'slandscape.cladnames and the light scale and lightmap levels are the ones it was made with; otherwise (an older world,mjolnir_light_scale) it builds the dynamic instance as before. Ascension's 40,390 rocks took 0.5 s of Lua at every load before; its load went from 2.3 to 1.6 s solo and 3.5 to 2.6 s on a client (the hub copy without the remaster: 0.7 and 2.3 s). - Everything baked is tagged
FluxHide, as the loader tags its own actors, so Flux's ground capture does not see it. - What the world carries decides, not the level file. The launcher copies
the hub's
level.jsonintoMJOLNIRMaps/<CODE>on every launch and leaves installed containers alone. With the old rule (spawn unless the level saysbaked), a baked world under the hub's level file got every clump and rock a second time: trees with a second, swaying copy of their leaves (no calm settings) and rocks flickering inside each other. On a map with a landscape world the loader now looks forMJFol_*andMJClad_*first and spawns only the groups the world does not carry, whatever the level file says. Tested with the hub's level file over the baked world (nothing spawned twice), and with a baked level file over an unbaked world (rocks spawned). - MJOLNIRHud's
mjolnir_benchnow measures every visible instanced mesh, so it covers baked foliage too (MJOLNIRHud 0.11.2).
Before and after, PC 1 (RTX 5090), 3840x2160 borderless, Epic, same procedure:
fresh launch, Enter once, mjolnir_auto host DTI slayer private.
Grass and ground cover first (rocks still spawned by the loader):
| Runtime (before) | Baked (after) | |
|---|---|---|
foliage: line | 6.1 s (6.2 s on a second load) | 1.5 s (the cladding rocks and the dressing pass) |
| Long load frame | 15.5 s (15.3 s) | 10.7 s (10.8 s at Low) |
| Instanced meshes | 245 | 788 (245 drawn at Low) |
| Clumps drawn, Epic / Low | 534,835 / 161,520 | 534,835 / 161,581 |
| LevelLoader Lua heap, live (two full collections) | 5.3 MB | 5.2 MB |
| Actor handles the loader holds | 8,581 | 8,524 |
| 5 min standing, median / p95 / p99 | 13 / 14 / 15 ms | 12 / 13 / 14 ms |
| Hitches in those 5 min (under 50 / 50-100 / 100-250 ms) | 28 (6 / 15 / 7) | 30 (12 / 13 / 5) |
| Lua in those 5 min (worst loop) | Hud tick 2 ms | Hud tick 3 ms |
mjolnir_bench at the test camera: base | 16.42 ms | 15.53 ms |
| no foliage / foliage cost | 13.80 / 2.62 ms | 13.20 / 2.33 ms |
| foliage wind / shadows | 1.33 / 0.59 ms | 0.90 / 0.49 ms |
What this says:
- Load: 4.6–4.8 s off the load frame. The foliage step went from 6.1 s to 1.5 s, and what was left of it was the 7,696 cladding actors.
- Heap: no real change. Since the generational GC and the shared out-parameter table (PR #206) the loader's live heap is 5 MB either way. The handles it holds are the cladding rocks and the decor; only 57 actor handles went.
- Frame rate: no regression. The two benches came from two launches. The no-foliage frame also differs by 0.6 ms between them, so the baked build reading 0.3 ms less for foliage is within launch-to-launch noise. The extra components (788 against 245, from the tiers) did not raise Draw or RHIT. The two 5-minute windows spawned at different points, so their medians are not a like-for-like comparison either.
- Looks the same. At the test camera the mean pixel difference from the runtime shot is 1.7/255 (1.2 over the grass), with the same mean grass colour; what differs is waves and clouds. Low thins it as before.
Then the cladding rocks too (all 75 groups baked), same procedure:
| Rocks spawned (grass baked) | Everything baked | |
|---|---|---|
foliage: line | 1.5 s | 0.2 s |
| Long load frame | 10.7 s (9.8 s on another launch) | 9.1 s |
| LevelLoader Lua heap, live | 5.2 MB | 2.5 MB |
| Actor handles the loader holds | 8,524 | 828 |
| 5 min at the test camera, median / p95 / worst | 16 / 17 / 21 ms, no hitches | |
mjolnir_bench at the test camera: base / foliage cost | 15.53 / 2.33 ms | 16.39 / 2.61 ms |
- Load: another 1.3 s. From the first runtime build, Death Island's load frame went from 15.5 s to 9.1 s, and the foliage step from 6.1 s to 0.2 s.
- Heap halved, handles down by 90%. The loader no longer holds a handle per rock. What it holds now is the decor (790 pieces) and its own actors.
- Frame rate unchanged. The bench base moved by 0.9 ms between launches (15.53 to 16.39) with the same foliage on screen, and the runtime build read 16.42. That is launch-to-launch noise, not the bake.
- Rocks look the same. At a camera close to a cluster of 122 rocks, (-9309, -12608, 5046), pitch -14.9, yaw -123.2, the mean pixel difference between spawned and baked rocks is 0.24/255.
Then the swapped B30 scenery (760 tree and rock pieces), and a faster asset lookup in the loader, same procedure:
| Rocks baked | Scenery baked too | And the faster lookup | |
|---|---|---|---|
| Decor step (CE terrain, flares, scenery) | 7.1 s | 4.1 s | 0.3 s |
| CE terrain's 94 materials | 2.9 s | 3.1 s | 0.25 s |
| LevelLoader tick (the load frame) | 9.2 s | 6.3 s | 0.9 s |
| LevelLoader Lua heap, live | 2.5 MB | 2.3 MB | 2.3 MB |
| Actor handles the loader holds | 828 | 68 | 68 |
mjolnir_bench base at the test camera | 16.39 ms | 16.33 ms |
- Scenery is baked as
MJDecor_<id>mesh actors (BakeDecor). The loader finds them with oneFindAllOf, gives the 736 tree pieces their calm wind values (scalars) and keeps no handle. Two things had to be matched:- Rotation. UE4SS does not give an actor spawned from Lua the rotation
it was asked for: pitch alone comes out negated, and mixed angles compose
differently (one term of the quaternion's Y has its sign turned; fitted
to seven probes). The first bake copied that, to match. But a tilted
tree is 20 to 60 pieces, each turned about its own pivot, and turned
wrong they stood apart: the user found a Death Island tree with a gap in
its trunk, and the loader's copy had it too.
BakeDecornow uses the rotation the level file asks for, and the loader sets it exactly after spawning (K2_SetActorRotation), which fixes the swapped trees on Battle Creek and Infinity as well. A piece with no pitch was never affected. - Numbered names. 147 tree meshes are named like
SM_..._Big_6, which Unreal stores asSM_..._Bigplus a number. The editor'screate_assetlost the number (every stand-in became oneSM_..._Big;CreateStandInMeshmakes them by full path now).mjolnir level bakehashed the world's imported package names without their numbers too, so the world asked forSM_..._Bigand every numbered piece drew nothing (fixed incrates/blam-cli/src/level.rs).
- Rotation. UE4SS does not give an actor spawned from Lua the rotation
it was asked for: pitch alone comes out negated, and mixed angles compose
differently (one term of the quaternion's Y has its sign turned; fitted
to seven probes). The first bake copied that, to match. But a tilted
tree is 20 to 60 pieces, each turned about its own pivot, and turned
wrong they stood apart: the user found a Death Island tree with a gap in
its trunk, and the loader's copy had it too.
- The terrain's 3 s was asset lookups, not materials. A spike timed the
terrain's 94 materials: making them, setting their parameters and
assigning them took 0.01 s; resolving their 124 textures took 2.8 s.
UE4SS's
StaticFindObjectcosts ~21 ms a path in this build, loaded or not, and the loader called it first for every asset. A soft-pathLoadAsset_Blockingreturns an object already in memory in ~0.03 ms and loads one in ~1 ms, soresolveMeshnow tries that first. It speeds up every converted map, baked or not: Blood Gulch, nothing baked, went from 8.6 s to 4.3 s on the same launch procedure. The terrain's materials did not need baking after all.
Death Island overall, from the first runtime build: the loader's load frame went from 15.5 s to 0.9 s, its live heap from 5.3 MB to 2.3 MB, the handles it holds from 8,581 to 68, at the same frame rate and look.
What is left
-
Bake the other remastered maps (
bake_foliageper map, a full editor, cook, bake, assemble run each). Update 2026-10-21:bake_foliageis on for every remastered map with a landscape world intools/level/ce_upgrade_maps.json(BGL, DTI, YOY, ICE, SDW, TMB, INF, GPH, BCK, DCN; d5719b82, PR #208). Rat Race isindoor, with no landscape world to bake into. -
Other
StaticFindObjectcalls. The loader still calls it (throughfindObject) for classes and default objects in about 50 places; most run once a load. Any in a loop that runs often is worth the same treatment. -
The HUD's first tick of a match holds the game thread 68–77 ms once (hooking incidents, making the widgets, the first name-tag sweep). It is one frame at the start, not a beat, so it was left for now.
-
Measure weaker PCs. Every number above is from a 5090, apart from one player's RX 9060 XT benches.
/benchon PC 2, and from players, fills the Benchmarks tab with real hardware. -
Pick the foliage tier from the GPU.
sg.FoliageQualityonly helps players who open Video settings.Saved/GpuBenchmark.jsonhas agpuScore(2060 on the 5090), and every bench report carries it with the foliage cost. Once the Benchmarks tab holds a few cards, the loader can choosekeep/cull/stillfrom the score; picking thresholds before that would be a guess. -
Fewer, cheaper clumps on Epic. Death Island has 535,000. The
bandsand cull ranges (100–300 m for grass) were chosen for looks. A density or range pass, checked withmjolnir_benchand screenshots, is the biggest remaining lever. -
Hitch summaries from players.
/benchcovers the steady frame rate; the hitch log's per-map summary (median, p95, hitches) could go the same way, opt-in. -
Two leads the tools should catch: the user's own Blood Gulch session had bursts of 15–25 ms frames with no Lua in them, and ended in a GPU crash (device lost) after 39 minutes. Process memory read 13–16 GB in
stat uniton Death Island.