The Inefficient Detour Grid
After playing some OpenTTDCoop games I thought about a local game with a grid all over the map. All you need is a crazy network plan, a lot of time and a jackass who build this plan, me.
Read the rest of this entry »
Non-blocking SL to ML mergers
With centralized aproach which is taken by #openttdcoop community it’s hard to overstress importance of prioritizing traffic streams. It is very essential to keep mainline traffic moving because under high volume conditions, when trains are closely following each other, slowing down one train means slowing down whole lane. That might (and often does) cause a chain of negative events leading substantionaly lower throughput of network and traffic jams at other part. Bear in mind – stoping traffic is nearly instant, however accelerating whole lane might take months of game time. This is something to be avoided at all costs, sideline traffic must wait untill there is a gap and only then merge into ML without any intereference to ML stream.
This is why i recommend designing SLHs with non-blockign idea in mind and having properly sized priority windows.
Express and Local ML separation
Basically, the concept is to separate empty and full trains hence giving them different priorities and manipulating train streams with more efficincy while still maintaining single network.
Express in this case means trains headed to the end of mainline, either to drop or drop/pickup station.
Local would be the opposite – from drop to SLH and raw materials pickup stations.
All bi-directional trains carrying goods, pax and other applicable cargo that under circumstances goes both ways – should be using express lanes. All full trains headed to drop – should be using express lanes, but are lower priority and to be inserted into express stream with minimal interuptions of express trains stream (read: priority queue and loadbalancers needed).
All returning to pickup empty trains are getting there via local lanes, which are hubbed in close-to-regular way.
Updated Blog to WP 2.1.3 & The Feedburner will leave
Today I updated our Blog to version 2.1.3 (the newest stable release). It didn’t change too much. Improved security and some other changes come into play. If you want details, check the wordpress website.
Another Important Note is: I’ll remove this feedburner thingy again. Its not used by much visitors and therefor it is only interesting if you use it from the scratch.
The Feddburner-Plugin is already de-activated and I’ll remove our feed in one week. Please change back to the normal feed-urls:
Blog-Posts: http://blog.openttdcoop.org/feed/
Comments: http://blog.openttdcoop.org/comments/feed/
Anyway quite some task on my ToDo-List. 🙁
Maybe you want to help me.
Passenger Destinations – we need them!!
Hello community,
today, I read this forumpost about passengers with specific destinations. It seems like a lot of improvements were made and prssi supplied a pretty stable code by now. Therefore, I decided to compile myself a Pax-Destination-patched OpenTTD.
Read the rest of this entry »
