|
1 Ships: |
|
2 ====== |
|
3 Set the YAPF (Yet Another Path Finder) type in the "Configure Pathes/Vehicles/YAPF for ships": |
|
4 - 0 - No YAPF (NPF or old PF) |
|
5 - 1 - YAPF type 1 (Node = Tile/Trackdir, 90 deg. turns allowed) |
|
6 - 2 - YAPF type 2 (Node = Tile/ExitDir , 90 deg. turns allowed) |
|
7 - 3 - YAPF type 3 (Node = Tile/Trackdir, no 90 deg.) |
|
8 - 4 - YAPF type 4 (Node = Tile/ExitDir , no 90 deg.) |
|
9 |
|
10 |
|
11 Set the "npf_max_search_nodes" value in your openttd.cfg to tune the pathfinder behavior. |
|
12 This value tells, how many nodes (Tile/Trackdir or Tile/ExitDir) combinations the pathfinder |
|
13 should visit before it ends. The lower number would mean quicker, but less accurate results. |
|
14 The "npf_max_search_nodes" value is shared between NPF and YAPF and has the same meaning. |
|
15 |
|
16 The pathfinder without such limit would be unusable on large maps, where number of visited |
|
17 nodes can exceed 10 milions. NPF on my machine (dual code AMD 4400+) with 1 milion of nodes |
|
18 visited took 2 minutes to finish, but with this limit set to 10000 it takes 20 miliseconds. |
|
19 The new YAPF had similar results (18 seconds vs. 4 miliseconds). |
|
20 |
|
21 |
|
22 Road Vehicles: |
|
23 ============== |
|
24 Set the YAPF (Yet Another Path Finder) type in the "Configure Pathes/Vehicles/YAPF for road vehs": |
|
25 - 0 - No YAPF (NPF or old PF) |
|
26 - 1 - YAPF type 1 (Node = Tile/Trackdir, 90 deg. turns allowed) |
|
27 - 2 - YAPF type 2 (Node = Tile/ExitDir , 90 deg. turns allowed) |
|
28 |
|
29 Trains: |
|
30 ======= |
|
31 Same types as for ships: |
|
32 - 0 - No YAPF (NPF or old PF) |
|
33 - 1 - YAPF type 1 (Node = Tile/Trackdir, 90 deg. turns allowed) |
|
34 - 2 - YAPF type 2 (Node = Tile/ExitDir , 90 deg. turns allowed) |
|
35 - 3 - YAPF type 3 (Node = Tile/Trackdir, no 90 deg.) |
|
36 - 4 - YAPF type 4 (Node = Tile/ExitDir , no 90 deg.) |
|
37 |
|
38 |
|
39 |