|
PublicWiki / LoadingByObject |
SearchWiki PublicWiki.RecentChanges Edit Page Page Revisions |
figureResFile directive.
Within an actor, prop, or other geometry-based Poser object the objFileGeom keyword is declared, followed by two integers (generally zeroes) and then by the path to the Wavefront OBJect? to be loaded:
<objectType> <objectID>
{
storageOffset <float> <float> <float>
objFileGeom <int> <int> <path>
}
For unknown reasons, if a storageOffset? is used (which it doesn't appear to need to be), the numbers associated with that directive are generally 0, 0.3487, and 0 respectively.
For instance, if you wanted to load up a prop called SuperLaserRaygun? from a Wavefront OBJect? file called 'superLaserRG.obj' in your 'CheesyBlaster?' folder under your Geometries folder, your actor predeclaration and geometry loading block might look like this:
This is generally a preferred method for props to load over the default method with which Poser 4 stores them (Embedded Geometry?). You can manually convert a prop or other file with (Embedded Geometry?) to use this loading technique like this.
Warning: array_merge() [function.array-merge]: Argument #2 is not an array in /home/poserpros/poserpros.daz3d.com/pmwiki/pmwiki.php on line 657
Warning: array_merge() [function.array-merge]: Argument #2 is not an array in /home/poserpros/poserpros.daz3d.com/pmwiki/pmwiki.php on line 657
prop SuperLaserRaygun { storageOffset 0 0.3487 0
Warning: array_merge() [function.array-merge]: Argument #2 is not an array in /home/poserpros/poserpros.daz3d.com/pmwiki/pmwiki.php on line 657
objFileGeom :Runtime:Geometries:CheesyBlaster:superLaserRG.obj }