Unreal FAQ

Frequently Asked Questions

How should I package my game?

This guide will point out various options you have for packaging your game: Packaging Projects documentation by Epic.

Packaging Error: Import failed for chain error while packaging

If you come across an error while packaging that looks like this:

UATHelper: Packaging (Windows): LogInit: Display: LogObj: Error: LoadConfig (/Script/EmergenceEditor.Default__EmergencePluginSettings): import failed for Chain in: (Chain=Ethereum,EthereumChain=GoerliInfura,PolygonChain=MainnetInfura,UseCustomNodeURL=False,CustomNodeURL="",UseCustomTokenSymbol=False,CustomTokenSymbol="")

This is likely happening because you have upgraded Emergence from 0.2 to a newer version without resetting the configuration in DefaultGame.ini. To do this, go to <your game's directory>/config/DefaultGame.ini find the [/Script/EmergenceEditor.EmergencePluginSettings] heading and delete it, and all of the configs between where that heading was and the next heading / end of file. This will allow Emergence to update these configs when you next launch it. Remember to update your project settings after doing this, as these will have been reset.

Game Error: Plugin 'Emergence' failed to load because module 'Emergence' could not be found

If you come across a error/crash in a built game that looks like this:

Fatal error: [File\build\++UPlugin 'Emergence' failed to load because module 'Emergence' could not be found.  Please ensure the plugin is properly installed, otherwise consider disabling the plugin for this project.

This error can occur if you have packaged a game which is a "blueprint only" project while using a version of Emergence which has been installed to the game's plugin directory rather than being installed via the marketplace. To get around this issue, you'll just need to add any c++ class to your project. This can be done by clicking "New C++ Class..." in the editor, then selecting a parent class (doesn't really matter which one you pick if you aren't actually going to use it) and then creating the class. This will make unreal look for c++ plugins when it builds your game from now on, and you shouldn't get the error.

Packaging Error: Issues with WBP_ControlRig / WBP_MorphTarget

These VRM4U assets rely on other external plugins / features that we don't include with Emergence as they are for working with body tracking. We include these with VRM4U in-case you do want to add those extra features, but if you don't you can delete the \Plugins\VRM4U\Content\Util\Actor\Latest folder. You might struggle to delete all of these files from Unreal Engine 4's editor as they might not show up due to be UE5 assets, in which case, use file explorer to find the files / folders and delete them manually.

Packaging Error: VRM4U file / map "is too old"

If you're building from Unreal Engine 4 and you're getting this error, it likely these files are (unintuitively) actually too new, they're from Unreal Engine 5. If you come across any of these you can delete them from the VRM4U files as they are not required. You might struggle to delete all of these files from Unreal Engine 4's editor as they might not show up due to be UE5 assets, in which case, use file explorer to find the files / folders and delete them manually.

I have an bug, suggestion or question not listed here!

You should visit our discord! https://discord.gg/openmetadao

Last updated