|
Being curious myself, I did a little research and experimentation. If this has been posted before, please excuse me as this is the only sky-conductor thread that I could find on this forum.
Yes, Sky-Conductor-2 can be used on WP3, but not directly. Sky-Conductor works by writing new X.env files to the ENVFILES of the route directory. However, it uses the "default" names, such as UKSUN.env, etc. 3DTrains in WP3 used more descriptive names, such as SummerClear.Env. Thus, even though SC writes the files for the requested sky to the directory the naming convention prevents that change from being seen by the sim.
To make it work, you have to go back to the main directory for SC and add the appropriate named X.env file to the ones for the route. For instance, for breeze, you go to Sky-Conductor_2\a-breeze\WP3\ENVFILES and make a copy of one of the X.env files there and then rename that copy to <seasoncondition>.env for example, springclear.env. Once you use the SC control board and select breeze, that will then overwrite the springclear.env in the WP3 files with the one you created above and you will have breeze skys when you select spring clear on the MSTS "drive train" selection screen.
There are serious drawbacks to this. One is that you would have to make a new file for every <seasoncondition>.env you want to have that specific SC sky pertain to. For example, the above sky would only show up in spring clear, not summer clear unless you made a file for that one also.
The second is that SC uses the original default aces so you will need to copy those into the WP3 ENV files to.
The third is that once selected that sky stays there until it is overwritten by another choice. Definitely make a copy of the original X.env files. Also, this kind of work is painstaking and detailed and not for the weak of heart. Some experience with MSTS file structure would also be helpful.
Jack W
|
Feather River Route help
Jun 26 2008, 6:01 AM
