I don't usually respond to necro-posting (or anything lately) but I want to point out:

Python 2 was started in 2000, Python 3 in 2006

Python 2 was announced as end of life in 2008, with a termination in 2015 - 7 years notice - plenty of time to get ready

But lots of people refused/ignored the notification (including Poser team) so Python 2 was extended to January 1, 2020. It has been completely dead now for over 2 years.

It is irresponsible for Poser to include Python 2. It is unsupported and has security vulnerabilities WHICH WILL NOT BE FIXED, EVER.

Stop asking for it to come back - it will never happen. 

Thank you very ,much, sir--I was thinking about typing what you did yesterday but you were a lot more succinct.

As to old scripts: as those are the property of the people who wrote them who in a lot of cases no longer in business/ working with Poser--it is not Rendo's responsibility to upgrade them, however much we'd like to. They are not theirs. Believe me. I got a ton of old scripts that no longer worked after Python 2 came out and then another slew that no longer works after Python 3 was finally implemented in Poser 3. It is what it is, and we can't expect a company to purposefully introduce security vulnerabilities into their program to please a few users (including me). Some very important scripts were updated, like EZSkin and EZDome (third party) and some new ones have been written.

I harp on this every now and then on these forums because yes, old scripts deprecated and it sucks not to be able to use them. But until old scripts are either updated by those who wrote them or they are allowed to be updated by people who know how to (officially, I mean, not homebrew), I can only offer what I already said a few times: use a previous version of Poser for those scripts, then open the scene back into Poser 12 and adjust as necessary.

(Lamenting at least two old scripts that added wounds and scars and dirt IMMENSELY, and I wish someone would write one of those. It should be a basic functionality for non-Matroom verse users, and the *other* software has it. Currently the only way to do it is either go back to 11 with the scene and add it there, or try to use 'layers' in Poser 12 which...is not well documented for this at all and is extremely time consuming and sometimes works and sometimes doesn't).

Could it be possible to have a list of those old V2 treasures, to see if something can be done, I mean: from scratch!

I have the source (from when it was made freely available) to three PoseWorks utilities Glowworm, Particles 3 and ShaderSpider.

Sadly, my Python-Fu is weak.

I will get a list together later today, Phil... baking hot cross buns for Easter atm.

SnarlyGribbly has provided the source code of Particles. I've started to check, and a few lines of Python need some adaptations, which is not a problem. But some of the examples provided such as the Clouds will need to be adapted to Cycles, or at least to PhysicalSurface because the actual mats settings are specifically for Firefly.

But it's manageable.

Glowworm and Shaderspider: I don't know them.

Okay:

Wet&Wounded (sold here)--this was a great little script to add blood, wounds etc. but it's very old--looked absolutely killer though. I miss this greatly for wounds and bruises, there is literally no replacement unless I want to do texture map alterations in a graphics program by hand

Advanced Shaders by  SemiDieu (used to be at RDNA)--this unfortunately came with a not user friendly how-to-use manual I literally did not understand 90% of it.

ShaderWorksLibrary Manager v. 2.6 was the last version by  SemiDieu (used to be at RDNA)--this was a great library replacement (other users also miss this a lot)

Advanced Figure Randomizer by  SemiDieu ,used to be at RDNA)

Texture Variation by  SemiDieu (used to be at RDNA)

Hybrid Grunge (including Gore-Dom, Grime-Inizer, Rag-Erator, Rust-Icator)--over at the D-place--this adds grime and blood and rust to materials--used to use this daily while it worked

Silkessence for Poser, over at the D place again--this generated silk matierals for Poser and the script let you specify multiple matzones of the item, the materials were also high quality

Furify for Poser, over at the D place--great 'make fur' script

Jiggles and crying time, along with the Wet and Wounded mentioned above, used to be crucial for me. I also used Snarly's EZ Skin 3 on every render for Superfly, his snow machine, and the "sweaty" script quite a lot. The worst loss for P12 from my perspective was Virtual Dynamics for hair and cloth. I have to import my figures into P11 for "pre-work," and then render them in P12 now. That's an added and frustrating step for me.

