WILL_I_AM posted at 1:18 PM Sun, 2 April 2023 - #4460521

adp001 posted at 2:40 PM Thu, 30 March 2023 - #4460055

Had to quote myself:

adp001 posted at 2:11 PM Thu, 30 March 2023 - #4460034

Regarding EZSkin (for all who don't want to change the script on their own):

Download the following script (one-liner) and run it with Poser. It will change the information delivered from AppVersion() into something useable. It works for the current session only. After closing Poser you have to run the script again.

https://adp.spdns.org/FixEZSkin.py

You may download and save the script into the folder with the other scripts Poser delivers (..\Runtime\Python\poserScripts\ScriptsMenu).
Then you can select this script from Poser Scripts menu.

or

Run the script directly from Posers menu: File -> Run Python Script...

So we are still in the situation that we require a third party fix to make a second party fix to the short comings of Poser actually work.

Not sure there is an easy answer to that for example I use Dawn SE and Poser includes new skin textures for Dawn SE based on cycles so there would be no need to use EZskin in my case, assuming I wanted to go down that route.

 

 

I use Poser 13 on Windows 11 - For Scene set up I use a Geekcom A5 -  Ryzen 9 5900HX, with 64 gig ram and 3 TB  storage, mini PC with final rendering done on normal sized desktop using an AMD Ryzen Threadipper 1950X CPU, Corsair Hydro H100i CPU cooler, 3XS EVGA GTX 1080i SC with 11g Ram, 4 X 16gig Corsair DDR4 Ram and a Corsair RM 100 PSU .   The desktop is in a remote location with rendering done via Queue Manager which gives me a clearer desktop and quieter computer room.