Posted December 02, 2009
This applies to both FreeSpace 1 and 2 which have the following bugs (tested on Windows XP):
- Afterburner does not work
- Briefing stalls in the first screen and does not advance
This is due to a too fast CPU - the GOG minimum requirements are bogus: FreeSpace was desigend for a target CPU frequency of 133 to 166 MHz. The game uses QueryPerformanceCounter() for timing and does not get it right on today's GHz CPUs.
Of course, such a bug should properly be fixed in the game itself before rereleasing it marked as "compatible with Windows XP" and "1.4 GHz CPU recommended" . ;-)
There is a bogus solution out there to enable Windows 95/98 compatibility mode. But introduces a new bug:
- Input lag with hardware rendering
I developed a solution using Microsoft Application Compatibility Toolkit 5.6: http://www.microsoft.com/downloads/details.aspx?familyid=24DA89E9-B581-47B0-B45E-492DD6DA2971
1. Download "Application Compatibility Toolkit.msi" using the link above.
2. Download http://www.oldgasworks.org.uk/FreeSpace.sdb for FreeSpace 1 (Mirror: https://mega.co.nz/#!c4xRBaIb!AdaXeW5OmYJ0MRlZqnulOAdMGt4ovWYmWJJLt-rnwLA )
3. Download http://www.oldgasworks.org.uk/FreeSpace2.sdb for FreeSpace 2 (Mirror: https://mega.co.nz/#!E0IAEY6S!TJRTjRqdtwzxq1ObO-4vwQoSvN1NVnDjzpoaK17kSow )
4. Install "Application Compatibility Toolkit.msi"
5. Run "Compatibility Administrator" from the "Microsoft Application Compatibility Toolkit 5.5" program group
6. Select "Open" and open FreeSpace.sdb
7. Right-click "FreeSpace [...FreeSpace.sdb]" under "Custom Databases" and select "Install"
7. Select "Open" and open FreeSpace2.sdb
8. Right-click "FreeSpace2 [...FreeSpace2.sdb] under "Custom Databases" and select "Install"
9. Close "Compatibility Administrator"
10. If you previously had enabled Windows 95/98 compatibility mode on your FreeSpace or FreeSpace 2 shortcuts respective FS.exe or FS2.exe, go to its properties and disable any compatibility options.
11. If you previously disabled hardware rendering, run FreeSpace.exe or FreeSpace2.exe, select Setup and re-enable it.
11. Done
Now afterburner and briefing screens should work and no input lag should occur.
Have fun!
Edit: Mirrors for sdb files added, thank you, simonhales
- Afterburner does not work
- Briefing stalls in the first screen and does not advance
This is due to a too fast CPU - the GOG minimum requirements are bogus: FreeSpace was desigend for a target CPU frequency of 133 to 166 MHz. The game uses QueryPerformanceCounter() for timing and does not get it right on today's GHz CPUs.
Of course, such a bug should properly be fixed in the game itself before rereleasing it marked as "compatible with Windows XP" and "1.4 GHz CPU recommended" . ;-)
There is a bogus solution out there to enable Windows 95/98 compatibility mode. But introduces a new bug:
- Input lag with hardware rendering
I developed a solution using Microsoft Application Compatibility Toolkit 5.6: http://www.microsoft.com/downloads/details.aspx?familyid=24DA89E9-B581-47B0-B45E-492DD6DA2971
1. Download "Application Compatibility Toolkit.msi" using the link above.
2. Download http://www.oldgasworks.org.uk/FreeSpace.sdb for FreeSpace 1 (Mirror: https://mega.co.nz/#!c4xRBaIb!AdaXeW5OmYJ0MRlZqnulOAdMGt4ovWYmWJJLt-rnwLA )
3. Download http://www.oldgasworks.org.uk/FreeSpace2.sdb for FreeSpace 2 (Mirror: https://mega.co.nz/#!E0IAEY6S!TJRTjRqdtwzxq1ObO-4vwQoSvN1NVnDjzpoaK17kSow )
4. Install "Application Compatibility Toolkit.msi"
5. Run "Compatibility Administrator" from the "Microsoft Application Compatibility Toolkit 5.5" program group
6. Select "Open" and open FreeSpace.sdb
7. Right-click "FreeSpace [...FreeSpace.sdb]" under "Custom Databases" and select "Install"
7. Select "Open" and open FreeSpace2.sdb
8. Right-click "FreeSpace2 [...FreeSpace2.sdb] under "Custom Databases" and select "Install"
9. Close "Compatibility Administrator"
10. If you previously had enabled Windows 95/98 compatibility mode on your FreeSpace or FreeSpace 2 shortcuts respective FS.exe or FS2.exe, go to its properties and disable any compatibility options.
11. If you previously disabled hardware rendering, run FreeSpace.exe or FreeSpace2.exe, select Setup and re-enable it.
11. Done
Now afterburner and briefing screens should work and no input lag should occur.
Have fun!
Edit: Mirrors for sdb files added, thank you, simonhales
Post edited June 19, 2013 by jtsn
This question / problem has been solved by simonhales