This is great work and all but I think it is distracting from what should really be developed, a pathing function. Fixing the z is just a temporary fix. We need proper pathing. When we do we will throw away all these fixes. And throwing away all of those man-hours makes for a lot of these: <insert tear emoticon here (no tear emoticon is maybe even sadder /tear)>
I am working on a couple pathing algorithms and am wondering if anyone has done some work on this already?
I'm using 2 strategies to reduce the complexity of the pathing algorithm:
(1) weighing node paths based on location between point a and b. (2) reducing the data set by pathing between the larger map subspaces then fine tuning the path.
The 3d rendering on page1 shows the triangles in the map to be grouped into larger square regions. You can build paths based on these larger square regions first by drawing a line between persuer and persuant than dropping it onto the map. Then building a path inside each square from entry to exit point.
This is really succesful for maps that dont require much pathing such as the karanas. But it has troubles in dungeons, where pathing is actually needed. I'm still looking at possible ways to break maps up into smaller 3d spaces that make sense as a graph. This will have to be done when a zone loads, since it is sucks the life force from any cpu. The first time a zone loads this 3d map could be generated and saved for future use.
My problem is this next step is like... a lot of work. I'm wondering if it wouldn't be better to just build path maps by hand.
Or be lazy and have zones listen to player movements and mutate pathing maps from those coordinates.
Either way, this is problem #1 in the emulator and should get more attention.
|