Cage opened this issue on Dec 20, 2006 · 1232 posts
Cage posted Thu, 28 December 2006 at 2:34 PM
Hi-res to low-res is working pretty well, at least when the geometries line up tolerably well. (JoePublic has found some limitations to this technique when meshes don't align well.) But the model currently in use involves checking each vertex in the target and looking for the nearest vert in the source, so it's built on completely different foundations than what you and svdl and Ockham suggest, using vert to polygon comparisons.
In thinking about this, the method of weighting the target vertices does seem like the tricky part. I assume it would somehow be a function of distance from each vert divided by length or width of the poly, or distance along one of the planar axes of the poly. But Poser, unlike Blender, only gives us bare-bones data about polygons, and no data at all about edges. The polygon distances would have to be constructed from the set for the poly. I can imagine that requiring the use of trigonometry.... ick... and then I start to get panicky. It seems like the idea has a lot of promise, but I despair for my ability to implement it. Cage != math guy. Hoo boy. Right now I'm still struggling to implement the ideas svdl outlined for 'raycasting', back on the previous page....
I'm thinking about ways this could work, though. I can tell it's a strain because of the smoke coming out of my ears....
I'm beginning to wonder if all of this should use kaweki's suggestion for parsing the object data out of a .obj file, instead of using the Poser internal methods. Would it be faster? One pass through the .obj file could be used to organize all the data needed for polygons and verts, and the line information is in the .obj for edges.... Hmm.
Thank you for all your thought about this. I hope I can live up to all of the ideas everyone is contributing. :scared:
===========================sigline======================================================
Cage can be an opinionated jerk who posts without thinking. He apologizes for this. He's honestly not trying to be a turkeyhead.
Cage had some freebies, compatible with Poser 11 and below. His Python scripts were saved at archive.org, along with the rest of the Morphography site, where they were hosted.