Snarlygribbly opened this issue on Aug 23, 2012 · 195 posts
bagoas posted Sat, 25 August 2012 at 4:13 AM
Quote - In my thread somebody said this
All the morphs are made from the base mesh. The exporter would have to be able export out not only the sub-d mesh but all the morph deltas sub-d without changing vertex order.
That would be one solution, but it would require further action from DAZ which will not bring them much return; It would mean unleashing their Genesis figure in Poser and there would be no need for Poser users to ever start their DS front-end again.
Note that with every subdividision step in the mesh, the number of vertex deltas and weights for Weight-mapped joints rises exponentially, and if you copy this rise again in the deltas and weights you end up with a memory hog. The rough low-res mesh+subdivision approach was necessary to keep memory requirements within limits. The consumer type user is DS (and Poser) bread and butter.
The cunning route Snarly has now so kindly opened for us of course permits to work like DS does: subdivide only just before you render. If the script is appended with commands to kick start the renderer and upon completion delete the subdivided mesh and turn the figure visible again, you would have the transparant one-click solution.
There is one issue of course, and that is connection. As said, there is not only the number of vertices, but subdivision causes drift in the geometry description. The original vertices are moved. So, if you subd one object, say the head, the geometry will no longer fit at the neck. So, you have to choose one single single mesh to maintain the connections.