Response received: it was forwarded to the "appropriate team".

¯\_(ツ)_/¯

Dang, quite a few non-trivial fixes in there.

Looks like any kind of interest died pretty quickly. Unless GOG would add online play I guess.

It might be a bit late, but I got the patcher working on the GOG version. It can be done by doing the following steps:

- Install or copy the game files under the following path: C:\Program Files\THQ\Gas Powered Games\Supreme Commander - Forged Alliance\
- Rename bin\SupremeCommander.exe to bin\ForgedAlliance.exe.
- Copy the patcher to the bin folder and run it.
- The initial process will fail, so uncheck the Safe Mode checkbox and press Start.
- It will still say it failed, but it will actually update the EXE.
- Rename bin\ForgedAlliance.exe back to bin\SupremeCommander.exe.
- The main menu now should have the 3603 version number in the top right corner.

I didn't do any significant testing, but the game and the campaign launches fine. I did this on a permanently offline rig, so I believe the patched EXE is still DRM-free.

Compared to the Steam version now the only differences are the EXE (obviously) and lua.scd. I diff'd the LUA files and all the differences seem to be related directly to Steam or the multiplayer lobby in general, neither should really matter for solo or LAN.

Just gave this a try. I got the same result as you for the most part, but I would like to ask you if you have any differences in loc_US.scd between the GOG and Steam versions since that is the file that triggers the patch failure.

Nope, they're exact matches even before the patch. The only differences between GOG's 3599 and Steam's 3603 from the start are the EXE and a couple of LUA files in lua.scd. It seems the patcher only supposed to update the EXE for 3599, the rest of the changes are for older versions. It maybe also supposed to make some minor changes to lua.scd (if it weren't choking up on loc_US.scd), but I didn't find any differences between the two files that seemingly matter outside of Steam.

Awesome! Well done on the investigation - post it up on the PCGamingWiki for others to try.

BTW, actually installing in that directory is not needed, it's sufficient to copy the existing game directory there, haven't tried doing so with just the affected files.

EDIT: Seems to me GOG was a bit lazy and used the 3599 EXE variant that had SecuROM removed and applied that to 3603...

EDIT 2: Sent them a support ticket to hopefully include the correct EXE.

Thanks, I've updated the original comment to reflect that you can do either. I just used the install path of describing things, as it uses less steps. I'll try to get it on the wiki.

As for the version, that's certainly possible, but without a retail copy of 3599 we'll never know for sure.

Sorry for beeing late to the party.
Does that mean, the GOG version already includes the fixes/changes of the 3603 beta patch?

Well, this thread is all about late replies, heh.

Unfortunately, no, the GOG version wasn't updated since its release, it's still at 3599. However, now we figured out how to apply the latest official beta patch (I got the one from ModDB) to the GOG version. The steps required to do so are detailed on the PC Gaming Wiki.

Just wanted to add my two cents here in case someone else finds this and wonders.
After following the steps detailed on PC Gaming Wiki my version still shows as 3599 but it seems the changes are applied e.g. Hoplite at 450H Mongoose at 650H T1 Bomber Cost 80M 1400E etc.

Edit: I was wrong. See the posts below.

Your attempt failed, then. As soosgjr wrote above: I observed the same when I found this thread and applied the instructions for patching it. Using the original GOG offering, I saw 3599. After following the instructions in this thread, I see 3603. Also, incidentally, I find 3603 to be far more stable than 3599. 3599 crashed on me at least once every 6 hours of play, seemingly randomly. I have not had any crashes with 3603 since I switched. As implied but not exactly stated in earlier posts, GOG's offering uses the 3603 unit statistics, despite using a 3599 executable. Therefore, if you installed from GOG, then you will see the 3603 prices regardless of whether you successfully apply the 3603 beta patch.

Well thanks for clearing that up. Kinda sucks that the patcher won't work then. I'll try if I can get it to work.

Edit: Ok got it to work. It was the stupidest thing, too.
From earlier posts I figured that I had to actually create the "THQ/Gas Powered Games/" part of the path. But what I just now noticed is that it ends in Supreme Commander - Forged Alliance while the default gog folder does not include the hyphen...
So thanks for letting me know that it actually failed and making me look closer into it.