(1) Who is Drizzt? (2) An intricately bumpy pattern can often be described more economically by a bump map than in solid as mesh, for example the corrugations round my suction-dredger-sub's suction hose (in the Poser Fun Stuff).

I suspect a lot of it has many more polygons that it needs. I once found an .OBJ mesh where someone had used half a megabyte to describe such a simple shape as a baseball bat!

In each CR2 file there are TWO lines that point to the .OBJ file. Or, two for each model, if the .CR2 file contains more than one model.

That might make the combined package rather enormous. But it would make it easier to pose in Poser and get Bryce-type rendering. At the moment, getting anything complicated across from Poser to Bryce including all texturing is rather like loading the pack elephant and then unloading it at the other end. - Or, let Bryce read and FULLY understand .PZ3 files. And let Bryce output in PZ3 format also, or in some format legible by humans. At the moment, trying to decipher .BR3 and .OBP file format is like trying to get into Area 51.

Probably this: Call up the joint-editing window. Then do the same as adjusting a joint articulation center, but select the figure's root segment (Hip if it is a human). Or with the figure's BODY selected. Note that the center of the root segment is not the same as the center of the BODY.

And don't forget to delete the universe also - crumbs that sounds a megalomaniac sort of idea -

I know that. The hierarchy displayed with everything checked, so I left it like that. What I meant was that, in Poser 3 I can export to .OBJ with the faces for each body segment preceded by a g line, as was in the geometry line; but I can't in Poser 4.

My "man in overall and heavy boots" model is wearing a pair of my boots. Call search for "overall".

Winzip runs under Windows. In Windows Explorer, if you click a .ZIP file (or some other packed modes), it shows a directory of what is in the file. If you right-click a file, the resulting menu has extra lines which pack the selected file or files into a zipfile. If it is a self-extracting .EXE file, that menu has an option to see what is inside the file.

With a text editor. Poser embedded props are the text of an .OBJ file incorporated in the .CR2 file.

That hat would look just right at the big horse race meeting at Ascot on England where the fashionable women wear the latest weird hats. Except one year when the weatherman got tired of all that sillyness and send a thunderstorm and cloudburst there on the day.

Also, if I render on a white background to use as a 2D cut-and-paste, if I JPG it, much of the white background near the image becomes that annoying few units darker than proper white (red=green=blue=255) and the 2D graphics program has trouble telling what is background and what is image. One way round that is to put along with the picture another picture which is white for background and black for image and, GIF-code it. - I remember handling a JPG'ed photo of an alien in a wood from a Gerry Anderson UFO site: when I came to extracting the alien, the alien's spacesuit is red, the forest is mostly green:: easy:: except that along the edge of the alien, the JPG process had made an annoyingly wide border of intermediate fawn and russet pixels, and I had to put into my 2D graphics program a special border-sharpening facility.

I use .BMP for the texture maps in my models. OK, the files are big, but in zipping they compress spectacularly (since they are only black and white). If I JPEG such a file, oh yes, here come the diffraction-type fringes along the borders between the colors. - Also: I wrote a 2D graphics handling program, and when I put JPG support in, the JPG matter's source code is enormous. GIF support code is much shorter.

The foreign language is French.

And find how much it would affect realism if we allow each ray of light to me affected once only by it, to save on render time.