my py script wish list:

1: My main one. A way to paint textures right on a mesh(object)inside Poser instead of having to export out the mesh, do that unwrap thing, paint it, then back in again. Nothing elaborate, just basic and quick. I mean just doing pose, one can export an image and post work it with Paint Shop Pro, or a-dopey.. but in animations..you need to texture the object 360..I hate the material room, that shine / reflect crap, etc..I actually liked the Poser 4 way better..pick a bump, slap it on, done.. lol. This would be a handy tool for like texturing a mountain scene, and adding a snow cap to your own specs, not prefab mapping.

2: A bvh randomizer.. a sort of basic loop within a loop, overlap loop. etc. Would make some animations a bit less mundane.

3: Make all those Poser menus stay on top the way the parameter dials do for the others such as..light, camera, tools etc..that way you could expand your documanet window edge to edge.

4: One true click method to turn of IK, and zero pose the figure.

5: A better way to adjust lights..maybe something like point and click in the window.

6: And of course make this stuff affordable for everyone.

I use Poser 5 by the way, and I don need no stinking vista

That's all for now :o)

4: One true click method to turn of IK, and zero pose the figure.

This one wouldn't be too hard.  The problem, apparently, with the IK would be determining in one click which IK chains to deactivate.  If you want all of them in one go, it's a simple script.  If you want to pick and choose, you probably need a GUI, so you end up with almost as many clicks as using the pull-down menu.

For zero pose, the following might work, in one click.  (Written off the top of my head, here, so this is untested....)

#############
import poser

scene = poser.Scene()
fig = scene.CurrentFigure()

for act in fig.Actors():
    if act.IsBodyPart():
        parm = ParameterByCode(kParmCodeXROT)
        parm.SetValue(0.0)
        parm = ParameterByCode(kParmCodeYROT)
        parm.SetValue(0.0)
        parm = ParameterByCode(kParmCodeZROT)
        parm.SetValue(0.0)
##############################

Number two may already be covered to some extent, possibly by one or more of Ockham's free scripts.  Numbers one and five would be difficult, if they're even possible with PoserPython.  There doesn't seem to be any "hook" to allow Python to figure out how the mouse is relating to the 3d view.  I can't even guess about number three....

Thanks for the reply, Cage.. Yeah I was thinking it might be more than just a few lines of code for some of my wishes..lol

And yes I think you are right about the bvh,,I do recall seeing something similar to that around..

Just wish there was a way for my main one,,number one..life would be a lot easier doing the detailing right inside Poser, less costly too, I hope.. :o)

That's becoming the problem of trying to enjoy Poser these days, the price of all the other software you need is sort of taking the fun out of it all..especially when  lot of these utility cost 2 times if not more than the price of Poser itself...

But thanks for the script,,everything that saves me time is a blessing :o)

Here's a script to to turn all of the IK off. You need to have a blank line on the end so that the for loop knows it's ended.

import poser

scene = poser.Scene()
fig = scene.CurrentFigure()

# Turn off IK
for name in fig.IkNames(): 
  fig.SetIkStatus(fig.IkNames().index(name),0)

*"You need to have a blank line on the end so that the for loop knows it's ended."

Really?  Is this always true?  True of PoserPython, or Python in general?  Wow, I had no idea.   

Quote - *"You need to have a blank line on the end so that the for loop knows it's ended."

Really?  Is this always true?  True of PoserPython, or Python in general?  Wow, I had no idea.   

No, but you need to make sure that there is a newline after the last script line, to stop the Python parser throwing a spurious syntax error (might be fixed in 2.4).

Ah that's what it is. It was producing some wierd errors, which were fixed when I added the additional blank line. I've seen similar problems with other script parsing software so that why I tried that.

*"No, but you need to make sure that there is a newline after the last script line, to stop the Python parser throwing a spurious syntax error (might be fixed in 2.4)."

*Good to know.  Thank you!  :)

Hi all, thank you for the scripts.. Glad someone can write this stuff..because I sure can not.. lol