Copying Session programming between sesisons, How to?

davemare

Member
I currently have 6 sessions built on my Columbia and Western RR with all of the Driver rules for operations completed. Each session has approx 15 engines and over 100 driver actions per engine, so years of complex programming is completed and tested and operational.

I am now adding Train Schedule and Train orders to the session. The Train Orders use session programming such as Trigger Checks, Messaging, Objectives and Waits. I have programmed the Train Order forms into one session to prototype the solution and have it functioning now.

I would like to copy the session programming from one session to the other 5 so i don't have to recreate all the Train Order forms and content.

I know I could save the current session to create new sessions, but I don't want to loose years of work of getting the Driver Rules operating smoothly.

I tried copying to the current sessions config file, however this doesn't seem to create the programming within the session

Does anyone know which files and location I would need to copy/ change to move the Session programming to an existing session?

Alternatively, does anyone know how to copy Drivers Rules for insertion into an existing session?

thanks

Dave
 
If you open the route+session and go to edit session in the drop-down menu, you can right-click on any entries, copy and paste into a different edit session.
 
It would be useful to able to copy the set of commands for a single driver, but to my knowledge there is no way to do this. You must copy the whole Driver Setup rule. This makes it hard (tedious) to merge instructions for drivers from multiple existing sessions.

Would love to hear that I am wrong!
 
Phil,

I did some wishful checking and sadly we can't do that.

There's a solution for that by using the Schedule Library rule and the companion Copy Commands From driver command.

Create schedules in the Schedule Library just as if you were adding the commands to a driver's schedule. You can group them if you want by division or station routing. I use terminating stations for my groups on one route, i.e., Eastport for example, with all driver schedules going to Eastport are placed under this group. On another route, I used divisions. When setting up the schedules in the Schedule Library, don't put in such things as repeat commands. Other than that, everything works as if you've added the commands to the individual drivers.

Once you've added the driver commands to the schedules in the Schedule Library, you can then copy them and edit them as you need. This is great for multiple drivers following the same route or part of the same route, and really useful for passenger trains.

After all your schedules are created, you can now use them by inserting the Copy Commands From driver command. When you insert this command, you need to choose the source and always use insert from library rather than append. Append never worked even years ago, so it's not a recent issue. Inserting the commands from an existing driver is hit or miss whether it works or not as well and is mostly a miss.

It's highly recommended that you use a wait... 20 seconds command in the beginning of the Copy Commands From. You can chain them up one after another but remember to put in a wait command in between. Outside of the very first which requires the 20 seconds, the others can be quicker than that. I found 5 or 10 seconds works fine for my drivers. The reason for this is to give the commands to load up before the driver reacts otherwise there will be confused AI drivers doing more screwy things than normal.
 
Back
Top