Quote - The project is on a very short break :)  We'll start working on the conversion script again tomorrow and it should ship very shortly after that. It's as good as ready.

But is that why those forum sections were removed?  Seems a little drastic.  There was a lot of good information in there to just shut them off.

Quote - Could we please have bug/imperfection reports posted (with pictures) to THIS THREAD at PoserPlace? That way Diogenes/Phantom3D will have access to them.

What happened to this V4-WM bug report thread?  In fact, what happened to the whole V4-WM forum section at Poser Place?

I'm sure I was looking at it just a couple of days ago but now it's missing.  So's the Antonia section from the looks of things.

I don't know enough about the CR2 files structure but I'm curious enough about this issue to learn.  I'll open up the bad and the good versions and compare.

Coincidentally, why would some figures be saved as just a very large CR2 while others are a CR2 with a OBJ file?  Does it depend on what was used to create the figure in the first place?  If so, how do these large CR2 files (that include geometry) get created in the first place?  Does it have something to do with the constituent PP2 props that it includes? 

I'm little mirky on how all these various files play together in Poser apparently.

So it didn't actually wipe out the UV information.  What ended up happening by entering the Setup room was a shuffling of just the material names, along with a wipe of all the details in 2 of the materials.  What I was expecting to be the propellor material actually ended up being the map3 material, and so on, so of course the UVs didn't match up. 

I now have it all sorted (other than materials being mislabeled) and the revised figure has been successfully added to the library.  I'd still like to know what strange events happened to have caused all this in the first place.

Played a little more with it.  If I pop into the Setup room and back out without changing anything it wipes out on of the texture groups (along with it's UVMap) but it does allow me to save the figure to the library afterwards.

Anyone know a quick way of restoring the UVMap information for a given texture group?  I could drag the obj into UVmapper but I was wondering if there's a way to do it within Poser.

They are pretty small lights (port holes really) so what I'm likely going to end up doing is just using photoshop to select the light's color, which is unique to the rest of the composition, copy to a new layer, and blur for effect.  That'll give me my glow simply enough.

This is in PP2010.  Beyond checking IDL in the render settings is there anything else I should be considering?

Shaderworks is great.  The only thing I wish it did was work with the Poser undo.  Nothing worse than applying a freebie pose or expression and having it wipe out all your morphs, then not have an undo to correct it.

Quote - Yes the Poser Tool Box and BVH Helper scripts have this ability.

http://www.philc.net/PTB_page2.php#figureUtilities

http://www.philc.net/BVH_helper.php

Wow!  I like the looks of your tool box!

Couple of questions...

• Does the Better Hand Posing work on all figures equally well, or was it optimized for V3 or V4?  And does this perform like the Grasp morphforms of the later figures?  Just trying to figure out if this would be redundant on Gen4s.
• Would the Vertex Magnets serve to "indent" a surface as well as pull it as shown in the example?  

Again, great looking utilities!

My personal email address got picked up in a spammer distribution list at some point and over the course of 5 years got to a point where about 98% of the inbound email was spam.  Outlook was filter about 2/3 of it but I fixed it for good by moving my POP services from a mom&pop hoster to godaddy.  About 99% of the spam stopped immediately.  Godaddy must have a well managed spam filter (probably uses a blacklist to filter out spammers SMTP servers).

If your account is on hotmail or gmail or any other web-base email system then I suppose you're SOL.  If it's a private email address (ie. your own domain) then you could look a moving to another hoster that stops spam at the gateway.

Figured out how to create a new 3d layer (first option under the 3d menu), but still no idea how to improve performance.  I have tweaked everything possible under the performance and 3d options, which had helped some but still looking for a better way.

Thanks for the breakdown Kage.  I feel that I'll start getting a better feel for fStop values that match the focal distance the more I play with it.  Generally, my subject is no more than 2 units in depth so it should be fairly easy to draft a quick and dirty table of focal distances and corresponding fStops.  I just kinda hoped someone had already done it.  :)

Thanks again!

In reference to the OPs original gripe, I too just recently started having my renders stall out (still running at 100% but going nowhere).  Again, copious use of props and interiors, monsterous skins (10+mb range) and IBLs with AO and depth of field.  I'm running Win7 64-bit with 8GB and although my reported memory usage never went above 70% I still have issue with scenes requiring more than average resources.  I was able to resolve the issue with a bit of trial and error however.

What works for me is to make sure the textures are loaded into memory before I try cranking out a HQ render.  I do a number of LQ test renders so that's usually not an added consideration.  The reason I say this is because I can almost guarantee a freeze up if I restart Poser and try to start a HQ render right off the bat.  When I do load up my HQ render settings I found that it's key to lower the max bucket size from 256 to 64.  That last bit seems to have been the real clincher for getting it to complete a render without freezing up (knock on wood). 

I actually found that the difference in render speed with varying max bucket sizes all fell within a range too small to be differentiated from a conservative margin of error.  We're talking less than +/- 30 seconds on a 20 minute render.  But this bit of verbosity is a bit tangential to the discussion at hand.  :)