I'd gamble that my script is quite a bit simpler than what Paul has written. Basically, it writes a temporary poser file from the object in Poser and then loads that and takes out the parts that aren't needed in a MAT file then resaves it. You might be thinking... why write a temporary file first? Well, the problem is that Poser Python is incomplete. It will not write settings like multiply through object color, multiply through highlight and so forth using only Python commands. The reason that you have to use the material room and click on each material first is because that it appears that Poser 5 writes node information "on the fly" as it opens each material - I mean this specifically in regards to opening a P4/PP created object or figure in P5. In the cr2, that node information is not natively present, so P5 builds it. It may create that information when doing a Firefly render - I haven't investigated that - but it doesn't build node information upon loading a P4/PP file. Case in point - if you use the script on an object that has 6 materials and you only click on 3 of them in the material room before running the script, guess which 3 don't get node information written (remember it's writing a full poser libary file then parsing that into what it needs). Now, if Paul has done this in a more clever or complete fashion within Poser, I think his scripts would be definately merit a closer look :) MAT Pose Edit is also another possibility to look at as it does provide batch conversions from P4 to P5 MAT files - though I'm sure by it's very nature that it isn't perfect. Nothing "automated" is always going to get things right - maybe even a good bit of the time, but not always :)

.