Download OpenRCT2 0.0.6.0-develop build 4f61cae

Status & Branch: develop
Based on commit hash: 4f61cae8a80145880e6db11e56a518eb10e4b63b
Available since: 2017-01-09 20:58:47 (1 month ago)

Available downloads

Platform & Type Download SHA-256 Checksum File size
Windows x86 Portable ZIP OpenRCT2-0.0.6.0-develop-4f61cae-windows-win32.zip d9eb1d573… 5.22 MB
Windows x86 Installer OpenRCT2-0.0.6.0-develop-4f61cae-windows-win32.exe 29a91d866… 4.72 MB
Windows x64 Portable ZIP OpenRCT2-0.0.6.0-develop-4f61cae-windows-x64.zip de7109ff7… 5.94 MB
Windows x64 Installer OpenRCT2-0.0.6.0-develop-4f61cae-windows-x64.exe f3ab27f7d… 5.27 MB
macOS OpenRCT2-0.0.6.0-develop-4f61cae-macos.zip 3deb71877… 6.91 MB
Linux x86_64 OpenRCT2-0.0.6.0-develop-4f61cae-linux-x86_64.tar.gz 50d67d78a… 13.18 MB
Linux x86 OpenRCT2-0.0.6.0-develop-4f61cae-linux-i686.tar.gz 82cc0eac8… 5.91 MB
Windows x86 Debug Symbols OpenRCT2-0.0.6.0-develop-4f61cae-windows-win32-symbols.zip d4b4e45ff… 7.63 MB
Windows x64 Debug Symbols OpenRCT2-0.0.6.0-develop-4f61cae-windows-x64-symbols.zip 142f14e56… 8.28 MB

Changes in this build

Author Message
zaxcav Restrict peep backtracking further via pathfind_history[i].direction Dependent on the path layout it is possible for peeps to get stuck in backtracking cycles between two or more path tiles - each such tile is a turn around point because from that tile, the reachable tile on the search boundary that is closest to the peep destination is in the direction the peep came from. When storing/updating the pathfind_histroy, remove the direction the peep came from (in addition to the chosen direction) from the directions left to try to prevent such backtracking.
zaxcav Increment network version
zaxcav Reword comments with "from from".
zaxcav Update debugging messages to reflect changes in how pathfind_history[].direction is updated.
Gymnasiast Merge pull request #4997 from zaxcav/restrictBacktrack Restrict backtracking during peep pathfinding