Page 4 of 6

Re: Version 3.03.4-R2 (17.09.2016) - TEST

Posted: Sun Sep 18, 2016 5:34 pm
by aoktar
unsergio,
is it R1 or R2? There is a C4D bug when alpha enabled for materials. So i try to workaround by a way. So this can be about this problems. I don't want to cancel alpha/opacity for materials. But i may have to do if i couldn't avoid this.

Re: Version 3.03.4-R2 (17.09.2016) - TEST

Posted: Sun Sep 18, 2016 6:58 pm
by unsergio
It's R2

Re: Version 3.03.4-R3 (19.09.2016) - TEST

Posted: Mon Sep 19, 2016 9:46 pm
by aoktar
I've uploaded a new build with some improvements about gpu usage/temperature display and some alghoritm to avoid the overtheating of gpus in animation renders. These are some images to show that.
a1.jpg
a2.jpg
a3.jpg

Re: Version 3.03.4-R3 (19.09.2016) - TEST

Posted: Tue Sep 20, 2016 10:39 am
by NVN
aoktar wrote:I've uploaded a new build with some improvements about gpu usage/temperature display and some alghoritm to avoid the overtheating of gpus in animation renders. These are some images to show that.
a1.jpg
a2.jpg
a3.jpg
nice!

Re: Version 3.03.4-R3 (19.09.2016) - TEST

Posted: Tue Sep 20, 2016 4:07 pm
by Ron
Great! Thanks for re-arrangement of slave info in PV! Appreciate that very much.

Question to device order test: in my case it seems to kill C4D - it's running endless with spinning wheel. How long should the test run if you have 4 Gpus?

Cheers

Ron

Re: Version 3.03.4-R3 (19.09.2016) - TEST

Posted: Tue Sep 20, 2016 4:16 pm
by aoktar
Ron wrote:Great! Thanks for re-arrangement of slave info in PV! Appreciate that very much.

Question to device order test: in my case it seems to kill C4D - it's running endless with spinning wheel. How long should the test run if you have 4 Gpus?

Cheers

Ron
not more than one minute. But try to render a scene in LV at maxsamples high to be sure that will not stop before test. And try again to run test.
What's your C4D version and OS?

Re: Version 3.03.4-R3 (19.09.2016) - TEST

Posted: Tue Sep 20, 2016 4:36 pm
by Ron
aoktar wrote:
Ron wrote:Great! Thanks for re-arrangement of slave info in PV! Appreciate that very much.

Question to device order test: in my case it seems to kill C4D - it's running endless with spinning wheel. How long should the test run if you have 4 Gpus?

Cheers

Ron
not more than one minute. But try to render a scene in LV at maxsamples high to be sure that will not stop before test. And try again to run test.
What's your C4D version and OS?
I did run a scene that renders > 5 min. Will try again.
C4D version R18.020
OS: Win 10 64bit

Note: the GPU temp and activity is shown on LV and PV after restarting C4D

Re: Version 3.03.4-R3 (19.09.2016) - TEST

Posted: Mon Sep 26, 2016 11:49 pm
by Weirdpictures
Hey Ahmet,

great new version - just a quick thing and that might be absolutely intended, but when rendering with the new version we now get most of the time only 3 of our 4 GPU's to show up in the render stats bar while rendering final image. The 4th GPU is only showing as a non moving line in the picture viewer. Once i go and activate any background app like GPU z to measure the GPU load and temp it shows that GPU with 0% load as well. I do have to say, that it might be also a problem of my render temps, since they are always hovering around 88 C, even though if i check the GPU that is not running in GPU -Z it shows the temp of that GPU as only 64 C.

Any way around this and getting all 4 GPU's to render again like before?

Thanks Ahmet, awesome work as always :-)

Re: Version 3.03.4-R3 (19.09.2016) - TEST

Posted: Tue Sep 27, 2016 10:00 am
by sdanaher
Some of these new features are great (zoom window, A/B).

Would it be possible to have the zoom window re-render 1:1 at the higher resolution (perhaps as an option)? For high-res print work it would be absolutely amazing to quickly inspect sections at a higher res.

Re: Version 3.03.4-R3 (19.09.2016) - TEST

Posted: Tue Sep 27, 2016 7:39 pm
by miohn
Hi Ahmet,

working with latest R3 and latest nvidia driver 72.90 and still have the
problem with transparent/unvisible objects in the main 3D-view.

Do you think there will be a fix for that soon or do you recommend to
go back to a previous version?
Or is there another workarround for that problem?

thanks
Mike