Darktoz opened this issue on Dec 19, 2020 ยท 21 posts
Y-Phil posted Mon, 21 December 2020 at 4:04 PM
ChromeStar posted at 4:00PM Mon, 21 December 2020 - #4408149
Darktoz posted at 2:16PM Mon, 21 December 2020 - #4408084
Nothing that even briefly involves a script does work anymore. Like specific morphs...meaning half of my library. It is too frustrating, so I give up and go back to Poser 11.
But thanks for trying to help me out.
Some scripts still work. V4 injection morphs still work. There is definitely a lot broken and needing update, but it depends how things were written. It would be nice if Poser would at least automatically catch and fix the easy obvious issues (e.g. inconsistent use of tab vs space for indenting should be possible to autocorrect, or changes in how things need to be capitalized), and the magic number error which is about the Python version number (I don't see any reason the user shouldn't be allowed to override that and at least give it a try). I don't know enough Python (I don't know Python at all in fact!) to know how many of the changes could be addressed that way vs things that require serious attention.
In fact, that magic number also kind of protects against habits in Python2.x that must be changed in Python3. Furthermore, there's some APIs that changed from Poser11 to Poser12.
Just in case, API stands for Application Program Interface, these are Poser functions at your disposal, for example to create a dialog, to fill lists, turn on/off lights in Poser's rooms, etc... They are made available through the use of a specific library, provided by Poser. The same kind that allowed us to use the JSON importer in previous versions of Poser, for example.
๐ซ๐ฝ๐๐
(ใฃโโกโ)ใฃ
๐ฟ Win11 on i9-13900K@5GHz, 64GB, RoG Strix B760F Gamng, Asus Tuf Gaming RTX 4070 OC Edition, 1 TB SSD, 6+4+8TB HD
๐ฟ Mac Mini M2, Sonoma 14.6.1, 16GB, 500GB SSD
๐ฟ Nas 10TB
๐ฟ Poser 13 and soon 14 โค๏ธ