Files @ r4682:f3c270aa98d4
Branch filter:

Location: cpp/openttd-patchpack/source/yapf.txt - annotation

miham
(svn r6587) WebTranslator2 update to 2006-09-30 17:59:21
brazilian_portuguese - 44 fixed by tucalipe (44)
czech - 3 changed by Hadez (3)
hungarian - 8 fixed by miham (8)
polish - 8 fixed, 4 changed by meush (12)
swedish - 8 fixed by cjw (8)
Ships:
======
Set the YAPF (Yet Another Path Finder) type in the "Configure Pathes/Vehicles/YAPF for ships":
 - 0 - No YAPF (NPF or old PF)
 - 1 - YAPF type 1 (Node = Tile/Trackdir, 90 deg. turns allowed)
 - 2 - YAPF type 2 (Node = Tile/ExitDir , 90 deg. turns allowed)
 - 3 - YAPF type 3 (Node = Tile/Trackdir, no 90 deg.)
 - 4 - YAPF type 4 (Node = Tile/ExitDir , no 90 deg.)


Set the "npf_max_search_nodes" value in your openttd.cfg to tune the pathfinder behavior.
This value tells, how many nodes (Tile/Trackdir or Tile/ExitDir) combinations the pathfinder
should visit before it ends. The lower number would mean quicker, but less accurate results.
The "npf_max_search_nodes" value is shared between NPF and YAPF and has the same meaning.

The pathfinder without such limit would be unusable on large maps, where number of visited
nodes can exceed 10 milions. NPF on my machine (dual code AMD 4400+) with 1 milion of nodes
visited took 2 minutes to finish, but with this limit set to 10000 it takes 20 miliseconds.
The new YAPF had similar results (18 seconds vs. 4 miliseconds).


Road Vehicles:
==============
Set the YAPF (Yet Another Path Finder) type in the "Configure Pathes/Vehicles/YAPF for road vehs":
 - 0 - No YAPF (NPF or old PF)
 - 1 - YAPF type 1 (Node = Tile/Trackdir, 90 deg. turns allowed)
 - 2 - YAPF type 2 (Node = Tile/ExitDir , 90 deg. turns allowed)

Trains:
=======
Same types as for ships:
 - 0 - No YAPF (NPF or old PF)
 - 1 - YAPF type 1 (Node = Tile/Trackdir, 90 deg. turns allowed)
 - 2 - YAPF type 2 (Node = Tile/ExitDir , 90 deg. turns allowed)
 - 3 - YAPF type 3 (Node = Tile/Trackdir, no 90 deg.)
 - 4 - YAPF type 4 (Node = Tile/ExitDir , no 90 deg.)