Slow exporting-memory Problem!!!suv?

Kosmokrator · Post by **Kosmokrator** » Sun Jul 22, 2007 4:27 am

hi suv i tes your new exporter and indigo 0.9 with some complex scene...i model some mechanic bug and when i export takes ages at building kd tree....the problem found on bug legs....i dont know why ....

Code: Select all

Building Mesh '3D_Object14'...
	181734 vertices (4.160MB)
	60578 triangles (709.898KB)
	Couldn't find matching cached tree file, rebuilding tree...
	TriTree::build()
	calcing root AABB.
	AABB: (-5.343173, -11.867516, -5.835740), (-2.318515, -0.879027, 2.262084)
	max tree depth: 33
	reserving N nodes: 60578(473.266KB)
	leafgeom reserved: 242312(946.531KB)
	0/64 nodes at depth 6 built.
	1/64 nodes at depth 6 built.
	2/64 nodes at depth 6 built.
	3/64 nodes at depth 6 built.
	4/64 nodes at depth 6 built.
	5/64 nodes at depth 6 built.
	6/64 nodes at depth 6 built.
	7/64 nodes at depth 6 built.
	8/64 nodes at depth 6 built.
	9/64 nodes at depth 6 built.
	10/64 nodes at depth 6 built.
	11/64 nodes at depth 6 built.
	12/64 nodes at depth 6 built.
	13/64 nodes at depth 6 built.
	14/64 nodes at depth 6 built.
	15/64 nodes at depth 6 built.
	16/64 nodes at depth 6 built.
	17/64 nodes at depth 6 built.
	18/64 nodes at depth 6 built.
	19/64 nodes at depth 6 built.
	20/64 nodes at depth 6 built.
	21/64 nodes at depth 6 built.

please i send u the leg part to exam what realy happents!
its not heavy polygon...i have much more heavy objects in my scene and export fast.....take a look please!thnx a lot!!

Kosmokrator · Post by **Kosmokrator** » Mon Jul 23, 2007 12:01 am

suv....r u check your e-mail for the scene?
u have some idea??

suvakas · Post by **suvakas** » Mon Jul 23, 2007 12:10 am

Hmm..this is not a Maxigo issue here...
It's Indigo that is slow on building mesh tree from exported *.3ds model.. I used Meshlab to check if the *.3ds model file is Ok and I found no problems. It opened instantly.
So it is a question to Ono. Maxigo works fine

Using BIH tree instead of KD tree speeds things up though. Since your model is only like 60k polys or so, then you can use 50k for BIH tree value under Maxigo's "Advanced Setup" rollout (just remove one digit from default value)

[edit] The BIH tree value tells Indigo when to use BIH instead of KD. Value 50000 tells indigo to use BIH tree for models that have 50k polys or more.

Post by **OnoSendai** » Mon Jul 23, 2007 12:11 am

Yup, see if it helps to set the bih tri threshold to 50K like suv said.

suvakas · Post by **suvakas** » Mon Jul 23, 2007 12:35 am

Works fine with BIH tree.

Kosmokrator · Post by **Kosmokrator** » Mon Jul 23, 2007 12:36 am

ohhh....thnx man!!!now exports in a second!!!!thnx both of u ppl!!!
keep it up!!!!

Post by **OnoSendai** » Mon Jul 23, 2007 12:38 am

this is gonna be a cool render

Kram1032 · Post by **Kram1032** » Mon Jul 23, 2007 12:55 am

nice model!

Kosmokrator · Post by **Kosmokrator** » Mon Jul 23, 2007 3:21 am

i wonder...about instances.......how i can use instances of one model?
is this economy at memory ram?
i ask becaouse i have a heavy scene (over 2 gb in my ram) and the hard disk start the cashing.....i have set the supersample factor to 2 but nothing
happents to memory amount....
any ideas?

Kram1032 · Post by **Kram1032** » Mon Jul 23, 2007 3:35 am

every object has a mesh.
If you use the same mesh, two times, but with different sizes and rotations, you can do it in two ways:

1) change object data
2) change mesh data

changing the object's data is more economic, as you can use the same mesh, instead of having to reload it.

That's the trick.

I dunno, how to make an instanced mesh in Max, though...

suvakas · Post by **suvakas** » Mon Jul 23, 2007 3:42 am

When doublicating a model in max pick "Instance" instead of "copy".
Maxigo should then export only one copy of the mesh and not the others - well..at least in theory

It may not work when using "Fix mesh errors" though.
You have to test it. I wrote the instancing part a long time ago and i didn't know maxscript so good back then...

Kosmokrator · Post by **Kosmokrator** » Tue Jul 24, 2007 6:05 am

suv i found instances very usefull...it works very well (55% more eficiency in ram)....but as u mention....instances dont work with fix mesh errors....and unfortunaly my scene generate errors without fixmesh....

is possible to rewrite some code for instancing?
my scene is too heavy.....

thnx for your time...
keep it up!

suvakas · Post by **suvakas** » Tue Jul 24, 2007 12:09 pm

Kosmokrator wrote: is possible to rewrite some code for instancing?

It should be possible.
I'm planning to rewrite quite a large part of geometry export. It should increase the overall compatibility. I also want to lose the "Fix mesh errors" thing and make it automatic.

Kosmokrator · Post by **Kosmokrator** » Tue Jul 24, 2007 8:46 pm

great news....take your time man!
thnx for your answer!

Slow exporting-memory Problem!!!suv?

Slow exporting-memory Problem!!!suv?

Who is online