Forum Coordinators: RedPhantom
Poser - OFFICIAL F.A.Q (Last Updated: 2025 Jan 11 12:18 am)
Why do you have ray tracing on? I don't see anything in the above pic that is reflective. Or did you turn it off for this render? Maybe use a reflection map on the car's outside instead. Ray tracing is very processor and memory-intensive. BTW, you might want to move your V3's hip down a little as she looks like she's levitating right now ;-)
"you are terrifying
and strange and beautiful
something not everyone knows how to love." - Warsan
Shire
Hi Thanks for your replys and I am studying my windows task manager to see what my set up is possible of coping with before it freezes the bucket Idea and the ray trace option seem sound ideas and I thank you for your input I shall continue to work on this draft till I can achieve a good finished result without to much post work By the way is 1 gig of ram enough for this type of work Regards Keith
1 gig should be fine. I have 1.5, I've never had any app use that much. It does allow me to use a smaller swap file and reclaim some disk space. You should probably enter a value for displacement if you are using it, if not you can uncheck it. Unless you are using raytraced shadows, reflections, or refractions, you can uncheck raytracing. Raytrace bounces should be kept to a minimum also. Yes, if you are doing alot of chrome and want perfect reflections, you could go higher. I usually stick with 2 to start. Keep the lights to a minimum, as well shadow map size. If you don't need a particular light to cast a shadow you can turn shadows off for that light. Removing backfacing could shave some time off. I haven't used texture filtering all that much, I guess if you aren't doing closeups, you could limit the map size and use the filtering to compensate for the smaller map. This would be nice if you had the option for each object, instead of the whole scene. As far as locking up, setting the bucket low should help the most, in my opinion. I go with a 32, for lots of raytracing, I go as low as 8. If you trim the fat, Firefly ain't too bad.
Hi Mark many thanks for your reply, you have given me lots to try out and I will be recording the details to see which is helping to make large images without loss of detail. I have just re-booted and have closed un-necessary apps running in the background and then in Poser Render options un-ticked Raytrace but left the others on with a Bucket of 16, A size of 2155X1616 pixel and a res of 200 and it flew throw with no problem so I think that I can now move on to artist content and style a much harder problem ;-) So thanks again for your help and I love you "Hope" image it is gorgeous Regards Keith
Also always check the size of the textures for each item. I once had a problem rendering a complicated image until I reduced the sizes of several textures. For example, one pair of shoe props used a leather texture that was 4000x4000! I saved the original and reduced it in photoshop to 1000x1000 which was more than enough for my purposes.
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.
Content Advisory! This message contains nudity
The file is about 180 Meg
The Render is set for production
Firefly on
Use displacement maps set at 0.00
Raytacing on
Cast shadows on
Smooth polygons on
Remove back facing off
Use texture filtering on
the Resolution is set to 200 dpi and the sise is 8"x8"
my PC is a 3 Gig P4 1 gig Ram 128 meg graphics card
it will render if I reduce it down in size but then it looks pixilated when you zoom in
I have succeeded before on oter images
Am I trying to do to much
Regards
Keith