Project Versions

The mapping toolchain is split into three parts, each with its own version number. You can see all three in the VHMap setup window.

Component	Current Version	Where it lives
VHMap plugin	1.0.25	Plugins/VHMap/VHMap.uplugin
VHOLUME bridge	1.0.3	Plugins/VHOLUME/VHOLUME.uplugin
Mapping project	1.0.14	Config/DefaultGame.ini

When reporting a bug, include all three versions so we can reproduce your exact setup.

Check for an update before starting a new map

Downloading a fresh mapping project and starting your map there gets you everything the release contains.

You can also update the project you already have: copy Plugins/VHMap and Plugins/VHOLUME out of the new zip over the ones in your project, leaving your own map folders alone. VHMap will offer to rebuild the base release next time you pack.

That brings the tools and the actors across, but not anything a release adds to the project itself, such as new template content. Those have to be copied over by hand.

Changelog

1.0.14

Released: 2026-08-19

Component	Version
VHMap plugin	1.0.25
VHOLUME bridge	1.0.3
Mapping project	1.0.14

Starter assets. Content/VHStarter now holds four blockout meshes, a base material with concrete and metal instances, and their textures. Use them freely -- VHMap packs the ones your map uses into your .pak.

Want to import them yourself? Grab the source meshes and textures.

• Mapping project -- Bumped to 1.0.14 and added Content/VHStarter.

1.0.13

Released: 2026-08-18

Component	Version
VHMap plugin	1.0.25
VHOLUME bridge	1.0.3
Mapping project	1.0.13

Workshop images over 1 MB are caught before they break your upload. The 1 MB limit is per file, and Steam rejects the whole upload with ERROR 25 without saying which image was at fault. VHMap now names it and stops before the cook.

Importing meshes as GLB no longer blocks packing. Unreal imports GLB differently from FBX, and VHMap was pulling its import-settings assets into your map, where the content check refused them. Update and pack again -- nothing needs re-importing.

• VHMap 1.0.24 -- Oversized Workshop images are rejected at the image picker, at Pack & Publish, and in the game's upload window, each naming the file and its size.
• VHMap 1.0.25 -- GLB/glTF imports no longer drag Unreal's import-settings assets into your map plugin.
• VHMap 1.0.25 -- MetaSounds pack as map content.
• Mapping project -- Bumped to 1.0.13 and refreshed the bundled plugins.

1.0.11

Released: 2026-08-16

Component	Version
VHMap plugin	1.0.23
VHOLUME bridge	1.0.3
Mapping project	1.0.11

Niagara effects can go in a map now. Placing a Niagara system used to stop your map from packing. Niagara is accepted now, along with fifteen other asset types that were being refused for the same reason.

Needs VHOLUME 1.0.1.274 or newer for proper support.

• VHMap 1.0.23 -- Niagara systems and emitters pack as map content.
• VHMap 1.0.23 -- Skeletal meshes actually work now. They were already listed as allowed, but every skeletal mesh brings a Skeleton asset with it and that was refused, so packing failed anyway. Skeletons, physics assets and animation sequences are all accepted. An animated prop needs no Blueprint: place a Skeletal Mesh Actor and set its animation mode to use an animation asset.
• VHMap 1.0.23 -- Also accepted: material functions, material parameter collections, physical materials, sound attenuation, sound concurrency, reverb effects, float/vector/colour curves, texture arrays, volume textures, IES light profiles, and foliage types. Sound attenuation in particular means your audio can finally be positioned in 3D.
• VHMap 1.0.23 -- Still not supported, and packing stops if your map contains them: Blueprints, widget blueprints, animation blueprints, Level Sequences and data assets. The message you get when that happens now says what is unsupported and what to do, instead of offering an export that would not have loaded in game.
• Mapping project -- Bumped to 1.0.11 and refreshed the bundled plugins.

1.0.10

Released: 2026-08-12

Component	Version
VHMap plugin	1.0.21
VHOLUME bridge	1.0.3
Mapping project	1.0.10

If you build with the modeling tools, update. Meshes made with Cube Grid and the other modeling tools could be missing from your packed map, with nothing reported. They were in your level and absent from the pak.

• VHMap 1.0.21 -- Anything in your map's folder that has not been saved is now written to disk before packing. The modeling tools leave their output unsaved under Maps/_GENERATED/, and packing reads files rather than what is open in the editor, so that work never reached the pak. This also covers assets you have edited but not saved since.
• Mapping project -- Bumped to 1.0.10 and refreshed the bundled plugins.

1.0.9

Released: 2026-08-12

Component	Version
VHMap plugin	1.0.20
VHOLUME bridge	1.0.3
Mapping project	1.0.9

VHMap now tells you when a new mapping project is out. Nothing updates itself, so until now the only way to find out was to come and look at this page.

• VHMap 1.0.20 -- A notice appears in the setup window when a newer mapping project is published, with a link straight to the download page. There is also VHMap > Check for Update... if you want to ask. It shows which parts changed, and says so explicitly when the update includes a new VHOLUME bridge, because that means your base release needs rebuilding.
• VHMap 1.0.20 -- The check is silent when it cannot reach the site, so working offline is unaffected. It never blocks anything and never asks twice in one session.
• VHMap 1.0.20 -- Opening DefaultMapTemplate now offers to open one of your own maps instead, rather than offering to save work you have not done yet. Saving into it still offers to move your work out, which is the point at which there is something to move.

