Even if it found it, it would decide that the Poser version was too old anyway. When a D3D script looks for the fourth element, it crashes. only three elements, and a much lower build number. Many scripts look for the build number to check for the availability of certain features. It used to be something like 11.0, i.e four elements with the build number being the fourth one. Poser Pro 2014 Game Dev has been merged with Poser Pro 2011 and that is why you didn't have to pay extra for Game Dev licenses & functionality like Kinect. Then I installed all the SMDM Poser 2011.1 Content after downloading it. No - the core problem is that Bondware have changed the version number format of Poser, and reset the build numbering to 1. I then manually re-named the Poser Content directory to be what Poser Pro 2011.1 expects by default. The core problem is that D3D's scripts aren't written to work with any new version of Poser itself. 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.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |