Command Line Options File: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| (3 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
A useful way to specify command line options is to use a text file named < | {{DeveloperNav}} | ||
A useful way to specify command line options is to use a text file named <code style="font-size:12px">options.txt</code> placed in the '''same''' directory as the simulation executable. This text file may be edited so that each command line option is on one line of the file. An example <code style="font-size:12px">options.txt</code> is shown below: | |||
<pre style="color:blue;font-size:16px"> | |||
-x | |||
-l | |||
-notrains | |||
-simspeed | |||
</pre> | |||
The above <code style="font-size:12px">options.txt</code> file enabled Developer mode, logging, disallows trains, and allows free simulation speed. | |||
{{DeveloperNavBottom}} | |||
Latest revision as of 20:38, 27 October 2011
Contents | Developers pages | Command Line Options | Timetables | Scenario Creation | Developing Installers
A useful way to specify command line options is to use a text file named options.txt placed in the same directory as the simulation executable. This text file may be edited so that each command line option is on one line of the file. An example options.txt is shown below:
-x -l -notrains -simspeed
The above options.txt file enabled Developer mode, logging, disallows trains, and allows free simulation speed.
Contents | Developers pages | Command Line Options | Timetables | Scenario Creation | Developing Installers