Page 1 of 2

15.600.012 triangles

Posted: Tue Sep 26, 2006 9:52 am
by Fernando Tella
Sorry Tim. :mrgreen:

I'm sure you can make the triangles count go higher.

Image

Memory usage for mxcl was near 3.5GB; 3dsmax around 2.5GB.

Posted: Tue Sep 26, 2006 10:00 am
by NicoR44
lol

Posted: Tue Sep 26, 2006 10:02 am
by devista
la leche :twisted:

Posted: Tue Sep 26, 2006 10:04 am
by tom
There's no triangles like there's no spoon now :P :lol:

Posted: Wed Sep 27, 2006 2:14 am
by Tim Ellis
Wow. :shock:

ImageImageImageImageImageImageImageImageImageImageImageImageImageImage

Congratulations. :D

Have you tried a limit yet? Can your machine cope with 20million?

Tim.

Posted: Wed Sep 27, 2006 2:49 am
by Fernando Tella
Thanks Tim.

I have not tryed yet.

I'm quite intrigued though why max crashes (out of memory) with some finished scenes with ~1.5mill triangles (more textures and more objects) but without using all the memory. Maybe something to do with virtual memory.

Posted: Wed Feb 07, 2007 6:25 pm
by Leonardo
I don't see any triangles.... only marbles :? :lol:

Posted: Wed Feb 07, 2007 6:59 pm
by Fernando Tella
:lol:

Here they are, well, in fact we can't see the triangles but the polygons.

Image

Image

Posted: Tue Mar 20, 2007 4:29 pm
by ivox3
Hey Fernando ....

Just a few questions ....

Which OS? .....and was that 3.5GB's all physical ram?

I can't seem to get mxcl to use over 2gb's with x64 ? ....always stops at 2GB physical and then begins using virtual/paging memory ..... ?

Posted: Tue Mar 20, 2007 6:19 pm
by Fernando Tella
Are you playing with your new monster limits?

I'm using XP64 too. The windows task manager showed ~3.5GB though I increased virtual memory up to 8184MB (it is 2048MB by default).

I'll try to repeat the test increasing the polys a bit, let's see what happens.

Posted: Tue Mar 20, 2007 6:23 pm
by ivox3
I am. :)

I'm finding that Studio is horribly slow(latent) with x64 .....?

Are you noticing anything similar?

It takes me about 3-5minutes in-between mouse-clicks.... :(

thx for the info ....

Posted: Tue Mar 20, 2007 7:59 pm
by Fernando Tella
I have to make a correction. Memory usage probably was around 3.2GB cause I have made a new test (and succesful :D ) with 15600012 polys and it went up to 3.3GB.
I've tryed with 16080012 polys and it crashes, but just a while after starting voxelization and with much lower memory usage.

I'll provide some screenshots in a while.

Slow Studio? Without heavy geometry loaded? Nop. Works fine here.

Posted: Tue Mar 20, 2007 9:59 pm
by ivox3
hmmmmm ... interesting. Keep us posted ..... I know you will. ;)

Posted: Tue Mar 20, 2007 11:28 pm
by Fernando Tella
New record!! :D

The scene is basically the same but with one half floor added:

50 x 50 x 6.5 = 16250 marbles x 960 triangles per marble = 15600000 triangles + 12 box triangles = 15600012 triangles

Peak memory consumption:

http://www.ftella.com/links/16millpolysmemory.jpg

Mxcl with scene data tab:

http://www.ftella.com/links/16millpolysrender.jpg

Wires:

http://www.ftella.com/links/16millpolyswires.jpg

I tryed with 5 more rows on top floor and it crashed. It seems that mxcl looks for the needed free memory space when voxelitation starts; if there's not enough --> crash.

The render was launched from mxcl loading the exported mxs file.

Cheers!

Posted: Wed Mar 21, 2007 12:36 am
by ivox3
Well done Fernando ....!

A little under 3 hours, 15mil tri's, ...dielectric material ....pretty good I'd say.



Now I'm 8 million or so triangles behind ..... :lol: