Because of a Poser 5 bug that does all kinds of goofy things when "apply all" is used for textures (randomly disconnecting nodes, not always applying all material nodes to new textures, etc.--none of which is addressed in R4), it's sometimes easiest to delete the figure and start from scratch when I'm playing around with textures. It would be faster if there were a way to delete all the textures from a figure instead of having to reload the figure. I did a search in freebies to see if Ockham had a script for this purpose, but couldn't find one.

The attached file is a super-simple way to set all the textures of current figure to "NO_MAP". I don't know if it will affect the nodes in P5, though. Take the file and rename it to something like Deltex.py before using.

But if you're talking about that mysterious list of all textures used during the current Poser session, I don't know how to reach that!

"But if you're talking about that mysterious list of all textures used during the current Poser session, I don't know how to reach that" I was hoping CL had fixed this in SR4 since they stated it had "improved texture memory management." But alas, no such luck. The problem that's existed since at least P4 then continued through ProPack, P5, and all SR's is that Poser retains all textures used during each Poser session. STILL, after all this time, the only way to clear the list is to close then reopen Poser.

If I remember correctly, it was stated be CL that only the texture names stay in the list, not the texture itself in memeory. It is still anoying, but hopefully not a memory hog.

I haven't had any trouble with the "apply all" myself. Basically it runs through the materials and disconnects but does not delete all existing nodes, then it pastes and connects the nodes you had seleceted when you did the apply all. That means you have to be careful about which nodes you select. In most cases you probably want all of them. I just wish it would delete the pre-existing nodes instead of just disconnecting them.

I was hoping CL would have openned a lot more up for Python. They may have and its undocumented.

"If I remember correctly, it was stated be CL that only the texture names stay in the list, not the texture itself in memeory." Exactly, names & paths are cached by the texture manager, all bitmap data is removed from memory, unless you choose to use the respective texture again.

"I haven't had any trouble with the "apply all" myself. Basically it runs through the materials and disconnects but does not delete all existing nodes, then it pastes and connects the nodes you had seleceted when you did the apply all." That's odd because the only time I haven't had trouble is when I'm only applying a texture. If there are also bump and trans maps, a texture can be disconnected when "apply all" is used on the bump map. The problem becomes more pronounced as the figure increases in complexity (such as with millenium figures). It becomes all but impossible to play with different textures because so many odd things happen. I've had times when the preview image shows everything textured, but the render loses one or two materials and renders default white while everything else is textured. If I'm the only one having a problem with Poser 5's "apply all" for textures, I'm at a loss as to what's causing it. MATs work fine, but manually applying textures becomes a horrendous chore because of the odd things that happen.

I'll have to test it some more. Usually if I want to use it, I want to copy all of the nodes to all of the materials. I'm not sure if I've ever even tried applying just a bump map to all materials.

Attached Link: http://thenetherworks.com/

RReynolds, I've had this problem too - it seems to come when I've had Poser open for a long session and been switching materials around a lot. Netherworks has a free Python script which will remove all nodes as well as setting all material groups to white with no map. Go to the Freebies>Utility Poses section.

:) And thanks to ockham for all his help in helping me write that.