caisson posted at 7:46PM Thu, 21 November 2019 - #4370814

The point with OSD is that the speed, mesh compatibility and accuracy improved a lot from version 2 to version 3. Poser was updated to the new v3, and had the boundary rule change, because it gives better results with meshes that have not been designed for subD, including all the legacy content. The problem with morphing at higher resolutions seems to be an unintended side effect. The topology that OSD generates is the same as long as the base topology is fixed, so I would guess that there must be a point when morphing a mesh using GoZ where it decides that the topology has changed, and it would seem that OSD v3 is more sensitive than v2. I am guessing though, I will check on the GIT report in a few days and see if it has gone to the dev team.

Right now I would say that workflow is the most important thing as I don't believe that this is something that only affects some installations - I'm hoping Ghostman might chip in with advice/info.

I will try to spend some time to spend on this over the next few days.

Thank you and please keep us in the loop here on the post about any developments. Also please read Ironsoul's point posted today. Ironsoul makes a good and relevant point I think.