Irrlicht Engine

posting the pay is good lol

hmm i do not understand what do u mean by make it faster?
before going on to discuss shaders, the rendering of such an amount of polygons is done by ogl or dx. irrlicht tries to do its best to deliver a good list for these renderes and does the best job, cuz i do not think there is another way to do ...

not to mention that (maybe for me only) but i found the source code of Irrlicht highly commented, readable and understoodable and easily changed.

here is the implementation
http://irrlicht.sourceforge.net/phpBB2/ ... p?p=100349

every time we move the camera, the engine recalculates the view frustrum.
in the irrlich implementation, an aabb is used to represent the frustrum.
the aabb is defined by 2 points a min and a max (MinEdge and MaxEdge).
so the frustrum iaabb is calculated using this function:

inline void ...

after further reading into the code i do not know how i missed it
but the frustrum is actualling being built from the projection and view matrices.
If i understand it correctly, it transforms the frsutrum into a normal box and for each cull test, the node aabb is tested if it interestcs with the ...

you r right, i will implement and build my idea then we discuss it

why would you need a special node for every type of object?
the inertia can be calculated from the volume. (from any mesh). so why have different nodes?

hello.
I have been decoding and playing with irrlicht.
I noticed that frstrum is calculated using intersections between planes while it
can be done faster from the view and projection matrices.
also the culling is pretty fast but really not that accurate (it does not have any of the special cases ...