Reinstall XCOM If Custom UMAPs Don't Load

[abeclancy]

Just a note to anyone who seems to have a corrupted custom UMAP file that isn't loading in the XCOM 2 Editor (ModBuddy > Tools) or the XCOM 2 game itself. If your Editor is crashing when attempting to load the file, or the XCOM 2 game isn't properly generating a mission map for your level/missions (and you get a message in your Launch.log indicating that a ULevel object can't be found), just try deleting the \steamapps\common\XCOM 2 and \XCOM 2 SDK directories and redownloading or restoring the directories. Might not work for you, but it did for me. Must have messed up my local directories at some point, preventing the file from working properly.

 

edit: Could have also been fixed by deleting the local XCom*.ini files in my User directory. Try both.

 

edit edit: Well, XCOM's still having trouble with my level, but it loads in the Editor at least!

 

You should probably also make backups of your UMAPs, just in case something does go wrong with it.

Edited March 8, 2016 by abeclancy

[davidlallen]

Deleting the local XCom*.ini files only takes a few seconds, and this cures many problems. I highly recommend trying this first, before re-downloading 90 GB worth of stuff.

[abeclancy]

sigh

 

UMAPs at least load in the Editor, but only when I revert the entire XCOM 2 SDK directory tree. Apparently some part of modding XComGame core packages is causing the editor (and the game itself) to freak out and either crash or hang on level generation respectively, even when the modded files are completely removed and unloaded. The editor crashes with assertion failures and no World.TheWorld error message, and the game complains about no ULevel object in the mission script package.

 

At the very least, my UMAP is loadable and I can always save it out to another file, copy the scripting to another file, or what-have-you. I'm yet to figure out exactly what the issue is, but once I do I will update this thread with what I find out, unless someone else knows additional information regarding this and posts first.

[abeclancy]

Figured it out.

 

Turns out there's a reason why all the vanilla UMAPs in the game have the prefix "Obj_" on them. If your UMAP has the same name as the mission name you are creating, it will refuse to load. Attempting to make the debug menu's Tactical map generator make a mission will cause it to hang, and a missing ULevel error appear in your Launch.log file. So, someone can add that to a list of things to watch out for when modding.

 

Here's an example from the vanilla mission type Protect Device. Notice the "Obj_" prefix on the MapNames, which is the name of the corresponding UMAP file.

-arrMissions=(MissionName="ProtectDevice", sType="ProtectDevice", \\
    MissionFamily="ProtectDevice", \\
    MapNames[0]="Obj_ProtectDevice", \\

The more you know!