#openttdcoop

Quite some time passed since the last (and first) World wide OpenTTD game day was celebrated. As on most accounts it was a very nice and joyfull experience, we decided to make steps forward to a next experience of that kind: Up to 55 players playing on a single map in different companies with the possibility to share infrastructure for a price with other companies.

Read the rest of this entry »

Join our small town #openttdcoop, located in the heartlands of the United Kingdom 😉

Update:
Some of us should visit http://openttdcoop.myminicity.com/ind instead. It is the next level.
Update 2:
Level three is now unlocked, please use: http://openttdcoop.myminicity.com/tra to improve our transport network.
Update 3:
I installed a little plugin which automatically generates the best link to trigger and also shows you our stats (thx Doke for the XML link).

Since a few days a nice patch is discussed at the tt-forums. It is another try to implement PBS in OpenTTD. The first idea of PBS is almost three years old. The old PBS was only supported by NPF (the old ‘new-pathfinder’) and since YAPF became the common standard the development was not continued.
We are currently running a dev server with YAPP (r12062M)
IP: dev.openttdcoop.org:3982
You can find the password at our irc channel: #openttdcoop.dev @ irc.oftc.net

This new patch looks really promising. The code is clean and fits to the standard openttd developers prefer. Now, lets have a look at the details. Read the rest of this entry »

Wouldn’t that be a cool thing to try?

dihedral and me talked about that and we came to the idea to make a “World Wide OpenTTD Game Day”. So, we are searching for a day where most people are online and we all should try to play together.

Read the rest of this entry »

stillunknown created an awesome patch which reduces the CPU usage quite a bit. The idea is to reduce the train collision checks with a sort of cache instead of a an on-going loop (details @ tt-forums).
Tonight we did some tests how this patch affects the game and it is quite impressing. I don’t want to say this is was a real performance test, but we checked the CPU load with a patched and an unpatched version of OpenTTD (r10048). My local machine was used as the server (PPC G5 2GHz) and as references we used Public Server Game #09 and Game #34.

The Results (vary with network layout, amount of trains and so on):
cpu usage in percent
Game#34: w/o patch: ~45%; patched: ~40% (~700 trains)
Game#09: w/o patch: ~67%; patched: ~50% (~1300 trains)

Especially games with a big mainline loop profit from this great patch.