How to compile/build SFC2 EAW or OP Missions
Contents |
Software Pre-requirements
Windows 95/98/Me/NT/2000/XP 32bit
The StarFleet Command 2 games were compiled on a 32-bit host, which was quite normal for the days around 1999-2001. Compiling the missions scripts will require the same. Additionally, it's necessary to install certain support software onto this build environment. I do NOT recommend you use your primary computer to do this.
FireSoul's example: I have a home PC with Windows Vista Home Premium 64, and thus decided not to use this as my build OS. I decided to look into using a Virtual Machine environment, setting up Windows XP SP3.
My Virtual Machine specs:
- VMWare Player
- Free for non-commercial use.
- See: http://www.vmware.com/products/player/
- ALTERNATIVE: Virtual PC 2007
- 1.5GB of memory
- I could do with far less, but I also use 3DSMax R5 to create/modify my SFC 3D models
- 40 GB diskspace
- diskspace is cheap now-a-days. I have a 1TB drive in the main host.
- 2 CPU cores
- I have a Intel I7 Quad Core system. I decided to increase the number of cores in the VM from the default of 1 to 2 so that I can do other stuff while it compiles.
Microsoft Visual C++ 6.0
It has to be Microsoft Visual C++ 6.0. Nothing else will work.
No .NET. No "2005" or younger.
MSVC++ 6.0. Really.
Service Pack 5 for MSVC++ 6.0
IMPORTANT! Do not use Service Pack 6!
I cannot legally redistribute SP5 on my site, but I definitely have kept a copy around. It is true that SP6 is far easier to find, but it will SCREW THINGS UP if you install it!
EAW Scripting API
- download: SFC2_API_R1.3.zip
OP API R2.2 - Scripting API
- download: SFCOP_API_R2.zip
- Installation instructions: OP API R2.2 readme.txt