I'm not entirely new to Poser, but I would like to now what is the advantage of loading a .PP2 prop over importing a .OBJ prop, especially when there are no moving parts? Does it have something to do with textureing, scaleing, or some other aspect that I'm missing? Thanks

That is a very good question? I like to know to.

The PP2 format allows to load and apply morph targets in the mesh and it's needed to do Smart Props, which are props that follow character parts or other props.

So basically, if I'm using say....a flower pot, that's just going to be sitting around in the background, theres no real need to convert it to .PP2. But if I were to import some eyeglasses that needed to load correctly on the face, and be parented to the head, I would need to convert to .PP2. (or wanted to morph them into different styles)

Well, one pretty obvious advantage of pp2s is that they sit in the library and you can just click on them without having to go look for an obj and import it. A flowerpot doesn't need to be a pp2, but it won't take up much more space as a pp2 than an obj. And, as I said, you don't need to hunt for it. Other than that, smart-propping and morphing are the obvious advantages. Texturing is no problem, nor is scaling. Although, when your prop is smart, you can apply MATs to it, which makes texturing easier. All in all, I'd say pp2s win over objs mac

Basically, if you're going to use the obj more than once, I'd suggest converting it to a pp2. That way it ends up in your library and it's just more convenient :o) But you're right, if it's something you just want to load in the background for one image, there's no REAL reason to concert it to PP2. it's just easier. And since you get a neat li'l thumbnail too, the possibility of forgetting what "Neat_Prp.obj" was gets eliminated :o)

"Neat_Prp.obj" LOL mac

PS ernyoka - There's a handy little free app by Kawecki called Prop Viewer for those "Neat_Prp.obj" files. It views most 3d formats. mac

.obj files don't store transparency information. .pp2 files, however, store all of the prop's material settings, including transparency.

By default, Poser saves the OBJ within the PP2. The next step is to convert the PP2 to an external call. (Or use an existing external call PP2 and paste in the new OBJ name - like Jim Burton suggested.) If there aren't a lot of morphs, the file is then small. The geometry can be used for morph stock. If you change or remap, give the new OBJ version the name and location of the extisting one and the PP2 will use it. The geometry does not need to be in a Runtime.

another advantage not yet mentioned.. is scale... objects can import in so huge that they're naught but a large shadow on the ground. you can scale it down to where ye want it.. save it as a pp2 then it'll load at proper scale for the render. as well as all teh other things mentioned above, matability, transparencies, smartpropability.. etc. 8 ) just coining words..

For scaling, Poser Import has setting to adjust it. But, you can't use the OBJ that is the source of the import as morph stock if you do. If you use the dial of the library file to do it - you are usually scaling to 1-2% of the original scale, the PP2 'remembers' the original size, so you are trying then to do fine scaling in a scene after you have already burned 98-99% of the sensitivity. Better = Import and scale to the Poser size - either with the Import options or the dial and then Export as this new size. Now, Import this with no options checked and you have the full range of the dial scale.

Didn't know about the prop viewer, I gotta go grab that :o) Wizzard is also right about the scale, but the same thing CAN be accomplished by importing your HUGE Neat_prp.obj, scaling it to the correct size and then exporting it again, still as obj. Next time you load it, don't check any of the scaling or whatever boxes and it will load at the correct size. But it's more of a hassle than to have it sitting in a palette :o)

The advantage of .obj files is they can be used in many other programs. A .pp2 has to be converted to .obj first. For smart props that will definitely be positioned in Poser, .pp2 is best. For flowerpots, etc, .obj can be more convenient for those making the final render outside of Poser.

I just want to make sure I'm clear on this: You're talking about straight .obj files vs. .pp2 files. Can't .pp2 files that reference outside .obj files be smart propped and contain texturing information? Thanks! Cres the Confused

Yep, it sure can, it can do can do anything an internal call can, in fact. It also has the advantage of an easy change if you revise the mesh, just replace your external OBJ file, props don't even save RSR files like figures, so no need to delete one. DAZ requires all props to use external OBJ files, BTW.

Crescent, Think on it this way. A pp2 or cr2 file is split into 3 parts. A declaration, a definition and a figure block. The declaration - Tells poser where to go to look for the geometry, and (if it's a cr2), how that geometry is split into groups. In the pp2, this declaration is just a couple of lines pointing to the external obj. In a cr2, it's split into groups and lists all the parts of the obj file so that poser can make a figure. The definition - Tells poser how the prop should behave - scale, rotate, trans channels, joint parameters, etc. In the cr2, this definition also includes the body parts and parenting information. The figure block - Contains all the materials and their attributes, plus what to add to the menu - the prop name or the body parts of a cr2. This block is what is used in MAT files. So, when you add a pp2 to the library, it stores all the geometry information from the obj within the pp2. All you are doing when you point it to an external obj is replacing the geometry with a declaration - ie. a path to where poser can find the same information. As Jim says, there are several advantages to external geom, which is why DAZ insist on it. A simplistic explanation, but that's really all there is to it. mac

I figured that was the case but I wanted to make sure I understood it correctly before I did something stupid later on. Thanks a ton!