Hard Light Productions Forums

Modding, Mission Design, and Coding => FS2 Open Coding - The Source Code Project (SCP) => Topic started by: RandomTiger on October 10, 2002, 09:57:15 am

Title: fs2_open command line flags
Post by: RandomTiger on October 10, 2002, 09:57:15 am
Could we have a list please, or someone direct me to the list.
Title: fs2_open command line flags
Post by: Righteous1 on October 10, 2002, 10:30:30 am
*Slaps head*

Should have thought of a command line option myself!  

Here's a list from cmdline.cpp  The names seem to be self-explanatory:

cmdline_parm standalone_arg("-standalone", NULL);
cmdline_parm nosound_arg("-nosound", NULL);
cmdline_parm nomusic_arg("-nomusic", NULL);
cmdline_parm startgame_arg("-startgame", NULL);
cmdline_parm gamename_arg("-gamename", NULL);
cmdline_parm gamepassword_arg("-password", NULL);
cmdline_parm gameclosed_arg("-closed", NULL);
cmdline_parm gamerestricted_arg("-restricted", NULL);
cmdline_parm allowabove_arg("-allowabove", NULL);
cmdline_parm allowbelow_arg("-allowbelow", NULL);
cmdline_parm port_arg("-port", NULL);
cmdline_parm connect_arg("-connect", NULL);
cmdline_parm multilog_arg("-multilog", NULL);
cmdline_parm server_firing_arg("-oldfire", NULL);
cmdline_parm client_dodamage("-clientdamage", NULL);
cmdline_parm pof_spew("-pofspew", NULL);
cmdline_parm d3d_32bit("-32bit", NULL);
cmdline_parm mouse_coords("-coords", NULL);
cmdline_parm timeout("-timeout", NULL);
cmdline_parm d3d_window("-window", NULL);
cmdline_parm almission_arg("-almission", NULL); //DTP for autoload Multi mission
cmdline_parm gf4fix_arg("-GF4FIX", NULL); //DTP for random tigers GF4fix
cmdline_parm dshowvid_arg("-dshowvid", NULL); //DTP for random tigers GF4fix
Title: fs2_open command line flags
Post by: RandomTiger on October 10, 2002, 10:34:44 am
Oop's! You can see where I've just cut and pasted!
Can we make this sticky or put the info on a site or something?
Title: fs2_open command line flags
Post by: Inquisitor on October 10, 2002, 12:16:29 pm
Yeah, we should make this a standalone document for the readme as well, I'll check it into CVS.
Title: fs2_open command line flags
Post by: Galemp on October 10, 2002, 01:24:51 pm
Quote
Originally posted by Righteous1
cmdline_parm almission_arg("-almission", NULL); //DTP for autoload Multi mission


Can we have this for single-player missions too? Or have an option in FRED: Test current mission?
Title: fs2_open command line flags
Post by: RandomTiger on October 10, 2002, 02:05:18 pm
That would be great for code testing too.
Title: fs2_open command line flags
Post by: DTP on October 10, 2002, 02:33:10 pm
Quote
Originally posted by GalacticEmperor


Can we have this for single-player missions too? Or have an option in FRED: Test current mission?


Well have not much practice in GUI with FRED2, most of the things i changed inside FRED was some hard limits.

heck, I prepared FRED2 for an beamfree all in initial orders checkbox and the result was i could not jump out.

my guees is i screwed up some bit things there.

but i guees i can learn fast.

regarding the singleplayer mission, well fs2 already has a swift way of loading a singleplayer mission.

guees I can tweak it a bit so that it quickloads an arguement passed from commandline.
Title: fs2_open command line flags
Post by: DTP on October 10, 2002, 02:37:05 pm
Quote
Originally posted by Righteous1
*Slaps head*

Should have thought of a command line option myself!  

Here's a list from cmdline.cpp  The names seem to be self-explanatory:



well just in case

Command line options      description

-standalone         Starts a standaloneserver

-nosound         no sound at all, no Sound effects and no music

-nomusic         no music, but sound effects

-startgame         starts a net game as client master uses last pilot,
            DTP NOTE: did not work with the original release by
            volition, had the really annoying side effect of not
            letting you quit out to main hall.
            
            furthermore, it did not take into consideration that the
            last pilot that was used may could have been a single player pilot.
            fixed.
            
-gamename X         useful when used with startgame for setting the name of the game where X is the name

-password X         useful when used with startgame for setting a password of the game where X is the password

-closed            useful when used with startgame for starting with a closed game for whatever reason

-restricted         restricted, hmm, don't know what it does, can only speculate.

-allowabove X         allows ppl with rank above X, where X is the RANK.

-allowbelow X         allows ppl with rank below X, where X is the RANK.

-port X            overrides default port setting and sets port to be X, where x is the port number.

-connect X         Connects to a Game started by someone else On ip X, where X is an valid IP like 192.168.0.1

-multilog         logs chat and events to a file in your Freespace2 directory in multi player

-oldfire         shooting like in Freespace 1 multi player. meaning that Fire will be delayed according to the servers
            respond time(ping) to your PC as client.
            
-clientdamage         Means that the client, when on his screen he does damage, the server accepts this, instead of having
            the server determining if the client is doing damage. (net stuff; ping; lag; prediction etc )

-pofspew         not tested, but i suppose data is spewed out about a POF file. how i do not know yet.

-32bit            32bit instead of 16bit colors. Forcing 32 bit so to speak regardless of current video setting.

-coords            spews out coordinates for the mouse cursor, live on screen. Useful for determining positions
            for ANI files etc etc.
            
-timeout X         the amount of time before a client is booted when no response is received in X seconds, where X is Seconds.

-window            starts the game in a window instead of full screen.

-almission X         starts a net game and auto loads mission X where is the filename of the mission file.
for example in a bat file   DTP NOTE; this is added by me, the mission in question has to be a multi player file and
"fs2dtp.exe almission kickass"   it has to exist. check your spelling carefully. or else the game will crash since it cannot
            find the mission. the extension is not needed.
Title: fs2_open command line flags
Post by: EdrickV on October 10, 2002, 08:23:23 pm
Pofspew makes a text file in the data folder containing stuff like this:

rockeye.pof
RAW
Submodel rockeye-b total : 16 faces
Submodel thruster01b total : 5 faces
Submodel rockeye-c total : 12 faces
Submodel thruster01c total : 3 faces
Submodel rockeye-a total : 46 faces
Submodel thruster01a total : 10 faces
Model total 92
BY LOD

LOD 0
Submodel thruster01a total : 10 faces
Submodel rockeye-a total : 46 faces
TOTAL: 56
TOTAL not counting destroyed faces 56
TOTAL destroyed faces 0

LOD 1
Submodel thruster01b total : 5 faces
Submodel rockeye-b total : 16 faces
TOTAL: 21
TOTAL not counting destroyed faces 21
TOTAL destroyed faces 0

LOD 2
Submodel thruster01c total : 3 faces
Submodel rockeye-c total : 12 faces
TOTAL: 15
TOTAL not counting destroyed faces 15
TOTAL destroyed faces 0

------------------------------------------------------------------------
Title: fs2_open command line flags
Post by: RandomTiger on October 11, 2002, 07:47:12 pm
Another useful thing would be to have a list of compile flags and what they do, which are default, which were made by V and which were put in by us.
Title: fs2_open command line flags
Post by: DTP on October 27, 2002, 06:28:37 pm
From the next release as i just implemented this

fs2_open.exe -mod X where X is the name of you mod directory
will look for additional files in ´../Freespace2/ X /all-legal-sub directories.

all files found there like ani, pcx,tga, tbl, wav will be used

mission files are a bit special, they have to be there as it is right now.

VP in the mod directory is not supported yet, but i know what to do to make them supported.

just commited so that it would be there in case "i would be run over a bus" :D.

all directories must exist, mod_support dont create any yet. A thing that will also come as i gets this tweaked up.

example

fs2_open.exe -mod mymod

will look for additional files in

../freespace2/mymod/
../freespace2/mymod/data/
../freespace2/mymod/data/tables/
../freespace2/mymod/data/missions/

and so on.

VP files are not supported yet because it will look for files
in similar paths inside the VP file, which is not good.

Something i will have to fix, and i beleive i know how.

This will work with every kind of mod out-there.

A real benefit is that when you start your mod for the first time you will kind a be forced to create a new pilot since it looks for pilot files in the /mymod/data/players/ directory. an annoyance is that it asks for CD2 since it beleives this is the first time you run the game, in order to play the intro. could be used for something like run a vidio.

The mod flag, in this case mymod. Must match the directory name to the point. And ofcourse must be a valid directory name. so dont include signs like "!"#¤%&/()=?@£$€{[]}" in your directory name or mod flag.

Some Directories must be there as it is right now.

fs2_open.exe -mymod
where X is mymod

mymod/data/missions/                     :because it looks for mission and Campaign files here only

mymod/data/players/single/                     :because it looks for single player files here only
mymod/data/players/multi/                     i think you know why

not sure on data/players/images and data/players/squad, but just add them to be sure.

anything found in the mod dir will be used instead of filename mathcing what found in the defaults directories or Vp files because fs2_open has this search order for files.

1. Check plain files not packed, meaning that mod directories are first checked if the mod flag is used. And then it checkes the default directories, but it will use those found in the MOD directory because it found them first.

2. Check VP files in an alphabetical order, meaning a file found in AAA.vp will be used instead of the one found in BBB.vp that has a matching filename.

Thats why when you make a packfile and name it XS.vp it will not use whatever found in there that has a matching filename, in another packfile.

Its first come first served. regarding VP files in the same directory.

oh dear, back to coding.

EDIT1------

Basic VP files support has been added, campaign files & missions are not loaded from that vp file however, but all other files that usually are in a VP file is.

note that files found in any VP files that are found in the mod directory will be used instead of those in the freespace2 directory

If more vp files exist in the same mod dir, then it will pick the file that is in the VP file that lexicographically comes first.
----------

when i get it commited

modsupport is now finished. it supports VP files, mission/ campaign files in VP files, and so on

will add some create/check directories funtions later
Title: fs2_open command line flags
Post by: RandomTiger on October 29, 2002, 04:49:27 am
Might as well unsticky this. All the info in here is now in the KBase.
See sig for link.
Title: fs2_open command line flags
Post by: Inquisitor on November 07, 2002, 08:20:59 am
Works for me, was gonna also stick it in the readme to be included with the next exe.