Do all the Poser 5 Python scripts work in Poser 6? My favorite, Ockham's "delete lights" script? PhilC's Clothing Creator?

I can confirm that the Clothing Creator works in Poser 6. Templates are now available for James and Jessi. Incidentally I have just completed the templates for Koshini, Ichiro and Krystal also.

Most of my stuff works, including Delete Lights. Some actually works better: my DeleteProps used to leave Poser holding a false list of the props, and now it doesn't. Must be better handling of deletion in the internals. One doesn't work: SaveImage. (I don't think this is in freestuff, but it's one I use a lot.)

One hint: scripts that use a PYD module will need to have that module in the P6 runtime, as well as moving the script itself. If you don't want to reinstall, look at the runtime/Python/DLLs and runtime/Python/Lib folders; you can probably tell by dates and names which PYD files are not part of the standard stuff. (My PYD files all start with an underscore and an uppercase letter, like _Talkbubmodule22.pyd while the standard stuff is all lower-case.) Copy those PYDs into the corresponding P6 folders.

Thanks! Good to know.

And I was wondering, lazy soul that I am, if I could just tell P6 to look next door in the P5 Python folder. Guess not. :-)

For the vast majority of scripts, that will be fine. I don't think any of my commonly used ones have PYD helper files. But if you've set up a set of sub-palettes, you will need to transfer all of that, because the palette lookup doesn't work across runtimes. (The alternate-runtime setup for libraries doesn't include Python.)

"Delete lights" is one of the many default python scripts that comes with Poser6. thefixer poser coordinator

Didn't I read somewhere that Poser is now more 'fully open' to Python in P6 than previous versions? If so, I wonder what new potential this gives it.

"Fully open" means that the shader nodes and dynamic cloth and hair parameters are now controllable. Far as I can tell at this point, some other long-standing 'hopes' have not been satisfied. Still can't save the render from a new window, and there's no access to walk designer or point-at internals.

Umm, didn't someone mention a few days ago that P6 Mac still has an issue with tkinter based scripts?

The tkinter on Macs is still hosed, but for simple situations the alternative Dialog calls are usable (and cross platform).

I found two (now confirmed) bugs, one for the Cloth Room interface, one for ShaderNodeInput.

ockham >> Some actually works better: my DeleteProps
used to leave Poser holding a false list of
the props, and now it doesn't.

[Hi ockham!] I was testing a bunch of scripts in P6 last week and got the following error for delprops:

:0: SyntaxWarning: name 'Deletables' is assigned to before global declaration

The script ran anyway despite this message, but I wonder what it means. Might be some problem with my particular setup, though.

Hope you're enjoying P6! I'm getting to like it better and better. TG

If it's more open.. maybe someone will (PLEASE!!) create one that translates P4 materials into P5-6 Materials (move Gradient Bumps into Bumps, and all the other stuff that I've never been aware of). maybe it can be done, maybe not with what nruddock said with "ShaderNodeInput"... who knows.. I forgot how to program anything about 13 years ago.

Rick

Fortunately the bug with ShaderNodeInput has a workaround.
Funnily enough, I was writing a script to move the Bump maps when I discovered it.
I got a little side tracked by the alternative Dialog stuff, and DAZ's March Madness, but I'll post a first version later this weekend.

How about one that translates P5 materials into P6?

I don't know what needs to be translated from P5 into P6.
My copy of P5, since neither hair nor cloth worked all that well, is still installed but never used (at least very little). but I'm sure that SOMETHING will need translating on that part... and that one will be good too... (not of use for me tough).
It's just good that the material room works better with python now...
Now an Idea.. if Gradient bump does not render in Firefly (manual says... ) what about an option to "copy" the nodes.. so one can still use the p4 renderer AND firefly.
I hope you put that script for free... no dough since P6

What exactly would you want the script to do ? I didn't think there was that much difference between P5 and P6 materials.

http://www.enmeshed.com/shadermagic/

But the P6 skin shader node is different. If you use P5 MAT files that use the skin shader node in P6, the result isn't pretty. Example is our lovely model, Victoria 3, wearing the DAZ high-res universal textures. In P6, with the MAT file from the tutorial, she looks like she's three days dead.

Apparently, the solution is to add an extra node between the skin shader and the texture map.

Ok, I understand now. Before and after screenshots of the material room would be good, along with any other hints as to how you want input values / colours setup when adding the new node (or a link to a thread where the fix was discussed).

Attached Link: http://www.renderosity.com/messages.ez?Form.ShowMessage=2187315