Jiggles and crying time, along with the Wet and Wounded mentioned above, used to be crucial for me. I also used Snarly's EZ Skin 3 on every render for Superfly, his snow machine, and the "sweaty" script quite a lot. The worst loss for P12 from my perspective was Virtual Dynamics for hair and cloth. I have to import my figures into P11 for "pre-work," and then render them in P12 now. That's an added and frustrating step for me.

have you thought about saving your skin mats as MC6 files in the mat library? This covers any/all zones on a figure or prop so you only have to convert your skin one time. Keep in mind that roughness is on a different scaling between P11 and P12. A roughness value from P11 should be square-rooted to get a value for P12. Other than that they are the same. I set up a figure's mats 1 time only and then just click the preset after that anytime I want to use that character morph.

The scripts I miss and haven't found p12 equivalents for are scene fixer by snarlygribbly, curl up and dye by philc especially the portion where it copies the hair shader from one hair group to the rest, Shderworks advanced lights and cameras

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.

Since I use custom characters, I essentially keep P11 and P12 versions of each. I only have to re-load P11 for EZ Skin when I'm loading a new figure. I had no idea about the roughness issue, and honestly, I can't tell that P12 is different in that regard.

Snarlygribbly posted at 4:02 AM Fri, 15 April 2022 - #4437210

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.

Dear @Snarlygribbly would you mind to give me the source code of the Scene Fixer? I mean: on cobrablade, the zip  only contains the .pyc.
Thank you in advance.

PM me an email address, and I'll send it.

Hi everybody.

SnarlyGribbly gave me the source code, and I've uploaded here a first version, updated for Poser12, but it is better to be careful and save before.
I have posted a dedicated thread, because I think that I'm going to make it evolve.
One last note: I'm using Windows 10, and I have no access to any Mac, so I can't test on these computers.

That would be great if you can make it work for P12.  Definitely, I will test drive this script.  Thanks.

Looks good so far. thanks. I've missed this script

@hborre @RedPhantom I'm always happy if I can help

Thank you for your time and effort - this was sorely missed!

Kalypso posted at 1:11 PM Fri, 22 April 2022 - #4437550

Thank you for your time and effort - this was sorely missed!

thanks!

ghostship2 posted at 2:30 PM Fri, 22 April 2022 - #4437558

thanks!

I thanked you on the other thread but it's on an obscure forum, so here is the more public one--this is great and I'm super happy it works again. It's indispensable for older clothing textures that often render solid black in Superfly, and it does not require an entire rebuild of shaders manually.

So, ah, what does it do?

It's easier if I snippy the main interface here:

That is pretty clear! Thanks!

Version upgraded:

Downloadable here.

anupaum posted at 1:15 PM Sun, 24 April 2022 - #4437681

Hello Snarly!

Thank you for doing the work to get EZ Skin 3 into Poser 12. It works really well, except, I can't figure out how to get Cycles into the rendering engine options. There's a "wet skin" box in the Cycles engine interface that doesn't exist for Superfly. Is this something you're still working on?

There is a Cycles plugin that exists for EZSkin 3 P11 version that recreates the shader with the CyclesSurface node.  It works beautifully in P11 but flags an error when opened in P12.  It's annoying because recently I've been converting some Firefly shaders that were destroyed with the latest versions of P11 (illegal node connections) to Superfly.  It would be nice to repair that plugin so I wouldn't switch between the P11 and P12.

There is a Cycles plugin that exists for EZSkin 3 P11 version that recreates the shader with the CyclesSurface node.  It works beautifully in P11 but flags an error when opened in P12.  It's annoying because recently I've been converting some Firefly shaders that were destroyed with the latest versions of P11 (illegal node connections) to Superfly.  It would be nice to repair that plugin so I wouldn't switch between the P11 and P12.

anupaum posted at 4:08 PM Sun, 24 April 2022 - #4437692

