Well I though I'd stress test the engine.. (nothng better to do on a Sunday
the object was to be loaded as a terrain mesh.. it has 74000 polys (it is a big mesh,(covnerted) DEM file of a chunk of Mars, in OBJ format
It took 77666ms to create the OctTree for it..
http://shadowrunonline.sourceforge.net/ ... ypolys.jpg
And as you can see the polys are looking more like a haystack than chunk of mars.
Is there a limit to the octTree, how many subdivisions does octTree make. is the reason why the polys are borked because of the amount of them and octTree is unable to process that many..
I know I being silly loading a mesh with that many polys, but it is nice to test. BTW the orginal mesh I have has just over 200K polys.. it took 641597ms to create the octTree and I gave up waiting the screen refresh
Possible maximu poly count reached for .OBJ
Possible maximu poly count reached for .OBJ
Project Admin -
http://shadowrunonline.sourceforge.net
------------------------------------
There are 10 kinds of people, those that understand binary and those that don't.
http://shadowrunonline.sourceforge.net
------------------------------------
There are 10 kinds of people, those that understand binary and those that don't.