The storage of the floating point values natively (in 4-byte format) conserves much more file space than in ASCII format (which can be anywhere from 1-byte to 10-or-20 bytes per value).  But with external binary morphs (.pmd) you do run that risk of scene corruption.  I'd opt for the text method (disable the external binary morph preference) which takes a bit more disk space but is 99% more reliable.  The speed difference is negligible on load.

I no longer back up my Runtimes - just the downloaded content.  If I even had an inkling that my drive was about to go, I'd copy everything to an external harddrive.

As far back as Poser 5 they have been no longer required but some content vendors (starts with a 'D') still use .rsr and Mac resources in their products (and considering that MacOS 10.5 is trying to wipe their continued use out completely).  Luckily, Poser converts them to png for us. :)

http://www.philc.net/tutorialsIndex.htm

?

.rsr is the Windows equivalent of a MacOS resource.  Its only use for Poser (these days) is to store the Library thumbnail for a Poser content item.  Poser uses them for this automatically - you don't import them.

You import the related Wavefront .obj file and Poser will handle the .mtl (there is a reference in the .obj file pointing to the .mtl if it exists).  The .mtl is very simple and usually you will only get a few parameters from it and possibly some texture maps stored as image files.  For the image file texture maps, they will need to be with the .obj and .mtl in a relative location (either in the same folder or a sub-folder depending upon the extent of the references in the .mtl file).  Both .obj and .mtl are text files, so you can simply open them up in a text editor to see any references.

To be a bit more explanatory ;), the reason is that going from spline based hair to polygons isn't all that difficult (and supported of course).  But going from polygons to splines is nearly impossible.  You'd need to specify which strings of vertices are to be converted into splines and that would be grudge work indeed.

The percentage discount with minimum purchase hurts them I think.  I have a hard time rationalizing a purchase of so much just for so much discount unless the opportunity already exists - and that is rare.  I have to have the funds, the desired products, and be within the timeframe of the coupon all harmoniously coincidental to put it into use.  Unfortunately, the amount of stuff which is desired isn't there at all.  If I see something new that is desired, I'll purchase it right off (if a coupon covers it, all the better).

Rendo really should consider more varied sales like Daz.  At Daz, inevitably, whatever you're looking to purchase is on sale some time - and all the better with the PC membership.

No.

09:00 here when I looked - I was up until 1:30 AM installing a new 1TB SATA II data drive.  Eeks!  It took 4-1/2 hours to format - but it also took 3 hours each side to copy and recopy the 315GB of data (although my mobo supports 6 SATA drives, the PSU only has four power connectors - drat!).  Basically, 12+ hours just to do that. ;P

Actually, I would have been the first but had other things to do (like make breakfast). :)

If you are considering doing it manually, then your best place to start is by referencing an existing Inj pose file (not one of the awfully complex DAZ Mil figure ones though as they readScript and readScript - you'll go batty).  Basically, all you need is the version section, each actor section affected with only the channels needing to be injected, and an empty figure section.  Edit a copy of the cr2 so you have a backup!

TIFF

As long as you are rendering from Poser as single frame images at at least 30 fps, you should be good.  Most video (TV, movie, DVD, etc.) is at around 29.97 fps (making 30 fps close enough for conversion).  It is better to render the frames as single images because you are not involved with formats or compression issues (esp. mpeg-ing).  This provides the most control.  And Adobe After Effects and Premiere both work with these easily.

AE and Premiere can compensate for aspect ratio, but it can get tricky.  When I did renders for a DVD intro-outro in Cinema 4D, I set the aspect ratio in the renders there (the renders looked stretched on the computer) but the results out to TV were perfect (using Pinnacle DV500 for TV output preview).  So, you'll have to find some way to verify your results in that respect without having to produce the entire thing.

One problem that you'll encounter isn't just the dimensions but more the pixel aspect ratio.

Computers use a 1:1 pixel aspect ratio.  Standard TV is 4:3 and High-Definition TV is 16:9.  This is the x:y pixel size - that is, on a computer, pixels are square whereas on TV they are some rectangle.  I don't think Poser's renderer can compensate for aspect ratio.  "Constrain Aspect Ratio" only pertains to the render dimension not the pixels.

On the actual dimensions,  you'll need to determine the target audience.  NTSC (US) and PAL (Europe) standards use different screen dimensions.

I looked at this new update and there doesn't seem to be much of which to speak.  This type of thing is not easy to do for sure, but $30 to upgrade gives me what exactly?

• 1. MorphBrush
• 1. TextureBrush Work Directly on Your Shapes/Textures, Retouch Freely!
• As a standalone import/export to Poser, Maya, 3D Max and other 3D applications
• New EASY 3-point interface
• Improved Texture mapping
• Improved 'Mirror' feature
• Up to 4098x4098 pixels output
• New 'Profile' features profile matching
• New 'Watch-me' video at your fingertips
• New Manual
• Moveable dialogs, resizable window
• Interactive 'Tooltips'

The final four items are nothing that should indicate a new major version - these should be given for any new major version.  It boils down to two new improved features and two features which don't seem to improve my output much (I can do morphing and texturing in other apps).

In my case, it isn't the photo-texturing that is most important either.  It is the shaping of the geometry to match the head in the photo that is my goal.

Let's make this clear:

As EnglishBob states, the file extensions are meaningless in this situation - it just lets Poser see the file as the proper type (no matter what) in the category and add it to the library.  But Poser does make distinction between content creation filetypes and content modification filetypes (though light and camera categories are dual-purpose).

Just because these so-called 'clothing props' are in the Props category doesn't mean that they are actually props.  They are actually full-fledged figures with the file extension changed so that they can be listed in the Props category instead of supposedly clogging the Figures category.

Props have several differences compared to figures.  Props only have one body part (BODY or NOT!) and are fully defined within the prop section.   Figures usually have more than one body part each of which is defined within an actor section (very similar to a prop section) and finally with a cohesive 'figure' section that establishes the hierarchy among other things.

One way to make the distinction after loading the object is simply to check the drop-down lists.  If the new item shows up under the Prop list, it is a prop.  If it shows up under the Figure list, it is a figure.  Simple? :)