Irrlicht Engine

What is your screen depth? It looks like you have screen depth set to 16 bits so it's dithering colors.

With both the release 1.4 for Mac OS and the latest SVN, if I try to compile the examples "out of the box" (launching the XCode project file which builds the library and most of the examples) the examples do not work. Demo runs but intermittently displays the axis inversion issue I reported earlier ...

Okay I found that the bulk of examples that didn't build failed because they require console input (as I recall console can be added to a Cocoa app).

My quick fix was to modify all the main.cpp files for the examples to default to OpenGL (and yes to any of the yes/no questions), skirting the ...

I was delighted to see the Mac OS support for Irrlicht 1.4 and immediately built the engine and demos on my Intel iMac using XCode 3.0 under Leopard (Mac OS X 10.5).

The Demo runs with OpenGL, but in full screen mode it looks like axis are being inverted, especially for the textures. In window mode ...

I sounds like you may be writing the internal 16 bit wide character format in the Linux version. This would explain why a simple text editor might believe it was a binary file, and why you're seeing spaces between characters.

I think the place you'd have to change would be in the meat of COpenGLNormalMapRenderer.cpp

I see a lot of hand coded D3D asm code that has been directly translated to its OpenGL equivalent. I'm going to have to get a lot deeper into the OpenGL docs before I'd venture a guess (and this from a guy ...

Ok lets solve one problem at a time. Looking back at your original code problem I see you're referencing "./Data..." in the first instance and "../Data..." in the second.

Try building the demo app. Then try changing to your alternate mesh.

The call to load the archive simply tells the file system ...

The .BSP is located in the .PK3 file (which is really a .zip archive). After you've told the file system about the .PK3 just load the mesh "Map.BSP". Do not include the path to the directory the PK3 is in unless you have another separate BSP file in there with the same name.

There is an interesting discussion of the concept of "bones" in mesh animations here http://www.okino.com/conv/skinning.htm

Doing a search of the engine source with XCode I only see one animated mesh format that addresses the concept of "bones" (skeletal mesh animation) in CAnimatedMeshB3d.cpp, so ...

Programs are composed of data types and the methods or functions for manipulating them. To actually combine two programs you will need to at least be familiar with the features of those two programs.

Since Irrlicht uses object oriented programming throughout it is fairly straightforward to get at ...

What format is the other mesh in?

As for the default value of material shininess I'd have to search the engine code. Obviously non-zero since that changed the behavior you observed.

Shininess is the quality of reflecting light. Look at a real life black object that's shiny (maybe a black car). Try to look at it objectively and ...

Although I have spent a bit of time learning the Irrlicht 3D Engine your question made me curious so I looked at the Ogre site. Downloading the source I found it a bit fragmented for purposes of easy compilation (there seems to be a Windows section and a Linux & Mac section...I opened the XCode ...

Unfortunately that physics engine only seems to support Windows(TM) operating systems and I am currently devoting my efforts to cross platform SDKs.

Looking at the Irrlicht tutorial page it appears that this tutorial was tested with Irrlicht 0.14. Perhaps if you download that version of the ...

Ok I saw the picture so now I can see what you mean by "grey". You are referring to the lighter color when the object is set to "lighted".

Looking in the engine source the flag EMF_LIGHTING is defined in the header SMaterial.h as a flag used when dynamic lighting is present. What is your light ...