hborre posted at 2:12 PM Sun, 24 April 2022 - #4437685

There is a Cycles plugin that exists for EZSkin 3 P11 version that recreates the shader with the CyclesSurface node.  It works beautifully in P11 but flags an error when opened in P12.  It's annoying because recently I've been converting some Firefly shaders that were destroyed with the latest versions of P11 (illegal node connections) to Superfly.  It would be nice to repair that plugin so I wouldn't switch between the P11 and P12.

That's exactly the issue.

:)

I have asked Snarlygribbly if he would be so kind to share with me the source code of EZSkin3, so that I can check what's wrong. I suspect that some typical Python object have lost some old functions, to benefit from new ones, so that our beloved EZSkin3 needs an update.

Just remember to drop the files in the ZIP at the right place. In my case:

That worked, as far as getting the Cycles option into EZ Skin 3, but it's giving me THIS error now:

Traceback (most recent call last):
  File "L:\Poser development\Poser 12\EZSkin 3\EZSkin3.py", line 5612, in Apply
  File "E:\Poser Runtime\Render Tools\Cycle-plugins-v1\CycleSkin.py", line 110, in BuildShader
    method(mat, p)
  File "E:\Poser Runtime\Render Tools\Cycle-plugins-v1\CycleSkin.py", line 585, in Cyclemouth
    n013=mat.AddNode('ccl_VoronoiTexture', name='Pores', loc=(1800,20), collapsed=False, preview=False, Scale=1050, Coloring=2,)
  File "L:\Poser development\Poser 12\EZSkin 3\EZSkin3.py", line 3878, in AddNode
  File "L:\Poser development\Poser 12\EZSkin 3\EZSkin3.py", line 4585, in SetInputValue
AttributeError: 'NoneType' object has no attribute 'Type'

I've never seen that before.

These errors are popping because this script was written in Python 2 and is not formatted to run in Python 3.  There might be syntax errors or formatting that need to be converted.

Well... here we are: a pure EZSkin3 render: skin, hair and clothes

I am not used anymore to EZSkin3, and there are some subtilties such as lower the specular parameters, raise the roughness of the hair, but all in all you have EZSkin3 restarting its Poser12/Python3 life.

What is new: Snarlygribbly is kind enough to release his EZSkin3 to the public domain.
I have had to update 3 python scripts: rearrange them, rewrite a few details. And specifically: the CycleSkin was written using a mix of tab and spaces, which is forbidden in Python3. so that, I had to make some decision for what concerns the logic (the blocs of code must be correctly indented)

So: if you see some weird results: the fault does not necessarily lie with your choices or with certain incompatibilities, but may also be due to the choices I have made during the code reformatting, so you should not forget this in such cases

Oh and: you will have to change your menu entry for EZSkin3: the version you're going to download is nt the compiled version but the source code: replace "Ezskin3.pyc" with "Ezskin3.py".
The ZIP that contains the three script that are going to replace the ones on your system is here.

And just a reminder: the "CycleMaterials.py" and "CycleSkin.py" must be place in the directory indicated below.
Example for my PC:

Thank you very much.  Something else ported over to P12.

The updated files worked! Thank you!  Bless you!

:)

I'd like to thank Y-Phil for keeping these scripts alive.
Kudos to the Poser community.

Snarlygribbly posted at 8:35 AM Tue, 26 April 2022 - #4437749

I'd like to thank Y-Phil for keeping these scripts alive.
Kudos to the Poser community.

I must have missed something, but in a nutshell, what are the differences between Snarly's Poser 12 version of EZSkin3.1 and the newly compiled from source version Y-Phil worked on?

As stated in one of the posts above, there are 2 plugin scripts, CycleMaterials and CycleSkins, that worked in the EZSkin 3 P11 version that was broken in P12.  Y-Phil was so kind as to undertake the task of correcting those scripts and making other changes in EZSkin 3 P12.  In a nutshell, EZSkin 3.1 still looks the same but those scripts now work in creating Cycle-based material.  

