Ah hah! I think I've found what I was looking for... http://www.renderosity.com/messages.ez?Form.ShowMessage=1474180 Describes how to create a morph carrier CR2 file which readScripts in the original character CR2. Unfortunately I'm off on vacation for 2 weeks, so I won't have time to play or respond before I come back, boo hoo ;-(

Thanks ockham, I was hoping I wouldn't have to go down that path, but it had occurred to me. The DrawAll() might help, though.

Since that's the body part pop-up menu, they're probably phantom limbs given you've just tried to amputate M3 ;-) SJCR

For the Poser 6 Mac OS X side, I want to see: Multi-processor support Stability Maintain GUI responsiveness when Poser has been running for hours or days and many scenes have been created/closed/opened. Stability CL acknowledgement and actual support of MAT pose files and material setting outside the material room Python interface access to material shader nodes, parameter key interface (not inherited) values for the ability to save morph targets in pose files. Working memory management/garbage disposal when loading new or opening existing scenes and/or controlling Poser from Python. Network rendering Full, internally consistent scene scaling to eliminate underflow artifacts in Raytraced renders using reflection and refraction. Fix the render engine discrepancy/bug that ignores the effect of figure scaling on displacement maps in direct to camera views but applies the figure scale to displacements in reflected views (a la "Picture of Dorian Grey". Fix the GUI's incessant and irrelevant insistence on hiding windows when Poser is not the frontmost application. Let the OS do it! The ability to select the Figure from the same actor heirarchy menu at the top of the Parameter palette. Internal ability to manage/view JCM/ERC parameter influences. Pre-stretched dynamic cloth, i.e. optional "Shrink-wrap" drape rather than just a gravity based drape.

Ockham, I just stumbled on what I had been doing wrong in trying to print the kParmCode constants. I needed to prefix them with "poser." as in: import poser print "kParmCodeGEOMCHAN = ", str(poser.kParmCodeGEOMCHAN) the output listed above should read (as printed by Python): kParmCodeGEOMCHAN = 43 kParmCodeCENTER = 44 kParmCodeCURVE = 45 kParmCodeHAIRDYNAMICS = 90 kParmCodeDYNAMICPARENT = 92 kParmCodeCLOTHDYNAMICS = 91 Cheers!

You probably want to check under the Display Menu that the Figure Display Style is Texture Shaded or Use Document Style and that the Document Display Style is Texture Shaded.

maxxxmodelz, I should clarify - Poser 5 Python on Mac does not support Tkinter which is invariably used by the PC creators of Python scripts to implement their GUI. If all the user interface of a script needs to do is select a file or enter a bit of text or answer a yes/no type question, all of those can be done in Mac Python without resorting to Tkinter, it just takes more effort than most PC Python creators without access to a Mac for testing are willing/able to expend (absolutely no offence or flame war ignition intended). I've spent a fair bit of time recently, poking under the hood of Poser 5 Python on the Mac, trying to find GUI workarounds for some of the most popular commercial, PC only Python scripts. I have not given up hope that some external link to another Mac Tkinter enabled Python can be made to interface Poser with some of the scripts that Mac users are hanging out for. I don't think I can hold my breath until P6 comes out...

DPI settings in general are mostly irrelevant for images intended for viewing on a computer monitor, given that the image resolution (pixel dimensions) either will or won't fit completely on someone's monitor and hence require scaling or window scrolling to view. 72dpi is the "standard" monitor pixel density, but resolution switching monitors may have 120dpi (or more?) on their higher resolution modes. As soon as you start talking about print media and computer proofing, dpi takes on some significance. My understanding is that it's all about the tradeoff between physical image size and viewing distance. As soon as the pixel dimensions subtend an angle smaller than the human eye can discriminate at a particular viewing distance, further detail or dpi is completely irrelevant. For CGI, anti-aliasing can give the illusion of more detail by eliminating jagged edges defined by pixel colour boundaries.

Wow! this is inspiring (and extremely frustrating, since none of the HDRI utils or Python scripts can run on a Mac)!

3DNeo, you might also check out this thread on the same sort of joint deformation topic including sample images of knee and buttock deformers for extreme bend poses: http://www.renderosity.com/messages.ez?Form.ShowMessage=1946492 Before the making the set of deformers that the images in that thread illustrate, I attempted to cancel out the effects of the deformation zone which flattens the top/front of the thigh when the thigh bends more than 65. What really needs to happen is some seriously complex JCM/ERC and the hardest part is trying to create a morph that cancels particular sections of the effect of a joint deformer in a controlled and seamless manner. If you can get the morphs done, the JCM/ERC is definitely the easy part (relatively speaking) and can even incorporate staggered/delayed onset.

What's missing from Python on P5 Mac is Tkinter support, so no GUI for python scripts. Any script that can do without the dialog boxes (other than a simple yes/no/cancel) can be made to work on the Mac. The worst part of P5 Mac is its lack of stability (though I see just as many complaints from PC users about Poser crashing). There seem to be gaping holes in lots of its memory management/garbage collection. That said, the current P5 on OS X is not fully native. It uses the CFM binary format intended as a migration aid from OS 9, rather than the fully native MachO binary format. This adds significant overhead to every bit of I/O the program does (excluding compute bound renders which are only limited by being unable to utilise a second CPU at all). I hear that CL are working on Poser 6. If the Mac release lags the PC version by 18 months (as happened last time), the only excuse I would tolerate would be that they were making it fully OS X native and adding multi-processor support. Setup and cloth rooms both work as well as the rest of P5 on the Mac. I wouldn't want to put you off upgrading to P5 though. Most of my complaints are of the genre "Huge Scope For Improvement", rather than "Don't Waste Your Time and Money". ;-) Prefix-GeoffIX-Suffix

[watch and learn]

[bookmark]

[eyeball of thread]

Thanks EnglishBob. Got MinFig (thanks to Les Bentley BTW), have a nice bit of script for parenting the top level orphans to the new figure (CR2 file created and loaded by the script on the fly), preserving any prop heirarchy they might have below them. BUT, the internal names of the props do not receive the expected :# suffix indicating they are parented, though they obviously appear and act so in the interim heirarchy before I orphan them again. This appears to restrict the ability of the MAT Pose from modifying their materials list. I've tried manually adding the figure number suffix to the prop name in the MAT file, but it makes no difference, the pose doesn't take and there's no Python interface to allow the prop's internal name to be modified. Short, that is, of saving the scene file, changing the prop reference to actor and reloading, but then you might as well save the scene and clear the materials directly in the scene file before reverting the document. Ah well, there's usually only the GROUND prop unparented in the default scene and any prop loaded later and manually parented to ... [THINKS]... [HACKS] [TESTS] [SUCCEEDS - like a budgie with no beak] We have a Winner!!! If the MAT Pose file uses the keyword actor, rather than prop, it can be applied to unparented scene props like GROUND, YAY!!! Attached is ClearAllMaterials1.3.py which successfully clears all figure materials and parented or unparented prop or actor materials. No props or actors had their parentage modified (though it was questioned ;-)) during the running of this script. Enjoy, and post here if you do have any problems with it.