Irrlicht Engine

Great! Thank you for the quick fix

Here is a .zip with both the original .blend file and an exported .irrmesh: http://yellow-hut.com/images/Cube.zip

As a quick test I just modified the 04.Movement example, like this:


/*
Now we create another node, movable using a scene node animator. Scene
node animators modify scene nodes ...

I'm having some problems using irrb exported objects with flat shading. Everything seems to work fine when I use gouraud shading or no lighting at all but without gouraud shading I get results like this:

http://img259.imageshack.us/img259/108/samplew.th.png

On the left there is an irrlicht test ...

Okay, got it working. It was just a combination of screwed up normals and messed Blender imports

I have tried both with the test cube and several meshes in different formats.

I haven't used Irrlicht for a while but I think this still worked on my machine a few versions ago when I last tried.

Edit: I can post some test code and screenshots later when I get home.

Nope, that's not it. I'll have to do some more testing; it feels like it would have something to do with normals but the problem is same with unscaled test cube and shouldn't ambient color have some effect anyway.

Gouraud shading seems to work fine but I'm getting some weird results when trying to render flat shaded objects with EMF_LIGHTING on and EMF_GOURAUD_SHADING set to false.

Basically the problem is that all the polygons are either fully lit or completely dark, there are no gray areas. Ambient ...

I have the same problem when using OpenGL device on my laptop (ancient Unichrome videocard, might be part of the problem). There are no visible textures at all and I'm not sure if it is a driver problem since all the other OGL software works fine. I think it still worked with some older Irrlicht ...

I have noticed that Irrlicht programs act quite weird when run from emacs; the game window is invisible but otherwise the game runs seemingly fine, e.g. possible mouselock is activated etc.
I have no idea what might be causing it, but I have never seen similar behaviour with other apps or libraries ...