Irrlicht Engine

cassini wrote:being an ex Ogre user, I prefer Irrlicht hands down for its simplicity.
Ogre is the kind of gratuitously overly complex exercise in OPP for not particular reason.

Use ALT-F4 to exit the demos. ESC isn't support.

Midnight wrote:If you have a lifetime then then take the way of lazy jane, sit back and wait for Irrlicht to evolve.

It's what I'm doing!

OpenGL on Linux is still very slow - 235fps for the terrain demo. I'll see if I can profile it if I have the time.

Profile your application and the Irrlicht library to see what's taking so long.

No, no, no! Don't just ignore the warnings - fix them! One of them is a potential loss during a conversion. This should be fixed. The other seems to be implying you're mis-using delete.

Ignoring warnings is bad!

Create one complete model and several models for the broken object. While the object is whole render the complete single model. When the object breaks, quickly replace the complete single model with the broken models, arranged so they look like the complete model. In subsequent redraws move the brok...

Modify the Irrlicht source for the FPS camera. Rebuild Irrlicht and voila!

Why do you think we're treating you like a spammer?

Is your homework due on Friday? Have you invented a time machine?

No?

Ooh you in trouble boy!

For one thing the Unreal and Quake3 engines are already used in released titles and are both complete FPS engines. Irrlicht is incomplete and untested. Graphically, I've seen nothing to convince me that Irrlicht can rival either. But then Irrlicht is open source (as is Quake 3) and was written prima...

Where does it crash? Did you use the debugger?

zziplib?

Create a small "bone" in the model at the end of the barrel. When the gun is fired, retrieve the location of that bone and use that as the starting point for the bullet. Does Irrlicht even support bones??

Did you use the debugger to find out why it's crashing?