|
|
| (21 intermediate revisions by 11 users not shown) |
| Line 1: |
Line 1: |
| − | ''By [[user:Phazorx|PhazorX]], written up by [[user:OwenS|OwenS]], this is a development from the concept LBR mainlines''
| + | #REDIRECT[[Shift Mainline]] |
| − | ==Shift Mainlines==
| + | |
| − | [[Image:Shift_Mainline.png|thumb|right|200px|Design of a junction]]
| + | |
| − | Shift Mainlines are a new concept that has only recently been developed. '''Warning: It has not been tested thoroughly yet - It is currently being tested in a game on the public server'''
| + | |
| − | | + | |
| − | Shift Mainlines remove much of the complexity of building junctions on a traditional mainline by only requiring that trains be injected into the left most lanes. The design causes YAPF to prefer the inner lanes, and as such if the inner lane is free YAPF will cause the train to shift right.
| + | |
| − | | + | |
| − | Trains in the second inner most lane are shifted into the inner most lane first, to ensure trains in the outer lanse get a chance to shift into the inner lanes, and this is repeates getting further out for as many lanes as exist. The outer lane should now be mostly free, which should result in minimum waiting at prios by trains.
| + | |
| − | | + | |
| − | This is especially good for games in which very fast trains are used, like the default Maglevs. Instead of holding up the flow, or requiring rediculous prios, they instead go into the outer lane which should be mostly free. In addition, trains get a chance and will always try to move into a more inner lane to avoid them.
| + | |
| − | | + | |
| − | This ensures that both flow and speed on the network are increased dramatically
| + | |
| − | | + | |
| − | ''More text will be added as the research continues''
| + | |
| − | | + | |
| − | {{R&D_header|Switch Mainlines}}
| + | |
| − | {{R&D_content|Use first implementation|PhazorX and OwenS|done|See above|claimed|Waiting for a plan to be chosen in public server game #44|unclaimed|Waiting for plan|N/A}}
| + | |
| − | {{R&D_footer}}
| + | |
| − | | + | |
| − | ===Shift Mainline Implementation===
| + | |
| − | more is coming later [[User:Phazorx|Phazorx]] 06:43, 17 June 2007 (UTC)
| + | |
| − | | + | |
| − | Network design keypoints:
| + | |
| − |
| + | |
| − | SLHs as often as possible and as efw as needed
| + | |
| − | ML lanes are separated by one tile
| + | |
| − | switchers are to be between / before any SLHs
| + | |
| − | any part of ML can be easily expanded by adding outter lanes with only shifter replication
| + | |
| − | shifter bypass is exactly TL
| + | |
| − | shifter window is about TLx2
| + | |
| − | ML exits to SL from ALL lanes
| + | |
| − | | + | |
| − | ====two lane mainline====
| + | |
| − | [[Image:SML2-SLH.PNG|thumb|200px|SML]]
| + | |
| − | [[Image:SML2-Shifter.PNG|thumb|200px|SML]]
| + | |
| − | | + | |
| − | TBD
| + | |
| − | | + | |
| − | | + | |
| − | | + | |
| − | | + | |
| − | | + | |
| − | | + | |
| − | | + | |
| − | | + | |
| − | | + | |
| − | | + | |
| − | | + | |
| − | | + | |
| − | | + | |
| − | | + | |
| − | | + | |
| − | | + | |
| − | | + | |
| − | | + | |
| − | | + | |
| − | | + | |
| − | | + | |
| − | | + | |
| − | | + | |
| − | | + | |
| − | | + | |
| − | | + | |
| − | | + | |
| − | | + | |
| − | | + | |
| − | | + | |
| − | | + | |
| − | | + | |
| − | | + | |
| − | | + | |
| − | | + | |
| − | | + | |
| − | | + | |
| − | | + | |
| − | | + | |
| − | | + | |
| − | | + | |
| − | | + | |
| − | | + | |
| − | | + | |
| − | | + | |
| − | | + | |
| − | | + | |
| − | | + | |
| − | | + | |
| − | | + | |
| − | | + | |
| − | | + | |
| − | | + | |
| − | | + | |
| − | | + | |
| − | | + | |
| − | | + | |
| − | .
| + | |
| − | | + | |
| − | ====three lane implementation====
| + | |
| − | [[Image:SML3-SLHa.PNG|thumb|right|200px|SML]]
| + | |
| − | [[Image:SML3-SLHb.PNG|thumb|right|200px|SML]]
| + | |
| − | [[Image:SML3-2xShifter.PNG|thumb|right|200px|SML]]
| + | |
| − | | + | |
| − | TBD
| + | |
| − | | + | |
| − | ==Situation switcher==
| + | |
| − | ''Concept by [[user:XeryusTC|XeryusTC]]''
| + | |
| − | [[Image:Shift_mainline.png|thumb|right|200px|Alternate design]]
| + | |
| − | Don't use stations to force trains on other lines, use the current situation instead. This type of shifting forces a train on line A to go to line B when there is no upcomming train AND there is a train joining the mainline on line A at that moment.
| + | |
| − | Prio 1 should be considered as a normal prio but doesn't have to be as long to prevent the train from joining when there are upcomming trains. Prio 2 only has to be as long as the TL plus enough space to allow the train on line A to go over the 2 tile diagonal switch line. This way no train will ever block the other line while switching when all trains are at top speed.
| + | |
| − | | + | |
| − | The benefit of this approach is that you don't force trains to go onto the other line under usual circumstances, you will get a properly balanced ML. You also don't need to have a big priority line for every lane as in a normal balancer, but 2 smaller ones instead.
| + | |
| − | | + | |
| − | {{R&D_header|XeryusTC's switcher}}
| + | |
| − | {{R&D_content|Use first implementation|XeryusTC|done|See above|wip|First implementation build, waiting for trains to go over it|claimed|Testing|Will be taken a look at later}}
| + | |
| − | {{R&D_footer}}
| + | |
| − | | + | |
| − | [[Category:Research]]
| + | |
