RobZhena posted at 2:04PM Fri, 20 September 2019 - #4362888

smallspace posted at 8:59AM Fri, 20 September 2019 - #4362758

In view of python incompatibilities, maybe Bondware should just undo the changes they made to Poser python and roll it back to the code they got from SmithMicro.

The core problem is that D3D's scripts aren't written to work with any new version of Poser itself.

No - the core problem is that Bondware have changed the version number format of Poser, and reset the build numbering to 1. It used to be something like 11.1.0.35540, i.e four elements with the build number being the fourth one. Many scripts look for the build number to check for the availability of certain features. The new version is reported as 11.2 .272, i.e. only three elements, and a much lower build number. When a D3D script looks for the fourth element, it crashes. Even if it found it, it would decide that the Poser version was too old anyway. The fact that the reported version also has a space in the middle of it doesn't help either :)

Free stuff @ https://poser.cobrablade.net/