Okay,

Just to make sure I understand this.  On the Geometry call backs -

Is this what I am supposed to see when I open the CR2 file for the newly added figure?

{

version
    {
    number 9
    }
morphBinaryFile :Runtime:libraries:Character:Ragtopjohnny's Clothes:Ragtopjohnny's Prison Guard

And is that all that is needed for the call backs?  I ask because I'm about to upload a new package to the store (not what you see here) but something else and wanted to make sure that it was the proper way it states things.   

This new item is a prop, so I know it will be as a prop too but I just find the whole aspect of the call back really confusing. 

Thanks in advance.

As I recall, you always want to set the number to 0 so Poser can pick the number it needs, and you should get rid of spaces in your file path. File paths always get mucked up when they have spaces in them.

Thanks Joe.  I'll remember this.   

Quote - Is this what I am supposed to see when I open the CR2 file for the newly added figure?

{

version
    {
    number 9
    }
morphBinaryFile :Runtime:libraries:Character:Ragtopjohnny's Clothes:Ragtopjohnny's Prison Guard

'morphBinaryFile' is used in a cr2 (a pp2 uses 'morphPmdFile') to load morphs when

'Use external binary morph targets'

was selected in your General Preferences (before saving the file). Note that it does not load the base geometry, that is done by the two 'figureResFile' lines.

The path in your example does not seem to contain a file name, which means it would not actually load anything, and would probably generate an error message. Apart from that the format seems correct. The version number will generate an warning message if the file is opened in a version of Poser lower than that number, and for that reason the version number should be the lowest version that will support the essential features of your figure.

Quote - And is that all that is needed for the call backs?

The 'morphBinaryFile' (with a complete path with file name) is all that you need to load the morphs, assuming the associated PMD file is in the correct location. Personally I would keep the morphs internal to the cr2, and not use a PMD file, as I feel this is simpler, and provides less scope for things to go wrong.

Thanks lesbentley.  COMPLETE PATH with the FILE NAME is needed.  I was wondering too how would Poser know what to call back upon.

Thanks!

Sorry I though that was the figure number. Ben a while since I CR2 hacked. Listen to Les about version number.

http://www.kuroyumes-developmentzone.com/poserfilespec/ucr2filespec_dec2004.pdf

http://www.kuroyumes-developmentzone.com/poserfilespec/introduction.html

This might help.

OT - I'm assuming that runtime path maps to a real directory. If it does suggest considering if you really need those apostrophe characters in the path name - its not wrong but in rare cases may cause problems with non-Poser scripts, particularly Linux where that character can be used as a string deliminator on command line functions.

Yeah... apostophies are a no-no also. Missed that one.

Thanks all.  I'm planning on finishing up these props today.  I'll let you all know if I have any issues.  Hopefully not.