Thx i was getting a ctd just after starting the first mission and this fix worked for me :)

i'd not played since last year and it worked fine then, strange

Is this edit still needed or did GOG fix it?

The most they could be bothered with is putting it in a support page: https://support.gog.com/hc/en-us/articles/360011450038-Star-Trek-Starfleet-Command-flickering-screen-fix?product=gog

I found a little batch file fix for people who still want to play the game in the original starting routine, i.e. see the intro movie automatically before the game starts.

Like many others I found out the game out of the box doesn't register any keyboard input and just returns a Windows ping signal if one tries to enter keyboard commands in-game. Also if I wanted to press Escape for getting back into settings/menu in skirmish or campaign, the game would actually react to ESC, but just get minimized and only comes back with bad colors when re-maximizing it, effectively making continuing impossible. This happens for me despite setting async=0 in the sfc.ini.

But this problem could be overcome by just starting the game not with sfc.exe, but with the Starfleet.exe, like many already pointed out. Then it will accept keyboard input and works just normal, as far as I can see.

Now, the intro movie gets skipped by starting the game with Starfleet.exe, you can access the intro movie in the movie folder and just start sfcintro.exe on its own to see it, but the automatic starting routine of the game wouldn't be avilable by starting it with Starfleet.exe.

But I found out you can simply write a batch file starting the sfcintro file first and then automatically proceeding starting Starfleet.exe:

@echo off
c:
cd "C:\GAMES\Star Trek - Starfleet Command\Movie"
start /w sfcintro.exe
cd "C:\GAMES\Star Trek - Starfleet Command"
start /w Starfleet.exe

This batch works on my system just as the sfc.exe SHOULD work, starting the intro movie, then starting the game itself, still able to accept keyboard input. (Of course you will have to change the paths according to your specific installation settings.)

The relevant step seems to be the /w variable behind both "start" commands (for wait for further steps until the command has totally finished its process).

When I leave out the second /w part, the game would still give me the "ping" keyboard bug, but with it, for some reason the bug is gone. At least on my system it is, perhaps this could also work on other systems.