Random Comments on the Irrlicht Engine

maxmare · Post by **maxmare** » Wed Apr 15, 2009 1:02 pm

I was advocating the use of Irrlicht as a basis to build a game engine and someone posted this:

"IRRLicht very fast? that made me laugh so hard. I know irrlicht and it's everything but fast is uses DrawPrimitiveUp to draw trianglelists on the directx renderer, and everyone that knows a little bit of Direct3D knows that it's a funcion you should use ONLY for debugging.
It's a nice engine, clearly designed and with several years of support, it runs almost everywhere, but it's not fast at all "

I am not that far down the rabbit hole and I still think irrlicht is the best choice for my projects. I was just curious to see what you guys make of that comment.

Thanks, Rob

Sylence · Post by **Sylence** » Wed Apr 15, 2009 1:14 pm

Googled a bit around because I'm not that deep into Dx and found this
http://nexe.gamedev.net/directknowledge ... rimitiveUP

So from what they say DPUP doesn't seem to be that bad...

JP · Post by JP » Wed Apr 15, 2009 1:27 pm

If they think that function should only be used in debug why the heck didn't they inform the irrlicht devs? They just decided to let the engine waddle along using apparent debug functions instead? Their fault!

hybrid · Post by **hybrid** » Wed Apr 15, 2009 1:29 pm

Since Irrlicht 1.4 (wasn't it?) we have hardware buffers. So you can easily switch to the DrawPrimitive calls by changing the hardware hint of the mesh/meshbuffer.

CuteAlien · Post by **CuteAlien** » Wed Apr 15, 2009 6:16 pm

hybrid wrote:Since Irrlicht 1.4 (wasn't it?) we have hardware buffers.

I think it was 1.5 ;-)