LAST EDITED ON Dec-04-02 AT 11:44 AM (EST)
Then I have the solution for you! The command-line switch /scaledlevs can help. It allows you to add a multiple to the distances at which the distance levels kick in (as set in the .s file). The usage is /scaledlevs:(multiple) where (multiple) is a percentage value, i.e. /scaledlevs:100 means no change, and /scaledlevs:200 means the distance levels take twice as long to kick in. To use the switch, it needs to be added to the command line for MSTS. Most people call it from a shortcut. The easiest way to add it is to edit the shortcut. This can be done by right clicking on the shortcut and selecting "Properties". The "Target:" field in the shortcut should be of the form
"drive:\path to trainsim\train.exe"
or
"drive:\path to trainsim\launcher.exe" /rungame
If the latter is true, you will need to change it to the prior configuration. Simply add /scaledlevs:(your value here) to the end of the string, after the closed quotes, with at least one space separating the switch from the quotes.Also, if you already have some command line switches, such that it appears as
"drive:\path to trainsim\train.exe" /fsaa /anisotropic
or such, you simply have to add it anywhere in the list of command-line switches.
So the end product will look something like this:
"drive:\path to trainsim\train.exe" /scaledlevs:200
or
"drive:\path to trainsim\train.exe" /fsaa /anisotropic /scaledlevs:200Note: I've been looking for the "optimal" value on my machine such that the distance levels do get utilized, but I don't see much switching up close. A range of 250-300 so far seems promising.I haven't done any stringent tests of adverse effects on framerates, although theory would indicate that they will drop. I didn't see a significant (i.e. visually noticeable) change during my testing. Hopefully I can come up with some info on that later, as well as some of you testing it and posting your results. Scott
Printer-friendly page | Edit | Reply | Reply With Quote | Top