AI Libraries for Panda3D


Currently we do not have any plans to do this because of the amount of time commitment required.

If you look at page 2 in this post, towards the end there are details about what the csv data is. If you need further information let us know.

Hope this helps. Thank you!


ok so i found this:

Grid Size - size of the mesh.

NULL - specifies if a node exists or not.
0 - exists
1 - does not exist.

Node Type - specifies if it is the main node or the neighbor node.
0 - main node.
1 - neighbor node.

GridX - row index
GridY - col index

Length - length of each cell.
Width - width of each cell.
Height - currently overwritten as 0 since height info is not used.

PosX, PosY, PosZ - position of the node in the cell.

and it tells me a little about the Navmesh.csv in the fact theatim assuming it gives all info but things i dont understand are:

  1. ordering (does it care what order the information is in?)
  2. what does the position of the node do?
  3. shouldnt most of the length/widths of the cells be the same as squares are generally used?
    4.does the info start at the bottom left or does it matter?
  4. if a node does not exist does this mean not at all? if so why did we record it??
  5. I see in the static ob demo we can make things marked as not traverable is there an easy way to setup a csv to use my terrain as completely traverable then I can mark the stuff off i need? (I use a 1024X1024 terrain for now and i would like the map to use the same size if possible)

this is just some basic info that is nice to know course some of it really dosnt matter but i think it will help since i will probable have to build my mesh by hand. (Bascally im trying to come up with a way to use your system to hand write a csv but this will be time consuming and i need to know alot of what the system does without being able to read c++ so maybe a simple tutorial on writing the csv would suffice instead of answering all this)(the plan is to use this to write a python code to write a csv it may take time but its a tool so it dosnt need to be fast)

I hope that i didnt bother you too much and thank you in advance for any help you can provide!

Edit: Course I could just need to understand NavMeshes better myself I will be researching this subject to see if I can get a better understanding and with that hopefully be able to work with navmeshes with heightmaps.

Edit 2: I think i have found a round about way to make a navmesh. I use a heightmap in blender to make the terrain export it to egg this allows me to have my terrain info so that i can use it with PandaAI. If you wish to know how to do this go to: … heightmaps
the only downside is that the ratio in blender and Panda are not exactly the same so you may have to work with Panda or blender a bit to get it working properly for you.


this should probably be changed:

Pursue::Pursue(AICharacter *ai_ch, NodePath target_object, float pursue_wt) {
	_ai_char = ai_ch;

	_pursue_target = target_object;
	_pursue_weight = pursue_wt;
// i think this should be added
	_pursue_direction = LVecBase3f(0.0, 0.0, 0.0);

	_pursue_done = false;


another thing, the completion of the seek and pursue is determined by “int(target_distance) == 0”. meaning a distance to the target < 1 will make it finish, but depending on the scale of the models used in a game this isnt very practical.

  1. Yes you need to maintain the order as the data will be read in the same order into a vector which is then used for pathfinding.
  2. The AI characters will be using these node positions to traverse the mesh. These are the world space coordinates of the nodes. It will be the center of each grid cell.
  3. The constraint for the mesh is that it should have the same number of rows and columns. So if you have a rectangular mesh, then all the grid cells will not be squares and cells will have some minute dimension variance.
  4. The info starts at bottom left if I am not mistaken. I will confirm this anyhow.
  5. If a node does not exist (which means it is an obstacle) it will be specified as null when the data gets written into the vector during runtime. During pathfinding the A* checks if a node is traversable by doing a null check.
  6. So you can pretty much divide your entire 1024 X 1024 map into a grid. Make sure your grid has same number of rows and columns and then find the center position of each of the grid cells and assign it as the node positions in your csv. At this point all the nodes in your grid exist and are traversable. Now in the code you can toggle whether these nodes are traversable or not. As long as the data in the csv that you generate is in the same format I don’t see why you should have any issue using our pathfinding.

Just so that we are on the same page, we use waypoint meshes in PandAI as compared to Navmesh. And we know the confusion is due to the naming convention we used to explain the mesh generation process and pathfinding. Our apologies.

Hope you find this useful.



That was a great responce and it really helped I managed to get it working but there are a few issues: as i already posted this info see thread below for question. There seems to be something wrong with the egg file it looks right though…

I think you guys are probable the only ones that can tell me what im doing wrong.


Unfortunately PandaAI currently does not support blender models. We are still working on it. The way triangles are ordered in Blender eggs are very different from how Maya and Max does it. Hopefully we can get it working soon. Meanwhile if you have access to Maya or Max you shouldn’t have any problems.


Noted. I think rather than post bugs here on this post, we should do it on a common front. Any suggestions on a bug repository.


How about Launchpad?
You could possibly use a tag to mark PandAI-related bugs.


Ok so I would like to announce that the first version of the code to produce a navmesh.csv has been successful. This system was setup for use with geomipterrain. I am now able to pathfind perfectly with this code.

How it works: I used the code to setup a geomipterrain and then grab a bunch of information from the terrain then math code is looped through and a set of points are created that represent the grid that will be used to setup the paths. This does include finding all the neighboring grid squares in the correct order. as it is going throught the lines of the code it is writing them to navmesh.csv now you have the file you need to use PandaAI without having to recreate your terrain in maya or Max.

This system could be rewritten to use any type of terrain the only limit ive found so far is the number of lines in excel. This means that larger terrains Like geomip or |Craigs| new paging terrain may have issues if you make them too big as you would need lots of decent size squares to fill the terrain. (This system could be changed to paging as well if the code runs fast enough)
also depending on the version of excel used this may limit you to 65k lines (office 2003: around 75 squares per row so terrain smaller than 700px X 700px).

To find out the number of excel rows needed before you try to make the file use (N*N)*9 where N is number of sqaures requested. to find a good number for squares you may need to test although i find using the length of my picture/9 shows me aprox the number of squares i want as i find 9px per square is pretty accurate.

I plan on releasing the code later today once optimizing the code is completed.

I would like to take the time to thank a few people that made this possible:
JohnKol (for giving me the info for setting up the navmesh)
|Craig| (For walking me through optimizing the code)
CMU (For making the PandaAI)

Also thank you to everyone in IRC chat that let me bounce ideas off you for this as it was a big help in figuring out how to write the code.
Edit: This code has been fixed for issues that were found below this post.

import direct.directbase.DirectStart
from direct.showbase.DirectObject import DirectObject
from panda3d.core import PNMImageHeader, Vec3, Texture, GeoMipTerrain, VBase4
from panda3d.core import Filename, BitMask32, TextureStage
#import csv
class World(DirectObject):
    def __init__(self):
        This is a simple system to make PandaAI work with Geomip terrain
        Use ctrl-F to find the line you need to change by using the code inserted at the number in this text
        Things you need to change to make this work:
        1.use your heightmap                            - self.terrain.setHeightfield(Filename("Terrain/Level 1/terraintest.bmp"))
        2.change to number of blocks you want to use    - self.terrain.setBlockSize(64)
        3.Change your texture                           - loader.loadTexture('Terrain/Level 1/ground.jpg')
        4.change this to your heightmap again           - header.readHeader(Filename("Terrain/Level 1/terraintest.bmp"))
        Now you can use this code to make your Navmesh.csv for PandaAI.
        #Load the first environment model
        self.terrain = GeoMipTerrain("ground")
        self.terrain.setHeightfield(Filename("Terrain/Level 1/terraintest.bmp")) #Terrain/game heightmap.bmp
        # Set terrain properties
        self.terrain_tex = loader.loadTexture('Terrain/Level 1/ground.jpg')
        self.terrain_tex.setMagfilter (Texture.FTLinear) 

        # Store root NodePath for convenience then set root settings for the terrain
        root = self.terrain.getRoot()
        #Set the terrain itself to be collide-able.
        ts = TextureStage('ts')
        header = PNMImageHeader()
        header.readHeader(Filename("Terrain/Level 1/terraintest.bmp"))
        hy = header.getYSize()
        hx = header.getXSize()
        bs = self.terrain.getBlockSize()
        cuber = (hx-1)/bs
        cubing2 = ((hx-1)/bs)/2

        file=open("navmesh.csv", "w")
        def doLine(*x): file.write(','.join( str(v) for v in x)+'\n')
        doLine("Grid Size",bs)
        for j in range(bs):
            cubing = ((hx-1)/bs)/2
            for i in range(bs):
                def h(f,a,b,c=1):
                    if f: doLine(1,1,0,0,0,0,0,0,0,0)
                    else: doLine(0,c,i+a,j+b,cuber,cuber,0,cubing+cuber*a,cubing2+cuber*b,self.terrain.getElevation(cubing+cuber*a,cubing2+cuber*b)*self.terrain.getRoot().getSz())
                h(False,                   0, 0,c=0)
                h(i-1 < 0 or j+1 > bs-1,  -1, 1)
                h(i-1 < 0,                -1, 0)
                h(i-1 < 0 or j-1 < 0,     -1,-1)
                h(j-1 < 0,                 0,-1)
                h(i+1 > bs-1 or j-1 < 0,   1,-1)
                h(i+1 > bs-1,              1, 0)
                h(i+1 > bs-1 or j+1 >bs-1, 1, 1)
                h(j+1 > bs-1,              0, 1)
                cubing += cuber
            cubing2 = cubing2 + cuber
        #Updates the taskMgr
        taskMgr.add(self.updateTask, "update")

        #this updates the terrain when needed
    def updateTask(self, task): 
        return task.cont 




Thanks. I have started setting up bugs in bugs.launchpad.


Added your pursue find to the bug list.

To the community, please feel free to add bugs to this list. Tag them as PandAI for easy searches.


Sounds exciting! I am really interested in looking at this working and the source code.


Nice job Chia_Pet! It would be great if you could post your code to the community so that others can make use of it. And thanks for making use of our libraries.

.csv just means a bunch of comma separated data and is not in anyway an excel format. You can always open it in a notepad or any other text editor for debugging. Excel just recognizes the format and shows it to you in a clean tabular form. So in short the .csv format is not limited by Excel’s limitation. Hope that makes sense.


Well I hope everyone likes the above code. I know I do and again thanks to |Craig| who made this code run in like 2 seconds rather than 6 minutes (origional runtime) lol.

Now one thing you need to know when you can see your terrain the code is done so shutdown and grab your navmesh.csv to use in your real game! (I did it this way so you knew that it didnt just crash on you and i had to load the terrain to make it work with auto number system anyway)


ok new problem, I got the AI working but im not sure what im doing wrong. Ralph can normally move around my terrain just fine using setZ so i figured by making him walk by himself it should be the same but if he is no at 0 height he will fall over i am wondering if this is something to do with PandaAI or maybe my heightmap I generate (as it dosnt include height cause you said to overwrite height). I cannot seem to findout why he will fall when no on level terrain so any advice would be great.

Never mind I figured what i did wrong in the code I made. I designed it for 0 on al z’s so as soon as i went and tried to go above that our code was fighting even though in your demo you overwrite both sets of Z coord’s apparetly this shouldnot have been done. that being said I am working on a fix to my code to work properly for 3d so that this issue dost happen again!


Hi all,

Is anyone else using PandAI with Maya? I’ve followed the tutorial videos but the resulting navmesh.csv doesn’t seem to work. I always get the errors “couldnt find destination” and “couldnt find source.”

Here’s the sequence I used:

  1. Created a 60x60 plane centered at (0,0,0) in Maya 2009
  2. Under INPUTS->polyPlane1 (my plane) I changed the subdivision width and heights to 4 to give me a 4x4 grid
  3. Exported this plane as “env_full.egg” and verified it looked right in pview
  4. Selected three of the center faces and deleted them
  5. Exported this new plane as “env_col.egg” and verified it looked right in pview
  6. Ran C:\Panda3D-1.6.2\bin\egg-trans on BOTH “env_full.egg” and “env_col.egg” to create “env_full_tri.egg” and “env_col_tri.egg,” respectively
  7. Ran “meshgen env_full_tri.egg env_col_tri.egg” to create navmesh
  8. Swapped out my “env_col_tri.egg” and navmesh in the PandAI demo StaticObstacleDemo as a means to test it out. (Note: I repositioned ralph and the destination so that they were inside of my area at the start)

Both ralph and the arrow are definitely inside of the plane, but I get the source and destination errors mentioned above. Any ideas what I’m doing wrong?

Thanks for your help!

Well, I’ve tracked down the source of the problem. Here it is for others to learn from.

The navmesh.csv that’s being generated from my eggs appears to have swapped Length with Height and PosY with PosZ.


Grid Size	3								
NULL	NodeType	GridX	GridY	Length	Width	Height	PosX	PosY	PosZ
0	0	0	0	4.44E-15	20	20	-20	-4.44E-15	20
1	1	0	0	0	0	0	0	0	0
1	1	0	0	0	0	0	0	0	0
1	1	0	0	0	0	0	0	0	0
1	1	0	0	0	0	0	0	0	0
1	1	0	0	0	0	0	0	0	0
0	1	1	0	4.44E-15	20	20	0	-4.44E-15	20

If I swap them by hand, then the navmesh works great.

Root cause:
I was using Maya in Y-Up instead of Z-Up coordinate system. Do’h.


I’m really excited you guys are looking at AI stuff for Panda3D, but I was a bit disappointed by the navigation mesh functionality. It seems as if it’s more of a navigation grid than a mesh, and it looks like it needs to be created manually.

So, I took a look at that Recast project, and ended up getting a small portion of it working with Panda3D. Basically I modified the source of their demo application to export .obj files, which I then imported into Blender, and exported to .egg files. Then I used Panda’s vertex reading utilities to go through the vertices and generate pathfinding data.

I got pathfinding to work pretty well with my own methods brainstormed in Python, but I cut some corners for performance, and it’s certainly not a textbook navmesh implementation. However, it makes me think that someone experienced with the C++ workings of Panda3D could crank out some good code fairly quickly, especially since a lot (if not all?) of it is already done in PandAI.

I think the ability to use automatically-generated navmeshes from Recast is a great feature, and it’s already saved me a lot of time. So, does the current version of PandAI support navigation meshes with different shapes (actually, just triangles)? If not I might look into working on it in C++, but it will take me some time to get up to speed.


Wofire guys also used it: … ion-meshes


@ et1337

Yes you are right it is really a navigation grid.

I think it would be a great idea to get Recast working with PandAI and it was something we really didn’t have the time to integrate into Panda3D but really wanted to.
It is something I have been meaning to work on too. If you wish to try it, let me know if you reach any hurdles on the PandAI side of the code.


Could you please elaborate on which ones you used and an explanation of how.

@ treeform

Thanks for the link.



Here’s my vertex processing code, It’s mostly ripped straight from the manual.

I extract all the edges, and then use them to form “nodes” which are basically triangular areas in the mesh. The edges then link the nodes together, forming a graph which I can traverse with A*.

def _processNode(self, node):
		geomNodeCollection = node.findAllMatches('**/+GeomNode')
		for nodePath in geomNodeCollection:
			geomNode = nodePath.node()
		for edge in self.edges:
			if len(edge.nodes) <= 1:
				# This edge isn't between two nodes, so we don't need to worry about it when pathfinding.
				# But we still need it for determining which node an agent is in.
				edge.navigable = False

	def _processGeomNode(self, geomNode):
		for i in range(geomNode.getNumGeoms()):
			geom = geomNode.getGeom(i)
			state = geomNode.getGeomState(i)

	def _processGeom(self, geom):
		vdata = geom.getVertexData()
		for i in range(geom.getNumPrimitives()):
			prim = geom.getPrimitive(i)
			self._processPrimitive(prim, vdata)

	def _processPrimitive(self, prim, vdata):
		vertex = GeomVertexReader(vdata, "vertex")
		prim = prim.decompose()
		def getVertex(index):
			vi = prim.getVertex(index)
			return vertex.getData3f()
		for p in range(prim.getNumPrimitives()):
			s = prim.getPrimitiveStart(p)
			e = prim.getPrimitiveEnd(p)
			for i in range(s, e):
				v = getVertex(i)
				if i + 1 >= e:
				v2 = getVertex(i + 1)
				edge1 = self.addEdge(v, v2)
				if i + 2 >= e:
				v3 = getVertex(i + 2)
				edge2 = self.addEdge(v2, v3)
				edge3 = self.addEdge(v3, v)
				self.nodes.append(NavNode(edge1, edge2, edge3))

To determine which node an agent is in, I just do a dot product from the agent’s position to the center of each of the three edges. If all three dot products are positive (or negative, I can’t remember), the agent must be inside the node. I do some other stuff for vertical testing as well. It’s all in the A3P repository.


I hope it’s my search skills failing, but I haven’t been able to find a version of the Navigation Mesh Generator for Linux. In the download section of the PandaAI website there’s only Windows exe and source. Is it included in Panda 1.7? And if so, under what name and/or in what directory (of it’s not /usr/bin)? Thanx in advance.