Does the Python update break old scripts? Specifically do the ShaderWorks scripts still function? Might be a deal breaker on an upgrade from 11 Pro.

No, unless they were included with previous Poser versions when you bought them, no 3rd party Python scripts work now. Includes Lubrary Manager which was essential for my workflow, for example.

I wish that a lot of the old scripts I used up to Poser 11.3 still worked. I'm guessing (and this is a guess from someone who knows next to nothing about scripting) that all my lovely scripts need to be rewritten/recompiled in Python 3.7.9 to work. ?‍♀️

yes, scripts need re-writing.

Thanks for the replies. Yeah, Library Manager was the main one I was thinking about but there are lots of scripts I use a LOT. There is little to no chance of the ShaderWorks ones being updated as I believe the vendor left the Poser space when RDNA changed hands. More than happy if someone can correct that assumption but right now I have a new features/old functionality decision to make. BTW, really happy that Poser is getting the attention it deserves and I understand things move on, and rightly so.

Yup, that is the headspace am in right now. Happy to support but until at least the EZ scripts are updated I may as well just stick to Poser 11.3.

As the devs already explained, they made the break from Python v.2.xx and are now working in Python v.3.xx. Which breaks pretty much all older Py scripts. Even the little ones.

Bondware needs to fix this. I'm not going to modify a thousand scripts just to satisfy a version change. Netherworks can't modify his scripts because he moved on to other work. PhilC moved on to other work. D3D moved on to a better world where people aren't forcibly imprisoned and forced to wear muzzles and forced to keep up with microsecond-scale Github switches in every aspect of life.

I'm tired of this.

@ Haruchai - check the Scripts Menu dropdown for new versions of ShaderWorks scripts. I saw that folder being installed earlier.

We are currently working on quite a few scripts to update to python 3. We are working with the developers of previous scripts to get them working in Poser 12. As was stated previously, implementing python 3 in Poser did break compatibility with a lot of the existing scripts, but please rest assured we are taking steps to get as many of those working in Poser 12 as possible.

McGrandpa posted at 3:37PM Tue, 03 November 2020 - #4403047

@ Haruchai - check the Scripts Menu dropdown for new versions of ShaderWorks scripts. I saw that folder being installed earlier.

Sorry, not sure where you mean to check. If you mean in 12 I haven't upgraded yet. If you're saying there are new versions already in 12 then that is great. Could you clarify, I'd appreciate it.

The ones that were included from Shaderworks in vanilla Poser are updated. Unfortunately, library manager is not one of those.

Jenn, yes, you guys said that before on forum posts and emails and the effort is greatly appreciated. It is unfortunate that the information was not disseminated better so now there is an inevitable flailing period. Maybe a sticky here on the forum when you got a spare second? ( haha)

Oh right. It is ShaderWorksMetadata Builder, not a major one?

ockham posted at 4:58PM Tue, 03 November 2020 - #4403045

Bondware needs to fix this. I'm not going to modify a thousand scripts just to satisfy a version change. Netherworks can't modify his scripts because he moved on to other work. PhilC moved on to other work. D3D moved on to a better world where people aren't forcibly imprisoned and forced to wear muzzles and forced to keep up with microsecond-scale Github switches in every aspect of life.

I'm tired of this.

"2to3.py" is delivered with each Python 3 installation. It can help upgrading scripts from Python 2 to Python 3:

https://docs.python.org/2/library/2to3.html

"Compiled" scripts can be "decompiled". At least for private use this may be ok.

https://sourceforge.net/projects/easypythondecompiler/

After the decompile process, "2to3.py" can probably make the script working in Poser 12.

As I said I understand that things move on and this will leave old things behind. I'll do what I did a few versions ago, upgrade and run both side by side sharing a Runtime, unless that's not feasible for some reason, until the Python updates start to come through making 11 redundant. Thanks for all info, appreciated.

You know, it is great that those tools are around. But I am not a programmer and I suspect the majority of pure Poser user aren't either. What you guys talked about above regarding script compiling etc. means exactly nothing to me. I don't even know where to start. Why is it assumed if ppl use Poser they know this stuff???

I can't go back to P11. It vanished when I put in the serial number for P12 . . . :(

What!! I still have my P11 on 2 machines after my upgrade to P12. P12 should install into its own folder without disturbing or overwriting P11. You can redownload P11.3.818 from Posersoftware.com as long as you have your license number.

I agree with you Rhia474, not everyone has the skills to work wonders with Python scripting. However, if someone could do a quick, concise tutorial on how it can be done, some of us may benefit from trying to update the scripts ourselves.

D3D's "XL Extended Library" is at the heart of my Poser workflow...So exactly how are you going to update a dead man's scripts?

jennblake posted at 10:49AM Tue, 03 November 2020 - #4403050

We are currently working on quite a few scripts to update to python 3. We are working with the developers of previous scripts to get them working in Poser 12. As was stated previously, implementing python 3 in Poser did break compatibility with a lot of the existing scripts, but please rest assured we are taking steps to get as many of those working in Poser 12 as possible.

