Okay. Then I've already been using it! :) It is somewhat brief, but helped alot in making sense of the basic Poser file structure. Thanks, maclean. Kuroyume

The ensuing war with Iraq over, hmmm, oil, I suppose. Not to get into a political discussion (which should be moved to The Virtual Tavern), it appears to me that the first war with Iraq was justifiable because they had invaded a neighbor country, which is covered by the UN Security Council. Pres. Hussein should have been removed then. Now, though, the justification is on flimsier ground despite still being covered by the UN Security Council - Iraq has broken many guidelines and rules setup in Resolution 1441, the worst being the expulsion of the UN inspectors some years ago. Personally, I think exile for Hussein with continued UN inspections is the best option. BYS

Maybe there is something to a name. Shamms Mortier seems to be nothing but a sham when writing books for Poser. No wonder many people feel that Poser is a useless toy. There are very few books for Poser and three of them (by you know whom) are just BS. Maybe P&T could do a show about him. ;0) There are so many talented, knowledgeable, wonderful people using Poser at a master level. We should urge them to collaborate on a book worthy of our time. BYS

Once again, Renderosity eats a long post... :( I must remember to select all and copy before I Post Reply. Here's the synopsis: The thing about JPGs is balance, balance between filesize and quality. Personally, high quality JPGs retain good information while still being smaller in size than BMPs and TIFs. It'd be great if templates could be saved in vector format instead of bitmapped image. The only real solution is to use gray-scale (as B&W doesn't show up very well when zoomed out) and JPG high-quality. That should keep the filesizes somewhat restrained. BYS

I think it has something to do with ease of scaling (down) of the texture without too much interpolation and the fact that computers are binary systems. Powers of 2 are easily halved all the way down to the base (2) without ever encountering an odd number. BYS

There are ways to make textures repeat, at least in P5, but Poser uses UV mapping (stretching over the object). There is no preferred size, but it is always a good idea to make it a power of 2 (512x512, 1024x1024, 2048x2048, etc), 4096x4096 being a good size for hires textures. IMHO, the best format is a non-lossy format like .bmp or (uncompressed) .tif, but a high-quality .jpg will do just as well. DPI is only relevant for printing. It does not matter at all. It's the pixel size, not DPI, that makes the difference. BYS

pakled, well said (and that's what I wanted to say but haven't had time). If you want to protest, do what artists do and make your own statement, not someone elses.

Nope, nothing of the sort. Actually, what you say is mostly true. My only disagreement is that many of the "new features", i.e. Rooms and Firefly, in Poser 5 caused problems because they were not integrated well into the base code, causing major crashes or odd behavior. This would definitely transfer over to Mac or any other system for that matter. I love MacOS 10 (and the underlying BSD) and, if it weren't for financial woes, would still have my Mac. I do plan on getting another in the future; hopefully after Apple stops releasing faster systems every other month. ;0) They need a system upgrade program so that your six month old computer can be reasonably upgraded for a newer one. But that's probably an issue for all computer users (?). BYS

And, to JoeyAristophanes. Yes, there are my versions of Windows. There are many versions of MacOS (hmmm, how did they get to OS10 anyhoo?). WinXP Home is an upgrade to WinME (yuch!) which is an upgrade to Win98SE which is an upgrade to Win98 which is an upgrade Win95 which is an upgrade to Win3.1, dah du-dah du-dah. WinXP Pro is an upgrade to Win2000 Pro which is an upgrade to WinNT 4.1 which is an upgrade to WinNT 3.5, etc. Office isn't a version of Windows OS. So, pffffffffffffttt on you... ;0) BYS

Bobasaur, see first message, re: "all i have to say is CL going to have to really convince us Mac users that its worth it. we aren't as easy sells as PC users are." Just herd all Wintel users into a single category and color us, well, stupid? That's elitist. I'm not a follower, not stupid, and probably have been using a computer since he was sucking his thumb. :) Had the Mac version been released at the same time as the Windows version, the Mac users would have: A: Flown to Curious Labs to see the program work on a Mac prior to purchase. B: Waited several months before any of them purchased to see how the PC version faired (which would make no sense, really). C: Purchased it just like any normal human being with an interest in new features would. BYS

Although imperfections were expected on a new full release, the delivered product (Poser 5) was a sorry sight indeed and would expect that it would be as dismal on a Mac as a PC as these were bad integration and coding issues, not platform issues. I agree with Spit. Your smugness belies an elitist view about "PC users" only due to the fact that the Mac version was not released simultaneously, thus allowing for your 20/20 hindsight vision to corral us all into a "fodder for the Big Brother Gates Society". I, for one, was using Amiga computers before basically being forced into the Wintel world. And you didn't see me castigating PC or Mac users. And you may ask, "Well, duh, why didn't you get a Mac?". Well, duh, Macs were very expensive and not very useful for someone working in an industry that used Wintel systems (business computer programming and engineering). And, FYI, until very recently, I also owned a Mac (PowerMac G4 933MHz w/Superdrive and FPD 17" Studio Display). If CL had released a P5 for the Mac, I would have purchased that also. Purchasing software isn't different for Mac users than for PC users. You propose a false dichotomy with nothing to back it up but a hypothetical platitude. You know where you can shove that platitude... ;0) BYS

Hierarchies, by definition, don't loop. Otherwise you end up with recursive referencing (Part A -> Part B -> Part A (which references Part B, and ad infinitum)). Look at the purse as a hip with two legs (even though the legs are actually fused together at the souls of the feet, by analogy). I don't remember offhand if you can make a part the child of two different parents, but i doubt it. So, you might need to divide the purse strap into two parts and make each a child of the purse and connected at their relative areas. BYS

Just copy the URL link from IE's Address text box (if you're using IE) and paste the URL into the URL: text entry box below: | | | / :) BYS

That seems unusual because the AreolaBig morph should not only be changing the mesh geometry, but dictacting how the texture is applied. So, if the texture fits the default areola and you apply that morph, the texture should adjust to fit. Have you confirmed that the nipples are assigned the correct texture map? If that's in order, then boulder's suggestion, albeit something that shouldn't be necessary, is a good one. Be certain to edit a copy of the texture image and use that in order to retain the original unedited. BYS

This is a little late, but just in case nobody figured it out: The "big number" colors in the posershell.xml are just the combined hex values converted to decimal. 13879224 = D3 C7 B8 = 211, 199, 184 (RGB) That simple! BYS