#openttdcoop wiki - User contributions [en]

User:Zerpa

2010-03-17T23:13:53Z

Zerpa: Created page with '==My Person== '''Born:''' 1977 '''Home:''' {{flag|dk}}, http://en.wikipedia.org/wiki/Aalborg '''Email:''' [mailto:zerpa.openttdcoop@belunktum.dk zerpa.openttdcoop@belunktum.…'

==My Person==
'''Born:'''
1977

'''Home:'''
{{flag|dk}}, http://en.wikipedia.org/wiki/Aalborg

'''Email:'''
[mailto:zerpa.openttdcoop@belunktum.dk zerpa.openttdcoop@belunktum.dk]

'''Started playing TTD:'''
I don't remember exactly, but probably some time around 1995-6. Probably played 100h+ at this time and then some more on and off again over the years. Rediscovered OpenTTD November 2009 after my gaming PC stopped working :P

'''Joined #openttdcoop:'''
December 2009.

'''Specialist on:'''
Building stuff that's against the rules when i'm drunk and tired.

'''Prefers:'''
Back-to-the-basic games. Everyone doing their own little area of the map, with help and inspiration from others.

== Ideas ===

* [[Two-way_Prio]]
* [[Auto-refilled Self-regulating Pick-up Station]] -- See PSG 176 and 177.

Community:Members

2010-03-17T23:03:42Z

Zerpa:

__NOTOC__
==Active Members of #openttdcoop [20]==
*{{User|Ammler|ch}}, the one who dances with the newgrfs '''*'''
*{{User|Combuster|nl}} joins and parts the whole day '''*'''
*{{User|Hylje|fi}}, the silent guy always and never around.
*{{User|KenjiE20|uk}}, the master of puppets, pulling your strings '''*'''
*{{User|Mucht|at}}, the oldie who controlls our community from background.'''*'''
*{{User|ODM|nl}}, the innocent ''black'' lamb of #openttdcoop '''*'''
*{{User|Osai|de}}, doctor of the web and autopilot, who can hit back, if needed '''*'''
*{{User|Phazorx|iru}}, what does a communist in the tycoon world?
*{{User|planetmaker|de}}, Make(file) newgrfs and patch packs '''*'''
*{{User|Progman|de}}, builds bigger networks on his Pentium2 at home, than 20 members on publicserver. '''*'''
*{{User|SmatZ|cz}}, pest-controller on all levels of OpenTTD(coop) '''*'''
*{{User|^Spike^|nl}}, the last Dutchy
*{{User|StarLite|nl}} master of the magic roundabout that everybody fears ;-)
*{{User|thgergo|hu}}, the one who builds bridges
*{{User|Thraxian|us}}, makes some little members
*{{User|tneo|nl}}, the spelling angel '''*'''
*{{User|V453000|cz}}, the network construction consultant
*{{User|valhallasw|nl}}, BOFH, Wiki-god and mainly werkloos '''*'''
*{{User|XeryusTC|nl}}, Rebellous doing-stuff-differently-from-convention type of guy '''*'''
''Note: '''*''' Admins have shell access to our servers, all others have rcon access''

==Honorary Members of #openttdcoop [3]==
*{{User|Brianetta|uk}} (our amiable host who is responsible for making #openttdcoop to such a vital community it is today) '''*'''
*{{User|Phoenix the II|nl}} (our host for the most busy [http://www.openttdcoop.org/blog/public-server/ PublicServer], thanks to him, we don't need to finish a game, because of the server limits.)
*{{User|TrueLight|nl}} (for being a bugfixer over ... a long time ;-) )

==Currently Inactive Members of #openttdcoop [8]==
*{{User|Adm.Spock|nl}}
*{{User|dp|de}}
*{{User|e1ko|cz}}
*{{User|Guru3|se}}
*{{User|Kommer|nl}}, we lost his exclusive love to openttd
*{{User|Mark|nl}} Currently on a trip around the world, expecting to be back in 2012
*{{User|ottd-king|uk}}
*{{User|Piratejerk|ca}}
*{{User|xahodo|nl}}

==The usual suspects around the Public Server [56]==

{|
|-
| valign="top" |
*{{User|A3aan|nl}}
*{{User|Addi|ch}}
*{{User|Alanin|de}}
*{{User|AlexanderB|nl}}
*{{User|Andyp|us}}
*{{User|AntB|uk}}
*{{User|Atdt}}
*{{User|Avdg|be}}
*{{User|Bennythen00b|no}}
*{{User|Chris booth|uk}}
*{{User|Clifs|us}}
*{{User|csuke|uk}}
*{{User|Damalix|fr}}
* {{User|DCritic|us}}
*{{User|DJNekkid|no}}
*{{User|draconnier|lu}}
*{{User|einKarl|de}}
*{{User|Elske|nl}}
*{{User|Farden|fr}}
*{{User|Floffe|se}}
*{{User|fmauNeko|fr}}
*{{User|Fuco|sk}}

|                  
|valign="top" |
*{{User|Giles|uk}}
*{{User|Gleeb|uk}}
*{{User|h3rzb1ut|de}}
*{{User|Hans|nl}}
*{{User|Intexon|cz}}
*{{User|Kejhic|cz}}
*{{User|Kirov|ar}}
*{{User|Kolo|pl}}
*{{User|Levi|de}}
*{{User|LittleMikey|au}}
*{{User|LordAzamath|ee}}
*{{User|mensi|ch}}
*{{User|Microshit|nl}}
*{{User|mitooo|fr}}
*{{User|mixrin|ru}}
*{{User|narc|ro}}
*{{User|Nickman|be}}
*{{User|OwenS|uk}}
*{{User|Petert|us}}
|                  
|valign="top" |
*{{User|Pikita|uk}}
*{{User|RMJ|dk}}
*{{User|Rob|us}}
*{{User|S m w|de}}
*{{User|sbn|be}}
*{{User|Sedontane|uk}}
*{{User|Talonius|uk}}
*{{User|Tautrimas|lt}}
*{{User|Thijs|nl}}
*{{User|thomashauk|uk}}
*{{User|Tim|de}}
*{{User|Torben Paw|dk}}
*{{User|Tussengas|nl}}
*{{User|Walle|be}}
*{{User|Wouterr|be}}
*{{User|Zakjan|cz}}
*{{User|ZarenorDarkstalker|us}}
*{{User|Zerpa|dk}}
*{{User|Zuu|se}}

|}
''And of course all the others above!''

== Exsuspects & retired members [51] ==
If you are on the ex-suspects list and you start playing again, please move yourself up to the suspects list !
If you are still active and on the ex-suspects list, sorry for the moving :) we sometimes cannot find an IRC log of you while you are still active

{|
|-
| valign="top" |
*{{User|Alendo|no}}
*{{User|Bob27|us}}
*{{User|ChrisM|de}}
*{{User|Cipri|nl}}
*{{User|Dark_Link|se}}
*{{User|Davil|at}}
*{{User|dihedral|de}}
*{{User|Doke|de}}
*{{User|Dopefish|de}}
*{{User|eJoJ|no}}
*{{User|EmiT|cz}}
*{{User|Franco|hu}}
*{{User|Gamer|nl}}
*{{User|Godde|no}}
*{{User|Green-devil|dk}}
*{{User|hdp|us}}
*{{User|hzzzln|de}}

|                  
|valign="top" |
*{{User|Ichi|nl}}
*{{User|Ihmemies|fi}}
*{{User|itsnotvalid|hk}}
*{{User|Jinx|be}}
*{{User|John|sk}}
*{{User|Juustro|fi}}
*{{User|Kolbur|de}}
*{{User|Kul|nl}}
*{{User|Logix|us}}
*{{User|MDGrein|se}}
*{{User|MooUK|uk}}
*{{User|N101|au}}
*{{User|Nazirro|pl}}
*{{User|Nitehawk|us}}
*{{User|Phil|uk}}
*{{User|RaWt|no}}
*{{User|Red|us}}
*{{User|RichK|uk}}

|                  
|valign="top" |
*{{User|Satyap|in}}
*{{User|SerriaRomeo|us}}
*{{User|Shader|pl}}
*{{User|Sian|dk}}
*{{User|Skasi|at}}
*{{User|Skidd13|de}}
*{{User|Spectre100|us}}
*{{User|Stoffe|se}}
*{{User|strstrep|us}}
*{{User|Teddy|no}}
*{{User|UnderBuilder|ar}}
*{{User|Vinni3|uk}}
*{{User|Volny|cz}}
*{{User|welterde|de}}
*{{User|Zavior|fi}}

|}

Talk:Two-way Prio

2010-03-17T08:55:57Z

Zerpa: /* Gif */

==Gif==
What did you use to make the animated gif? --[[User:Petert|Petert]] 00:53, 17 March 2010 (UTC)

:Gimp 2.6 of course :-) Check out this [http://www.gimp.org/tutorials/Simple_Animations/ This guide] [[User:Zerpa|Zerpa]] 08:55, 17 March 2010 (UTC)

Talk:Two-way Prio

2010-03-17T08:49:10Z

Zerpa:

==Gif==
What did you use to make the animated gif? --[[User:Petert|Petert]] 00:53, 17 March 2010 (UTC)

Gimp 2.6 of course :-) Check out this [http://www.gimp.org/tutorials/Simple_Animations/ This guide]

Two-way Prio

2010-03-15T18:21:44Z

Zerpa:

A standard prio gives priority to trains on the mainline and makes trains on the sideline wait. In some joins, especially at BBHs, a prio may build up long queues waiting to enter the mainline. The usual solution to this it to extend the mainline.

The two-way prio is an intermediate solution that can increase the overall throughput of a join. The basic idea is that when a waiting train gets a chance to enter the line, every train behind it should also be allowed to enter. The mechanism is similar to a real-life traffic light. It releases all traffic in one direction and then switches to the other direction and releases all traffic from there (although, the Two-way prio does not have a timeout, like traffic lights).

[[File:twowayprio.gif]]

A standard prio that is highly loaded tends to generate a pattern of trains with just one of the trains from the joining line between each block of trains from the joined line, with a gap between each join. The two-way prio allows all waiting trains to enter, so there will be overall fewer gaps.

== How to build ==

Add a small TL1 train on a segment that crosses the two lines. The TL1 train should be blocked by a standard prio in both direction by using a two-way entry signal.

A two-way prio does not need a long prio on the tracks. It just needs to be long enough that trains waiting will enter the prio before the logic train has a chance to switch.

A place to use this is in BBHs where neither of the MLs is more major than the other. A simple join will leave huge gaps, and a standard prio may build big queues even with good balancing.

== Disadvantages ==

* When the load ratio between the lines is low, e.g. 1:20, the Two-way prio may not be as effective, as it leaves a gap between trains when it switches. This gap is bigger than on a standard prio and pre-accelerated prio's.

== Benefits ==

* Releases entire queues in both directions at once without breaking the queue.
* This usually give tight packing as the entire queue is release at once.
* Adapts well to the traffic load. On light traffic, the logic train is usually blocked in the prio before a single train can reach it, leaving the path open.
* Handles load ratios close to 1:1 very well, and cases when the load on the lines is very dynamic.

File:Twowayprio.gif

2010-03-15T18:21:01Z

Zerpa: uploaded a new version of "File:Twowayprio.gif": Better gif for showing the two-way prio

Shows how the two-way prio works.

Two-way Prio

2010-03-15T18:20:18Z

Zerpa:

A standard prio gives priority to trains on the mainline and makes trains on the sideline wait. In some joins, especially at BBHs, a prio may build up long queues waiting to enter the mainline. The usual solution to this it to extend the mainline.

The two-way prio is an intermediate solution that can increase the overall throughput of a join. The basic idea is that when a waiting train gets a chance to enter the line, every train behind it should also be allowed to enter. The mechanism is similar to a real-life traffic light. It releases all traffic in one direction and then switches to the other direction and releases all traffic from there (although, the Two-way prio does not have a timeout, like traffic lights).

[[File:twowayprio2.gif]]

A standard prio that is highly loaded tends to generate a pattern of trains with just one of the trains from the joining line between each block of trains from the joined line, with a gap between each join. The two-way prio allows all waiting trains to enter, so there will be overall fewer gaps.

== How to build ==

Add a small TL1 train on a segment that crosses the two lines. The TL1 train should be blocked by a standard prio in both direction by using a two-way entry signal.

A two-way prio does not need a long prio on the tracks. It just needs to be long enough that trains waiting will enter the prio before the logic train has a chance to switch.

A place to use this is in BBHs where neither of the MLs is more major than the other. A simple join will leave huge gaps, and a standard prio may build big queues even with good balancing.

== Disadvantages ==

* When the load ratio between the lines is low, e.g. 1:20, the Two-way prio may not be as effective, as it leaves a gap between trains when it switches. This gap is bigger than on a standard prio and pre-accelerated prio's.

== Benefits ==

* Releases entire queues in both directions at once without breaking the queue.
* This usually give tight packing as the entire queue is release at once.
* Adapts well to the traffic load. On light traffic, the logic train is usually blocked in the prio before a single train can reach it, leaving the path open.
* Handles load ratios close to 1:1 very well, and cases when the load on the lines is very dynamic.

Two-way Prio

2010-03-15T17:44:07Z

Zerpa: Added notes on gaps and load ratios

Two-way Prio

2010-03-14T20:18:47Z

Zerpa:

A standard prio gives priority to trains on the mainline and makes trains on the sideline way. In some join, especially at BBHs, a prio may build up long queues waiting to enter the mainline.

On PSG 178, we experimented with a concept named a Two-way Prio. The basic idea is that when the waiting trains begin to roll, they should keep rolling and not stop for a few trains on the ML. The mechanism is similar to a real-life traffic light. It releases all traffic in one direction and then switches to the other direction and releases all traffic from there (although, the Two-way prio does not have a timeout, like traffic lights).

[[File:twowayprio.gif]]

== How to build ==

Add a small TL1 train on a segment that crosses the two lines. The TL1 train should be blocked by a standard prio in both direction by using a two-way entry signal.

A two-way prio does not need a long prio on the tracks. It just needs to be long enough that trains waiting will enter the prio before the logic train has a chance to switch.

A place to use this is in BBHs where neither of the MLs is more major than the other. A simple join will leave huge gaps, and a standard prio may build big queues even with good balancing.

== Benefits ==

* Releases entire queues in both directions at once without breaking the queue.
* This usually give tight packing as the entire queue is release at once.
* Adapts well to the traffic load. On light traffic, the logic train is usually blocked in the prio before a single train can reach it, leaving the path open.

Two-way Prio

2010-03-14T20:15:05Z

Zerpa:

File:Twowayprio.gif

2010-03-14T20:08:00Z

Zerpa: Shows how the two-way prio works.

Shows how the two-way prio works.

Two-way Prio

2010-03-14T20:07:19Z

Zerpa:

Two-way Prio

2010-03-14T19:48:59Z

Zerpa: Created page with 'A standard prio gives priority to trains on the mainline and makes trains on the sideline way. In some join, especially at BBHs, a prio may build up long queues waiting to enter …'