What startup parameters can be set for Oolite?

[JazHaz]

In the thread, Problem with R4665, Kaks wrote:

In windows you can add -fullscreen to Oolite-Trunk's shortcut (so that instead of pointing at C:\Oolite-Trunk\oolite.app\oolite.exe it'll point at C:\Oolite-Trunk\oolite.app\oolite.exe -fullscreen) and Oolite will start normally: no inconsistent states, and the game will respond to normal input.

I currently start Oolite with -nosplash as a parameter. Is there an order in which parameters should be put, or can they be in any order?

What other parameters can be used? I can't find a list on the wiki.

[Kaks]

Can be in any order, and override your configuration settings.

As far as I know there are 3 command line parameters: -splash -nosplash & -fullscreen. In case you type both -splash & -nosplash, -nosplash 'wins'.

I seem to dimly recall seeing them on the wiki, under the 'running Oolite' heading, but I might be remembering wrong...

[another_commander]

There is also the -load [full path to savefile] parameter, which starts up Oolite with the savefile specified automatically loaded.

[JazHaz]

Thanks for those. Are there any others?

I have added a section about these to the wiki page, Hidden Settings In Oolite.

I don't know if these parameters work on Mac and Linux (or even how to do that), so I've left out those for now.

[JazHaz]

I seem to dimly recall seeing them on the wiki, under the 'running Oolite' heading, but I might be remembering wrong...

Looked at the four "running Oolite" pages on the wiki, but there is nothing about the parameters on there.

Have also previously searched for "nosplash" on there with no hits.

[Kaks]

Thanks for that!

[JazHaz]

There is also the -load [full path to savefile] parameter, which starts up Oolite with the savefile specified automatically loaded.

Try as I might, I cannot get this to work.

I have the following in the shortcut target field:
C:\Oolite-Trunk\oolite.app\oolite.exe -nosplash -fullscreen -load [\oolite-saves\Poseidon.oolite-save]

I have tried the -load parameter with & without a space, with the full path ie
C:\Oolite-Trunk\oolite.app\oolite-saves\Poseidon.oolite-save
and with the path in quotation marks (""). I have also tried without the path, ie just [Poseidon.oolite-save]

What is happening is that Oolite loads and presents me with the Load Previous Commander (Y/N) screen. Either I press Y and get the file selector, or I press N and get Jameson loaded.

I have also checked my log, and I am seeing an error in the header:

Code: Select all

11:34:12.750 [log.header]: Opening log for Oolite development version 1.75.4.4668 (x86-32 test release) under Windows at 2011-12-02 11:34:12 +0000.
2 processors detected.
Build options: spoken messages, mass/fuel pricing, JavaScript console support, OXP verifier, localization tools, debug GraphViz support, JavaScript profiling.

Note that the contents of the log file can be adjusted by editing logcontrol.plist.

11:34:12.750 [gnustep]: 2011-12-02 11:34:12.750 oolite[148] autorelease called without pool for object (0x15ddf00) of class GSCBufferString in thread <NSThread 0x10adf90>

[Kaks]

Those square brackets are to blame!

C:\Oolite-Trunk\oolite.app\oolite.exe -nosplash -fullscreen -load c:\oolite-trunk\oolite.app\oolite-saves\Poseidon.oolite-save

should work (yep, we're in windows, so we can ignore upper/lower cases...

[another_commander]

What Kaks said. The command line used works for me too.

Edit: The GNUstep error is indeed present though. I will commit a small fix and would like to hear if all is still good after testing.

[JazHaz]

Those square brackets are to blame!

C:\Oolite-Trunk\oolite.app\oolite.exe -nosplash -fullscreen -load c:\oolite-trunk\oolite.app\oolite-saves\Poseidon.oolite-save

should work (yep, we're in windows, so we can ignore upper/lower cases...

What Kaks said. The command line used works for me too.

Edit: The GNUstep error is indeed present though. I will commit a small fix and would like to hear if all is still good after testing.

I can report that removing the square brackets worked for me too. EDIT: have updated the wiki for this too.

I checked the log again, after it sucessfully loaded my game (Commander Poseidon is my usual commander name), but got four errors this time:

Code: Select all

13:42:35.968 [gnustep]: 2011-12-02 13:42:35.968 oolite[2040] autorelease called without pool for object (0x136bae8) of class GSCBufferString in thread <NSThread 0x10a91c0>

13:42:35.968 [gnustep]: 2011-12-02 13:42:35.968 oolite[2040] autorelease called without pool for object (0x1318628) of class GSCSubString in thread <NSThread 0x10a91c0>

13:42:35.968 [gnustep]: 2011-12-02 13:42:35.968 oolite[2040] autorelease called without pool for object (0x136df78) of class GSCInlineString in thread <NSThread 0x10a91c0>

13:42:35.968 [gnustep]: 2011-12-02 13:42:35.968 oolite[2040] autorelease called without pool for object (0x1316c98) of class GSCInlineString in thread <NSThread 0x10a91c0>

Will look out for the fix in the next nightly, and report back.

[JazHaz]

Are the parameters the same for Mac & Linux? I assume that when using the terminal on Linux you just type the parameters after the application, but what about on the desktop?

[RyanHoots]

Are the parameters the same for Mac & Linux? I assume that when using the terminal on Linux you just type the parameters after the application, but what about on the desktop?

The -load parameter doesn't work for me on Linux (Fedora 14). Not sure about the others. Of course, I've only tried using the launchers, it might indeed be a terminal-only thing, or I might have the syntax wrong. Here's my launcher's command to execute:

Code: Select all

/home/ryan/GNUstep/Applications/Oolite/oolite -load /home/ryan/oolite-saves/Ryan Hoots.oolite-save

[Mauiby de Fug]

The space in your save name is probably the reason...

[RyanHoots]

The space in your save name is probably the reason...

/home/ryan/GNUstep/Applications/Oolite/oolite -load "/home/ryan/oolite-saves/Ryan Hoots.oolite-save" didn't work, either. Oolite is just ignoring the -load parameter... I need to do some more testing.

Edit #1: -nosplash works. So maybe I need to rename my savefile.
Edit #2:Yep, renaming my savefile to RyanHoots.oolite-save worked.