Marmoset Toolbag 5.03 shipped August 5, 2026, and the two changes that matter for game-ready GLB texturing are a Scatter layer that stamps wear directly onto a bake, and physical light units that make Toolbag's preview match what Unity, Unreal, and Godot actually render. If you bake normal and AO maps in Toolbag before exporting a GLB, both change how close your preview gets to the in-engine result.
What changed in Toolbag 5.03
The release adds four things worth tracking: a Scatter layer type, Text mode for Vector layers, Layer Caching, and IES light support with physical units. Layer Caching is the headline number — Marmoset reports roughly 2.7x faster compositing on complex projects by skipping redundant layer recalculation. The rest of the release is bug fixes: a Tile Strip normal-map artifact in Vector layers, a crash saving objects or USD files to the library with invalid names, duplicate texture resources on USD export when File References is set to Keep Paths, UDIM tiles not exporting from Texture Projects with USD files, camera types resetting in the Setup Workspace on scene load, and Texture Projects holding stale UVs after a mesh reload — the last one is the one that quietly corrupts a bake without throwing an error, so it's the fix worth knowing about even if you skip the rest of the changelog.
The Scatter layer replaces manual detail passes
Scatter reuses Toolbag's existing brush preset system, but instead of one stamp per click it distributes elements across a mesh using random or grid placement, and it works in 3D, UV, or Decal projection space. Rust freckles, bullet scoring, moss patches, bolt heads — anything you'd normally hand-place stamp by stamp — now gets laid down as a repeatable, editable layer instead of a baked-in one-shot.
That matters for a game-ready pipeline specifically because it's non-destructive. If a client or a lead asks for "50% less rust," you're adjusting a scatter density slider, not repainting a 4K texture from a saved PSD. On a heavily worn asset like a scavenged vehicle or armor set, that's the difference between a five-minute revision and starting the bake over. BitSoul's Wasteland Mercenary is the kind of asset where this shows up immediately — heavy edge wear across armor plating is exactly the scatter-in-UV-space use case, and it's a useful reference mesh if you want to test the layer against real game topology before touching your own files. A free account's two monthly downloads cover evaluation; commercial use is included with paid memberships (see pricing).
Physical light units close the preview-to-engine gap
Before 5.03, Toolbag's lights used arbitrary intensity values with no fixed relationship to a real-world unit, which is exactly why a "hero" render in Toolbag could look overexposed or flat once the same PBR texture set landed inside Unity's URP or Unreal's Lumen. IES light profiles and physical units fix the reference point.
| Light type | Unit before 5.03 | Physical unit in 5.03 |
|---|---|---|
| Omni | Arbitrary intensity | Lumens |
| Spot | Arbitrary intensity | Lumens |
| Directional | Arbitrary intensity | Lux |
This isn't cosmetic. Lumens and lux are the same units most modern engine light components expose, so you can now set a Toolbag directional light to roughly the lux value of your engine's sun and get a preview that's honest about how a metallic-roughness texture set will actually read once it's lit by someone else's renderer. If you're validating a bake before export, cross-checking the result inside BitSoul's 3D Studio — free, runs in-browser on your own GPU — gives you a second, engine-agnostic look at material response without opening a full game engine project.
Four fixes worth knowing before you upgrade
The stale-UV bug is the one to care about: if you reload a mesh mid-project, the Texture Project could keep the old UV layout, so your bake and your texture silently fall out of sync — no error, just wrong output that looks fine until you inspect it closely. 5.03 fixes it, which alone justifies updating if you iterate on meshes while texturing rather than finalizing geometry first.
The other three are narrower. Tile Strip mode in Vector layers was producing normal-map artifacts on translation — relevant if you build tiling trims or greebles procedurally. USD export was duplicating texture resources when File References was set to Keep Paths, and UDIM tiles weren't exporting from Texture Projects saved as USD at all — both matter if your pipeline round-trips through USD rather than going straight to GLB. And the Setup Workspace was resetting camera types on scene load, a minor annoyance unless you're doing turntable renders for a marketplace listing and re-loading scenes constantly.
None of these are exotic edge cases. The stale-UV issue in particular is the kind of bug that produces a texture set that passes a visual check in Toolbag and then looks subtly wrong once it's actually mapped onto the exported GLB — worth a spot-check on any project you built in 5.00 through 5.02 before you ship the bakes.
If you're validating texture compression choices for the export itself rather than the bake, see how KTX2 textures load across engines and how to catch texture stretching before it ships — both are the next step after a clean Toolbag bake, not a replacement for one.
---
*This post is part of the Ultimate Guide to Free 3D Game Assets — BitSoul's complete reference for formats, texturing, rigging, optimization, and engine integration.*