[AV8R]

In an effort to try and minimize drive waste and backup time, I was going through my games folder and tossing files that are obviously unneeded (TXTs, read mes, TMP files, etc). However, I've come accross some files under my Freespace folder that I don't know if I should keep or toss. Has anyone every stripped their Freespace files/folders to bare minimum - just enough to get the game to work with either retail graphics or with all FS2Open graphics turned on?

Especially in the root folder (C:\GAMES\Freespace2) what are the bare minimum retail, GOG and FS2Open files that are needed to run Freespace retail and FS2Open (not including Fred files/tools, non-FS2 engine mods, etc)? I've already went through all of my data and mediavp folders and can't remove any more files from them (or something will break) so it's just the root Freespace folder I'm trying to get a minimal inventory on.

Other info - The only campaigns I have installed (for now) are FS2Open, FSPort, ST-R and Destiny of Peace.

[AV8R]

Here's a list of files currently in my Freespace root folder (see attachment).

[attachment deleted by ninja]

[Yarn]

You can get rid of fs2.bmp and mod.ini. If you removed the "unins000" files, then you can also remove fs2uninst.dll. If you're using wxLauncher and not the older launcher, then you can remove launcher.exe and launcher6.ini. You can also delete fred2.exe if you want. The other files that don't end in ".vp" should stay.

Now for the VP files. Technically speaking, the only ones you absolutely must have are root_fs2.vp and sparky_fs2.vp. If you want to be able to play in 1024x768 resolution or greater, then you also need sparky_hi_fs2.vp. The others aren't needed but they're highly recommended, save for one. Here is what those files contain:

• smarty_fs2.vp: Intelligence animations, probably the one that you'll miss the least
• stu_fs2.vp: Voice acting
• tangoX_fs2.vp: Command briefing animations
• warble_fs2.vp: Music

[headdie]

isnt mod.ini needed with wxlauncher to recognise the folder as a mod?

[AdmiralRalwood]

isnt mod.ini needed with wxlauncher to recognise the folder as a mod?

The freespace root folder shouldn't be classified as a mod.

[AV8R]

isnt mod.ini needed with wxlauncher to recognise the folder as a mod?

The freespace root folder shouldn't be classified as a mod.

Thank you for your reply, Yarn. Your knowledge of the finer points of FSOpen is appreciated as always.   

As far as the MOD.INI, wouldn't the Freespace root folder be considered the retail vanilla "mod" (original Freespace with original graphics and such)?

[AdmiralRalwood]

wouldn't the Freespace root folder be considered the retail vanilla "mod" (original Freespace with original graphics and such)?

Yes, the root folder is "retail", or "vanilla", meaning "unmodified". Why would you call it the "retail vanilla mod"? That's just silly, confusing, and contradictory.

[AV8R]

Yes, the root folder is "retail", or "vanilla", meaning "unmodified". Why would you call it the "retail vanilla mod"? That's just silly, confusing, and contradictory.

You answered your own question with your first sentence. 

I suppose a couple of parenthesis around vanilla would have made my post more clear.

[AdmiralRalwood]

Yes, the root folder is "retail", or "vanilla", meaning "unmodified". Why would you call it the "retail vanilla mod"? That's just silly, confusing, and contradictory.

You answered your own question with your first sentence. 

I suppose a couple of parenthesis around vanilla would have made my post more clear.

And you didn't read that sentence very well... "vanilla" means "unmodified", so calling it a "mod" is, as I mentioned, confusing and contradictory (and silly; can't forget silly).