3dcheapskate opened this issue on Jun 14, 2022 ยท 16 posts
3dcheapskate posted Tue, 14 June 2022 at 3:25 AM
That's the runtime-relative filepath as per the PoserPython manual. It's the LoadMaterialCollection() and LoadMaterialSet() (which don't, according to the manual, include a path) that are puzzling me. But as noted in my previous post it appears that the manual is wrong, or at least slightly misleading.
Given that the Poser file extensions for materials are mt5 and mc6 I'd guess that the methods for loading/saving materials were added in Poser 5 and 6 - designed, implemented, and documented by somebody different. And of course they're not scene methods.
It appears from my previous post that LoadMaterialSet() does/can in fact take a path as its argument. LoadMaterialCollection() probably does/can too.The 3Dcheapskate* occasionally posts sensible stuff. Usually by accident.
And it usually uses Poser 11, with units set to inches. Except when it's using Poser 6 or PP2014, or when its units are set to PNU.
*also available in ShareCG, DAZ, and HiveWire3D flavours (the DeviantArt and CGBytes flavour have been discontinued).