smallspace posted at 8:35PM Tue, 03 November 2020 - #4403096

D3D's "XL Extended Library" is at the heart of my Poser workflow...So exactly how are you going to update a dead man's scripts?

I have updated that script for Poser 12. I need it to be tested, though - would you be willing to do that?

Well let's see. UDEMY has a great PYTHON course by Derek Banas. (He has [and there are by others, like freeCodeCamp.org] loads of free vids on Youtube also) HUMBLE BUNDLE had a great sale on Python books.

It has been a long time for me to try and get ShaderSpider working and I really have some incentive and tools to give it a go! Expand your minds...and change lanes once in a while. You may enjoy the view.

Thanks. That's kind of you and yes, I'm willing to test it. However, it will be a couple of days before I can get Poser 12. I'll contact you when I have it installed.

Snarlygribbly posted at 10:00PM Wed, 04 November 2020 - #4403108

smallspace posted at 8:35PM Tue, 03 November 2020 - #4403096

D3D's "XL Extended Library" is at the heart of my Poser workflow...So exactly how are you going to update a dead man's scripts?

I have updated that script for Poser 12. I need it to be tested, though - would you be willing to do that?

Actually some Python scripts work without modification. Anything compiled will require a new compilation but the uncompiled scripts might work.

The V4 randomize scripts all work without any (new) problems. I did modify them in Poser 11 to get them to work to my liking and could use them in Poser 12 without any problems. So simple scripts might just work.

https://www.renderosity.com/mod/forumpro/?thread_id=2954238

I posted a possible fix here. The python dir is missing dirs from the python 3 library. Plus Tkinter is now tkinter. I got most of my old scripts working.

