Dan wrote:It is a shame that there is nothing like the old Switchlist generator program.
Chuck - to help scenario makers perhaps you could describe how a 'day of switching' would/ought to take place? The information would certainly be useful and interesting.
Hi! This is the method that I've been taught. Firstly, use the switchers to couple all the required cars. Then pull forward to a point where the last car of the first block is just short of the switch to yard 7. Uncouple and pull forward so that the last car is clear of the switch to yard 7, throw the switch and reverse into yard 7, only going far enough in to let the car closest to the engine clear the switch. Uncouple and go back to the main string of cars. Again, pull forward until the last car of the next block is just short of the switch to yard 7, uncouple and pull forward until last car clears the switch, then reverse to couple to first block the push back to where the car closest to the engine clears the switch. Uncouple, pull forward and repeat. This is the most efficient method, saving time and fuel.
As far as RW IS concerned, this would be done as a FreeRoam Scenario without using the F1 Task List. I would prefer a printable switch list with sufficient info to describe what cars need to be picked up or set out, the locations and time required for the whole operation, but no specific instructions. Miscellaneous cars that need to be moved to complete the switch list must be returned to there original locations. The F1 Task List would be reserved to create paths through automatic switches and set major destinations. Pop-up messages are reserved for clearances and necessary directions from conductor to train crew. This method was used in MSTS with good results, and complicated switching problems can be duplicated, but I don't possess this kind of info.
I'm sure there is more to this then I have described, but this is the general layout for advanced switching scenarios. Cheers; Chuck F.
Edited for typos