[RandomTiger]

I would like to change the way the launcher works slightly but I thought I'd better check it out with people just incase.

I would like to change it so the command line you assemble using the launcher is picked up by fs2_open when you *dont* run the exe through the launcher as well.

This means you can setup the launcher once and run the exe without it (but with those options) next time. It would 'combine' the launcher param's with any new params that might come from a shortcut to an exe so you can have a mixure of both.

[RandomTiger]

Ooops, I meant to put this in the public forum.
Would someone be kind enough to move it for me?

[Kazan]

you can already do with

write to /data/cmdline.cfg

[RandomTiger]

The launcher could just setup that file then, but the question is should it work like that from the launchers point of view.

I'm trying to make it more user friendly incase this project is subjected to the wider audience that might be coming.

[Goober5000]

Moved.

I'm just worried that someone will run the program outside the launcher, expecting no command-line flags, and be surprised when they show up.

On the other hand, someone could run it, expecting the command-line flags to work, and be surprised when they don't.

[Fury]

And the answer to this dilemma:
Create a setting which says something like this:
"Use following command line parameters each time you start fs2_open.exe"
*Enabled
*Disabled


Just my two cents tho.

[Lightspeed]

Originally posted by Mr. Fury
And the answer to this dilemma:
Create a setting which says something like this:
"Use following command line parameters each time you start fs2_open.exe"
*Enabled
*Disabled


Just my two cents tho.

[Taristin]

I see no reason why it shouldn't do this. Go for it.

Edit: But can you also make it so that when you select which EXE you are using, it filters the files by *.exe, the current has the option, but it doesn't work. Thx.

[KARMA]

I'm a bit perplex...
it isn't a big deal to open the launcher in order to run the game, and if you want exe specific command lines, you still can create a specific exe, right?
now you can have
-no paramters (launch the exe directly)
-specific parameters (create a specific exe)
-standard parameters (use the launcher)
In your way you would have to create a specific exe with no commands, if you don't want them.
Maybe you could set up a button like "change exe's specific parameters" that will export the parameters setted in the launcher to the exe, so those who want to launch directly the game with command lines, will be able to do that, and they will be able to step back re-opening tha launcher, cleaning the commands and pressing the new button again

[Drew]

Originally posted by Mr. Fury
And the answer to this dilemma:
Create a setting which says something like this:
"Use following command line parameters each time you start fs2_open.exe"
*Enabled
*Disabled

sounds good to me.

[RandomTiger]

A tickbox that does that is the best solution: best of both worlds.

[Trivial Psychic]

Oh my God!  I feel like such an IDIOT!  I've just been launching FS_Open with its own icon.  I thought that the launcher would apply the command line tags whenever I launched that exe.  THAT's why ht&l and 32bit stuff haven't been working on my system.  THAT's why the _t build keeps crashing... the -htl flag wasn't being read by my icon.  Now there's a load off my shoulders.  So in short, I think this is a good idea.

[Update]

I've been trying it out with varying degrees of success, mostly good however.  Check the Nebulas-being-pinched thread for more details on how well I did.

Later!

[WMCoolmon]

For each parameter, give three options - persistent, enabled, and disabled. Persistent parameters are always run when fs2_open starts; enabled ones when launched from the launcer; disabled, never.

Oh, and I suggest adding a button to make all enabled parameters persistent.

IMHO, of course.