XCOM 2
[WotC] The MOCX Initiative
WOTC MOCX Mod Memory Leak/Crash Issue?
I seem to have encountered a strange memory leak/crash issue with this mod, which is most unfortunate be cause the MOCX mods have been my favorite mods since they were first published. I am not sure how long this problem has been going on, since the issue only becomes apparent exactly 3 missions after Gatecrasher when the game will suddenly crash when starting a new mission and run extremely poorly upon restarting the game and crash again when entering any loading screen. I have been doing rigorous tests over the past week to see what the problem was, and I discovered that the problem seemed to only exist when this mod was running even when running this mod alone. Eventually I noticed that whenever the crash issue was present, scanning in the Geoscape would lower the framerate by 5-30 FPS, which I know usually indicates a mod conflict (lag would be unlikely as my computer can run Ultra settings at 60fps with 300 mods when everything is working right), but as I said the issue would persist even when running WOTC MOCX alone. I have tried unsubbing and resubbing to the mod (though Steam said only downloads around 180mb instead of the 358mb advertized on the modpage), removing all lines with "ModClassOverrides=" in XComEngine.ini, verifying the game through Steam, the only thing I feel I haven't tried is completely reinstalling the game but I don't know if my game is the cause of the problem. I also checked the debug log whenever XCOM was in the middle of crashing, but it only showed the usual messages that show with or without MOCX and it ends abruptly. This issue has been quite the puzzle.

If anyone has any advice as to what might be the cause of the problem or possible solutions, I would appriciate it as I have created a nearly 50 soldier character pool specifically for MOCX and I often get writing ideas from the battles that ensue between my custom MOCX and XCOM characters. Let me know if there is any more specific information on the issue that I should share.
Last edited by Apple Juice for the Merry; Apr 21, 2019 @ 1:53pm
< >
Showing 1-12 of 12 comments
An additional piece of information I just remembered, on a campaign that I had this issue with, I was able to resume it just fine without crashes or any issues by only disabling the MOCX mod, so the save itself does not become corrupted.
And to specify as to why I designate it as a potential memory leak, XCOM usually takes up about 9gb out of 16gb of RAM for me, but when this crash occurs whenever the MOCX mod is enabled, the usage has raised over time to the peak of around 14gb to 15.9gb out of 16gb RAM usage. With the MOCX mod disabled, the RAM usage stays between 9gb to 10gb RAM usage on average.
Last edited by Apple Juice for the Merry; Oct 27, 2017 @ 9:48am
If it would help, I was able to vaguely capture some of the technical issues on a recent XCOM livestream I did, which I have a recording of on YouTube, though I did not know the cause of the issue at the time: https://www.youtube.com/watch?v=A9wy0T44-xA
Brett Nov 15, 2017 @ 11:19am 
I am having very similar issues with this mod. A few missions into the campaign and suddenly the issues start cropping up. Loading into the main menu alone takes 1 to 2 minutes whereas it normally takes a few seconds. Specifically it gets caught up on a black screen with no audio. When selecting to load the save file, the game locks up for a good 30 to 45 seconds before actually loading the save. I can generally get farther then 3 missions but after 3 or 4 months into the campaign, I can no longer load the save without the game crashing.

The only way to get the save working again is to disable MOCX. Disabling any and all other mods does nothing.
Brett Nov 15, 2017 @ 3:45pm 
So it appears that the issue with the black screen before the main menu is unrelated. Four mods (Cost Based Ability Colors, Yet Another F1, Custom Face Paints, and Free Camera Rotation) were not updated for WotC (they still all give the warning if launching from steam directly). Disabling those mods loads the main menu just fine.

However the save files still crash when trying to load the game with MoCX active.
BoNeZ Nov 21, 2017 @ 11:01am 
I have been having these issues too, however i have to uninstall this and start a new game.
RealityMachina  [developer] Nov 21, 2017 @ 2:34pm 
I can't replicate this after stress testing the mod with a 400+ mods campaign.
花兔 (Banned) Jan 28, 2018 @ 2:23am 
same question
Brett Jan 28, 2018 @ 3:25pm 
I thought I had responded to this a while back, sorry. With the help of someone else, we found a sorta workaround to keep MocX active. If you only ever have saves in the Avenger where there are no missions active on the hologlobe, you can load without issues. The initial loading time of the save file still gets a bit slow deeper into the campaign but it won't crash.

I have been saving immediately after I get back from a mission before I even go back into the hologlobe. Haven't had a crash since.
Ditto.
0A0 Jan 10, 2021 @ 6:58am 
Same even now
ArtanisKAI Nov 20, 2021 @ 4:00am 
mine seems different but its also a crash. when i looked up my crashlog, these words piqued my interest... DarkXCom: Dark XCom: Template being used due to no class name is None... how i interpret it is that either my MOCX is having trouble creating the soldiers because i have proficiency class and it kinda changes the class around or its calling a code not present. whatever the case it happens when MOCX deploys via teleport. also this might be telling that my MOCX is bugged but their sitrep is called MOCX has no title
< >
Showing 1-12 of 12 comments
Per page: 1530 50