Fri, Nov 8, 11:43 AM CST

Renderosity Forums / Poser Python Scripting



Welcome to the Poser Python Scripting Forum

Forum Moderators: Staff

Poser Python Scripting F.A.Q (Last Updated: 2024 Sep 18 2:50 am)

We now have a ProPack Section in the Poser FreeStuff.
Check out the new Poser Python Wish List thread. If you have an idea for a script, jot it down and maybe someone can write it. If you're looking to write a script, check out this thread for useful suggestions.

Also, check out the official Python site for interpreters, sample code, applications, cool links and debuggers. This is THE central site for Python.

You can now attach text files to your posts to pass around scripts. Just attach the script as a txt file like you would a jpg or gif. Since the forum will use a random name for the file in the link, you should give instructions on what the file name should be and where to install it. Its a good idea to usually put that info right in the script file as well.

Checkout the Renderosity MarketPlace - Your source for digital art content!



Subject: Question on a script


Poserfiend ( ) posted Wed, 04 July 2001 at 1:08 AM · edited Sun, 04 August 2024 at 4:54 AM

Was adapting Kamilche's great skin color matcher to set all the skin attributes to the other parts. Worked fine. Then I thought I'd also set the Transparancy Attributes from teh skin to everything else. When I run the script it sets the first three parts or so after the skin correctly , then fails to set the rest. No error messages. Sets the first couple exactly. May set some of the attributes, but never all of them after that. Any ideas?


bushi ( ) posted Wed, 04 July 2001 at 2:08 AM

Without seeing the code, it's like trying to diagnose what's in the blackbox. ;-) I'd expect to see something like this happen if the list of texture area names was predefined in the script rather then read from the figure at run time. If the figure being used had texture area names different from the pre-defined list, there could be problems. That's just a shot in the dark. You might want to add a 'try' program structure in the loop that's changing the parameters to see if you could trap an error that way. A well placed 'print' statement to list what's happening in the loop would also be useful. It would at least let you know how may iterations occured before the loop broke. You could set it up to print the current values for the variables being used.


Privacy Notice

This site uses cookies to deliver the best experience. Our own cookies make user accounts and other features possible. Third-party cookies are used to display relevant ads and to analyze how Renderosity is used. By using our site, you acknowledge that you have read and understood our Terms of Service, including our Cookie Policy and our Privacy Policy.