Sun, Dec 1, 12:04 PM CST

Renderosity Forums / Poser Python Scripting

All Forums

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: Bug: Setting Texture Map String for Image Node

dburdick opened this issue on Feb 27, 2008 · 3 posts
Back to Forum Print
dburdick ( ) posted Wed, 27 February 2008 at 1:23 AM · edited Thu, 28 November 2024 at 2:42 AM

I ran across this annoying bug when setting a texture map string in an ImageMap node.  Here's what I'm doing in Python:

  1. Get the texture pathname for a material (e.g. SkinTorso)
  2. Load in a mat pose file for that material (e.g. load mat.pz2)
  3. Find the image map node for the newly loaded material and change the image texture back to the original pathname captured in step 1

Everything get sets just fine, but when I go into the material room or render, it says it can't find the .jpg file even though it's listed correctly in the node.  This only happens when I try to set an image file that has previously been loaded into the Poser scene.  If I assign a completely new image file to the Image node via Python, no problem. 

I suspect this relates to bugs with how poser is cacheing files and it's getting confused when you set an image via Python that is already in the cache. 

Thoughts?

markschum ( ) posted Wed, 27 February 2008 at 1:43 AM

did you do the refresh tree thing ?

dburdick ( ) posted Wed, 27 February 2008 at 3:27 AM

Quote - did you do the refresh tree thing ?

Yes I did.  Didn't make any difference.  Anyway, I built a workaround by programmatically stuffing the original texture map pathname into the pose file and injecting the whole thing. 

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.