Forum Moderators: Staff
Poser Python Scripting F.A.Q (Last Updated: 2024 Sep 18 2:50 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.
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.
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?