Wed, Nov 20, 9:27 AM CST

Renderosity Forums / Poser Technical



Welcome to the Poser Technical Forum

Forum Moderators: Staff

Poser Technical F.A.Q (Last Updated: 2024 Nov 13 12:50 am)

Welcome to the Poser Technical Forum.

Where computer nerds can Pull out their slide rules and not get laughed at. Pocket protectors are not required. ;-)

This is the place you come to ask questions and share new ideas about using the internal file structure of Poser to push the program past it's normal limits.

New users are encouraged to read the FAQ sections here and on the Poser forum before asking questions.



Checkout the Renderosity MarketPlace - Your source for digital art content!



Subject: Poser 6 doesn't like my very, very simple MAT pose (OK in DS3!) - Help!


3dcheapskate ( ) posted Tue, 25 May 2010 at 11:15 PM · edited Wed, 20 November 2024 at 9:21 AM

Help!
I've created a simple prop model (.obj and .pp2 files) that seems to work fine in both DS3 and Poser6.
I've created a very simple MAT pose file to simply change a texture - here's the full file:

{
version
    {
    number 6
    }
prop Stupa
    {
    material Plinth
        {
        textureMap ":Runtime:Textures:3DCheapskate:Stupa:PlainBlack.jpg"
         0 0
        }
    }
}

This works fine in DS3. But when I select it in Poser 6, nothing happens. No pop-up dialog saying something's wrong, just a quick flash of a "Loading..." message at the bottom of the Library panel, then the Windows "Exclamation" sound (which I guess is Poser telling me that something's wrong).

Here's the stripped down .pp2 file that I'm using:

{

version
    {
    number 6
    }

prop Stupa
    {
    storageOffset 0 0.3487 0
    objFileGeom 0 0 :Runtime:Geometries:3DCheapskate:Stupa:Stupa.obj
    }

prop Stupa
    {
    name    Stupa
    on
    bend 1
    dynamicsLock        1
    hidden        0
    addToMenu    1
    castsShadow        1
    includeInDepthCue        1
    useZBuffer        1
    parent UNIVERSE
    creaseAngle 50
    channels
        {
        propagatingScale Scale
            {
            name scale
            initValue 0.1
            hidden 0
            forceLimits 0
            min 0.001
            max 100000
            trackingScale 0.004
            keys
                {
                static  0
                k  0.1  1
                sl  1
                spl
                sm
                }
            interpStyleLocked 0
            }
        translateY yTran
            {
            name ytran
            initValue 0
            hidden 0
            forceLimits 0
            min -100000
            max 100000
            trackingScale 0.001
            keys
                {
                static  0
                k  0  0
                sl  1
                spl
                sm
                }
            interpStyleLocked 0
            trackingScaleMult 1.000000
            }
        }
    endPoint 0 2.0925 0
    origin 0 1.04625 0
    orientation 0 0 0
    displayOrigin        0
    displayMode USEPARENT
    customMaterial    1
    material Plinth
        {
        KdColor 1 1 1 1
        KaColor 0 0 0 1
        KsColor 0 0 0 1
        TextureColor 0 0 0 1
        NsExponent 96.0784
        tMin 0
        tMax 0
        tExpo 0.6
        bumpStrength 1
        ksIgnoreTexture 0
        reflectThruLights 1
        reflectThruKd 0
        textureMap ":Runtime:Textures:3DCheapskate:Stupa:PlainWhite.jpg"
         0 0
        bumpMap NO_MAP
        reflectionMap NO_MAP
        transparencyMap NO_MAP
        ReflectionColor 1 1 1 1
        reflectionStrength 1
        }
    locked 0
    backfaceCull 0
    visibleInReflections 1
    visibleInRender 1
    displacementBounds 0
    shadingRate 0.2
    smoothPolys 1
    }

doc
    {
    addActor Stupa
    }
}

Just in case it's relevant, the obj file contains 10 materials, each of which is laid out like this (nothing spurious in the file except an initial mtllib line):

#vertices
v -0.104169 12.826638 -0.043142
...
#UVs
vt 0.936161 0.944094
...
usemtl Plinth
s off
#faces
f 112/1 10/2 11/3 111/4
...

I'm probably missing something really obvious  :oS
Like I said before - Help!


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).



EnglishBob ( ) posted Wed, 26 May 2010 at 3:21 AM

Attached Link: http://market.renderosity.com/mod/forumpro/showthread.php?thread_id=2735605

The correct keyword is actor, rather than prop. If you use the form actor $CURRENT, the pose will apply to the currently selected item - but this only works in Poser 5 upwards.

Les Bentley's Compendium of PZ2 techniques (linked) is the bible for this sort of stuff. :-)

DAZ|Studio is more forgiving of this sort of thing, because it was developed after a lot of the community-devised techniques that we now take for granted (ERC, MAT poses etc.).


3dcheapskate ( ) posted Wed, 26 May 2010 at 4:55 AM

Thanks for the link  - very clear and concise explanations.

I've fixed the .pz2 as suggested and it's fine, provided that I've also got a figure loaded (as Les points out).

 I also resorted to RTFM, where it mentioned MAT pose files and MC6 files. Converting my MAT pose file to a materials collection (changing the extension from .pz2 to .mc6,  changing "prop Stupa" to "mtlCollection", and moving the file from /Pose/ to /Materials/) seemed to do the trick.

So maybe I'll also convert the MAT poses to .mc6 files as well, just to cover the eventuality of no figure in the scene.


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).



LaurieA ( ) posted Wed, 26 May 2010 at 6:11 AM

I always use material collections now rather than MAT poses....saves clutter in the pose folders too ;o).

Laurie



EnglishBob ( ) posted Wed, 26 May 2010 at 6:26 AM

MC6s work better in Poser, but I'm not sure if D|S will accept them. You could always provide PZ2 style MAT poses for D|S users.

You also need Poser 6 or later to use MC6s, so you are cutting off a (probably small) part of your potential Poser-using audience. I tend to assume that people who are still persisting with older versions have enough know-how to apply materials by hand, anyway. ;)


LaurieA ( ) posted Wed, 26 May 2010 at 6:49 AM

Well, I have an unwritten rule: I don't support versions before Poser 6 ;o). And I don't normally for D|S either. That may change if I was a merchant, but I'm not, so Poser it is...lol.

Laurie



Privacy Notice

This site uses cookies to deliver the best experience. Our own cookies make user accounts and other features possible. Third-party cookies are used to display relevant ads and to analyze how Renderosity is used. By using our site, you acknowledge that you have read and understood our Terms of Service, including our Cookie Policy and our Privacy Policy.