phirekid718

I don't understand how someone gets away with publishing code that has memory leaks, leaving me to find them. I emailed the author, and I don't think I'm going to get a response.

I tried switching to the code found below, which is similar, and doesn't have any leaks. But the problem is that I am having trouble making it so that my character can hold something in his hand. With the textbook code, the application shows the character holding (a sword in this case) and moving it around just fine, but I can't find the memory leak after all this time. With the code in the article implemented the character can still make the motions, but the sword is not there.

If anyone has some insight please help. Maybe there's another resource on this subject? Thanks.

http://www.gamedev.net/page/resources/_/technical/game-programming/working-with-the-directx-x-file-format-and-animation-in-directx-90-r2079

Thanks. My problem was that I called D3DXCreateFont twice for the same object. A small, sneaky line created it the second time. The debug output was irrelevant in this case. The PIX object list output was also distracting. What worked best in this situation and probably will in most direct3d leak errors is to use PIX's  "log of all D3D calls made in frame number:" on frame one.