Creating Activity Behaviors in Timetable Mode
#21
Posted 20 March 2022 - 03:46 PM
As long, as Your project is intended to be published.
Otherwise, negotiation with route author(s) will be needed - to issue a patch, coming with Your timetables pack.
I'd at least ask them (if possible) about the reason (if it only was no by occasion), for them to place those markers in such odd manner.
This way, You may correct a missed mistake - for common benefit.
#22
Posted 21 March 2022 - 12:21 AM
Weter, on 20 March 2022 - 03:46 PM, said:
As long, as Your project is intended to be published.
Otherwise, negotiation with route author(s) will be needed - to issue a patch, coming with Your timetables pack.
I'm in touch with Dave Babb, the owner of Making Tracks. He's been helpful to Open Rails in the past, so I hope he would be again.
#23
Posted 21 March 2022 - 02:06 AM
Gwyd, on 20 March 2022 - 01:12 PM, said:
Use $extendplatformsignal, and add /closeup to the $triggers command in the #dispose field. That will bring in the train closer to the buffer stops.
Regards,
Rob Roeterdink
#24
Posted 22 March 2022 - 11:25 AM
#25
Posted 25 March 2022 - 04:23 PM
I discovered this when testing some services, and I reliably found the 3 minutes timing for Lewisham-New Cross to be very hard to keep up with. The route has London Bridge-Hither Green as a near dead-straight line all the way, where as in reality the line to Lewisham is almost straight but the line to Hither Green takes a rather sharp southerly turn. This funny geography has some rather funny implications, such as the notably straight Tonbridge-Redhill railway being, well, not straight. I've overlaid the map from the track viewer (black) on a map of the actual railway (pink)
map.jpg (52.61K)
Number of downloads: 3
Anyway, I'll press ahead with the timetabling. The only slight issue is the inaccurate track layout in a couple of locations, namely Lewisham, where a 4 track arrangement with a double crossover has turned into a diamond crossing, means that not all the trains will necessarily work. Oh well. We'll see what comes of it
#26
Posted 25 March 2022 - 11:40 PM
You are welcome for sharing gained experience of working around such issues.
What about posted map comparation, I feel disappointment, how inaccurate that payware add-on was with topographic base.
People paid their money for real-looking route, which prototype might be very familiar to some of them.
As a result, that's no possible to define real timetables on it...
Or did they posted a disclaimer, something as "this is only semi-real route/fictious route, based on ... network map"? That would be fair.
#27
Posted 26 March 2022 - 02:18 AM
Now I have a Route with the correct milage, were I can establish working timetables.
#28
Posted 07 November 2022 - 05:43 AM
#29
Posted 16 July 2023 - 10:31 PM
Attached File(s)
-
Sig1350.JPG (20.29K)
Number of downloads: 0 -
Train148.JPG (4.02K)
Number of downloads: 0
#30
Posted 20 July 2023 - 01:33 AM
Sadly, someone (not me!) changed the signal script code but did not properly update the code for the debug functions, which means these rather essential functions are no longer available.
Presently, due to this (serious) oversight, the program will no longer compile when these debug functions are activated.
Regards,
Rob Roeterdink