Irrlicht Engine

well, if this helps anyone, I solved (at least for me) the problem with the code in C++. The only change that needs to be made is:

In the modified headers, the class permission labels juggle where there's modifications. For example:

Public:
insert code here
Private:
insert code here
Public ...

refuses to compile in VC++ 6.0 also, but compiles in Dev-C++. So, in short, looks like I'm just gonna have to do it myself because DevC++ is evil and I refuse to use it, even if it does work sometimes.

visual studio 2003, flips out like mad when you try to compile Irrlicht with the changes. Vanilla Irrlicht compiles fine, but the minute I copy and paste the changed files into irrlicht, wham!

Irrlicht error LNK2001: unresolved external symbol "public: virtual void __thiscall irr::scene ...

why is this in advanced help?

f32 Radius
Radius of light. Everything within this radius be be lighted.


I'm pretty sure you just covered it right there.

If the light has 0 radius, it's not going to be producing light. If you continually modulate the radius you'll get a pulsing effect of sorts. Combine that with ...

yeah it is, maybe DirectX doesn't take overclocking too well. I know doom3 doesn't handle it well at all, and it is pretty dependent on direct x. If I set my clock rates at more than +10 on the core clock and +30 on the memory clock doom will crash every time. Though there's no point in overclocking ...

For me on an nVidia 7800, the difference is pretty massive.
OpenGL is usually 50% faster than DirectX. That's a pretty huge difference. Except for some reason when it comes to shadows, which is weird. Projective textures with OpenGL don't hit the framerate, but use shadows and then it will run ...