Tweet
Hi,
as big amounts of proxies fill up our scenes i noticed some strange behaviour inside MAX;
(using a box as an example, could also be a proxie in point/box mode. amounts are probably relative to pc-power)
1a) create 100.000 boxes. save the file. will take some time, maybe a minute or so.
1b) restart max, open the file. also takes about a minute. watch dr watson, you see memory usage build op, and afterwards max is ready to work on. so far so good.
2) now restart max, and insert the file as an XREF. watch dr watson. memory builds up same way as opening the file. but, after this max hang's for about 10 minutes at 25% cpu usage.
this is strange, why does it take max MUCH longer to load a file as an xref then it takes to just load the file?! also exitting max is suddenly very very slow.
3) draw 10.000 boxes save the file. create new max file, and xref the file 10 times. no issues. save the file containing only these 10 xrefs and re-open it. goes the way it should, no slowdown. open a new file and xref the compilation file with the 10 xrefs inside. no slowdown either...
i was wondering if someone else can confirm this behaviour? amount of objects will probably vary. it seems max has an issue loading xrefs that shows up when more then a certain big amount of objects are drawn. Not the amount of faces, amount of objects. drawing 100.000 points has the same effect.
the question for us is very relevant as spraying/filling around scenes with proxies (greenery) looks very good, but loading the xrefs really slows down our workflow! Scripting a 'split scene to #n smaller files and recollect in compilation xref' will probably work, but has no beauty price. Other solution is a script to add the xrefs while disabled thus not loading, and have another prerender callback enable them inside the queue.
so, anybody else experiencing this xref related slowdown in loading scenes?
best regards,
(3dsmax2010sp1hf7@xp64pro@8Gb@quadro fx1700)
as big amounts of proxies fill up our scenes i noticed some strange behaviour inside MAX;
(using a box as an example, could also be a proxie in point/box mode. amounts are probably relative to pc-power)
1a) create 100.000 boxes. save the file. will take some time, maybe a minute or so.
1b) restart max, open the file. also takes about a minute. watch dr watson, you see memory usage build op, and afterwards max is ready to work on. so far so good.
2) now restart max, and insert the file as an XREF. watch dr watson. memory builds up same way as opening the file. but, after this max hang's for about 10 minutes at 25% cpu usage.
this is strange, why does it take max MUCH longer to load a file as an xref then it takes to just load the file?! also exitting max is suddenly very very slow.
3) draw 10.000 boxes save the file. create new max file, and xref the file 10 times. no issues. save the file containing only these 10 xrefs and re-open it. goes the way it should, no slowdown. open a new file and xref the compilation file with the 10 xrefs inside. no slowdown either...
i was wondering if someone else can confirm this behaviour? amount of objects will probably vary. it seems max has an issue loading xrefs that shows up when more then a certain big amount of objects are drawn. Not the amount of faces, amount of objects. drawing 100.000 points has the same effect.
the question for us is very relevant as spraying/filling around scenes with proxies (greenery) looks very good, but loading the xrefs really slows down our workflow! Scripting a 'split scene to #n smaller files and recollect in compilation xref' will probably work, but has no beauty price. Other solution is a script to add the xrefs while disabled thus not loading, and have another prerender callback enable them inside the queue.
so, anybody else experiencing this xref related slowdown in loading scenes?
best regards,
(3dsmax2010sp1hf7@xp64pro@8Gb@quadro fx1700)
Comment