Suddenly having problems starting the mod

[mwonch]

I was able to play late last night, but today the game will not start (Steam version). It generates a crash log. I will post it below:

[0x00001c6c] 09-02-2017 08:12:04,862|    exename: C:\Program Files (x86)\Steam\steamapps\common\Star Wars Empire at War\corruption\swfoc.exe, cmdline: corruption\swfoc.exe LANGUAGE=ENGLISH swfoc MODPATH=Mods/Imperial_Civil_War
[0x00001c6c] 09-02-2017 08:12:04,862|    fidx: 11, search: swfoc.exe, fline: corruption\swfoc.exe LANGUAGE=ENGLISH swfoc MODPATH=Mods/Imperial_Civil_War
[0x00001c6c] 09-02-2017 08:12:04,863|    Unknown command line option: LANGUAGE=ENGLISH
[0x00001c6c] 09-02-2017 08:12:04,863|    Unknown command line option: SWFOC
[0x00001c6c] 09-02-2017 08:12:04,863|    Unknown command line option: MODPATH=MODS/IMPERIAL_CIVIL_WAR
[0x00001c6c] 09-02-2017 08:12:04,863|    Unknown command line option: NOARTPROCESS
[0x00001c6c] 09-02-2017 08:12:04,863|    Unknown command line option: IGNOREASSERTS
[0x00001c6c] 09-02-2017 08:12:04,863|    Checking windows firewall
[0x00001c6c] 09-02-2017 08:12:04,899|    Adding exclusion for C:\Program Files (x86)\Steam\steamapps\common\Star Wars Empire at War\corruption\swfoc.exe to windows firewall

[0x00000cb4] 09-02-2017 08:12:04,921|    DebugProcess: StarWarsG.exe[00001a08] Create Process: 1, process handle: 508, thread handle: 504, processID: 6664, threadID: 2796
[0x00000cb4] 09-02-2017 08:12:04,922|    DebugProcess: StarWarsG.exe[00001a08] DebugProcessLauncherClass::Update_Version_From_Process -- Version: 1.121.644744
[0x00000cb4] 09-02-2017 08:12:05,822|    DebugProcess: StarWarsG.exe[00001a08] DebugProcessLauncherClass::Cleanup
[0x00001c6c] 09-02-2017 08:12:05,933|    Removing exclusion for C:\Program Files (x86)\Steam\steamapps\common\Star Wars Empire at War\corruption\swfoc.exe from windows firewall


Apparently, the game will no longer recognize the MODPATH command for FOC. It seems it also does not recognize LANGUAGE=ENGLISH, which is odd. I'm assuming Steam did an update. Is there any way to work around this maddening issue?

[Slornie]

Petroglyph/Disney released a new patch on Steam yesterday (Force Friday), which re-enables multiplayer, adds Steam Workshop support and a few other fixes, but I don't believe that's necessarily the cause of your problem.  I've been able to launch ICW as normal today with no issue, using both Workshop and local installation copies, and have the exact same unknown command lines in my log.

Have you tried verifying the game files through Steam?  Also before the update turned up did you happen to have any mods installed which put files in the base game's Data folder, like Republic at War does?  It could be something is clashing between the new patched game and the modded files. 

[mwonch]

I verified the files twice. Both times it reported all was well. I have no other mods installed aside from ICW. I have, however, changed a few settings in the mod's files (not base game). I should add that not even the vanilla game is firing up.

My son is experiencing the same problem on another machine and a totally separate connection. He gets the same error message in the same log file as above.

I have had Steam do updates on other games which messed things up kind of like this. Usually an uninstall/reinstall fixes the problems. However, I hesitate to do that since the kid's having the exact same issue. His issue appeared at the same time as mine. I would say possibly incompatibility of the mod with the new update, but you say you can start yours without issue. Now, I'm really confused.

I guess I'll have to reinstall it. In the meantime, if there are any other suggestions, I am more than willing to try them.

[Corey]

It seems like you're running with a direct shortcut to the swfoc.exe, but that was also changed- FOC now uses an exe called StarWarsG.exe. that could be part of your problem.

[mwonch]

I tried using the other exe to start. Same thing. Basically, the update broke the game for me. I even reinstalled it. Same problem.

This is why I despise Steam and always have.

[Corey]

Is it giving the same error when you try to launch without any changed launch options, or is it different? Tried verifying integrity of game cache?

[mwonch]

Verifying the files is the first thing I did. Deleting the mod is the second. Reinstalling the game vanilla was third. None worked. Not even for vanilla. Then I found out they had a new patch. Turned off antivirus, added an extra exception to firewall (even though Windows FW is off). Still, with or without the mod, the game simply will no longer launch.

This is maddening. This (with your mod) is one of my favorite games! LOL

I don't think it's your mod. But, to be sure, I am once again uninstalling the game(s), deleting residual folders, and whatnot. Without knowing where to look, however, I cannot delete any relevant registry keys. OY!

But, yes - the same errors occur no matter which exe I use, with and without the added launch options.

[mwonch]

Manually changed all exe files to run as Admin. No dice. Tried using the names of the various exe files in Launch Options (including the files Steam uses: runme2.exe). No dice. Tried using the Workshop Mod for ICW. No dice. Deleted that. Tried MY zipped file containing the mod that last worked.No dice. Vanilla game does not launch (EaW ot FoC). I even tried your recently posted guides on Steam. No dice.

I guess I can no longer play this game...unless I download a cracked version to try this independent of Steam. Not sure if I want to do that. Steam blows...it really does.