General Question Command line parameters

[Danzig70]

Are there command line parameters that can be added to the orbiter.exe shortcut? I would like to load specific scenarios from a hyperlink.

The reason for this is that I would like to use the Orbiter Sim for traveling between places and then use something else for when you get there. (Like the space station)

Thanks.

 

[orb]

None that I know.

 

[martins]

The only interesting one is

-s <scenario-path>

to launch a scenario directly, bypassing the launchpad. Path is relative to $orbiterroot\Scenarios. Trailing .scn must be omitted. Enclosing the path in double quotes is a good idea.

There are a few other undocumented arguments, but they are either deprecated or not very useful for users.

 

[n122vu]

The only interesting one is

-s <scenario-path>

to launch a scenario directly, bypassing the launchpad. Path is relative to $orbiterroot\Scenarios. Trailing .scn must be omitted. Enclosing the path in double quotes is a good idea.

There are a few other undocumented arguments, but they are either deprecated or not very useful for users.

I like this. I created a second desktop shortcut to load the current state scenario, so I can easily pick up right where I last left off if I closed in the middle of a mission/activity.

Thanks for sharing!

Regards,
n122vu

 

[martins]

I forgot to mention: using the above syntax with -s (lower-case) terminates orbiter on closing the simulation session, independently of what shutdown option you have selected, while -S (capital) uses the default shutdown option (usually going back to the launchpad).

 

[Danzig70]

I forgot to mention: using the above syntax with -s (lower-case) terminates orbiter on closing the simulation session, independently of what shutdown option you have selected, while -S (capital) uses the default shutdown option (usually going back to the launchpad).

Great news! Thank you.

 

[Spacethingy]

Awesome! Just what I wanted! :thumbup:

Perhaps I should mention that the .bat has to be in the Orbiter folder to work...

 

[agentgonzo]

Awesome! Just what I wanted! :thumbup:

Perhaps I should mention that the .bat has to be in the Orbiter folder to work...

No it doesn't, you just need to set the target path of any shortcut to be the orbiter path.

 

[Spacethingy]

No it doesn't, you just need to set the target path of any shortcut to be the orbiter path.

It does for me. If it isn't, it finds the Orbiter .exe, but not the scenario you want - end results is a crash, and a message in the log, "can't find scenario".

 

[jangofett287]

because it is probably looking in the working directory. its no problem, you just need to add the following line before that command:
cd <ORBITER_ROOT>, eg:cd C:\Orbiter or what ever

 

[dougkeenan]

orbiter -s "(Current state)"

nice

 

[Ripley]

I was going to post this in the D3D9 thread, but realized it's more something for Dr. Martin himself:
Is it possible to make "orbiter_ng.exe" support command line switches like detailed in post #3?

I've tried this cmd file, but it doesn't work (it opens Launchpad though):

orbiter_ng -s "(Current state)"

whereas this one works well:

orbiter -s "(Current state)"

 

[orb]

I was going to post this in the D3D9 thread, but realized it's more something for Dr. Martin himself:
Is it possible to make "orbiter_ng.exe" support command line switches like detailed in post #3?

Try launching it this way from the Orbiter's root:

Modules\Server\orbiter.exe -s "(Current state)"

Anyway, passing parameters from the orbiter_ng wrapper to actual Orbiter process is considered.

 

[Ripley]

Thanks it works...though I don't understand why, since in that folder there's only "orbiter.exe"!

 

[orb]

Thanks it works...though I don't understand why, since in that folder there's only "orbiter.exe"!

Orbiter uses the working directory to read its configuration (and the same set paths of other its components). The Modules/Server/orbiter.exe is the actual non-graphics Orbiter server. Orbiter_ng is only a simple program which is only used to launch the Modules/Server/orbiter.exe with the working path set to Orbiter's root directory, nothing more.

 

[Topper]

For debuging mode with VS, it would be great if there could be a parameter to launch Orbiter in windowed mode, because I have to kill the task of VS if the debugger stop the program in full screen mode (because I forgott to change the video mode to Window)...

Just a small wish ...