0 CPU resource when running c4d

[ooo]

I don't have a clue, so no postcard for me.

But I do experience the exact same behaviour on my new quad G5 (7800GT OSX 10.4.5 R. 9.5.2):

rendering start fast with four renderlines, and after 45 minutes 3/4 of the render is done and then the "CPU-worm" kicks in and slows things down at a exeptional slow rate. My render is now at 11,5 hours and still not done. Two renderlines are ready but will not start a new line, So now only two lines are continuing.

I have no clue!

odo

[Rantin Al]

I've noticed that the renderlines sometime grind over at a point with a complex reflection.
EG, a high chrome headlight trim.

In the Render Setting Options, Ray Depth defaults to 15. I think this is generally accepted as too high in heavily reflectives scenes. Try reducing down to 5 or 6.
Other than that I cannot suggest anything else.

I have a Quad, 6 GB, 10.4.5, GForce 6600 card and V9.5.2.
Cheers, Al.

[imashination]

Install the latest nvidia drivers for your graphics card, your old drivers have a bug in them which occurs in dualcore/cpu systems.

[Kuroyume0161]

Cupie doll for imashination!

Yes, I experienced this as well with the newer dualcore nVidia drivers. Note that the latest drivers, 81.98, do not completely resolve all dualcore issues - see the Release Notes PDF, page 15.

Robert

[ooo]

Does this also apply to the mac-version of the 7800 in my G5? I'm afraid nVidia only supplies PC-drivers.

yes I know, this is not my thread, but my problem seems to be the same as described by Spankissimo. I hope the new drivers will solve your problems Spankissimo!

Any other G5 Quad users with 7800 GT with similar problems?

odo

[Srek]

Never heard about the mac having similar problems.
The original problem was discussed here http://forums.cgsociety.org/showthread.php?t=296417
On max 7 the same problem made max crash, similar problems arose with other apps.
Cheers
Björn

[ooo]

Never heard about the mac having similar problems.
The original problem was discussed here http://forums.cgsociety.org/showthread.php?t=296417
On max 7 the same problem made max crash, similar problems arose with other apps.
Cheers
Björn

Ok thanks Srek,

i will check some stuff out when the render is done. I need to present it tomorrow so no time to stop it now. Damn, I bought this Quad to help me with my deadlines, but now things are only getting worse.

odo

[SpanKissimo]

Thanks mash for the info, i've installed the latest drivers 84.21, released on 17 march and they seem to fix the problem. I'll be needing a maling adress for the postcard, pm me please!

PS: good luck odo and this is officially your thread now...

[ooo]

PS: good luck odo and this is officially your thread now...

Thanks SpanKissimo!

Maybe I should also offer an postcard for the one that can fix my problem ;)

odo

Edit: 14.38 hours for this render and still not done. The last renderline is moving very very very sloooooow. Why are the other processors not helping?

I'm going to stop this render and go to bed now. I'll try to retouche the missing part in Photoshop. Only one millimeter render left but it can still take hours is my guess. NOT AMUSED!

[noseman]

Just curious odo, have you updated MacOSX to 10.4.5?

Oh and BTW, don't underestimate the power of RAM beeing "sensitive" on the quads.
If you have a general system instability, it could probably be RAM problems.

One other thing I found out is, if you have some problems with sw, make a new user with admin priviledges and try working from that user account. It could solve some corrupt - system preference - problems.

Hope this helps.

Do I get a postcard? :P

[ooo]

Hi Noseman and whoever is interested,

This mornig I gave the scene another try and now without SPD. I had some heavy use of SPD going on yesterday and now the scene rendered in 23 minutes instead of 14+ hours...

Ok SPD is off course to blame for a slow render, but is it normal that the render is slowing down over time? Like I told the finished renderlines didn't jump to unrendered parts like they should and only 1 line tried to finish the render at the end. And that after the parts of the scene with SPD where already rendered. So still questions left.

BTW I have 4 gb RAM and run 10.4.5 on R9.5.2

odo

[Srek]

Before a new renderline becomes visible the renderer needs to do some precalculations, with SPD for example it needs to subdivide the mesh before visual rendering starts. This can take some serious time depending on your settings.
Cheers
Björn

[ooo]

But does it explain why there is this slowing down of the render? Even after the SPD-parts were rendered it was getting slower and slower. The first renderlines had stopped many hours before the last two kept going. Could that be some kind of memoryleak?

[Srek]

A memory leak can't cause a slowdown. It will either hav eno influence or stop the rendering completely due to out of memory.
SPD was only an example here.

Cheers
Björn

[ooo]

So to conclude: this is ordinary behaviour on a SPD-rich scene rendered on a quad G5.
Because the only thing I changed this morning was disable SPD and then the render was ready in no time. I still cannot understand why the render was slowing down so much over time. But if I understand you well there is no need to fear a hardware problem. Only optimising the scene will help to get better renderbehaviour.

Ok, postcards for everyone!

odo

[CGTalk Moderation]

This thread has been automatically closed as it remained inactive for 12 months. If you wish to continue the discussion, please create a new thread in the appropriate forum.