How to compile/build SFC2 EAW or OP Missions
(→Other APIs.. maybe your own?) |
(→Service Pack 5 for MSVC++ 6.0) |
||
| Line 39: | Line 39: | ||
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! | 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! | ||
| + | |||
| + | The filename is ''vs6sp5.exe''. It's 130 MB (136,410,832 bytes) in size. | ||
=== EAW Scripting API === | === EAW Scripting API === | ||
Revision as of 23:31, 9 June 2011
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!
The filename is vs6sp5.exe. It's 130 MB (136,410,832 bytes) in size.
EAW Scripting API
This is the part that links the sources to SFC2 EAW: the mission API. It will contain library files, c++ header files and some template mission scripts.
Be sure to follow the installation instructions!
- download: SFC2_API_R1.3.zip
- also see: SFC-related_missions,_sources,_patches_and_misc_utilities
OP API R2.2 - Scripting API
This is the part that links the sources to SFC OP: the mission API. It will contain library files, c++ header files and some template mission scripts.
Be sure to follow the installation instructions!
- download: SFCOP_API_R2.zip
- Installation instructions: OP API R2.2 readme.txt
- also see: SFC-related_missions,_sources,_patches_and_misc_utilities
ShipList API
The game's own API is very unhelpful when it comes to making proper ship picks. I strongly recommend installing, understanding and using the ShipList API so that you can create better missions.
- download: ShipList.20050118.zip
- also see: SFC-related_missions,_sources,_patches_and_misc_utilities
Other APIs.. maybe your own?
I made my own API kit in the hopes that it might help others. It includes OP R2.2 and a ShipList API revision from 2003.