Infinite Procedural Terrain Engine

AnimateDream · December 15, 2010, 4:41am

Sorry I built a custom panda out of the cvs to get true threads running.

I fixed this unintentionally actually. The program no longer caches heightmap images to disk. It was almost always a net loss for performance, and I haven’t gotten around to needing to add hand modifications to the procedural terrain.

Craig:

I looked in terrain.py and say a loop. I changed it to this:
        ys=self.image.getYSize()-1
        gh=self.terrain.getHeight
        sg=self.image.setGray
        yo= self.yOffset
        for x in range(self.image.getXSize()):
            xo=x + self.xOffset
            for y in range(ys+1):
                sg(x, ys-y, gh(xo, y + yo))
which cut the runtime of that code to about 66%. nothing special just localizing and avoiding some extra calls. I don’t really get what that code does, but faster is better right?

Yikes. Thank you for pointing that out. I really hadn’t done much optimization work yet. Also I’m still used to c++ where the execution time wouldn’t be too noticeably effected by some of those changes. Sorry.

Also the code just builds an image for a geomipmap out of my basic height/noise function.

Anyways, I understand better some of panda3d’s geomipmaps functions and properties and corrected a few dumb mistakes. I also just committed my first comprehensive revision aimed at restructuring things for better performance. Its still too slow in my opinion, but its at least somewhat presentable now.

I still have some comments and refactoring to make it simple to grasp. Bear with me. Thank you for all of your help so far.