Software Update: OpenTTD 1.1.0-beta2

The second beta release of version 1.1.0 of OpenTTD was released on Friday. In this open source clone of the Microprose game Transport Tycoon Deluxe, the goal is to build a transport empire by road, rail, water and air. OpenTTD can do more than just mimic the original game. For example, up to 64 times larger maps can be used than in the original, the AI ​​is worthy of its name and there is support for multiplayer and ipv6. Versions for Windows and Linux are available and the Mac OS X version has fortunately been picked up again after some absence. Here’s what’s changed in this release:

New features:

• Command logging using the admin interface (r21668)
• Concept of automatic station orders; add stub orders for intermediate stations and remove them when not visiting them anymore. This allows you to see what trains visit a station without actually having to order a vehicle to stop at all stations (r21642)

Added:

• [NoAI] AIEventTownFounded (r21664)
• [NoAI] AIRail::GetName() to get the name of a railtype (r21663)
• [NoAI] AITown::IsCity() so AIs can find out which towns grow faster than others (r21654)

Changed:

• don’t show price to build a bridge in the scenario editor as they are free to build there [FS#4358] (r21673)
• do not highlight tile when selecting a vehicle to clone or an order to skip to (r21616)

Fixed:

• Estonia introduced the Euro in 2011 (r21670)
• Autofill timetable had side effects in test mode, possibly causing desyncs in MP [FS#4354] (r21660)
• Cargo payment graph was not properly invalidated when payment rate changed [FS#4351] (r21658)
• Use a bool instead of uint8 to store a bool and use the dedicated accessor function when reading boolean settings [FS#4345] (r21656)
• Infinite loop in the road pathfinder due to bouncing around in an ‘one way’ trap; two one ways pointing towards eachother making it impossible to leave [FS#4338] (r21651)
• make'[centre|main] view’ consistent, and make'[main|global] view’ consistent [FS#4339] (r21650)
• Newly created skip-to order was created at wrong place (r21633)
• Ships with the old pathfinder would easily show up as lost, even when it would eventually find a path. Now also the distance from the ‘end’ of the pathfinding run to the destination is compared to the current distance to the destination; if the distance to the destination at the end of the pathfinder run is less than the current distance from the destination the ship will not be marked as lost. This means that the ships with the old pathfinder will less likely get marked as lost, but due to the design of the old ship pathfinder there ‘lostness’ is merely a best guess. When you still get a lost message you need to build buoys to guide the ship pathfinder [FS#4325] (r21631)
• Version detection of subversion branches and tags got broken (r21630)
• Crash under certain circumstances when using autorail [FS#4327] (r21619)