"Routes"
Posted: 30 Jul 2012 16:06
Hi guys
Not totally sure if this exists, or if I'm gonna have time for this, but it's something I'd like to see in game so I figure it's worth a discussion if anyone has any thoughts. I think it would fit in nicely with some of the timetable/cargodist type development at the moment, and frankly, I just want it myself so I'm willing to give it a go. I'll give it a suitably convoluted name and acronym shortly. Maybe Audigex's Route Corporation (ARC).
Basically I'm wanting to make timetables/routes more user friendly - sort of an expansion of the shared orders system. My last TTD game was on the UK map, and I found that I spent most of my time trying to fix timetable separation and routes. What I'm thinking of doing is allowing the user to setup route segments (in the same way as you'd give a train orders) between major junctions or destinations - ie
London-Birmingham
Birmingham-Manchester
Manchester-Carlisle
Birmingham-Liverpool
Birmingham-Carlisle
Carlisle-Edinburgh
Carlisle-Glasgow
(this is just discussing a few routes, in actuality it is more likely to include things like Manchester-Preston, Preston-Carlisle, Preston-Blackpool etc, smaller segments). These can be shared by multiple super-segments, but should rarely (possibly never) overlap. This part may be entirely/partially auto-generated, I'm not sure.
These are then combined into super-segments/routes. ie (London-Birmingham, Birmingham-Carlisle, Carlisle-Glasglow) which essentially make up one journey. This may also be auto-generated (ie the user chooses London and Glasgow as endpoints, and the system suggests routes via Birmingham and Carlisle, or Birmingham, Manchester and Carlisle, based on segments). Each train can be added to a route, similar to shared orders, and the route edited separately to the shared orders. Other statistics may also be available based on this. These may be made up of either segments or smaller super-segments, if you will. ie they can be used within other larger segments, but modifying the smaller segment changes the larger segment.
A final option/aspect would be combining super-segments into optional partial networks or similar - ie a pendolino circuit may include routes London to Liverpool, Manchester, Glasgow, Edinburgh and Birmingham. Perhaps specifying that there are 7 departures a day from London (Birmingham, Glasgow, Manchester, Edinburgh, Birmingham, Liverpool, Glasgow) or merely providing a circuit.
This would allow more powerful timetables and routing (plus modifying of several routes/shared orders at once), in exchange for a bit of thought when setting up the maps (hence wondering how much of the segment stage can be automated. My first thought on this is that it could be set up to allow the user to set the "full" route first - defining the entire route London-Glasgow, then going back through the route and "splitting" it into a tree. ie "split at <station>" and then build a new sub-tree from there to Edinburgh. These trees could then be merged back into the main trunk later, or finish at a new end-point.
I imagine it will take a fair bit more thought for the detailed planning of the system (although a lot of it, in my head, is already looking logical in terms of linked lists and trees), but it seems workable to me. Can anyone think of any major objections/obstacles I'll have to overcome, or any other ideas/thoughts/discussions on the idea?
Cheers
Not totally sure if this exists, or if I'm gonna have time for this, but it's something I'd like to see in game so I figure it's worth a discussion if anyone has any thoughts. I think it would fit in nicely with some of the timetable/cargodist type development at the moment, and frankly, I just want it myself so I'm willing to give it a go. I'll give it a suitably convoluted name and acronym shortly. Maybe Audigex's Route Corporation (ARC).
Basically I'm wanting to make timetables/routes more user friendly - sort of an expansion of the shared orders system. My last TTD game was on the UK map, and I found that I spent most of my time trying to fix timetable separation and routes. What I'm thinking of doing is allowing the user to setup route segments (in the same way as you'd give a train orders) between major junctions or destinations - ie
London-Birmingham
Birmingham-Manchester
Manchester-Carlisle
Birmingham-Liverpool
Birmingham-Carlisle
Carlisle-Edinburgh
Carlisle-Glasgow
(this is just discussing a few routes, in actuality it is more likely to include things like Manchester-Preston, Preston-Carlisle, Preston-Blackpool etc, smaller segments). These can be shared by multiple super-segments, but should rarely (possibly never) overlap. This part may be entirely/partially auto-generated, I'm not sure.
These are then combined into super-segments/routes. ie (London-Birmingham, Birmingham-Carlisle, Carlisle-Glasglow) which essentially make up one journey. This may also be auto-generated (ie the user chooses London and Glasgow as endpoints, and the system suggests routes via Birmingham and Carlisle, or Birmingham, Manchester and Carlisle, based on segments). Each train can be added to a route, similar to shared orders, and the route edited separately to the shared orders. Other statistics may also be available based on this. These may be made up of either segments or smaller super-segments, if you will. ie they can be used within other larger segments, but modifying the smaller segment changes the larger segment.
A final option/aspect would be combining super-segments into optional partial networks or similar - ie a pendolino circuit may include routes London to Liverpool, Manchester, Glasgow, Edinburgh and Birmingham. Perhaps specifying that there are 7 departures a day from London (Birmingham, Glasgow, Manchester, Edinburgh, Birmingham, Liverpool, Glasgow) or merely providing a circuit.
This would allow more powerful timetables and routing (plus modifying of several routes/shared orders at once), in exchange for a bit of thought when setting up the maps (hence wondering how much of the segment stage can be automated. My first thought on this is that it could be set up to allow the user to set the "full" route first - defining the entire route London-Glasgow, then going back through the route and "splitting" it into a tree. ie "split at <station>" and then build a new sub-tree from there to Edinburgh. These trees could then be merged back into the main trunk later, or finish at a new end-point.
I imagine it will take a fair bit more thought for the detailed planning of the system (although a lot of it, in my head, is already looking logical in terms of linked lists and trees), but it seems workable to me. Can anyone think of any major objections/obstacles I'll have to overcome, or any other ideas/thoughts/discussions on the idea?
Cheers