- Thu Oct 26, 2006 7:19 pm
#191383
(This smells like a thread hijack, sorry about that, but we're in the SW forum so I guess it's not that far OT)
Well polytrans has a mode where it can update changed parts, but when you actiate that you get a very large number of objects in Max (Almost one object per SW feature). If you "Optimize Hierarchy" you basically get one object per SW body, which is nice. I use this mode plus Polytrans option to read the SW tesselation instead of reading the surfaces and then tesselating them. SW's internal tesselation is actually very good, especially when you turn on "high quality" in Document Properties > Image Quality.
So with "Optimize Hierarchy" I can't use the automatic update feature. But since import using SW tesselation is VERY fast (maybe 10x to 20x faster compared to SW Maxwell plugin export), and the Max model has hierarchy preserved, I can easily delete the changed Part/Assembly in Max, and reimport the new version of the changed part only into the Max model. No need to reimport all the other parts of the assembly.
Of course the modified subassembly or part has to be retextured, but the rest of the model stays.
I have spent A LOT of time trying different approaches, and this is the only one where I have a decent modification workflow without crasher showstops.
Except now I am close to the max amount of polys that the Max plugin can handle too, but that's a different story
Well polytrans has a mode where it can update changed parts, but when you actiate that you get a very large number of objects in Max (Almost one object per SW feature). If you "Optimize Hierarchy" you basically get one object per SW body, which is nice. I use this mode plus Polytrans option to read the SW tesselation instead of reading the surfaces and then tesselating them. SW's internal tesselation is actually very good, especially when you turn on "high quality" in Document Properties > Image Quality.
So with "Optimize Hierarchy" I can't use the automatic update feature. But since import using SW tesselation is VERY fast (maybe 10x to 20x faster compared to SW Maxwell plugin export), and the Max model has hierarchy preserved, I can easily delete the changed Part/Assembly in Max, and reimport the new version of the changed part only into the Max model. No need to reimport all the other parts of the assembly.
Of course the modified subassembly or part has to be retextured, but the rest of the model stays.
I have spent A LOT of time trying different approaches, and this is the only one where I have a decent modification workflow without crasher showstops.
Except now I am close to the max amount of polys that the Max plugin can handle too, but that's a different story
- By Mark Bell
- By Matteo Villa