JonMyrlennBailey
Well-known member
The only way I can create a permanent/save-able schedule is to use Driver Setup. Many of my drivers of my trains use the same or similar schedules. There is no copy schedule feature in Driver Setup. It's going to be super tedious to place many command objects for each and every train on each and every schedule line alongside each and every driver by hand! Some long schedules might have 50 or more commands each. I might have 30 or more trains in my Session.
Is there an easy solution to this?
I can't use Trigger Multiple Signals in TS 2022 either.
I found out the hard way that any trains or any drivable vehicles should only be added to the tracks while editing the Session in Surveyor, NOT the ROUTE! I use only Classic Surveyor. I can add trains while editing the Route, but they will not show up in the original Session when the Session is driven or opened up in Surveyor. The original Session is the one I created to be associated with the Route at the time the Route was created. When saving the Route, I cannot save the Route and Session at the same time as an overwrite. I can only save a new DEFAULT Session. The trains added to the Route will show up on the track when the Default Session is opened up but not on the original Session that has a name to match the name given to the Route. In earlier editions of Trainz, I could indeed add trains to the Route and the original Session would recognize them, show them, even if I saved the Route along with a new DEFAULT Session and deleted that DEFAULT Session. I can add other content to the Route such as track, spline, static objects, cameras, rulers, track objects, etc. and the original Session will indeed pick those items up even without saving the original Session along with the Route or creating a DEFAULT Session. If it's something that can be driven, however, it has to be added directly inside the original Session to be kept permanently by that Session.
The Session is made up of Rules, Drivers, Environmental factors as Light, Time and Weather, Commands and Schedules. It should also be made up of drivable vehicles as well. In TS 2022, it is best to keep trains (anything on tracks that can move in Driver under commands or have a Driver assigned to it such as a hobo tent) with the Session layer.
Is there an easy solution to this?
I can't use Trigger Multiple Signals in TS 2022 either.
I found out the hard way that any trains or any drivable vehicles should only be added to the tracks while editing the Session in Surveyor, NOT the ROUTE! I use only Classic Surveyor. I can add trains while editing the Route, but they will not show up in the original Session when the Session is driven or opened up in Surveyor. The original Session is the one I created to be associated with the Route at the time the Route was created. When saving the Route, I cannot save the Route and Session at the same time as an overwrite. I can only save a new DEFAULT Session. The trains added to the Route will show up on the track when the Default Session is opened up but not on the original Session that has a name to match the name given to the Route. In earlier editions of Trainz, I could indeed add trains to the Route and the original Session would recognize them, show them, even if I saved the Route along with a new DEFAULT Session and deleted that DEFAULT Session. I can add other content to the Route such as track, spline, static objects, cameras, rulers, track objects, etc. and the original Session will indeed pick those items up even without saving the original Session along with the Route or creating a DEFAULT Session. If it's something that can be driven, however, it has to be added directly inside the original Session to be kept permanently by that Session.
The Session is made up of Rules, Drivers, Environmental factors as Light, Time and Weather, Commands and Schedules. It should also be made up of drivable vehicles as well. In TS 2022, it is best to keep trains (anything on tracks that can move in Driver under commands or have a Driver assigned to it such as a hobo tent) with the Session layer.
Last edited: