Forum Coordinators: RedPhantom
Poser - OFFICIAL F.A.Q (Last Updated: 2024 Nov 07 6:34 pm)
What are your system specs? Without mentioning those, it's not really worth much :o)
Mine is still at the download stage so I havne't tried it yet - I'm hoping it will perform better than P6 (thought that performs reasonably well for me most of the time), since some of the memory-issues should have been solved.
FREEBIES! | My Gallery | My Store | My FB | Tumblr |
You just can't put the words "Poserites" and "happy" in the same sentence - didn't you know that? LaurieA
Using Poser since 2002. Currently at Version 11.1 - Win 10.
NOTE: If you have a multi core machine, you probably want to adjust General Preferences -> Render -> Render Processes and set it greater than 1.
Content Advisory! This message contains nudity
Nothing special:
V4 with high-resolution maps and Kevin by CP. Backdrop by rdna, V4 facemorph by me. Default p6 lightning.
Wow, that third picture with the nostril glow is so Poser. They didn't do anything smart at all - people are still going to load a figure, push Render and get that sort of thing. No wonder Poser gets no respect in the CG community. After seven iterations, you'd think the lighting model would be just a teensy bit like all the other apps.
I have such a love/hate relationship with Poser. I can easily do the most crazy complicated shaders in Poser with ease. I love the shading model. But the lighting is lame. I hear P7 can do better than P6, but out of the box that looks exactly the same. So far I have not seen a single image from P7 that looks like it is from a modern lighting engine.
Consider this pair of renders (click to see detail). On the left is a P6 render, the result of hours of work in the material room, tweaking lights, and adjusting shadow parameters, plus a good 15 minutes to render. On the right, I loaded Vicky into Modo, spent about 30 seconds changing a couple specular values, did not adjust the lights at all, and rendered in about 45 seconds.
Sigh.
Renderosity forum reply notifications are wonky. If I read a follow-up in a thread, but I don't myself reply, then notifications no longer happen AT ALL on that thread. So if I seem to be ignoring a question, that's why. (Updated September 23, 2019)
I've tried it on both my Athlon 64 X2 4600 (2GB RAM, GeForce 6800 256 MB) desktop (running Windows X64) and my Turion MT-40 laptop (2GB RAM, WinXP Pro, Radeon X1600 256 MB) ...so far, I've been pleased with P7 - I haven't noticed a huge speed boost, but it has been able to render some scenes P6 would choke on without a problem and without needing to decrease the bucket size or lower the quality.
From what I can tell, the multi thread feature is a real mixed blessing...this is not a true multiprocessor renderer (like Carrara), it seems more designed to help with the setup and memory workload rather then the actual rendering...in simple scenes, in fact, having it multithreaded actually seems to slow things down. I'm no expert at this stuff, but I would image the real advantage to enabling multiple threads would be to get around the memory limitation to a single thread in Windows for very complex scenes.
Now I have the render option set to two threads using a separate process and things seem much quicker. The roadster is clearly a highly detailed item though. Loading a saved scene with simply the roadster takes 130 seconds, and this image took 10 minutes to render, with both my Athlon FX60 cores being fully utilised (at 100%) on final settings in firefly.
The new "content management" can only be accessed if the library palette is undocked... (see the Content Collections tab on top)... You can add any files via right clicking them to the content collections - folders don't seem to work though. But the good news is that it's using regular Windows shortcuts (at least the Windows version ;-)) so one should be able to drop folder shortcuts in there, too, if you feel brave ;-) The multi threaded rendering doesn't seem to be working in a too effective fashion, it's dividing up the image into big blocks first and then rendering each block in a separate thread... So if you're using two threads and one of those threads finished with its part of the image, that thread will idle till the end - so if the top of the image renders in 1 minute and the bottom needs 1 hours you'll have one thread doing nothing for 59 minutes :-(
It seems to be awfully slow at a simple test render. I am really beginner level at this TBH.
I am talking minimalist stuff here, one figure and no props. One that I could do in P6 in about 30seconds seems to bog down and even freeze it.
I have backed off the auto Firefly render to draft quality, but it still seems awfully slow!
Must have some things checked as default that P6 doesn't I suppose?
Anybody else got an issue like this?
( For the record 2 Gig Athlon64 2 Gig memory and 128M GeForce Graphics. )
Klutz :0/
********************************************************************************************************************
Life is a beta.
In faecorum semper, solum profundum variat.
my first p7 render ,using my own contribution to the app ofcoarse...lol
now I jumped from p5 to p7,so my render skills may not be up to par to show any differences
plus I havent figured out how to get all the jaggies out with firefly yet :0(
Funny YouTube video of the week - Bu De Bu Ai
only regret is the collections directory - only being able to add one item at a time.
I like what I see so far here is a sample done on my AMD 3200+, 2.5 gig ram, 256 ATI graphics.
It's V4, std skin and P7 default HDR lights.
The supreme irony of life is that hardly anyone gets out of
it alive.
Robert A. Heinlein
11th Gen Intel(R) Core(TM) i9-11900K @ 3.50GHz 3.50 GHz
64.0 GB (63.9 GB usable)
Geforce RTX 3060 12 GB
Windows 11 Pro
Quote - only regret is the collections directory - only being able to add one item at a time.
I guess you wouldn't be too happy when you could add lots of items at once. For the fun of it I exported my Advanced Library setup to the content collections folder. Well... Poser needed minutes to start up. And will always give a "this operation will take several minutes. [cancel] [ok]" message, when changing library categories - well, ok will crash Poser. Cancel will then show that it's the drop down for the collections that takes too long to build. So keeping the collections folder tidy is a good idea if you like Poser starting up fast.
This site uses cookies to deliver the best experience. Our own cookies make user accounts and other features possible. Third-party cookies are used to display relevant ads and to analyze how Renderosity is used. By using our site, you acknowledge that you have read and understood our Terms of Service, including our Cookie Policy and our Privacy Policy.
Here are some 'out of the box' renders that I have managed.