ssgbryan posted at 10:48AM Thu, 22 October 2015 - #4234708

Your argument that SM should take over the development of 64-bit Python from the developers of Python, just so they could rewrite Daz's code. And it WOULD have to be rewritten. Moving from 32-bit to 64-bit is a hell of a lot more than just pointing at new libraries. Ask Adobe or Microsoft.

You are right on 1 thing - The DSON Importer for Poser is certainly not ideal. Fortunately, we can bypass it. File - Export. Spend 10 - 15 minutes converting those .duf PCF to native Poser .mc6s, .pz2s, .cr2s, etc. If I can figure out how to do it in less than 30 minutes with no documentation from Daz (as usual), so could a vendor.

LOL. Really? I never said Poser needs to rewrite Python. The API could have access other than Python. Even with the current python, there are definite places the current API could be significantly more efficient.

And your export to Cr2 does not produce the same functionality, which is why that method was dropped. But you knew that already.