It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
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.
avatar
Plokite_Wolf: The 3603 beta patcher can't recognize it, either. Replays from my Steam version are listed in the replays menu but can't be played.
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.
Post edited June 30, 2021 by soosgjr
avatar
soosgjr: ...
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.
avatar
soosgjr: ...
avatar
Plokite_Wolf: 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.
avatar
soosgjr: ...
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.
Post edited June 30, 2021 by Plokite_Wolf
avatar
Plokite_Wolf: ...
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.
avatar
soosgjr: ...
avatar
Plokite_Wolf: 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.
Sorry for beeing late to the party.
Does that mean, the GOG version already includes the fixes/changes of the 3603 beta patch?
avatar
Plokite_Wolf: 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.
avatar
Ueber: 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.
Post edited January 13, 2022 by soosgjr