OTOY Forums

Weirdpictures wrote:Hi Ahmet,
we did some test renders with the new build today and noticed that our renders always stopped after 40 - 70 frames, when we had a denoiser pass activated. If we turn off the denoiser pass everything rendered fine, no problem. The log showed the denoiser cuda error. Are we missing something? Do we need a new cuda version?
Otherwise the build is pretty amazing and works great for us.
Thanks for the hard work,
Martin

Yes, i confirm this problem.

Weirdpictures wrote:Hi Ahmet,

we did some test renders with the new build today and noticed that our renders always stopped after 40 - 70 frames, when we had a denoiser pass activated. If we turn off the denoiser pass everything rendered fine, no problem. The log showed the denoiser cuda error. Are we missing something? Do we need a new cuda version?

Otherwise the build is pretty amazing and works great for us.

Thanks for the hard work,

Martin

Capture.JPG

That's a bug in Octane and will be fixed in the next release. The underlying problem was that some resources didn't get released when a device gets disabled and then enabled again for denoising, which happens in some plugins after every frame. We are trying to release a new bug-fix version as soon as possible.

abstrax wrote:

Weirdpictures wrote:Hi Ahmet,

we did some test renders with the new build today and noticed that our renders always stopped after 40 - 70 frames, when we had a denoiser pass activated. If we turn off the denoiser pass everything rendered fine, no problem. The log showed the denoiser cuda error. Are we missing something? Do we need a new cuda version?

Otherwise the build is pretty amazing and works great for us.

Thanks for the hard work,

Martin

Capture.JPG

That's a bug in Octane and will be fixed in the next release. The underlying problem was that some resources didn't get released when a device gets disabled and then enabled again for denoising, which happens in some plugins after every frame. We are trying to release a new bug-fix version as soon as possible.

Ah ok, good to know. We are about to instal different cuda and graphics drivers in order to troubleshoot and see if that would help, but maybe we rather stay with the system that is going now, since it is quite stable besides the denoiser render bug.

Thanks for letting us know.

Best,

Martin

y81r wrote:in LV, when Look resolution is active, compare A/B slider not move.

c4d r19.068

Same here. Also: sometimes the transmission pass wont show the right transmition color while the beauty pass shows correctly.
Mostly the plugins looks amazing!

I understand from the release notes that the Default Environment Color has been moved from the general preferences settings to a scene specific preferences setting. It seems that TeamRender Clients are not picking this info from the scene, and defaulting to full white. We tend to use full black as our default, so this can cause some significant issues.

A workaround is to add a black RGBSpectrum OctaneSky to every scene, first, but that really shouldn't be necessary.

Is anyone else seeing this behavior?

Additionally, the TeamRender Clients seem to be having difficulty letting go of their Octane licenses, often causing a hang which requires a forced quit or sometimes an Unexpected Quit. Subsequently, the only way to release the license is to launch the full C4D app on the machine in question and then quit, or manually sign out of Octane. Launching and quitting TeamRender Client, even without any crash, does not release the license.

My testing machines, both the master and the RenderClient are C4D R19.068, OctaneRender 4 RC 5, C4D plugin RC5. Mac OS 10.12.6.

Thanks for any insight.

(edit) and I just had a couple of those TR Client Octane crashes. One took down the whole TR Client app, the other was on re-launching the app after the first crash and is explicitly a plugin crash. "The plugin c4dOctane_R19.dylib has crashed. More information can be found in..."

(edit Part Deux) ...and it looks like it's our old friend the Denoiser causing the crashing problem, specifically, Denoiser + TeamRender. An example scene will render fine without denoising in both full C4D and TeamRender. The same scene will render fine with denoising on, if rendered with the full C4D app. The same scene will crash with denoising on, if rendered with the TeamRender on the same machine that renders the other two, all other settings identical.

Hello,
running c4d R20 + octane render 4 RC5, can not get the metal material to work, it remains white. I have tried all the BRDF modes with no difference. Moving the IOR slides has no effect (Artistic, IOR+color, rgb IOR)
Works fine on c4d R19 with 3.0.8.

Am I the only one with this issue? Is it a known bug?

@JELLY

works fine here. did u increase the specular map value?

Best,
G

jelly wrote:Hello,
running c4d R20 + octane render 4 RC5, can not get the metal material to work, it remains white. I have tried all the BRDF modes with no difference. Moving the IOR slides has no effect (Artistic, IOR+color, rgb IOR)
Works fine on c4d R19 with 3.0.8.

Am I the only one with this issue? Is it a known bug?

You should give a value to specular map.

aoktar wrote:

jelly wrote:Hello,
running c4d R20 + octane render 4 RC5, can not get the metal material to work, it remains white. I have tried all the BRDF modes with no difference. Moving the IOR slides has no effect (Artistic, IOR+color, rgb IOR)
Works fine on c4d R19 with 3.0.8.

Am I the only one with this issue? Is it a known bug?

You should give a value to specular map.

Ahmet perhaps its a good idea to have the specular map at 1 as default?


Btw, really having a good experience so far with this version. well done!


Best,
G

Studio21 wrote: Ahmet perhaps its a good idea to have the specular map at 1 as default?

Not because it's not a metallic material by default. Specular_map will be 1.0 if you create by "create metallic material" command.