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

×
Here's a list of HD mods and community patches for Starfleet Command games. Credits go to D4v1ks and TarMinyatur.

Starfleet Command 1 (incl. Gold)

- HD mod (for versions 1.02.1 and 1.03)

Starfleet Command 2: Empires at War

- unofficial 2.037 patch
- Community Edition (CE) 2.679 patch (not to be used to upgrade the regular version to CE)

Starfleet Command 2: Orion Pirates

- unofficial 2.564 patch

Starfleet Command 3

- 534b HD Patch

Other notable links

- Windows 10 fix by qwixter
- SFC Launcher (multiplayer emulation)
- Sprites.q3 Editor
Post edited December 03, 2018 by Plokite_Wolf
FYI, the GOG version is 1.03 and the HD pack works great with it thank you!!
Post edited March 13, 2018 by spacecav
Indeed, I found out about the HD patch via finding out what the SFC 2 Community Edition (I failed to see this thread :( )

The HD patch works a treat with the GOG version.

And I agree this thread should be stickied!
The 2.679 patch for SFC:CE cannot be used for SFC2:EAW. These games use completely incompatible executables (Starfleet2CE.exe, Starfleet2.exe).

The only unofficial patch that will work for SFC2: Empires At War is 2.037.

The future of the game for multiplayer is SFC2: Orion Pirates 2.564. Nothing else has any activity.
Post edited December 03, 2018 by tarminyatur
avatar
tarminyatur: The 2.679 patch for SFC:CE cannot be used for SFC2:EAW. These games use completely incompatible executables (Starfleet2CE.exe, Starfleet2.exe).
I'm pretty sure I was able to patch EAW with 2.67x before. I'll test that again very soon.
SFC:CE can theoretically use the text, model, and sound assets of EAW. But the EAW missions are a VC++ 5.0 product (circa 2000) while the Community Edition scripts are built on Visual Studio 2012.

I'm not saying it's impossible to drop the 2.679 Starfleet2CE.exe into the EAW folder, rename it to Starfleet2.exe, import all the CE missions, and play the game somehow.

Anyway, 2.679 is not an upgrade for 2.036 (or 2.037). All versions of Community Edition are inferior to EAW 2.037 because of bugs introduced in the official 2.670 that will never be fixed.
avatar
tarminyatur: SFC:CE can theoretically use the text, model, and sound assets of EAW. But the EAW missions are a VC++ 5.0 product (circa 2000) while the Community Edition scripts are built on Visual Studio 2012.

I'm not saying it's impossible to drop the 2.679 Starfleet2CE.exe into the EAW folder, rename it to Starfleet2.exe, import all the CE missions, and play the game somehow.

Anyway, 2.679 is not an upgrade for 2.036 (or 2.037). All versions of Community Edition are inferior to EAW 2.037 because of bugs introduced in the official 2.670 that will never be fixed.
Very well then, edited the first post accordingly.
Community Edition was a weird game. There was no community engagement. A mysterious group of amateur programmers fiddled with a modified version of Empires At War eight years ago. The whole endeavor would have been fruitless if Strat didn't persevere alone to release something playable.

We got SFC:CE 2.660 in 2012 and it was buggy and leaderless in maintenance. It had better frames per second than EAW but otherwise it was worse than the reliable 2.036 that we had been using since 2001.

I wouldn't group SFC:CE with EAW for any purpose. I am annoyed that Dynaverse.net continues to sell "Community Edition" as some sort of upgrade. The community would be better served if that game did not exist.