I must have missed something, but in a nutshell, what are the differences between Snarly's Poser 12 version of EZSkin3.1 and the newly compiled from source version Y-Phil worked on?

There aren't any specific differences. A small piece of code that I should have restored as it was, I simply forgot, but I had to comment a try/except to understand what the problem was, plus a small test in case a parameter was null.

As @hborre said: the main part was to update both plugins t make them Python3 compatible.

Note that Snarlygribbly's "Scene Fixer" has been updated to, and you may not only add an area light but also a grouping object.

And just to make everything clear

Scene Fixer:

EZSkin3:

Ah, that explains it, I was a little confused, as EZSkin already ran in Poser 12 but I knew the Cycles plugins weren't compatible yet.

This is really good news and sad news all at once, it's great we have Scene Fixer working in P12 now, and that EZSkin is even more compatible... but it also sounds like Snarly no longer plans to work on them either.

Just wondering how you both wanted to proceed. Would you like me to host your versions of Snarly's scripts Y-Phil over at https://cobrablade.net/snarlygribbly/poser.html?

It sounds like these will be replacing the originals going forward. Or would you rather keep them separate, hosted by yourself, as they are now?
I should also say thanks to both of you for being such a big help to the Poser community. Most of us couldn't do what we do without these scripts.

CobraBlade posted at 2:58 AM Wed, 4 May 2022 - #4438104

Ah, that explains it, I was a little confused, as EZSkin already ran in Poser 12 but I knew the Cycles plugins weren't compatible yet.

This is really good news and sad news all at once, it's great we have Scene Fixer working in P12 now, and that EZSkin is even more compatible... but it also sounds like Snarly no longer plans to work on them either.

Just wondering how you both wanted to proceed. Would you like me to host your versions of Snarly's scripts Y-Phil over at https://cobrablade.net/snarlygribbly/poser.html?

It sounds like these will be replacing the originals going forward. Or would you rather keep them separate, hosted by yourself, as they are now?
I should also say thanks to both of you for being such a big help to the Poser community. Most of us couldn't do what we do without these scripts.

That being said, and given the fact that we now have the source code, we can continue to make EZSkin and Scene Fixer evolve, at least I'm ready for this, as long as the knowledge can be shared here

I am happy to see that we are proceeding forward to delivering a better product that will make many users very, very happy in the long run.  My hat's off to the kind contribution of everyone involved.

@ Y-Phil: I believe I have found a major bug in EZSkin, a shader arrangement that is completely invalid with the current P11/P12 versions.  I'm going to run the script to determine where the problem is. 

I'm happy to report that after giving it a once-over with all the different render engines, there are no problems that I can see.  Simply ignore my comments in the previous post.

I'm happy to report that after giving it a once-over with all the different render engines, there are no problems that I can see.  Simply ignore my comments in the previous post.

I heard it too.

I can certainly host them. Scene Fixer started up fine, and I can try and test it here on my Mac a bit later.
EZSkin on the other hand... if I replace the EZSkin3.pyc in my ScriptsMenu folder with this EZSkin3.py  I get this...

I can certainly host them. Scene Fixer started up fine, and I can try and test it here on my Mac a bit later.
EZSkin on the other hand... if I replace the EZSkin3.pyc in my ScriptsMenu folder with this EZSkin3.py  I get this...

I have retrieved on my PC a similar plugin, but its displayed name is "BB Hair Shader by AP", and the python file is "BB Superfly Hair.py". It should be the same.
Besides this plugin, I've found another gem: EZGhost

Both had the same error: the way to use the Python "print..." as it's now a function, it requires parenthesis. Both are corrected on this point, and you may find the updated versions here.

BB Hair Shader by AP is one of my favourites, that's the one I missed the most when switching to Poser 12.

Scene Fixer works fine, so I've already uploaded it to https://cobrablade.net/snarlygribbly/poser.html as SceneFixer  (Updated version maintained by Y-Phil).
Replacing BB Hair Shader by AP with your updated version, and things are looking a lot better now.