correct and iB3D is the same way.  it has underlying types with the all the actual code.  the functions are essentially just wrappers to the type methods.  i am currently just documenting the functions and then will move on to the types.  it also has a factory system setup so that you can substitute your own extended types for each type iB3D creates, similar to how i did the 3Impact mod.

probably the coolest feature of iB3D are the functions made available that native Irrlicht doesnt have... like the move/turn functions and an easy to use input system.  the camera is definately an improvement over the base Irrlicht camera as well.  some pretty exciting stuff in here and getting better every day.

in the end im sure there will be features that i just cant figure out or do, but there will also be cool new functions/types for things like shaders and all the special entities Irrlicht has natively.  hopefully the end result will be making Irrlicht easier to use for folks familiar with B3D proper.  theres truly something to be said for the ease of use of B3D proper.  BRL really did a magnificent job.

and i forgot to mention the best things of all...  learning and a sense of accomplishment.  it just feels good

Ok, so the aim is to provide a B3d style interface. Which is a good thing.
However.... Simons MiniB3D interface is a better one. (I dont mean better than yours, I mean better than B3D),
That is the way he has organised the types so that for example any command that has the first parameter as an entity can be called as a method/Function of that entity

i.e
MoveEnity (AnEntity,x#,y#,z#) can now be expressed as AnEntity.Move(X#,y#,Z#)

An arbitary differance one might think, but an improvement nonthe less. So...... (Well you know)

some quick notes...  i finally fixed the camera roll issue where it didnt seem to be recognizing the Y rotation.  also got EntityInView() implemented.

cruisin

wat is it ?

Thanks, this module is great.