Not sure what that does, but merely doing what you describe in that thread does not fix 3rd party scripts. The bad magic number error still pops up (tested with Snarly's EZscripts). For a complete scripting idiot a bit more detail would be welcome. I'm willing to do things myself if I get the exact steps explained.

Snarly's scripts are compiled with a .pyc format. Those will give you that error. I have seen .py format files return a spacing or tabbing error that should be easily correctable.

Yes, so what is described as a fix is nor a fix, only for very specified instances.

That is what I gather. I have P12 installed on another computer that has a fresh copy of Python. I need to copy over some .py scripts and see if they run correctly after applying the fix.

That may help to narrow it down. If only we had 40 hour days...

The big differences I have seen are:

1. TKinter is now tkinter.
2. Either use all spaces or all tabs, no mixing, easily fixed.
3. string.atoi and string.atof no longer exist and now its int(string) or float(string)

Mason41 posted at 11:33AM Sun, 08 November 2020 - #4403664

The big differences I have seen are:

1. TKinter is now tkinter.
2. Either use all spaces or all tabs, no mixing, easily fixed.
3. string.atoi and string.atof no longer exist and now its int(string) or float(string)

TKinter is now tkinter. and TkDialogFile is now dialogfile (and some more to change probably), and no tcl lib is installed so it won't work. (just experienced that)

adp001 posted at 2:15PM Sun, 08 November 2020 - #4403060

"2to3.py" is delivered with each Python 3 installation. It can help upgrading scripts from Python 2 to Python 3:

https://docs.python.org/2/library/2to3.html

@adp001 : Thank you for the pointers. I found the 'easypythondecompiler' and it works like a charm. Could you please also give an exact example how to use 2to3 to convert a Poser script?

2to3 is only the beginning for any complex script with a user interface. 2to3 corrects the syntax, but nothing else. Any changes to the Python API require manual changes to the script to be done after 2to3 has done its work. wxPython has had many changes, and it is a substantial endeavour to update any UI to reflect the wxPython API changes. Also, some changes that 2to3 make are not enough in themselves. For example, it will correct the syntax for using Python dictionaries, but not rewrite the code to reflect that dictionaries can no longer use mutable objects as keys. Also note that in some cases, library functions have moved to different libraries in wxpython 4, requiring changes to your import statements.

In short, there is no quick fix for many scripts - 2to3 is just the start of a long journey.

As for my own scripts, the new Poser 12 versions are currently being tested (including EZDome and EZSkin) it's going well (in the sense that they are converted and running), but there are some issues with the output that means a few changes will need to be made to the code. Hopefully you'll have them before long…

Snarlygribbly posted at 3:11PM Sun, 08 November 2020 - #4403834

As for my own scripts, the new Poser 12 versions are currently being tested (including EZDome and EZSkin) it's going well (in the sense that they are converted and running), but there are some issues with the output that means a few changes will need to be made to the code. Hopefully you'll have them before long…

Awesome!

Snarly, this is great news and thank you ever so much for your hard work!

A journey starts with the first step. There are many simple scripts that do not have a complex GUI or mutable dictionary keys and for those simple code replacement may be all that is needed.

Curious if anyone has tried Reality 4 w/ P12? I still use Reality exclusively in P11 thanks to Snarly's script, and not interested in moving on just yet.

Snarlygribbly posted at 6:10AM Wed, 25 November 2020 - #4403834

As for my own scripts, the new Poser 12 versions are currently being tested (including EZDome and EZSkin) it's going well (in the sense that they are converted and running), but there are some issues with the output that means a few changes will need to be made to the code. Hopefully you'll have them before long…

Thank you so much for this, I simply couldn't see myself using Poser without EZSkin, so this is very welcome news.

pcw5150 posted at 8:36AM Wed, 25 November 2020 - #4404221

Curious if anyone has tried Reality 4 w/ P12? I still use Reality exclusively in P11 thanks to Snarly's script, and not interested in moving on just yet.

Reality will not work in Poser 12 unless somebody recompiles the program from the (open source) source code. My fix won't be enough in Poser 12.

Snarlygribbly posted at 2:12AM Sat, 20 February 2021 - #4405727

pcw5150 posted at 8:36AM Wed, 25 November 2020 - #4404221

Curious if anyone has tried Reality 4 w/ P12? I still use Reality exclusively in P11 thanks to Snarly's script, and not interested in moving on just yet.

Reality will not work in Poser 12 unless somebody recompiles the program from the (open source) source code. My fix won't be enough in Poser 12.

Nothing from there workking under poser 12 still. So, nothing new. No library manager not usefull scripts... Bravo... :(

Um, can we be a bit patient? There was an article a few days ago indicating work is being done, but most of this is 3rd party stuff that first needs to be actually acquired to be able to work on, and most of the code needs to be rewritten from scratch. It's nontrivial, from what I understand with my limited experience. Some of the scripts belong to people who no longer even in the Poser community, or passed. According to the article, the first scripts should be out in March. I'd call that pretty good progress, considering P12 has come out in November.

https://www.posersoftware.com/section/14/news

We might not have to wait until March for everything. LockMaster Pro just appeared in the marketplace in a P12 version. https://www.renderosity.com/rr/mod/bcs/lockmaster-for-poser-12/148152/

Looks useful, although like a lot of scripts, it seems to suggest ways Poser's UI should be improved....

Rhia474 posted at 1:28PM Sat, 20 February 2021 - #4413419

Um, can we be a bit patient? There was an article a few days ago indicating work is being done, but most of this is 3rd party stuff that first needs to be actually acquired to be able to work on, and most of the code needs to be rewritten from scratch. It's nontrivial, from what I understand with my limited experience. Some of the scripts belong to people who no longer even in the Poser community, or passed. According to the article, the first scripts should be out in March. I'd call that pretty good progress, considering P12 has come out in November.

https://www.posersoftware.com/section/14/news

Well. Yes, i try to be patient. Anyway i have not other way. But it is pity that poser use python which is incompatibile with older version, so it hapen always the same with every new version of poser software. And really i can't understand why we have not any chance to chose python version in software which we bought. So, we lose money and scripts which did what poser can't by itself.

ChromeStar posted at 1:37PM Sat, 20 February 2021 - #4413435

We might not have to wait until March for everything. LockMaster Pro just appeared in the marketplace in a P12 version. https://www.renderosity.com/rr/mod/bcs/lockmaster-for-poser-12/148152/

Looks useful, although like a lot of scripts, it seems to suggest ways Poser's UI should be improved....

Thanks for info, but for me this one not look too useful. I rather thought about ezskin, some library manager etc.

This story about scripts is a very serious matter for me. I use many scripts, some of which are crucial for my work, and I did not steal them - I ether download them if offered for free or purchased them directly, or as a part of certain content packages. It is a lot of time and money invested and the perspective that they should all go to garbage bin and that I should collect or buy them again is a rather bitter pill.

One that I won't swallow - be sure of it.

I remained loyal to Poser all this years since DAZ retracted it's models from Poser users. It was wrong from my perspective: morally, since someone wanted to curb the way my creativity works, but also economically. As a consequence, for almost 10 years my DAZ account is frozen, presumably until the day comes when their models will again be usable in Poser (that probably means for ever). This business with no backward compatibility for Python scripts smells the same. I feel betrayed and there won't be Poser 12 or later on my comp until this is resolved. Finally, if the fundamental disregard from both companies to their customers becomes equal, I may not need to persist on the distinction that I mentioned above.

Poser team, whether you see this as an angry letter, or a proposition, or a plea - whatever... please establish the backward compatibility to earlier Python scripts in Poser 12.

Sorry time progresses and backward compatibility isn't possible. Python has moved on and the Python developers have opted for new feature over compatiblity. The Poser developers had no option but to accept the only version currently supported. We have to live with choices made by others.

The problem isn't as big as it seems. Anything available in uncompiled format can be used (with some small modifications in a few cases). Most compiled scripts are now available in a new version and most are a free upgrade. Unsupported scripts probably require some rethinking as most things can be done in a better nowadays.

I'm happy to share the uncompiled source code of any of my scripts to anyone who wants it.
Most of it is already available, I think.