#openttdcoop wiki - User contributions [en]

https://wiki.openttdcoop.org/api.php?action=feedcontributions&feedformat=atom&user=Tim #openttdcoop wiki - User contributions [en] 2026-05-12T10:18:58Z User contributions MediaWiki 1.25.2 https://wiki.openttdcoop.org/index.php?title=PublicServer:Archive_-_Games_91_-_100&diff=7921 PublicServer:Archive - Games 91 - 100 2008-05-25T15:52:26Z

<p>Tim: </p> <hr /> <div><noinclude>{{PublicServerArchiveMenu}}</noinclude><br /> <br /> {{Archive_PublicServer|Public Server Game 95|17.05.08 - 23.05.08| {{User|BenTotterdell}}, {{User|Rob}}, {{User|tneo}}, {{User|pm}}, {{User|Mark}}, {{User|Satyap}}, {{User|Tim}}, (Add yourself)|[[Gametype:Cargo_Concept|Cargo]] |TL5 for primaries, TL9 for Goods/Food| 1024*256 Arctic|r13032 + [[Guides:Glossary:GRF|#openttdcoop-GRF-Pack 7.0]]|In this game we had all trains going down a LLLL10RRRR ML. Included in the game were two refit area's, one at each end of the map. The goods/food trains refit from one to the other with every trip, and ran on a timetable. As a consequence we could reduce the amount of trains on the mainline, but maintain a high and smooth cargo delivery rate. During the start of the game there was confusion regarding station design. All stations were meant to be terminus, but that was not clearly signed, creating lot of confusion when several stations needed to rebuilt to conform to the plan. The problems were eventually solved, and the network ended running very smooth. |95|Image:PSG95.png|Showing a BBH that caused a lot of problems. In the upper right you can see one of the refit areas where empty food trains were refitted to pick up goods.}}<br /> <br /> {{Archive_PublicServer|Public Server Game 94|11.05.08 - 17.05.08| {{User|Satyap}}, {{User|mixrin}}, {{User|Combuster}}, {{User|ninjamask}}, {{User|Rob}} (Add yourself)|[[Gametype:Cargo_Concept|Cargo]] |TL20 for ML trains, various for feeders| 1024*1024 Temperate|r13032 + [[Guides:Glossary:GRF|#openttdcoop-GRF-Pack 7.0]]|In this game we had small feeders feeding the huge 20-Tile Mainline Trains. A misunderstanding in the beginning of the game, along with the unspecified engine to be used for the ML trains, lead to the ML being designed for a curve length of 4, and unable to handle the fastest engines. ''(The fastest engine would have taken about 8 engines to handle TL20, anyway, if not more.)'' The challenge of designing the stations for TL 20 was very difficult. Surges in traffic could easily overlaod the waiting space and block the ML. |94|Image:PSG942.png|Showing one of the feeders.}}<br /> <br /> {{Archive_PublicServer|Public Server Game 93|30.04.08 - 11.05.08| {{User|Mark}}, {{User|mixrin}}, {{User|Addi}}, {{User|satyap}}, {{User|Rob}}, {{User|tneo}}, {{User|ninjamask}}, (Add yourself)|[[Gametype:Chaos Theory|Chaos]] + [[Gametype:Cargo_Concept|Cargo]] + Pax |Various ''(TL8 for inter-island transfer)'' | 256*2048 Temperate|r13016 + [[Guides:Glossary:GRF|#openttdcoop-GRF-Pack 7.0]]|A game making use of a new concept in which players got their own piece of map to manage locally. Later on the areas were connected with a Mainline network. |93|Image:PSG93.png|Venice of the South-West: well-serviced town with a station squeezed into available space}}<br /> <br /> {{Archive_PublicServer|Public Server Game 92|27.04.08 - 30.04.08| {{User|Addi}}, {{User|Ammler}}, {{User|XeryusTC}}, {{User|Combuster}}, {{User|Skasi}}, {{User|boes}}, {{User|ninjamask}}, {{User|Ehtirno}}, {{User|Altaree}}, {{User|Rob}} (Add yourself)|[[Gametype:Cargo_Concept|Cargo]] |3 | 256*1024 Arctic (alpine)|r12906 + [[Guides:Glossary:GRF|#openttdcoop-GRF-Pack 7.0]]|The next three tiles train with a big LLL RRR ring around the whole map and a LL RR line in the middle. There were never bottlenecks anywhere on the whole network since the beginning. Therefore would the network handle more trains, but the maximum of 1000 trains has been reached.|92|Image:PSG92.png|One of the two BBHs in the game}}<br /> <br /> {{Archive_PublicServer|Public Server Game 91|23.04.08 - 27.04.08| {{User|pm}}, {{User|Ammler}}, {{User|Mark}}, {{User|SmatZ}}, {{User|Combuster}}, {{User|XeryusTC}}, {{User|Rob}}, {{User|Altaree}} (Add yourself)|[[Gametype:Cargo_Concept|Cargo]] |3 | 512*512 sub-tropic|r12805 + [[Guides:Glossary:GRF|#openttdcoop-GRF-Pack 7.0]]|It was a massive game with a number of new players and in the end over 950 trains. The backbone consisted of two ML rings, one for empty, one for full trains. It proved fluent up to about 750 trains, after that jams started to show. - [http://www.openttdcoop.org/blog/2008/04/27/review-psg-91/ Review at blog] |91|Image:PSG91.png|Combined factory and refinery station, serving over 750 trains, 550 of them delivering stuff.}}</div>

Tim https://wiki.openttdcoop.org/index.php?title=PublicServer:Archive_-_Games_81_-_90&diff=7527 PublicServer:Archive - Games 81 - 90 2008-03-16T11:11:20Z

<p>Tim: </p> <hr /> <div><noinclude>{{PublicServerArchiveMenu}}</noinclude><br /> {{Archive_PublicServer|Public Server Game 85|02.03.08 - 16.03.08|{{User|Tim}}, (Add yourself)|Gametype:Cargo + Some Pax |6 for Cargo and Pax, 3 for S-Bahn|512x512 Arctic|r12322 + [[Guides:Glossary:GRF|#openttdcoop-GRF-Pack 7 beta-1]]|A standard Cargo setup with a passenger transport between two cities with S-Bahns and populations of about 100.000. The Norwegian Trainset was used, the Mainline started with two tracks each direction and was at some parts extended to 3 or even 4 tracks.|85|Image:PSG_85.PNG|The City of Tuomela and the surrounding assimilated Cities. You can see how it grew around the various stations, like the Paper Mill Pickup. }}<br /> <br /> {{Archive_PublicServer|Public Server Game 84|24.02.08 - 02.03.08|{{User|Addi}}, {{User|Mark}}, {{User|pm}}, {{User|tneo}}, {{User|SmatZ}}, {{User|VLengoc}}, {{User|Killian}} (Add yourself)|[[Gametype:ICE_SBahn|ICE S-Bahn]] |12 tiles electric rails asiastar for mainline, various TL for maglev s-bahn|512x512 Temperate|r12208 + [[Guides:Glossary:GRF|#openttdcoop-GRF-Pack]]|A special map w/o any industry except some coal for the MM was used and seven 0 population cities which only grow after removal of some road(s) - but then at very high speed. Huge local s-bahns transferred to the ICE terminals which connected to a ML grid. The biggest towns grew to over half a million probably beating the overall record for the transported PAX.|84|Image:PSG84_final.png|ICE terminal and part of Mark's and Den's huge city with more than 585.000 inhabitants. }}<br /> <br /> {{Archive_PublicServer|Public Server Game 83|18.02.08 - 23.02.08|{{User|tneo}}, {{User|pm}}, {{User|hylje}}, {{User|VLengoc}}, {{User|Killian}} (Add yourself)|[[Gametype:ICE_SBahn|ICE S-Bahn]] with maglev's|6 tiles for mainline, various for feeders|512x512 Temperate|r12208 + [[Guides:Glossary:GRF|#openttdcoop-GRF-Pack]]|A game with some difficulties in there. It had a different setting for signalling and used LRRL which made it confusing at times. Also the low terraform ruling proved to be challenging for some. It turned out to be a very short game, due to the high amount of (new) active players.|83|Image:PSG83.png|A dense developed city area with the central station. }}<br /> <br /> {{Archive_PublicServer|Public Server Game 82|08.02.08 - 18.02.08|{{User|tneo}}, {{User|Kommer}}, {{User|DJ-Nekkid}}, {{User|pm}}, {{User|Addi}}, {{User|Jortuny}}, {{User|Mark}}, {{User|ODM}}, {{User|Kolbur}}, {{User|VLengoc}}, [[User:LordAzamath|LordAzamath]], {{User|Killian}} (Add yourself)|[[Gametype:Cargo_Concept|Cargo]]|3 tiles|512x256 Artic|r12025 + [[Guides:Glossary:GRF|#openttdcoop-GRF-Pack]]| A game making use of the SML concept on maglev tracks. The plan chosen had to drop/ pickup station on the West and East side. Initially we started with 3 ML's and ended up with 6 or more at some points. The game proved hard to get a clean network after the initial start up, but it was a nice game overall. |82|Image:PSG82.png|Showing one of the shifters used in the game to balance traffice over all lanes. }}<br /> <br /> {{Archive_PublicServer|Public Server Game 81|31.01.07 - 08.02.08|{{User|tneo}}, {{User|Kommer}}, {{User|Floffe}}, {{User|DJ-Nekkid}}, {{User|pm}}, {{User|mazen}}, {{User|Phoenix}}, {{User|Kolo}}, {{User|pmatt}} , {{User|Addi}}, {{User|Jortuny}}, {{User|fR4g}}, {{User|Thraxian}}, {{User|Mark}}, {{User|Tim}}, {{User|ODM}}, {{User|Matte}}, {{User|Kolbur}}, (Add yourself)|[[Gametype:Cargo_Concept|Cargo]]|5 tiles|1024x1024 Temperate|r12025 + [[Guides:Glossary:GRF|#openttdcoop-GRF-Pack]]| This game was meant as a test for the new public server with an aim of 2000 trains running and every secondary industry producing about 10k our montly output. Layout was a square grid for the ML with a central factory and good drops at all corners as well as refinery and steel plant. Central factory and oil refinery with each 15k monthly output proved a real challange for the stations and also for the ML which were partly extended to LL__RRRRRR (factory to steel pickup) to cope with the load. Unfortunately the game was too huge for many clients |81|Image:psg81.png|Huge oil drop station designed by tneo, built by many.}}</div>

Tim https://wiki.openttdcoop.org/index.php?title=File:PSG_85.PNG&diff=7526 File:PSG 85.PNG 2008-03-16T11:03:42Z

<p>Tim: PSG #85 - Screenshot shows the City of Tuomela and the surrounding suburbs with the integradet stations.</p> <hr /> <div>PSG #85 - Screenshot shows the City of Tuomela and the surrounding suburbs with the integradet stations.</div>

Tim https://wiki.openttdcoop.org/index.php?title=Basic_Junctions&diff=7123 Basic Junctions 2008-02-09T11:00:57Z

<p>Tim: </p> <hr /> <div>[[Basic_Stations|<< Basic Stations ]] | [[Mainline_Junctions| Mainline Junctions >>]]<br /> <br /> In this part we build our first junction (in #openttdcoop we always call it "hub"). Since we always build multi-track-junctions, a junction is a bit more complicated than you may have done it before. We try to build ''efficient'' and ''fast'' railways and therefore we need ''efficient'' and ''fast'' junctions as well. For the start we will analyse a so-called [[Sideline_Hub|Sideline Hub]] - or '''SLH''' for short.<br /> <br /> <br /> [[Image:BasicJuntions1.png|center|thumb|600px|A very basic [[Sideline_Hub|Sideline Hub]] - Note the lack of [[Load_Balancers|load balancing]] ]]<br /> <br /> <br /> We find several important things in the image above:<br /> <br /> <br /> * A [[Mainline|'''mainline''']] (also known as "Axis" goes from south to north (you can find it quite easy, [[Mainline|mainlines]] have at least two tracks in each direction). The '''SLH''' has to connect a sideline to a mainline. This is the simplest case of a hub in our games. It is usually called '''"T-Hub"''' (just lean your head right and you will notice why). <br /> <br /> <br /> Note that there '''should be''' some sort of [[Load_Balancers|load balancing]] for trains coming from the Sideline and enter the Mainline. The Loadbalancers will be explained later on.<br /> <br /> <br /> [[Image:BasicJuntions2.png|center|thumb|480px|An early [[Load_Balancers|Loadbalancer]] - recent concepts are far better but this one already improves the balancing somewhat]]<br /> <br /> <br /> On the image above, you see the idea of the balancing: if a Mainline-track is used (which means: a train is on the part the Sideline-Train wants to enter) the signal state is red - and the Sideline-Train chooses the other Mainline-track.<br /> <br /> <br /> But for now, let us come back to our topic - basic junctions.I know what you are thinking: "Why are they doing this weird things?". The answer is: because it is the simplest thing in the end. Make a clean and intelligent building right from the start - it saves you and others later on. <br /> <br /> <br /> Just imagine a game with 300+ trains and 100+ stations and every station has its own connection to a mainline with high traffic. All this entering/leaving trains will slow down other trains - it's some kind of chain reaction. [[Sideline_Hub|'''SLH's''']] are intended to be ''fast connection points'' from sidelines to mainlines. Traffic from stations are bundled to sidelines and via a SLH they are bundled to a massive mainline. This - in the end - ensures a fast and comprehensive network!<br /> <br /> <br /> '''Every hub has a [[Naming_conventions|name]]!''' Not only because we are gifted writers but also because of finding all these hubs in the future. On a typical 512x512 map we end up with at least four "Backbone Hubs" (explained later on) and at least eight or even more Sideline Hubs. <br /> <br /> <br /> [[Image:BasicJuntions3.png|center|thumb|357px|The signlist - klick on a sign and you will get to the spot]]<br /> <br /> <br /> Since #openttdcoop has something to deal with both communication and coordination it has proven that "Look at SLH 3" is easier to communicate rather than "Look at this hub east to the hub which is west of the eastern one". This ought to be obvious.<br /> <br /> <br /> '''Close signaling!''' Always place signals as close as possible to a track split. This prevents unnecessary red-signal-times when a train moves over a split. <br /> <br /> <br /> [[Image:BasicJunction4.png|center|thumb|199px|The signals set as close as possible]]<br /> <br /> <br /> '''Think big!''' Our trains have a certain length (depending on the current game). If it is too long to enter a Sideline it therefore blocks not only the Sideline itself but also the Mainline. On a good junction the Sideline-entry is long enough for one whole train to wait. <br /> <br /> <br /> '''You can get from each direction to any other direction!''' Since we want to make our railline expandable, we don't want to rethink all the old hubs in the future. It is better to build a hub with as many features as possible right at the start rather than heaving a headache in the future.<br /> <br /> <br /> '''A clean building style!''' You are not at your own - and this is probably the best thing about #openttdcoop! Unfortunately, most of us can't read your mind and therefore it is best to make a clean building style everyone understands. To be more concrete: don't do unnecessary tracks, make comments (by using signs) of your ideas. Signs do not cost anything at all - except some pressed keys on your keyboard.<br /> <br /> <br /> '''Curve Radius'''. Depending on the game, we use a certain trainlength. Imaging a map with 3-tile-long-trains. This means: If you build curves with 3 tiles length each, the trains won't slow down! For monorail or maglev it's very important to remain at full speed. Just ask some experts around for the minimum radius for full speed-curves. ''Note: for larger trainlengths, you the radius is always smaller than the trainlength.''<br /> <br /> <br /> [[Image:BasicJunction5.png|center|thumb|650px|Different trainlengths afford different curve radiuses for full speed]]<br /> <br /> <br /> Finally, one thing is left to say: '''the Mainline has always the highest priority!''' Keep this in your mind for the next chapters!<br /> <br /> <br /> [[Basic_Stations|<< Basic Stations ]] | [[Mainline_Junctions| Mainline Junctions >>]]<br /> <br /> [[Category:Guides]]</div>

Tim https://wiki.openttdcoop.org/index.php?title=User:Tim/Tilelength&diff=7122 User:Tim/Tilelength 2008-02-09T10:56:01Z

<p>Tim: </p> <hr /> <div>==Introduction==<br /> Whenever starting a new game, one of the first settings to be chosen is the used tilelength for your trains. This length can vary from supersmall trains with only three carriages (which would be tilelength 2) to huge mammoth trains with more than 20 carriages, which would make a tilelength greater than 10...<br /> <br /> <br /> ==Why Odd Tilelengths are better than Even Ones==<br /> [[Image:Comparison_of_Tilelengths.png|thumb|300px|Comparison of TLs 3; 3,5; 4; 4,5 and 5]]<br /> Most people probably play with the Patch-Option "When Dragging, place Signals every: X Tiles" set to 2, accordingly there will always be one tile with a signal on it, one without one, one with a signal and so on. In #openttdcoop games, this is an undiscussed standard. As we do not want to change this setting, we should see how we can fit the tilelength of our trains to it. A common situation is that one or more trains are waiting before a station which is currently full. Those waiting trains could jam back until the mainline of our network and block it. The jammed part of the mainline would jam too and block other parts of the mainline, until the mess is complete. To avoid a situation like this, you can take various measures like expanding the jammed station or the waiting space before it. But just by choosing an odd tilelength, you can already ease the situation.<br /> <br /> [[Image:Diagonal_Comparison_of_Tilelengths.png|thumb|left|346px|Comparison of different Tilelengths on diagonal track]]<br /> <br /> If you look at the picture to the right, you will see that with "Place signals every 2 Tiles", trains with different tilelengths use the given space quite differently. While the trains with "natural odd" Tilelengths (3 and 5) have almost no space between them, the trains with other Tilelengths such as 3,5; 4 or 4,5 have quite some space between them - space which could be used more efficiently! However, to achieve that, you would have to place a signal each 5 tiles (with the example of Tilelength 4), which you can't do with the patch-setting of "Place signals every 2 Tiles", you would have to set this setting to either 5 or 1, both are not very satisfying solutions.<br /> <br /> However, this applies for straight tracks, if you look at diagonal tracks, the situation is almost the same. Here the trains with Tilelengths of 3,5 or 5,5 or 7,5... fit perfectly, while with TL 3 or 5 you have small gaps. Those are, however, still a lot smaller than those with TL 2 or 4 or 6.<br /> <br /> ---<br /> <br /> [[Category:Guides]]</div>

Tim https://wiki.openttdcoop.org/index.php?title=User:Tim/Tilelength&diff=7121 User:Tim/Tilelength 2008-02-09T10:54:25Z

<p>Tim: </p> <hr /> <div>==Introduction==<br /> Whenever starting a new game, one of the first settings to be chosen is the used tilelength for your trains. This length can vary from supersmall trains with only three carriages (which would be tilelength 2) to huge mammoth trains with more than 20 carriages, which would make a tilelength greater than 10...<br /> <br /> <br /> ==Why Odd Tilelengths are better than Even Ones==<br /> [[Image:Comparison_of_Tilelengths.png|thumb|300px|Comparison of TLs 3; 3,5; 4; 4,5 and 5]]<br /> Most people probably play with the Patch-Option "When Dragging, place Signals every: X Tiles" set to 2, accordingly there will always be one tile with a signal on it, one without one, one with a signal and so on. In #openttdcoop games, this is an undiscussed standard. As we do not want to change this setting, we should see how we can fit the tilelength of our trains to it. A common situation is that one or more trains are waiting before a station which is currently full. Those waiting trains could jam back until the mainline of our network and block it. The jammed part of the mainline would jam too and block other parts of the mainline, until the mess is complete. To avoid a situation like this, you can take various measures like expanding the jammed station or the waiting space before it. But just by choosing an odd tilelength, you can already ease the situation.<br /> <br /> [[Image:Diagonal_Comparison_of_Tilelengths.png|thumb|left|346px|Comparison of different Tilelengths on diagonal track]]<br /> <br /> If you look at the picture to the right, you will see that with "Place signals every 2 Tiles", trains with different tilelengths use the given space quite differently. While the trains with "natural odd" Tilelengths (3 and 5) have almost no space between them, the trains with other Tilelengths such as 3,5; 4 or 4,5 have quite some space between them - space which could be used more efficiently! However, to achieve that, you would have to place a signal each 5 tiles (with the example of Tilelength 4), which you can't do with the patch-setting of "Place signals every 2 Tiles", you would have to set this setting to either 5 or 1, both are not very satisfying solutions.<br /> <br /> However, this applies for straight tracks, if you look at diagonal tracks, the situation is almost the same. Here the trains with Tilelengths of 3,5 or 5,5 or 7,5... fit perfectly, while with TL 3 or 5 you have small gaps. Those are, however, still a lot smaller than those with TL 2 or 4 or 6.<br /> <br /> [Category:Guides]</div>

Tim https://wiki.openttdcoop.org/index.php?title=User:Tim/Tilelength&diff=7114 User:Tim/Tilelength 2008-02-03T22:27:29Z

<p>Tim: </p> <hr /> <div>==Introduction==<br /> Whenever starting a new game, one of the first settings to be chosen is the used tilelength for your trains. This length can vary from supersmall trains with only three carriages (which would be tilelength 2) to huge mammoth trains with more than 20 carriages, which would make a tilelength greater than 10...<br /> <br /> <br /> ==Why Odd Tilelengths are better than Even Ones==<br /> [[Image:Comparison_of_Tilelengths.png|thumb|300px|Comparison of TLs 3; 3,5; 4; 4,5 and 5]]<br /> Most people probably play with the Patch-Option "When Dragging, place Signals every: X Tiles" set to 2, accordingly there will always be one tile with a signal on it, one without one, one with a signal and so on. In #openttdcoop games, this is an undiscussed standard. As we do not want to change this setting, we should see how we can fit the tilelength of our trains to it. A common situation is that one or more trains are waiting before a station which is currently full. Those waiting trains could jam back until the mainline of our network and block it. The jammed part of the mainline would jam too and block other parts of the mainline, until the mess is complete. To avoid a situation like this, you can take various measures like expanding the jammed station or the waiting space before it. But just by choosing an odd tilelength, you can already ease the situation.<br /> <br /> [[Image:Diagonal_Comparison_of_Tilelengths.png|thumb|left|346px|Comparison of different Tilelengths on diagonal track]]<br /> <br /> If you look at the picture to the right, you will see that with "Place signals every 2 Tiles", trains with different tilelengths use the given space quite differently. While the trains with "natural odd" Tilelengths (3 and 5) have almost no space between them, the trains with other Tilelengths such as 3,5; 4 or 4,5 have quite some space between them - space which could be used more efficiently! However, to achieve that, you would have to place a signal each 5 tiles (with the example of Tilelength 4), which you can't do with the patch-setting of "Place signals every 2 Tiles", you would have to set this setting to either 5 or 1, both are not very satisfying solutions.<br /> <br /> However, this applies for straight tracks, if you look at diagonal tracks, the situation is almost the same. Here the trains with Tilelengths of 3,5 or 5,5 or 7,5... fit perfectly, while with TL 3 or 5 you have small gaps. Those are, however, still a lot smaller than those with TL 2 or 4 or 6.</div>

Tim https://wiki.openttdcoop.org/index.php?title=User:Tim/Tilelength&diff=7113 User:Tim/Tilelength 2008-02-03T22:26:37Z

<p>Tim: </p> <hr /> <div>==Introduction==<br /> Whenever starting a new game, one of the first settings to be chosen is the used tilelength for your trains. This length can vary from supersmall trains with only three carriages (which would be tilelength 2) to huge mammoth trains with more than 20 carriages, which would make a tilelength greater than 10...<br /> <br /> <br /> ==Why Odd Tilelengths are better than Even Ones==<br /> [[Image:Comparison_of_Tilelengths.png|thumb|300px|Comparison of TLs 3; 3,5; 4; 4,5 and 5]]<br /> Most people probably play with the Patch-Option "When Dragging, place Signals every: X Tiles" set to 2, accordingly there will always be one tile with a signal on it, one without one, one with a signal and so on. In #openttdcoop games, this is an undiscussed standard. As we do not want to change this setting, we should see how we can fit the tilelength of our trains to it. A common situation is that one or more trains are waiting before a station which is currently full. Those waiting trains could jam back until the mainline of our network and block it. The jammed part of the mainline would jam too and block other parts of the mainline, until the mess is complete. To avoid a situation like this, you can take various measures like expanding the jammed station or the waiting space before it. But just by choosing an odd tilelength, you can already ease the situation.<br /> <br /> [[Image:Diagonal_Comparison_of_Tilelengths.png|thumb|left|346px|Diagonal Comparison of the same TLs]]<br /> <br /> If you look at the picture to the right, you will see that with "Place signals every 2 Tiles", trains with different tilelengths use the given space quite differently. While the trains with "natural odd" Tilelengths (3 and 5) have almost no space between them, the trains with other Tilelengths such as 3,5; 4 or 4,5 have quite some space between them - space which could be used more efficiently! However, to achieve that, you would have to place a signal each 5 tiles (with the example of Tilelength 4), which you can't do with the patch-setting of "Place signals every 2 Tiles", you would have to set this setting to either 5 or 1, both are not very satisfying solutions.<br /> <br /> However, this applies for straight tracks, if you look at diagonal tracks, the situation is almost the same. Here the trains with Tilelengths of 3,5 or 5,5 or 7,5... fit perfectly, while with TL 3 or 5 you have small gaps. Those are, however, still a lot smaller than those with TL 2 or 4 or 6.</div>

Tim https://wiki.openttdcoop.org/index.php?title=User:Tim/Tilelength&diff=7112 User:Tim/Tilelength 2008-02-03T22:26:21Z

<p>Tim: </p> <hr /> <div>==Introduction==<br /> Whenever starting a new game, one of the first settings to be chosen is the used tilelength for your trains. This length can vary from supersmall trains with only three carriages (which would be tilelength 2) to huge mammoth trains with more than 20 carriages, which would make a tilelength greater than 10...<br /> <br /> <br /> ==Why Odd Tilelengths are better than Even Ones==<br /> [[Image:Comparison_of_Tilelengths.png|thumb|300px|Comparison of TLs 3; 3,5; 4; 4,5 and 5]]<br /> Most people probably play with the Patch-Option "When Dragging, place Signals every: X Tiles" set to 2, accordingly there will always be one tile with a signal on it, one without one, one with a signal and so on. In #openttdcoop games, this is an undiscussed standard. As we do not want to change this setting, we should see how we can fit the tilelength of our trains to it. A common situation is that one or more trains are waiting before a station which is currently full. Those waiting trains could jam back until the mainline of our network and block it. The jammed part of the mainline would jam too and block other parts of the mainline, until the mess is complete. To avoid a situation like this, you can take various measures like expanding the jammed station or the waiting space before it. But just by choosing an odd tilelength, you can already ease the situation.<br /> <br /> [[Image:Diagonal_Comparison_of_Tilelengths.png|thumb|346px|Diagonal Comparison of the same TLs]]<br /> <br /> If you look at the picture to the right, you will see that with "Place signals every 2 Tiles", trains with different tilelengths use the given space quite differently. While the trains with "natural odd" Tilelengths (3 and 5) have almost no space between them, the trains with other Tilelengths such as 3,5; 4 or 4,5 have quite some space between them - space which could be used more efficiently! However, to achieve that, you would have to place a signal each 5 tiles (with the example of Tilelength 4), which you can't do with the patch-setting of "Place signals every 2 Tiles", you would have to set this setting to either 5 or 1, both are not very satisfying solutions.<br /> <br /> However, this applies for straight tracks, if you look at diagonal tracks, the situation is almost the same. Here the trains with Tilelengths of 3,5 or 5,5 or 7,5... fit perfectly, while with TL 3 or 5 you have small gaps. Those are, however, still a lot smaller than those with TL 2 or 4 or 6.<br /> <br /> [[Image:Diagonal_Comparison_of_Tilelengths.png|thumb|346px|Diagonal Comparison of the same TLs]]</div>

Tim https://wiki.openttdcoop.org/index.php?title=User:Tim/Tilelength&diff=7111 User:Tim/Tilelength 2008-02-03T22:25:28Z

<p>Tim: </p> <hr /> <div>==Introduction==<br /> Whenever starting a new game, one of the first settings to be chosen is the used tilelength for your trains. This length can vary from supersmall trains with only three carriages (which would be tilelength 2) to huge mammoth trains with more than 20 carriages, which would make a tilelength greater than 10...<br /> <br /> <br /> ==Why Odd Tilelengths are better than Even Ones==<br /> [[Image:Comparison_of_Tilelengths.png|thumb|300px|Comparison of TLs 3; 3,5; 4; 4,5 and 5]]<br /> Most people probably play with the Patch-Option "When Dragging, place Signals every: X Tiles" set to 2, accordingly there will always be one tile with a signal on it, one without one, one with a signal and so on. In #openttdcoop games, this is an undiscussed standard. As we do not want to change this setting, we should see how we can fit the tilelength of our trains to it. A common situation is that one or more trains are waiting before a station which is currently full. Those waiting trains could jam back until the mainline of our network and block it. The jammed part of the mainline would jam too and block other parts of the mainline, until the mess is complete. To avoid a situation like this, you can take various measures like expanding the jammed station or the waiting space before it. But just by choosing an odd tilelength, you can already ease the situation.<br /> <br /> If you look at the picture to the right, you will see that with "Place signals every 2 Tiles", trains with different tilelengths use the given space quite differently. While the trains with "natural odd" Tilelengths (3 and 5) have almost no space between them, the trains with other Tilelengths such as 3,5; 4 or 4,5 have quite some space between them - space which could be used more efficiently! However, to achieve that, you would have to place a signal each 5 tiles (with the example of Tilelength 4), which you can't do with the patch-setting of "Place signals every 2 Tiles", you would have to set this setting to either 5 or 1, both are not very satisfying solutions.<br /> <br /> However, this applies for straight tracks, if you look at diagonal tracks, the situation is almost the same. Here the trains with Tilelengths of 3,5 or 5,5 or 7,5... fit perfectly, while with TL 3 or 5 you have small gaps. Those are, however, still a lot smaller than those with TL 2 or 4 or 6.<br /> <br /> [[Image:Diagonal_Comparison_of_Tilelengths.png|thumb|346px|Diagonal Comparison of the same TLs]]</div>

Tim https://wiki.openttdcoop.org/index.php?title=User:Tim/Tilelength&diff=7108 User:Tim/Tilelength 2008-02-03T00:34:18Z

<p>Tim: </p> <hr /> <div>==Introduction==<br /> Whenever starting a new game, one of the first settings to be chosen is the used tilelength for your trains. This length can vary from supersmall trains with only three carriages (which would be tilelength 2) to huge mammoth trains with more than 20 carriages, which would make a tilelength greater than 10...<br /> <br /> <br /> ==Why Odd Tilelengths are better than Even Ones==<br /> [[Image:Comparison_of_Tilelengths.png|thumb|300px|Comparison of TLs 3; 3,5; 4; 4,5 and 5]]<br /> Most people probably play with the Patch-Option "When Dragging, place Signals every: X Tiles" set to 2, accordingly there will always be one tile with a signal on it, one without one, one with a signal and so on. In #openttdcoop games, this is an undiscussed standard. As we do not want to change this setting, we should see how we can fit the tilelength of our trains to it. A common situation is that one or more trains are waiting before a station which is currently full. Those waiting trains could jam back until the mainline of our network and block it. The jammed part of the mainline would jam too and block other parts of the mainline, until the mess is complete. To avoid a situation like this, you can take various measures like expanding the jammed station or the waiting space before it. But just by choosing an odd tilelength, you can already ease the situation.<br /> <br /> If you look at the picture to the right, you will see that with "Place signals every 2 Tiles", trains with different tilelengths use the given space quite differently. While the trains with "natural odd" Tilelengths (3 and 5) have almost no space between them, the trains with other Tilelengths such as 3,5; 4 or 4,5 have quite some space between them - space which could be used more efficiently! However, to achieve that, you would have to place a signal each 5 tiles (with the example of Tilelength 4), which you can't do with the patch-setting of "Place signals every 2 Tiles", you would have to set this setting to either 5 or 1, both are not very satisfying solutions.<br /> <br /> [[Image:Diagonal_Comparison_of_Tilelengths.png|thumb|346px|Diagonal Comparison of the same TLs]]</div>

Tim https://wiki.openttdcoop.org/index.php?title=User:Tim/Tilelength&diff=7107 User:Tim/Tilelength 2008-02-03T00:34:04Z

<p>Tim: </p> <hr /> <div>==Introduction==<br /> Whenever starting a new game, one of the first settings to be chosen is the used tilelength for your trains. This length can vary from supersmall trains with only three carriages (which would be tilelength 2) to huge mammoth trains with more than 20 carriages, which would make a tilelength greater than 10...<br /> <br /> <br /> ==Why Odd Tilelengths are better than Even Ones==<br /> [[Image:Comparison_of_Tilelengths.png|thumb|300px|Comparison of TLs 3; 3,5; 4; 4,5 and 5]]<br /> Most people probably play with the Patch-Option "When Dragging, place Signals every: X Tiles" set to 2, accordingly there will always be one tile with a signal on it, one without one, one with a signal and so on. In #openttdcoop games, this is an undiscussed standard. As we do not want to change this setting, we should see how we can fit the tilelength of our trains to it. A common situation is that one or more trains are waiting before a station which is currently full. Those waiting trains could jam back until the mainline of our network and block it. The jammed part of the mainline would jam too and block other parts of the mainline, until the mess is complete. To avoid a situation like this, you can take various measures like expanding the jammed station or the waiting space before it. But just by choosing an odd tilelength, you can already ease the situation.<br /> <br /> If you look at the picture to the right, you will see that with "Place signals every 2 Tiles", trains with different tilelengths use the given space quite differently. While the trains with "natural odd" Tilelengths (3 and 5) have almost no space between them, the trains with other Tilelengths such as 3,5; 4 or 4,5 have quite some space between them - space which could be used more efficiently! However, to achieve that, you would have to place a signal each 5 tiles (with the example of Tilelength 4), which you can't do with the patch-setting of "Place signals every 2 Tiles", you would have to set this setting to either 5 or 1, both are not very satisfying solutions.<br /> <br /> [[Image:Diagonal_Comparison_of_Tilelengths.png|Thumb|346px|Diagonal Comparison of the same TLs]]</div>

Tim https://wiki.openttdcoop.org/index.php?title=User:Tim/Tilelength&diff=7106 User:Tim/Tilelength 2008-02-03T00:33:27Z

<p>Tim: </p> <hr /> <div>==Introduction==<br /> Whenever starting a new game, one of the first settings to be chosen is the used tilelength for your trains. This length can vary from supersmall trains with only three carriages (which would be tilelength 2) to huge mammoth trains with more than 20 carriages, which would make a tilelength greater than 10...<br /> <br /> <br /> ==Why Odd Tilelengths are better than Even Ones==<br /> [[Image:Comparison_of_Tilelengths.png|thumb|300px|Comparison of TLs 3; 3,5; 4; 4,5 and 5]]<br /> Most people probably play with the Patch-Option "When Dragging, place Signals every: X Tiles" set to 2, accordingly there will always be one tile with a signal on it, one without one, one with a signal and so on. In #openttdcoop games, this is an undiscussed standard. As we do not want to change this setting, we should see how we can fit the tilelength of our trains to it. A common situation is that one or more trains are waiting before a station which is currently full. Those waiting trains could jam back until the mainline of our network and block it. The jammed part of the mainline would jam too and block other parts of the mainline, until the mess is complete. To avoid a situation like this, you can take various measures like expanding the jammed station or the waiting space before it. But just by choosing an odd tilelength, you can already ease the situation.<br /> <br /> If you look at the picture to the right, you will see that with "Place signals every 2 Tiles", trains with different tilelengths use the given space quite differently. While the trains with "natural odd" Tilelengths (3 and 5) have almost no space between them, the trains with other Tilelengths such as 3,5; 4 or 4,5 have quite some space between them - space which could be used more efficiently! However, to achieve that, you would have to place a signal each 5 tiles (with the example of Tilelength 4), which you can't do with the patch-setting of "Place signals every 2 Tiles", you would have to set this setting to either 5 or 1, both are not very satisfying solutions.<br /> <br /> [[Image:Diagonal_Comparison_of_Tilelengths.png|thumb|300px|Diagonal Comparison of the same TLs]]</div>

Tim https://wiki.openttdcoop.org/index.php?title=User:Tim/Tilelength&diff=7105 User:Tim/Tilelength 2008-02-03T00:33:06Z

<p>Tim: </p> <hr /> <div>==Introduction==<br /> Whenever starting a new game, one of the first settings to be chosen is the used tilelength for your trains. This length can vary from supersmall trains with only three carriages (which would be tilelength 2) to huge mammoth trains with more than 20 carriages, which would make a tilelength greater than 10...<br /> <br /> <br /> ==Why Odd Tilelengths are better than Even Ones==<br /> [[Image:Comparison_of_Tilelengths.png|thumb|300px|Comparison of TLs 3; 3,5; 4; 4,5 and 5]]<br /> Most people probably play with the Patch-Option "When Dragging, place Signals every: X Tiles" set to 2, accordingly there will always be one tile with a signal on it, one without one, one with a signal and so on. In #openttdcoop games, this is an undiscussed standard. As we do not want to change this setting, we should see how we can fit the tilelength of our trains to it. A common situation is that one or more trains are waiting before a station which is currently full. Those waiting trains could jam back until the mainline of our network and block it. The jammed part of the mainline would jam too and block other parts of the mainline, until the mess is complete. To avoid a situation like this, you can take various measures like expanding the jammed station or the waiting space before it. But just by choosing an odd tilelength, you can already ease the situation.<br /> <br /> If you look at the picture to the right, you will see that with "Place signals every 2 Tiles", trains with different tilelengths use the given space quite differently. While the trains with "natural odd" Tilelengths (3 and 5) have almost no space between them, the trains with other Tilelengths such as 3,5; 4 or 4,5 have quite some space between them - space which could be used more efficiently! However, to achieve that, you would have to place a signal each 5 tiles (with the example of Tilelength 4), which you can't do with the patch-setting of "Place signals every 2 Tiles", you would have to set this setting to either 5 or 1, both are not very satisfying solutions.<br /> <br /> [[Image:Diagonal_Comparison_of_Tilelengths.png|Thumb|300px|Diagonal Comparison of the same TLs]]</div>

Tim https://wiki.openttdcoop.org/index.php?title=File:Diagonal_Comparison_of_Tilelengths.png&diff=7104 File:Diagonal Comparison of Tilelengths.png 2008-02-03T00:30:27Z

<p>Tim: </p> <hr /> <div></div>

Tim https://wiki.openttdcoop.org/index.php?title=User:Tim/Tilelength&diff=7103 User:Tim/Tilelength 2008-02-03T00:22:38Z

<p>Tim: </p> <hr /> <div>==Introduction==<br /> Whenever starting a new game, one of the first settings to be chosen is the used tilelength for your trains. This length can vary from supersmall trains with only three carriages (which would be tilelength 2) to huge mammoth trains with more than 20 carriages, which would make a tilelength greater than 10...<br /> <br /> <br /> ==Why Odd Tilelengths are better than Even Ones==<br /> [[Image:Comparison_of_Tilelengths.png|thumb|300px|Comparison of TLs 3; 3,5; 4; 4,5 and 5]]<br /> Most people probably play with the Patch-Option "When Dragging, place Signals every: X Tiles" set to 2, accordingly there will always be one tile with a signal on it, one without one, one with a signal and so on. In #openttdcoop games, this is an undiscussed standard. As we do not want to change this setting, we should see how we can fit the tilelength of our trains to it. A common situation is that one or more trains are waiting before a station which is currently full. Those waiting trains could jam back until the mainline of our network and block it. The jammed part of the mainline would jam too and block other parts of the mainline, until the mess is complete. To avoid a situation like this, you can take various measures like expanding the jammed station or the waiting space before it. But just by choosing an odd tilelength, you can already ease the situation.<br /> <br /> If you look at the picture to the right, you will see that with "Place signals every 2 Tiles", trains with different tilelengths use the given space quite differently. While the trains with "natural odd" Tilelengths (3 and 5) have almost no space between them, the trains with other Tilelengths such as 3,5; 4 or 4,5 have quite some space between them - space which could be used more efficiently! However, to achieve that, you would have to place a signal each 5 tiles (with the example of Tilelength 4), which you can't do with the patch-setting of "Place signals every 2 Tiles", you would have to set this setting to either 5 or 1, both are not very satisfying solutions.</div>

Tim https://wiki.openttdcoop.org/index.php?title=Community:Members&diff=7102 Community:Members 2008-02-03T00:21:42Z

<p>Tim: </p> <hr /> <div>__NOTOC__<br /> ==Active Members of #openttdcoop [14]==<br /> *{{User|Adm.Spock|nl}}<br /> *{{User|Ammler|ch}} '''(Admin)'''<br /> *{{User|dihedral|de}}<br /> *{{User|Hylje|fi}}<br /> *{{User|Kommer|nl}} '''(Admin)'''<br /> *{{User|Mucht|at}} '''(Admin)'''<br /> *{{User|Osai|de}} '''(Admin)'''<br /> *{{User|Phazorx|iru}} '''(Admin)'''<br /> *{{User|Progman|de}}<br /> *{{User|thgergo|hu}}<br /> *{{User|tneo|nl}}<br /> *{{User|Thraxian|us}}<br /> *{{User|valhallasw|nl}}, BOFH, Wiki-god and mainly werkloos '''(Admin)'''<br /> *{{User|XeryusTC|nl}}, Chairman of the #openttdcoop stupidness committee '''(Admin)'''<br /> ''Note: Admins have shell access to our servers''<br /> <br /> ==Currently Inactive Members of #openttdcoop [7]==<br /> *{{User|dp|de}}<br /> *{{User|e1ko|cz}}<br /> *{{User|Guru3|se}}<br /> *{{User|ottd-king|uk}}<br /> *{{User|Piratejerk|ca}}<br /> *{{User|StarLite|nl}}<br /> *{{User|xahodo|nl}}<br /> <br /> ==Honorary Members of #openttdcoop [2]==<br /> *{{User|Brianetta|uk}} (our amiable host who is responsible for making #openttdcoop to such a vital community it is today) '''(Admin)'''<br /> *{{User|TrueLight|nl}} (for being a bugfixer over ... a long time ;-) )<br /> <br /> ==The usual suspects around the Public Server [46]==<br /> *{{User|Addi|ch}}<br /> *{{User|Alendo|no}}<br /> *{{User|AntB|uk}}<br /> *{{User|Bob27|us}}<br /> *{{User|Cipri|nl}}<br /> *{{User|Dark_Link|se}}<br /> *{{User|DJNekkid|no}}<br /> *{{User|Doke|de}}<br /> *{{User|Dopefish|de}}<br /> *{{User|EmiT|cz}}<br /> *{{User|Farden|fr}}<br /> *{{User|Floffe|se}}<br /> *{{User|Franco|hu}}<br /> *{{User|Gamer|nl}}<br /> *{{User|Godde|no}}<br /> *{{User|itsnotvalid|hk}}<br /> *{{User|Jinx|be}}<br /> *{{User|Juustro|fi}}<br /> *{{User|Kejhic|cz}}<br /> *{{User|Kolbur|de}}<br /> *{{User|Kolo|pl}}<br /> *{{User|Kul|nl}}<br /> *{{User|LittleMikey|au}}<br /> *{{User|LordAzamath|ee}}<br /> *{{User|Mark|nl}}<br /> *{{User|MDGrein|se}}<br /> *{{User|MooUK|uk}}<br /> *{{User|N101|au}}<br /> *{{User|Nitehawk|us}}<br /> *{{User|Phil|uk}}<br /> *{{User|Phoenix the II|nl}}<br /> *{{User|Pikita|uk}}<br /> *{{User|RaWt|no}}<br /> *{{User|Red|us}}<br /> *{{User|RMJ|dk}}<br /> *{{User|Sedontane|uk}}<br /> *{{User|Shader|pl}}<br /> *{{User|S m w|de}}<br /> *{{User|Stoffe|se}}<br /> *{{User|Spectre100|us}}<br /> *{{User|strstrep|us}}<br /> *{{User|thomashauk|uk}}<br /> *{{User|Tim|de}}<br /> *{{User|Volny|cz}}<br /> *{{User|Walle|be}}<br /> *{{User|welterde|de}}<br /> *{{User|Zuu|se}}<br /> ''And of course all the others above!''<br /> <br /> ===== Exsuspects [20]=====<br /> *{{User|Alanin|de}}<br /> *{{User|ChrisM|de}}<br /> *{{User|csuke|uk}}<br /> *{{User|eJoJ|no}}<br /> *{{User|Green-devil|dk}}<br /> *{{User|Hans|nl}}<br /> *{{User|hdp|us}}<br /> *{{User|Ichi|nl}}<br /> *{{User|Ihmemies|fi}}<br /> *{{User|John|sk}}<br /> *{{User|Nazirro|pl}}<br /> *{{User|OwenS|uk}}<br /> *{{User|RichK|uk}}<br /> *{{User|SerriaRomeo|us}}<br /> *{{User|Sian|dk}}<br /> *{{User|Skasi|at}}<br /> *{{User|Skidd13|de}}<br /> *{{User|Teddy|no}}<br /> *{{User|UnderBuilder|ar}}<br /> *{{User|Zavior|fi}}</div>

Tim https://wiki.openttdcoop.org/index.php?title=User:Tim&diff=7101 User:Tim 2008-02-03T00:20:34Z

<p>Tim: </p> <hr /> <div>==About Me==<br /> <br /> '''Born:''' 01.07.1988<br /> <br /> '''Home:''' Bornheim (between Bonn & Cologne), Germany {{flag|de}}<br /> <br /> '''Email:''' tim@rehms.net<br /> <br /> '''Started playing TTD:''' I really can't remember when exactly, but i guess i was about eight years old... <br /> <br /> '''First Contact with #openttdcoop:''' November 2007 - Public Server Game #70, i just loved it, 700 Trains on a 256x256 map, my favourite Game until today :-)<br /> <br /> '''Specialist on:''' Finding & Fixing minor Issues, rebuilding a whole Hub because it would look better if it were one tile to the right...<br /> <br /> '''Prefers:''' Tilelenght 3 or 5, small & crowded maps, symmetric and good-looking layouts of stations, networks...<br /> <br /> '''Dislikes:''' Even Tilelengths, Huge Towns (in-Game...)<br /> <br /> <br /> <br /> ==Sub-Pages==<br /> * [[User:Tim/Tilelength| About Tilelengths]]</div>

Tim https://wiki.openttdcoop.org/index.php?title=User:Tim&diff=7100 User:Tim 2008-02-03T00:19:41Z

<p>Tim: </p> <hr /> <div>==About Me==<br /> <br /> '''Born:''' 01.07.1988<br /> <br /> '''Home:''' Bornheim (between Bonn & Cologne), Germany {{flag|de}}<br /> <br /> '''Email:''' tim[at]rehms[dot]net<br /> <br /> '''Started playing TTD:''' I really can't remember when exactly, but i guess i was about eight years old... <br /> <br /> '''First Contact with #openttdcoop:''' November 2007 - Public Server Game #70, i just loved it, 700 Trains on a 256x256 map, my favourite Game until today :-)<br /> <br /> '''Specialist on:''' Finding & Fixing minor Issues, rebuilding a whole Hub because it would look better if it were one tile to the right...<br /> <br /> '''Prefers:''' Tilelenght 3 or 5, small & crowded maps, symmetric and good-looking layouts of stations, networks...<br /> <br /> '''Dislikes:''' Even Tilelengths, Huge Towns (in-Game...)<br /> <br /> <br /> <br /> ==Sub-Pages==<br /> * [[User:Tim/Tilelength| About Tilelengths]]</div>

Tim https://wiki.openttdcoop.org/index.php?title=User:Tim&diff=7099 User:Tim 2008-02-03T00:19:21Z

<p>Tim: </p> <hr /> <div>'''Born:''' 01.07.1988<br /> <br /> '''Home:''' Bornheim (between Bonn & Cologne), Germany {{flag|de}}<br /> <br /> '''Email:''' tim[at]rehms[dot]net<br /> <br /> '''Started playing TTD:''' I really can't remember when exactly, but i guess i was about eight years old... <br /> <br /> '''First Contact with #openttdcoop:''' November 2007 - Public Server Game #70, i just loved it, 700 Trains on a 256x256 map, my favourite Game until today :-)<br /> <br /> '''Specialist on:''' Finding & Fixing minor Issues, rebuilding a whole Hub because it would look better if it were one tile to the right...<br /> <br /> '''Prefers:''' Tilelenght 3 or 5, small & crowded maps, symmetric and good-looking layouts of stations, networks...<br /> <br /> '''Dislikes:''' Even Tilelengths, Huge Towns (in-Game...)<br /> <br /> <br /> <br /> ==Sub-Pages==<br /> * [[User:Tim/Tilelength| About Tilelengths]]</div>

Tim https://wiki.openttdcoop.org/index.php?title=User:Tim/Tilelength&diff=7098 User:Tim/Tilelength 2008-02-03T00:13:42Z

<p>Tim: </p> <hr /> <div>==Introduction==<br /> Whenever starting a new game, one of the first settings to be chosen is the used tilelength for your trains. This length can vary from supersmall trains with only three carriages (which would be tilelength 2) to huge mammoth trains with more than 20 carriages, which would make a tilelength greater than 10...<br /> <br /> <br /> ==Why Odd Tilelengths are better than Even Ones==<br /> [[Image:Comparison_of_Tilelengths.png|thumb|300px|Comparison of TLs 3; 3,5; 4; 4,5 and 5]]<br /> Most people probably play with the Patch-Option "When Dragging, place Signals every: X Tiles" set to 2, accordingly there will always be one tile with a signal on it, one without one, one with a signal and so on. In #openttdcoop games, this is an undiscussed standard. As we do not want to change this setting, we should see how we can fit the tilelength of our trains to it. A common situation is that one or more trains are waiting before a station which is currently full. Those waiting trains could jam back until the mainline of our network and block it. The jammed part of the mainline would jam too and block other parts of the mainline, until the mess is complete. To avoid a situation like this, you can take various measures like expanding the jammed station or the waiting space before it. But just by choosing an odd tilelength, you can already ease the situation.<br /> If you look at the picture to the right, you will see that with "Place signals every 2 Tiles", trains with different tilelengths use the given space quite differently. While the trains with "natural odd" Tilelengths (3 and 5) have almost no space between them, the trains with other Tilelengths such as 3,5; 4 or 4,5 have quite some space between them - space which could be used more efficiently! However, to achieve that, you would have to place a signal each 5 tiles (with the example of Tilelength 4), which you can't do with the patch-setting of "Place signals every 2 Tiles", you would have to set this setting to either 5 or 1, both are not very satisfying solutions.</div>

Tim https://wiki.openttdcoop.org/index.php?title=User:Tim/Tilelength&diff=7097 User:Tim/Tilelength 2008-02-03T00:12:17Z

<p>Tim: </p> <hr /> <div>==Introduction==<br /> Whenever starting a new game, one of the first settings to be chosen is the used tilelength for your trains. This length can vary from supersmall trains with only three carriages (which would be tilelength 2) to huge mammoth trains with more than 20 carriages, which would make a tilelength greater than 10...<br /> <br /> <br /> ==Why Odd Tilelengths are better than Even Ones==<br /> [[Image:Comparison_of_Tilelengths.png|thumb|Comparison of TLs 3; 3,5; 4; 4,5 and 5]]<br /> Most people probably play with the Patch-Option "When Dragging, place Signals every: X Tiles" set to 2, accordingly there will always be one tile with a signal on it, one without one, one with a signal and so on. In #openttdcoop games, this is an undiscussed standard. As we do not want to change this setting, we should see how we can fit the tilelength of our trains to it. A common situation is that one or more trains are waiting before a station which is currently full. Those waiting trains could jam back until the mainline of our network and block it. The jammed part of the mainline would jam too and block other parts of the mainline, until the mess is complete. To avoid a situation like this, you can take various measures like expanding the jammed station or the waiting space before it. But just by choosing an odd tilelength, you can already ease the situation.<br /> If you look at the picture to the right, you will see that with "Place signals every 2 Tiles", trains with different tilelengths use the given space quite differently. While the trains with "natural odd" Tilelengths (3 and 5) have almost no space between them, the trains with other Tilelengths such as 3,5; 4 or 4,5 have quite some space between them - space which could be used more efficiently! However, to achieve that, you would have to place a signal each 5 tiles (with the example of Tilelength 4), which you can't do with the patch-setting of "Place signals every 2 Tiles", you would have to set this setting to either 5 or 1, both are not very satisfying solutions.</div>

Tim https://wiki.openttdcoop.org/index.php?title=User:Tim/Tilelength&diff=7096 User:Tim/Tilelength 2008-02-03T00:11:59Z

<p>Tim: </p> <hr /> <div>==Introduction==<br /> Whenever starting a new game, one of the first settings to be chosen is the used tilelength for your trains. This length can vary from supersmall trains with only three carriages (which would be tilelength 2) to huge mammoth trains with more than 20 carriages, which would make a tilelength greater than 10...<br /> <br /> <br /> ==Why Odd Tilelengths are better than Even Ones==<br /> [[Image:Comparison_of_Tilelengths.png|thumb|Comparison of TLs 3; 3,5; 4; 4,5 and 5]]Most people probably play with the Patch-Option "When Dragging, place Signals every: X Tiles" set to 2, accordingly there will always be one tile with a signal on it, one without one, one with a signal and so on. In #openttdcoop games, this is an undiscussed standard. As we do not want to change this setting, we should see how we can fit the tilelength of our trains to it. A common situation is that one or more trains are waiting before a station which is currently full. Those waiting trains could jam back until the mainline of our network and block it. The jammed part of the mainline would jam too and block other parts of the mainline, until the mess is complete. To avoid a situation like this, you can take various measures like expanding the jammed station or the waiting space before it. But just by choosing an odd tilelength, you can already ease the situation.<br /> If you look at the picture to the right, you will see that with "Place signals every 2 Tiles", trains with different tilelengths use the given space quite differently. While the trains with "natural odd" Tilelengths (3 and 5) have almost no space between them, the trains with other Tilelengths such as 3,5; 4 or 4,5 have quite some space between them - space which could be used more efficiently! However, to achieve that, you would have to place a signal each 5 tiles (with the example of Tilelength 4), which you can't do with the patch-setting of "Place signals every 2 Tiles", you would have to set this setting to either 5 or 1, both are not very satisfying solutions.</div>

Tim https://wiki.openttdcoop.org/index.php?title=User:Tim/Tilelength&diff=7095 User:Tim/Tilelength 2008-02-03T00:11:26Z

<p>Tim: </p> <hr /> <div>==Introduction==<br /> Whenever starting a new game, one of the first settings to be chosen is the used tilelength for your trains. This length can vary from supersmall trains with only three carriages (which would be tilelength 2) to huge mammoth trains with more than 20 carriages, which would make a tilelength greater than 10...<br /> <br /> <br /> ==Why Odd Tilelengths are better than Even Ones==<br /> [[Image:Comparison_of_Tilelengths.png|thumb|Comparison of TLs 3,; 3,5; 4; 4,5 and 5]]Most people probably play with the Patch-Option "When Dragging, place Signals every: X Tiles" set to 2, accordingly there will always be one tile with a signal on it, one without one, one with a signal and so on. In #openttdcoop games, this is an undiscussed standard. As we do not want to change this setting, we should see how we can fit the tilelength of our trains to it. A common situation is that one or more trains are waiting before a station which is currently full. Those waiting trains could jam back until the mainline of our network and block it. The jammed part of the mainline would jam too and block other parts of the mainline, until the mess is complete. To avoid a situation like this, you can take various measures like expanding the jammed station or the waiting space before it. But just by choosing an odd tilelength, you can already ease the situation.<br /> If you look at the picture to the right, you will see that with "Place signals every 2 Tiles", trains with different tilelengths use the given space quite differently. While the trains with "natural odd" Tilelengths (3 and 5) have almost no space between them, the trains with other Tilelengths such as 3,5; 4 or 4,5 have quite some space between them - space which could be used more efficiently! However, to achieve that, you would have to place a signal each 5 tiles (with the example of Tilelength 4), which you can't do with the patch-setting of "Place signals every 2 Tiles", you would have to set this setting to either 5 or 1, both are not very satisfying solutions.</div>

Tim https://wiki.openttdcoop.org/index.php?title=User:Tim/Tilelength&diff=7094 User:Tim/Tilelength 2008-02-03T00:10:49Z

<p>Tim: </p> <hr /> <div>==Introduction==<br /> Whenever starting a new game, one of the first settings to be chosen is the used tilelength for your trains. This length can vary from supersmall trains with only three carriages (which would be tilelength 2) to huge mammoth trains with more than 20 carriages, which would make a tilelength greater than 10...<br /> <br /> <br /> ==Why Odd Tilelengths are better than Even Ones==<br /> [[Bild:Comparison_of_Tilelengths.png|thumb|Comparison of TLs 3,; 3,5; 4; 4,5 and 5]]Most people probably play with the Patch-Option "When Dragging, place Signals every: X Tiles" set to 2, accordingly there will always be one tile with a signal on it, one without one, one with a signal and so on. In #openttdcoop games, this is an undiscussed standard. As we do not want to change this setting, we should see how we can fit the tilelength of our trains to it. A common situation is that one or more trains are waiting before a station which is currently full. Those waiting trains could jam back until the mainline of our network and block it. The jammed part of the mainline would jam too and block other parts of the mainline, until the mess is complete. To avoid a situation like this, you can take various measures like expanding the jammed station or the waiting space before it. But just by choosing an odd tilelength, you can already ease the situation.<br /> If you look at the picture to the right, you will see that with "Place signals every 2 Tiles", trains with different tilelengths use the given space quite differently. While the trains with "natural odd" Tilelengths (3 and 5) have almost no space between them, the trains with other Tilelengths such as 3,5; 4 or 4,5 have quite some space between them - space which could be used more efficiently! However, to achieve that, you would have to place a signal each 5 tiles (with the example of Tilelength 4), which you can't do with the patch-setting of "Place signals every 2 Tiles", you would have to set this setting to either 5 or 1, both are not very satisfying solutions.</div>

Tim https://wiki.openttdcoop.org/index.php?title=User:Tim/Tilelength&diff=7093 User:Tim/Tilelength 2008-02-03T00:10:07Z

<p>Tim: </p> <hr /> <div>==Introduction==<br /> Whenever starting a new game, one of the first settings to be chosen is the used tilelength for your trains. This length can vary from supersmall trains with only three carriages (which would be tilelength 2) to huge mammoth trains with more than 20 carriages, which would make a tilelength greater than 10...<br /> <br /> <br /> ==Why Odd Tilelengths are better than Even Ones==<br /> [[Bild:Comparison of Tilelengths.png|thumb|Comparison of TLs 3,; 3,5; 4; 4,5 and 5]]Most people probably play with the Patch-Option "When Dragging, place Signals every: X Tiles" set to 2, accordingly there will always be one tile with a signal on it, one without one, one with a signal and so on. In #openttdcoop games, this is an undiscussed standard. As we do not want to change this setting, we should see how we can fit the tilelength of our trains to it. A common situation is that one or more trains are waiting before a station which is currently full. Those waiting trains could jam back until the mainline of our network and block it. The jammed part of the mainline would jam too and block other parts of the mainline, until the mess is complete. To avoid a situation like this, you can take various measures like expanding the jammed station or the waiting space before it. But just by choosing an odd tilelength, you can already ease the situation.<br /> If you look at the picture to the right, you will see that with "Place signals every 2 Tiles", trains with different tilelengths use the given space quite differently. While the trains with "natural odd" Tilelengths (3 and 5) have almost no space between them, the trains with other Tilelengths such as 3,5; 4 or 4,5 have quite some space between them - space which could be used more efficiently! However, to achieve that, you would have to place a signal each 5 tiles (with the example of Tilelength 4), which you can't do with the patch-setting of "Place signals every 2 Tiles", you would have to set this setting to either 5 or 1, both are not very satisfying solutions.</div>

Tim https://wiki.openttdcoop.org/index.php?title=File:Comparison_of_Tilelengths.png&diff=7092 File:Comparison of Tilelengths.png 2008-02-03T00:05:12Z

<p>Tim: </p> <hr /> <div></div>

Tim https://wiki.openttdcoop.org/index.php?title=User:Tim/Tilelength&diff=7091 User:Tim/Tilelength 2008-02-02T23:58:58Z

<p>Tim: New page: ==Introduction== Whenever starting a new game, one of the first settings to be chosen is the used tilelength for your trains. This length can vary from supersmall trains with only three ca...</p> <hr /> <div>==Introduction==<br /> Whenever starting a new game, one of the first settings to be chosen is the used tilelength for your trains. This length can vary from supersmall trains with only three carriages (which would be tilelength 2) to huge mammoth trains with more than 20 carriages, which would make a tilelength greater than 10...<br /> <br /> <br /> ==Why Odd Tilelengths are better than Even Ones==<br /> Most people probably play with the Patch-Option "When Dragging, place Signals every: X Tiles" set to 2, accordingly there will always be one tile with a signal on it, one without one, one with a signal and so on. In #openttdcoop games, this is an undiscussed standard. As we do not want to change this setting, we should see how we can fit the tilelength of our trains to it. A common situation is that one or more trains are waiting before a station which is currently full. Those waiting trains could jam back until the mainline of our network and block it. The jammed part of the mainline would jam too and block other parts of the mainline, until the mess is complete. To avoid a situation like this, you can take various measures like expanding the jammed station or the waiting space before it. But just by choosing an odd tilelength, you can already ease the situation.<br /> If you look at the picture to the right, you will see that with "Place signals every 2 Tiles", trains with different tilelengths use the given space quite differently. While the trains with "natural odd" Tilelengths (3 and 5) have almost no space between them, the trains with other Tilelengths such as 3,5; 4 or 4,5 have quite some space between them - space which could be used more efficiently! However, to achieve that, you would have to place a signal each 5 tiles (with the example of Tilelength 4), which you can't do with the patch-setting of "Place signals every 2 Tiles", you would have to set this setting to either 5 or 1, both are not very satisfying solutions.</div>

Tim https://wiki.openttdcoop.org/index.php?title=User:Tim&diff=7090 User:Tim 2008-02-02T23:11:32Z

<p>Tim: New page: '''Born:''' 01.07.1988 '''Home:''' Bornheim (between Bonn & Cologne), Germany {{flag|de}} '''Email:''' tim[at]rehms[dot]net '''Started playing TTD:''' I really can't remember when exact...</p> <hr /> <div>'''Born:''' 01.07.1988<br /> <br /> '''Home:''' Bornheim (between Bonn & Cologne), Germany {{flag|de}}<br /> <br /> '''Email:''' tim[at]rehms[dot]net<br /> <br /> '''Started playing TTD:''' I really can't remember when exactly, but i guess i was about eight years old... <br /> <br /> '''First Contact with #openttdcoop:''' November 2007 - Public Server Game #70, i just loved it, 700 Trains on a 256x256 map, my favourite Game until today :-)<br /> <br /> '''Specialist on:''' Finding & Fixing minor Issues, rebuilding a whole Hub because it would look better if it were one tile to the right...<br /> <br /> '''Prefers:''' Tilelenght 3 or 5, small & crowded maps, symmetric and good-looking layouts of stations, networks...<br /> <br /> '''Dislikes:''' Even Tilelengths, Huge Towns (in-Game...)</div>

Tim