1.0.8

Released: 2026-08-12

Component	Version
VHMap plugin	1.0.19
VHOLUME bridge	1.0.3
Mapping project	1.0.8

If you have been building in DefaultMapTemplate, VHMap will now tell you. That level belongs to the toolkit, not to you: it cannot be packed, and its folder is replaced every time you update.

• VHMap 1.0.19 -- Opening or saving a level inside the VHOLUME folder now warns you, and offers to save what you have built into a map of your own. Nothing is moved without you asking.
• VHMap 1.0.19 -- Play, Pack and Share Map now refuse that level outright, instead of packing the toolkit and reporting your own meshes and textures as content from outside the map.
• VHMap 1.0.19 -- Fixed packing failing with "the file on disk does not reflect it -- N asset(s) would have been left out" on a map that was in fact correct. Any asset whose name ended in a number without a leading zero (T_Concrete_Plates_171, but not SM_Wall_005) could trigger it once it was pulled in from outside your map's folder. If you renamed an asset to work around this, you can rename it back.
• Mapping project -- Bumped to 1.0.8 and refreshed the bundled plugins.

1.0.7

Released: 2026-08-12

Component	Version
VHMap plugin	1.0.18
VHOLUME bridge	1.0.3
Mapping project	1.0.7

New maps now look like the game. Until now the default template had no post process volume, so the game fell back to engine defaults and custom maps looked flatter and brighter than the official ones. Existing maps are unaffected until you add a volume yourself.

• VHOLUME bridge 1.0.3 -- The default map template now ships with a Post Process Volume, carrying the same preset the official maps use: tuned bloom, exposure, ambient occlusion, contrast and film response, with motion blur off. It is unbound, so it applies to your whole level no matter where the player is, and its box size does not matter.
• VHOLUME bridge 1.0.3 -- That volume also turns Lumen global illumination and Lumen reflections off, which is the single biggest performance win available to a custom map. You lose bounce lighting and reflections; the template's directional light and sky light still light the scene. Turn them back on in the volume's details panel if your map needs them, and expect to pay for it in frame rate.
• Keep the Main tag. The game picks your map's post process volume by that tag. If you add a second volume, tag the one you want the game to read as Main, or it will pick whichever it finds first. Deleting the volume entirely is allowed and puts you back on engine defaults.
• Mapping project -- Bumped to 1.0.7 and refreshed the bundled plugins.

1.0.6

Released: 2026-08-11

Component	Version
VHMap plugin	1.0.18
VHOLUME bridge	1.0.2
Mapping project	1.0.6

If you are on 1.0.4 or 1.0.5, update. Those versions could pack a map that loaded and then crashed on the first frame, at random -- the same map, packed twice, could give you one working pak and one broken one. Nothing you did caused it and nothing in the map was wrong.

• VHMap 1.0.18 -- Packing is now deterministic. The map cook no longer reuses previous cook output, and every texture and mesh finishes building before the cook reads it. Packing takes longer than it used to; that is the fix, not a regression.
• VHMap 1.0.18 -- VHMap now records which plugin versions your base release was built against, and stops you packing against one that is out of date. Updating the VHOLUME bridge changes content that lives in the base release, so a base release built before the update produces a map that can crash on load. You will be offered a rebuild when it matters. Expect this prompt once after updating, then not again.
• Mapping project -- Bumped to 1.0.6 and refreshed the bundled plugins.

1.0.5

Released: 2026-08-11

Component	Version
VHMap plugin	1.0.15
VHOLUME bridge	1.0.2
Mapping project	1.0.5

• VHOLUME bridge 1.0.2 -- Added the Death Trigger actor. Place it over a pit, water, or anything else the player should not be able to fall into, and they die and respawn at their last checkpoint. It has no settings: the box you size is the volume that kills. See Death Triggers.
• Mapping project -- Bumped project version to 1.0.5 and added the Death Trigger documentation page.

1.0.4

Released: 2026-08-11

Component	Version
VHMap plugin	1.0.15
VHOLUME bridge	1.0.1
Mapping project	1.0.4

• VHMap 1.0.15 -- Ensures assets are fully built before they are written out for the cook, preventing shader-map and other build-related issues in packed maps.
• VHMap 1.0.14 -- Fixed a crash where the editor could die on the RHI thread after packing, by rebuilding render state before deleting imported copy objects.
• VHMap 1.0.13 -- Fixed a rendering-thread crash that could happen when the importer deleted copied assets after a map rewrite.
• VHMap 1.0.12 -- Reduced diagnostic noise when a map references content outside its own folder. If import_external_assets is enabled, this is now reported as a warning instead of an error, because packing automatically copies the referenced content into the pak. The same check no longer appears in the preflight modal; it remains visible in the diagnostics panel.
• VHOLUME bridge 1.0.1 -- Refreshed the default map template: replaced the old MapLevelDoor proxy with MapEndTrigger, and added an AmbientSound example.
• Mapping project -- Bumped project version to 1.0.4, updated the versions shown on this page, and added a direct download link.

1.0.0

Released: 2026-08-07

Component	Version
VHMap plugin	1.0.11
VHOLUME bridge	1.0.1
Mapping project	1.0.0

• Initial public release of the VHOLUME mapping project. Includes the VHMap editor plugin, the VHOLUME runtime bridge plugin, a VitePress documentation site, and the project packaging scripts.