I'm shooting for next week sometime. That said, there may be additional slips as I get to the end because of the way I am generating the morphs. Instead of physically editing the mesh I am finishing a set of Python scripts that will automatically generate the morphs for the clothing based on the figure morphs. I am shooting for being able to bring up Vicky2 and the clothing in Poser, run a sequence of scripts and have the new clothing CR2's ready to go without me having to do any additional work (outside of writing a couple thousand lines of Python script). So far it is going well and I hope to be able to post sample pics later this week. Technical considerations aside I have a day job and my wife had surgery last month so I have been stretched thin timewise of late.

FYI: I ( John Brugioni) am currently generating a version of the Victoria Clothing Pak 1, the one Daz put out at the same time as Vicky 1.0, with a set of morphs generated from Vicky 2 incorporated into the clothing CR2's.

How about we start a thread of requests for additions, changes, upgrades, fixes, etc to the Poser-Python interface? Then CL would have one place to look for feedback on that issue. A select item callback would be great. And yes, there is currently no way to generate a new figure. Talked with CL and they said "oops". But then they asked me a very pertinent question which is how would you want to generate a new figure, ie copy from an available figure, generate completely from scratch, etc.

Mason- post your script if the stuff below doesn't work. I think I know what your problem is as I ran into something similar. Want to start you script something like this: root=Tk() # rest of script. Use root as master for gui items root.mainloop() If you don't do the root=Tk() and then use root as the master to feed into all your gui items, when you exit the script you basically kill off the Tkinter instance that's running and he next Tkinter call in the next script you run will generate error messages. For example, if you just did a "Label(text="test") you'll kill the Tkinter instance that's running. Instead you want to do a Label(root, text="test"). This way root is feed in to the Label as the master so that when the Label is destroyed the script local instance of Tkinter, generated by the root=Tk(), is destroyed instead of the main instance. If you kill the Tkinter instance you then have to do a Reinitialize Python off the main Poser menu. Hope this helps. P.S. Try: http://www.pythonware.com/library/tkinter/ for the intro to Tkinter and http://www.python.org/doc/life-preserver/ for the Tkinter life preserver

Yeah, verily. A wish list would be a great idea. Can we get it put up the same way the Renderosity Store wish list is?

Depends on size of tabs. If you're using a editor thats not set up for Python it may be using the wrong number of spaces per tab. I believe that Python wants eight spaces per tab or something like that. Check www.python.org and then under documentation. Under the language reference guide, if my memory is correct, it gives the spec for tabs, spaces and other whitespace with respect to indenting.

Anybody found a way to generate or load body morphs using Poser-Python?

As far as I know you should be able to, I did. I think you have to have the update patch loaded on the installation that you install the pro-pack against. I have two separate poser installations running on my PC, so you can have multiple installs and they should work. I did it so that I could test files generated by ProPack for compatibility with regular Poser.

If I can throw my two cents in. What I would suggest is a gui like this: a list box that gives the scene prop actors after selecting an actor then slider then bulges the prop in and out interactively. Move the slider right and it gets bigger, move it left and it gets smaller. In the inner works you simply save off the orignal geometry state of the prop at selection and recompute off the base geometry every time the slider value changes. Set the initial value of the slider in the middle and you can positive and negative bulge prop. Add a "save" or ok button to save off the new prop with a popup to ask what to save it as. If anyone's interested in this I'll see if I can implement this tonight or over the weekend. Bushi- are you using a Mac? I'm getting some extra CR-LF crap on every line of your script when I save it from Netscape.

I agree with you about the usage of pass vs x=1 but I didn't write the original script, Curious Labs did. FYI for all listeners, the reason you have to wrap the Geometry() method with an exception handler is that is doesn't always return a value of 'None' if there is no geometry present. That's a quirk (as opposed to a bug) that CL is aware of and may fix later. For now, it's the only one, besides hand rolled file I/O , that I'm aware of that you really need to wrap with a try. For ScottA - go to http://home.earthlink.net/~redink3d/bulgePropsNormal.py This version works on my machine (WOMM). Beware that it also affects hair. Need to set a conditional for that. Will hopefully post a better looking version with a gui later this week/weekend.

If someone could figure (sorry no pun intended) out how to make a new figure I'd like to see it. I don't see a way to do it with the current interface. I emailed CL on it to see if they knew since that seems like an obvious thing we would want to be able to do. I did some hacking with the dir() and vars() functions against scene and didn't see anything undocumented that looked like a new figure function. FYI, the morph targets are under the Actor and Parameter methods. To see the current morph targets do parameters=actor.Parameters() then for parameter in parameters: and then parameter.IsMorphTarget(). Set the morph target deltas with a parameter.SetMorphTargetDelta() if the target allready exists or try a actor.SpawnTargetFromGeometry() where you provide the target geometry. If you only have deltas you'll have to pull the current geometry, add the deltas to it and then use that as the target geometry. Let me know if that doesn't work for you or if you need more help.

Heres a fix. One quirk is that hair items might be affected by the script below. Need to go back and figure out how to filter out hair items. The scene.Actors() is supposed to return only props. Since hair can be a smart prop it's probably getting lumped in. I'm going to set up a page on my website Monday night or Tuesday just for scripts and I'll post this one there. I've only posted the critical changes below starting from after the imports... scene = poser.Scene() actors = scene.Actors() for actor in actors: try: geom = actor.Geometry() except: # do anything so we don't have a syntax error... x = 1 else: if actor.IsProp(): verts = geom.Vertices() norms = geom.Normals() i = 0 for vert in verts: # do buling here # keep this inside if prop check actor.MarkGeomChanged() scene.DrawAll() What you want to do is use the scene.Actors() which returns all non-figure actors in the scene. Then do an if actor.IsProp() check to eliminate lights, magnets, etc.

If you have a straight up script it will not create a *.pyc file. If you have a set of modules, such as class defs, in a separate file(s) that you import it will then generate the *.pyc file. If you want to generate a *pyc file then break out most of the script functionality into a separate file and then use the import. As an example from one of my scripts: from Tkinter import * import Pmw import poser from ActorTest2 import * The ActorTest2 file which has my code in it will be compiled down to a *.pyc file. I haven't seen any real speed difference between the *.pyc and *.py files. There isn't supposed to be too much anyway. I see a bigger lag waiting for it to spin up Tkinter.

Bushi- You're on the right track. In the current interface you can access everything geometry and material related EXCEPT the texture coordinates. I've emailed CL on that one and they're going to include that in an updater sometime in the future. Have not looked at cameras and lights yet but I will. Downloaded LightFlow and found it will only work with Python 1.5.1, the one they have on their website, as it wants to have a Python 1.5.1 dll in the path. (double ugly item #1). I'll try it again as soon as I finish downloading their Python 1.5.1. FYI, Poser uses Python 1.5.2 so of course the versions would be incompatible (Murphy's Law of Programming #5- Versions will be different and incompatible). That could probably be fixed but will require someone somewhere to recompile the source. I emailed the Lightflow dude to see about getting it working with 1.5.2. In the short term could export the scene to a file and read the file into a Lightflow Python script and render it that way. FYI to get the python version run this script: import sys print(sys.version+'n') For those of you who haven't coded in the past the most important programming phrases to learn and master are: "Why isn't this !&^%$#@#%@ thing working!!!!" "Why did those &^$@)!*% idiots do it that $%&Q@$& way!" If anyone wants a custom file exporter the main thing needed to implement it will be a spec for the file format. Python can write out to both ascii text and binary files.

Downloading Lightflow now. Will take a crack at it when I have a spare minute.