dave/openttd
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

(svn r5136) Fix various style bugs:

Browse Source 
- Trailing whitespace
- Trailing empty lines
- Missing newline at EOF
- Missing svn:eol-style native
This commit is contained in:
tron
2006-06-05 18:10:43 +00:00
parent 30651e8bcb
commit aada042d57
24 changed files with 54 additions and 86 deletions
Download Patch File Download Diff File Expand all files Collapse all files

75
yapf.txt
View File

@@ -1,39 +1,36 @@
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.)
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.)