I haven't contacted HOTU yet, and before I do anything I want to get everyone's input.
I've put together a new package for HOTU, which is set up differently from the one currently available for download.
I did this for 3 reasons.
- The present HOTU version doesn't include sparky_hi (for 1024x768 mode).
- all of the files are extracted into the data directory, which makes grabing the rest of the vp files a bit of a pain due to the need to delete all the files in the data subdirectory.
- The registry is set up differenctly in the HOTU version (nothing critical)
One issue though, the present HOTU version is 219MB, while this version is 347MB. This package contains:
\data (and all subdirectories)
ENDPART1.MVE
ENDPRT2A.MVE
ENDPRT2B.MVE
Fred2.exe
freespace2.exe
FS2.exe (v1.2 no-cd)
FS2uninst.dll
patchw32.dll
pxo.url
readme.txt
root_fs2.vp (v1.2 retail)
sparky_fs2.vp (retail version)
sparky_hi_fs2.vp (retail version)
UpdateLauncher.exe
Now, this way, once individuals grab the HOTU version, all they are missing are:
stu_fs2.vp (contains all of the sounds in data\voice)
smarty_fs2.vp (contains intelligence animations in tech room)
tango1_fs2.vp (contains .ani in data\cbanims)
tango2_fs2.vp (contains .ani in data\cbanims)
tango3_fs2.vp (contains .ani in data\cbanims)
warble_fs2.vp (contains .wav in data\music)
I know that the loss of stu_fs2.vp really takes away from the atmosphere, and I was thinking of maybe making a vp (stu_fs2_HOTU.vp) that only contained the data\voice\personas.
Now HOTU may not take the 347MB package, so even if I have to remove sparky_hi (and then throw in as much of the infor from stu_fs2.vp), at least that simplifies havving people update to the full retail version.
Let me know what you all think.
In the .zip file submitted to HOTU, there will be the files:
FreeSpace2_HOTU.zip
├
├readme.txt
├Get FreeSpace 2 Open.url
├FreeSapce2_HOTU.exe
The readme will say where to get the missing VP files, and also promote FS2 Open.
Ley me know what you think. I'll wait to hear before I do anything more.
Cheers!