Troubleshooting

"This is not your map" / I have been building in DefaultMapTemplate

DefaultMapTemplate is the level that ships inside the VHOLUME plugin folder. It is the level New Map copies to create your map -- it is not a map you can work in:

• It cannot be packed or published. Everything you build in it counts as content from outside the map being packed, so packing stops and names your own meshes and textures.
• Its whole folder is replaced every time you update the toolkit, so work saved there is lost at the next update.

It is easy to end up in by accident: Unreal reopens whatever level you had open last, so opening it once to look at it makes it your starting point on every restart.

To move work you have already done out of it: with the level open, use File > Save Current Level As and save it into your own map's folder (<YourMap> Content > Maps). Everything you have built comes with it. If you do not have a map of your own yet, use New Map first -- it copies the template as it currently stands, so your work comes across that way too.

VHMap offers to do that for you when it sees you in that folder. Answering "No" leaves everything exactly as it is.

Packing fails: "it could not be brought in for packing"

VHMap copies content your map uses from outside its own folder into the pak for you, and checks afterwards that the copies really were written. Two different things produce this message:

• The map being packed is not yours -- see the section above. The fix is to work in your own map, not the template.
• "the file on disk does not reflect it" on a map that looks fine. This was a bug in VHMap up to 1.0.18, triggered by assets whose name ends in a number without a leading zero (T_Concrete_Plates_171). Update to mapping project 1.0.8 or later. Nothing was wrong with your map, and nothing was changed by the failed pack.

If you are on 1.0.19 or later and still see it, something outside the editor is putting your map file back while it packs -- revision control connected in the editor, a cloud-synced project folder, or antivirus. Turn those off and pack again, and send us the message and your Saved/Logs/ folder if it persists.

The player spawns at world origin and the map freezes

Make sure your level contains:

• Exactly one Start checkpoint.
• A PlayerStart actor co-located with the Start checkpoint.

The default map template includes both.

VHMap setup window shows red items

Click each red item and use the Fix button. Common fixes:

• Build the base release.
• Create a map plugin.
• Open the map level.

Packing stops on unsupported assets after importing a GLB

Importing meshes as GLB/glTF used to fill the content check with unsupported assets that you never created. Unreal imports GLB through a different system than FBX, and that system tags each imported asset with the import settings it used. VHMap was following those tags and pulling the settings assets into your map, where they were then refused.

Fixed in VHMap 1.0.25 -- update the plugin and pack again. Nothing needs re-importing. On an older VHMap, importing the same meshes as FBX avoids it.

Workshop upload fails with ERROR 25

An image is over Steam's 1 MB limit. The limit applies per file, to the main image and to every screenshot separately, so one oversized screenshot fails the whole upload even when the other nine are fine. Steam does not say which file it was.

VHMap now blocks this before it can happen: an oversized image is refused when you pick it, the Share Map window turns that warning red, and Pack & Publish stops with the file names and sizes. If the upload window in the game reports it instead, the images changed on disk after they were added.

Re-save the offending file smaller and add it again. 512x512 JPG for the main image and 1920x1080 JPG at moderate quality for screenshots are comfortably under the limit; PNG screenshots frequently are not.

Workshop upload fails

• Ensure you are logged into Steam.
• Ensure you own VHOLUME on the Steam account.
• Check the editor Output Log for detailed error messages.

Version mismatch

Include all three version numbers from the VHMap setup window when reporting bugs:

• VHMap plugin version
• VHOLUME bridge version
• Mapping project version

Still stuck?

Join the VHOLUME Discord server for help:

discord.gg/khsGJE5mSK