Cannot get FOC To Launch From Steam

[Aeradom]

So, I'm at a loss. I downloaded the game a couple of days ago to check out some mods. I can't quite remember the sequence of events but there was a point that I could launch FOC through Steam and now I'm not able to. I'm pretty sure this was after installing a mod but I doubt that has anything to do with it at this point as I've uninstalled/reinstalled the game multiple times. To be clear, I can start the game if I go directly to the executable in the folder, so it's not the game that is at fault (which now that I think about it, probably doesn't make this an Empire at War issue but I don't know where else to go as this is the only game with the issue). I've tried just about everything from restarting the computer, to disabling my security software. I'm completely at a loss right now. And as aside, wherever do they store the mods you download anyways.

One last thing, I attached a screen capture of the Corruption folder. I can't be sure, but it really looks like something is missing there as I thought I remembered having four folders instead of two. Might be my imagination, might be I'm just reaching for straws but I don't know where to go from this point.

Edit: Also tried running in compatibility settings. I don't know why that would help but thought I'd try it.

Edit 2: Oh it's Windows 10 I'm running, I figured someone would ask that. Let me too emphasize that I have played it before (played with this mod in fact which I was looking to reinstall), so it has worked, just not now.

Edit 3: One more thing I forgot to mention is that vanilla EaW launches just fine from Steam. So it's strictly FOC that is the problem (figures, right?)

[Corey]

Unfortunately not sure what would cause this. As for where mods are stored from the workshop, they go in: C:\Program Files (x86)\Steam\steamapps\workshop\content\32470

[Aeradom]

Unfortunately not sure what would cause this. As for where mods are stored from the workshop, they go in: C:\Program Files (x86)\Steam\steamapps\workshop\content\32470

Was afraid of that. I thought maybe there were remnants over int the mod folder for some reason but nothing there, at least not to interfere with it. I appreciate you taking the time to respond though. I really enjoy your videos.

[Slornie]

When you say you can't get FOC to start, what do you mean exactly (i.e. is it crashing, not opening when you try to run it, or are you just getting EAW every time?) and how are you trying to launch it within Steam (desktop shortcut, taskbar or from your library)?

[Aeradom]

When you say you can't get FOC to start, what do you mean exactly (i.e. is it crashing, not opening when you try to run it, or are you just getting EAW every time?) and how are you trying to launch it within Steam (desktop shortcut, taskbar or from your library)?

All of those are good questions that in all of my edits I really should have detailed. So for starters, I'm attempting to launch it through the sidebar on the left (as I don't think you can launch FOC from hitting the play button in the center). Now I've double clicked it and it's brought up the options for Vanilla or FOC, selected FOC, and that didn't work. I've also tried right clicking on the game and selecting it but to no avail. Now as to what it does; when I select FOC to play, it'll say next to the game in the sidebar "running" for about five seconds and then that goes away and the game never launches.

And to be super clear, though I think I said this already, I can launch the game by going into game directory and launch the game just fine there. The problem arises that when I attempt to relaunch the game to activate the mod, the game does exactly what I described above like I had just tried to launch it for the first time.

[TonPhanan]

That's a weird issue... do you run any beta version of the steam client? Did you try to deactivate the overlay and checked the properties if you somehow run it with any command or whatever :? It sounds more like an issue with Steam itself rather than one with FOC, since you can start that just fine from its directory...

[Aeradom]

That's a weird issue... do you run any beta version of the steam client? Did you try to deactivate the overlay and checked the properties if you somehow run it with any command or whatever :? It sounds more like an issue with Steam itself rather than one with FOC, since you can start that just fine from its directory...

No to the steam beta and just checked for the overlay and "run it" deal and that wasn't the issue either. Though I wouldn't be surprised if at some point this turns out to be steam just not finding the program. Actually, I don't think it's that as I recall trying to use the RaW mod and attempted to use the suggestion Anikan had on his mod page (have a direct path to the mod), but to no avail. It's so bizarre because it works just fine launching vanilla, just FoC. At this point, I'm kind of with you and leaning towards it being more of a Steam issue than it is a game issue. The thing is, I'm not having any problem with other games so if it is Steam, it be relegated to just this one game. Which is certainly plausible mind you. I tried to get a hold of their tech support but I couldn't figure out how to get to it as it directed me to the game support.

[Slornie]

Actually, I don't think it's that as I recall trying to use the RaW mod and attempted to use the suggestion Anikan had on his mod page (have a direct path to the mod), but to no avail. It's so bizarre because it works just fine launching vanilla, just FoC.

So for RaW you updated your Launch Options in the EAW Properties to reference the mod (using MODPATH=, or STEAMMOD=)?  I take it you've since removed any of those references from the options? (unless that what TonPhanan already suggested)

[Aeradom]

So for RaW you updated your Launch Options in the EAW Properties to reference the mod (using MODPATH=, or STEAMMOD=)?  I take it you've since removed any of those references from the options? (unless that what TonPhanan already suggested)

Oh! How I wish it was that simple! But no I tried it because I thought that might get the mod to work at least if it was pointed to a different executable. But I was sad to see in the mod folder there wasn't so that shot down that idea. Like I said though, vanilla pulls up just fine, it's just FoC that has the snag. I'm completely reinstalling steam because short of a complete reformat, I'm not sure what else to try.

[Aeradom]

Update: Nope, reinstalling Steam didn't work. I don't understand how this bug is possible at this point. And btw, when I uninstalled it, I did it with a tool that scans for leftover files so everything should have been cleaned out. I don't even know right now.

[Aeradom]

Update 2: So I managed to find a workaround, at least for this mod. Basically, I just launch directly utilizing the .bat using the Moddb files. So at least there's that to be happy about.

[Aeradom]

Final Update: So I finally figured out what was going on with it. I can't recall who it was in chat, but they actually gave me the inspiration for it. What I didn't understand about EaW is that they actually have a couple of steps prior to getting to swfoc.exe, one, in particular, being runme2.exe. On a hunch, I set those to compatibility mode and now they launch just fine. So if anyone runs into a similar issue, make sure to do compataibility mode to every executable, starting with that one, and eventually, it should work.