And the newest version also works from the Scripts Menu.  I'm probably not the first person to report that none of the EZSkin 3 versions respond to the close window; one has to click on the close icon within the app itself instead.

I want to thank you for your help. It appears that as I get older, I confuse a bit more easily, and this one (especially the peculiar behavior of the Poser 11 version) was confusing to start with.

In process on the Poser 12 installation.  It should be noted that the installation text file still refers to moving the contents of  the  'Custom shaders' folder into the Custom Engines folder; I think it is actually referring to the 'Engines' folder in the zip file.

To my pleased surprise, 3.1 DOES run from Scripts Menu in P12.  No idea what I did wrong the first time.  Did the same things: imported the definitions and presets.  I'm now going to delete the .pyc file and install the updated files from the latest P12 update and see how that goes.

I'm taking this step by step.  So, first, I cleared out all EZ Skin3 installations.  Then I installed the Poser 11 version (good thing to point out that the Poser 11 and Poser 12 versions don't interchange).

Then I ran it from the scripts menu.  Well, I tried.  Same result.  So I tried to manually run the script from the Poser Files menu instead.  THAT worked.  At that point, I specified Custom Engines, imported legacy definitions and presets.  Shut everything down again.  Loaded P11 again, and tried to run EZ Skin from the Scripts Menu.  No go.

On a hunch, I ran P11 from the Start Menu instead of the Task Bar.  That was actually worse: it loudly declaimed "

Failed to load URL http://127.0.0.1:11530/nonVirtualAssets/ContentLibrary-1.9.11/release-1.9.11/ContentLibrary/ContentLibrary.html with error (-401)."

Summary:  I can only run EZSkin3 manually.  I am now going to install the P12 version and try the same experiments.

I thought I posted here, but apparently not.  Odd.

At any rate, I apologize (again) for reviving this dead topic, in the hope that someone can help me.

I don't want to bother SnarlyGribbly if I can avoid it.  He's earned his retirement.  But I cannot get EZ Skin3 to work for me in Poser 11 OR Poser 12 .  I thought I understood how to install it, and I've tried several different locations for the supplemental folders in case that was somehow a problem.  (I created the Custom Engines folder on my L: drive, where the vast majority of my Poser content lives in various runtimes.)

My symptoms are decidedly uninformative:  I open the Scripts Menu, click on EZ Skin3, and the menu disappears.  That's it.  No error messages, no popups, no buttons appear in the Python window when I open it.  I am using the current versions of Poser 11 and Poser 12, and I use the "more than famous" Windows 10, also kept up to date.

Sorry it took so long.  I have revised the Read Me to thank you for the much-needed assistance, and updated the zip file with the new versions.  I'm going to upload it to my Freebies contributions in  a couple of minutes.

Thanks again.  I doubt I would have done it without you.

You shader masters have my awe-filled respect. I'm not competent to use the math nodes or most of the other functions you power-users use so nonchalantly.  When I want to create a shader that replicates the reflective safety stripes on safety vests and such, I just throw up my hands and babble.  And Superfly is utterly beyond me.

Well done, all!

Odd that you didn't get a syntax error; I did.  At any rate, removing the word "break" fixed my problem, and it's working again in Poser 12, for which I thank you and Y-Phil.

Please tell me that all of these changes and breakages of older scripts are actually worth it to those who code in Python regularly, because it's pretty frustrating to me.  Presumably to the others who had scripts die and can't fix them, too.

At any rate, as Chromestar quipped, "One down, millions to go".

Removing the word "break" was the final repair needed.  Thanks again, guys!

Damn.  Now it doesn't like the "break" syntax.  This script is too damned simple to be this much trouble, even if I was the one who screwed up the parenthesis fix.

Oops!  I put the parenthesis in the wrong place when I made the correction.  [sigh]

Thanks, guys!  I'll make the appropriate change to the lister, as well.

I do believe that you've hit upon  my problem:  Notepad2 apparently defaults to Tabs as Spaces.  I'll check that out in a little while.

And at least part of the problem has been solved with the print statements:  Nope, they weren't in brackets or parentheses.  Of course, now, it doesn't like how I handled printing variables.

You offer to assist with the code is most gracious, and I humbly and desperately accept:  I learned just barely enough Python to write the tools (Shadow Cam lister, and Shadow Cam renamer), and then promptly forgot everything I learned.

# script to set all Shadow Cam names to the
# same name as the light it works with.

import poser
scene = poser.Scene()

def main():
  for actor in scene.Actors() :
      if actor.IsLight() :
          kid = actor.Children()
          for cam in kid:
            if cam.IsCamera():
              vu = cam.Name()
              cam.SetName(actor.Name())
              print ('%s renamed to %s.') % (vu, actor.Name())
              break
          
main()
print ('\n Renaming completed.')

Sorry to raise this zombie, but I have driven myself nuttier trying to implement this very simple code change.  I get nothing but indentation error messages when I try the original modification and the proposed modification.  I feel like my head is full of cotton and I'm not thinking clearly, but I'm sober, so that's a bit less likely than otherwise.

(And just to pour acid on my wounds, I just discovered that my own simplistic Shadow Camera Rename freebie now is flagged for syntax errors, so the syntax must have changed as well.  Python has got me in a stranglehold and is starting to squeeze.  I might as well be a dead parrot for all that I'm accomplishing.)

Thanks, Shania!  Wonderful news, and I'm grateful for the grueling effort on your part.

I love the idea of the spreadsheet!  That's far more ambitious than what I was envisioning, which was merely to list what I have, and which ones I've updated.  However, Renderosity doesn't seem to know which sets I bought at Daz and Hivewire, only my more recent purchases.  (Yeah, I'm in "what's left" mode, too, as the list of the stuff I don't have is much shorter than the list of what I do. [chuckle])

Thanks for all of the info; I'll get right on that.

I've been stalking, er, admiring your work since the Daz days, and got more items during the Hivewire period.  I looks like I'm a wee bit behind in updating my birds, though.  [sigh]  At this point I've even lost track of which ones have been updated, and which have not.  Do I need to create another spreadsheet to get access to the updates already done, and the future updates.  [wry smile]

Because, as Miss B points out, these are looking great, sir.