[karajorma]

I'm adding a list of the folders FS2 uses and the order it looks in them. Have I got the order it checks them in correct?

FS2

    * \Freespace2
    * \Freespace2\Data
    * \Freespace2\Data\x

FS2 Open

    * \Freespace2\ModDirName\
    * \Freespace2\ModDirName\Data
    * \Freespace2\ModDirName\Data\x
    * \Freespace2
    * \Freespace2\Data
    * \Freespace2\Data\x

[TopAce]

Does FSO have an individual folder control system?
I didn't know it.
Do I have to make them manually, or FSO does it instead of me? Because I have been using FSO for a while(since I joined the SWC staff), and FSO has never made new folders to me.

[StratComm]

The reference is to the -mod command, and no, you have to make and fill the mod folders yourself.  Kara, don't forget the VP, some people may not know/realize that its last on the list.

[redmenace]

this is how you need to set up the folders useing the -mod option
Freespace2
--Root Directory
---+data
----Files and VPs
----SWFC
------VPs
------data
--------maps
--------tables
--------effects
--------pilots
--------all the rest of the files and folders

[karajorma]

Red I'm pretty much aware of how to set up FS2_open correctly. I was checking I've got the order correct so that I can add information to the wiki so people who haven't done it correctly can troubleshoot.
(i.e that if you mistakenly add something to the main FS2 folder will it override something in the data folder?)

Originally posted by StratComm
Kara, don't forget the VP, some people may not know/realize that its last on the list.

Good point. I believe that only \Freespace2 (and \Freespace2\ModDirName if you're using -mod) are checked for vp files. Correct?

[redmenace]

I was getting a little more detailed. especially about the vps. those are very important. That is not something i personally understood about them for a while. now all works just peachy. except screen shots.

[taylor]

VPs are searched recursively through all game directories.  You could have LS's hi-res planets in a VP in Freespace2\data\effects if you wanted but VPs are used in directory then alphabetical order so any files in a VP in Freespace2\ would get used first.

Mods can go in any directory in Freespace2\ with the patch specified, so if you had Blackwater Ops in a mod directory called BWO then the mod command would be "-mod BWO" if BWO was in Freespace2\data then it would be "-mod data\BWO", etc..  I recommend just putting all mods in Freespace2\ or in a special mod directory (ie. Freespace2\mods) for ease of maintenance sake but that's just personal preference.

[Kazan]

for organizations sake .vp's should be in the module root

ie fs2 retail module root =
a mod module root = /mod

[mrduckman]

I think I can make a little batch file to make them.

[karajorma]

Originally posted by taylor
VPs are searched recursively through all game directories.  You could have LS's hi-res planets in a VP in Freespace2\data\effects if you wanted but VPs are used in directory then alphabetical order so any files in a VP in Freespace2\ would get used first.

Now that I didn't know. When I first started using FS2_Open I'm sure I had trouble until I put the vp in /mod instead of /mod/Data. Must have been doing something wrong. I'll add that to the wiki in a bit.

Originally posted by Kazan
for organizations sake .vp's should be in the module root

ie fs2 retail module root =
a mod module root = /mod

That's exactly where I've told them to put them It's the most sensible choice.

 The idea behind the page of the wiki is to give people a good enough explaination of how FS2 works that they can solve their own problems. It's worked quite well in my FAQ for FS2 so I figured I might as well do the same thing for FS2_Open.

[TopAce]

Personally, I find it simplier to have all my data in the main FreeSpace/data. If I want to change from SWC to RR, I only change the tables.

But I guess it is only me ...

[Kazan]

being a dipwad too

use -mod

[TopAce]

dipwad?

[Kazan]

how about dimwit, fool, being daft... etc

use -mod it's there for a reason - mixing mod files is not only dirty but it's dangerous
additionally it negatively impacts performance

[TopAce]

Never occured problem to me, so I think I stay at the 'standard' solution.

[Kazan]

no you shouldn't for very many technical reasons - the standards solution IS the -mod flag now

[TopAce]

Needless efforts, Kazan. You cannot convince me. It is simpler than struggling with your command paratemeters, and I got used to it. This. Ends. Here.

[kasperl]

ok, no problem, but this pretty much invalidates you for ever *****ing about stability, performance or reliability. and reporting a bug would basicly mean nothing.

standards are set for a reason.

[TopAce]

I doubt. FSO quits every time I do those I listed to you via PM regardless of how I change between mods.

[kasperl]

let's see, the pilot file is known, and it isn't and issue if you backup regurlaly. and for the rest, it might be worth the try to follow the steps disrcibed in the wiki [scp][/scp] to the letter, instead of being a egocentric "i know it better" kind of guy.

edit: FYI, the pilot file isn't "corrupted" it is simply used to store more data, and therefore standard :V: stuff cannot read it, same with mission files and tables.