fatbuckel opened this issue on May 21, 2010 · 11 posts
fatbuckel posted Fri, 21 May 2010 at 9:32 AM
I thought Id give it another go as I
ve recently updated alot of my drivers. Well.....no luck. Still it slugs after four renders. Its a XP Pro 64bit Intel Duo-Core with four gig ram and 1.5 terabite and Nvidia GeForce so if this program can
t run on this puter I don`t know.
hborre posted Fri, 21 May 2010 at 9:41 AM Online Now!
How complex are your scenes? Are you using depth map shadows? DM is notorious for draining memory because it is stored information. You need to clear that cache after every render.
fatbuckel posted Fri, 21 May 2010 at 9:51 AM
One figure,four lights,two props.
hborre posted Fri, 21 May 2010 at 10:02 AM Online Now!
Could you work with 2 lights? Better yet, what is the nature of your scene and could you post an image and settings? My version gets jibbery after several renders, so on test renders I go lite with minimum settings, reboot the app, then increase everything within reason and accordingly for a final render.
fatbuckel posted Fri, 21 May 2010 at 12:16 PM
My poser is on a island (computer without internet) so Ill have to get an image to show you. Still,I don
t think I should have to jump thru hoops to run this program. I run the new C4D on the same puter without issue. Its a shame
cuz Poser is much simpler to use for quicker projects(or projects that don`t pay alot!)
seachnasaigh posted Fri, 21 May 2010 at 12:22 PM
I've been rendering resource-heavy animated scene frames in PP2010 and haven't noticed any problem.
Poser 12, in feet.
OSes: Win7Prox64, Win7Ultx64
Silo Pro 2.5.6 64bit, Vue Infinite 2014.7, Genetica 4.0 Studio, UV Mapper Pro, UV Layout Pro, PhotoImpact X3, GIF Animator 5
fatbuckel posted Fri, 21 May 2010 at 2:17 PM
Im sure it works for you.But I
ve lurked around here enough to realize that Im not the only person to have these and other troubles. I
m thinking that there are known problems with this software and that those associated with development of this software task themselves with the job of smokescreenery. Generally speaking, Ive dealt with companies where a problem(s) exist and the first thing they do is blame everything else. If I press them, If I confront them with proof or with questions they can
t answer, they usually admit to "issues" they have with this or that functionality Im thinking thats where we are now. Round one was "update your drivers" bla,bla,bla. I
m not going to round two. I`ve got C4D. I was just hoping that someone may have heard of a fix or workaround or something that could make this program USEFUL. If I have to spent all this extra time dancing thru rings of fire just to get a satisfactory result, I,ll use what I already have. Eventually C4D will get easier for me as I learn more and more about it.
vilters posted Fri, 21 May 2010 at 5:18 PM
Just a quick answer here, as you do not give a lot of details.
In Poserpro2010, or better since poserPor2010, I only use ONE infinite light.
And BB"s free env Sfere.
Mostly I have to reduce the light as the sfere is kind of "all around", and self iluminating.
But ; more questions??
HOW do you render?
in process?
In a separate process?
How many treats?
Bucket size?
Background renders?
Using the quemanager?
Boy I have a lot of questions for this one..........
Poser 1, 2, 3, 4, 5, 7,
P8 and PPro2010, P9 and PP2012, P10 and PP2014 Game
Dev
"Do not drive
faster then your angel can fly"!
mackis3D posted Fri, 21 May 2010 at 5:20 PM
Cinema 4 D uses MUCH LESS textures than Poser, so your RAM usage will not be used as much as with Poser. But as you wrote only one figure etc. I don't think that's the problem. The rendering with Poser is much slower than with C4D. And C4D uses far less of your processor when rendering. I know because I know C4D a little too.
I don't know why you blast off recommendations as "update your drivers" because you did not even specify which Nvidia Geforce you have, neither did you specify the Intel Duo Core processor. But usually the problem lies not there I agree.
I would check the settings under Render>RenderSettings>Preview (Display Engine should be OpenGL, OffscreenHandling SceneWindow and don't enable HardwareShading).
Dizzi posted Sun, 23 May 2010 at 6:10 AM
Quote - I
m thinking that there are known problems with this software and that those associated with development of this software task themselves with the job of smokescreenery. Generally speaking, I
ve dealt with companies where a problem(s) exist and the first thing they do is blame everything else.
So, what did Smith Micro tell you was the problem on your side? Did you even contact Smith Micro? Or do you expect them to magically fix problems they don't know about?
fatbuckel posted Mon, 24 May 2010 at 1:53 PM
machis3D...thanx,Ill check those settings when I get home...Dizzi.... Smith Micro suggested I update my video card drivers when I contacted them. They also suggested pixie dust but I don
t believe in magic. Again,to those who offered help,thanks.To the others, thanks for proving my point.