OTOY Forums

Hey everyone!

I've had problems with Octane crashing while saving out a frame in 3500x3500px (hasn't really happen to me when I was rendering 1080p).
Seems like the Render Layer Mask or the Denoiser was causing it, since it stopped once I turned the Layer Mask off and set only one out of four
cards to be used for denoising.

Scene only takes up around 850mb of VRAM, so I can hardly believe that I'm running out of ram here.

I'm on a workstation with 4 x 1080 8gb, 2 x Intel Xeon 4110 and 32gb ram. OS is Windows 10 Pro, build 17134.376


Since I'm working for a client, I can't really share the scene, unfortunately.

Thanks for your help, everyone!

frankmci wrote:

stefano-dear wrote:My slave computer on network render doesn't work any more:

OctaneRender 4.00 (4000021)

Launching net render slave (4000021) with master 10.39.12.184:1025
unpacked file image has unexpected type
didn't receive all required images from master
invalid message received from network connection
slave crashed or was stopped via CTRL-C
Started logging on 27.11.18 13:59:06

Any solution?

Thanks

MAC 10.12.6 + GTX 1080Ti - Driver NVIDIA 387.128
SLAVE Win 10 + 3x GTX 1080Ti + 2x GTX 980Ti - Driver NVIDIA 417.01
C4D R20.026

You might want to check to see if it's a command line renderer issue. I've found that Deadline isn't working because of an error that only gets thrown from the command line but not when rendering from C4D or from TeamRender. I've started a support ticked on the issue and will follow up in the forum if it gets resolved. There's a bit more on it in this thread:
viewtopic.php?f=30&t=60083&p=351759

Hi frankmci,

I have never worked via comandine and to be honest I do not even know what it is ...

Don't wanna make a dedicated thread for it, so I just ask here: Using blend materials instaed of Mix materials is such a pleasure but am I missing something, or is the "Assign" Tab missing? Losing the ability to see what object a blend material is assign to would be a oretty big bummer.

Just adding my warmest congratulations on R4 - it's a monumental piece of work.

I'm a small player in the Automotive Visualisation field, but Octane allows me to punch well above my weight - the new speed and AI denoising are really going to help us maintain and even increase our offering to clients. I can't see any other option for us, especially in terms of animation.

Also appreciate the sensible upgrade / subscription packages - I feel valued as a customer, which is something increasingly rare these days.

Wishing all of team OTOY continued success.

Funkdigit.

Ferdinand13 wrote:Hi,

I've been running into an issue a couple of times, where adding a HDRI image to a scene (using the Octane Sky) causes incredibly blown out areas on polygons facing the main light source of the HDRI. See the image below:

Desktop Screenshot 2018.11.26 - 14.46.53.39.jpg

Reducing the power of the HDRI has no effect. It goes from full white to black, once the power hits zero.

Any idea what causes this?

I've been digging into this 'overbright polygons situation' and found out that simply adding roughness to any material - while using Octane's HDR environment - makes this issue pop up. No roughness, no problem. Of course there is the problem that I NEED roughness

Ahmet, do you know, what could cause this? I'm really getting nervous, as I've got a deadline approaching and I'll need v4's denoiser to get it done on time. Cheers!

Ferdinand13 wrote:I've been digging into this 'overbright polygons situation' and found out that simply adding roughness to any material - while using Octane's HDR environment - makes this issue pop up. No roughness, no problem. Of course there is the problem that I NEED roughness

Ahmet, do you know, what could cause this? I'm really getting nervous, as I've got a deadline approaching and I'll need v4's denoiser to get it done on time. Cheers!

Hi

To me that looks like a colorspace issue. You have to use ImageTexture node with Gamma 1 there, don't just drag an image because that creates a C4D bitmap with default Gamma at 2.2 and no way to change it. To be sure that everything is setup correctly use the HDRI preset from LV and if it still happens then it's probably a core issue or a regression of a UI bug with Texture import type parameter (I guess). Could be even the map itself.

Cheers
Milan

Ferdinand13 wrote:

Ferdinand13 wrote: I've been digging into this 'overbright polygons situation' and found out that simply adding roughness to any material - while using Octane's HDR environment - makes this issue pop up. No roughness, no problem. Of course there is the problem that I NEED roughness

If its a bug with the roughness param, try using a very fine bump instead?

Ahmet, I'm seeing some unsettling behaviour with V4 and R20 - crashes that destabilise the machine (iMac 5k, + Titan X eGPU, OSX 10.12.6). It'll take the system down but in a weird way, not a flat out KP. Eg high-res still renders will reach the max samples but wont complete. It keeps rendering and never stops. If you stop the render manually Cinema hangs. A normal force quit seems to work BUT after you do apps will fail to launch: everything just bounces in the dock and you have to reboot. One time after force quitting Cinema's icon remained in the dock. its wasn't listed in top so I couldn't even find the PID to kill it. Again reboot required. It's very disturbing...

Also seeing a lot of general crashes/spinning beachball when doing routine iterative work with the LV active (crashes only happens when LV is running) and it requires a force quit (but those don't take down the system at least). Again this is all with R20.

I do not get this behaviour with R19 and V3.08. With the same scenes it renders fine.

milanm wrote:

Ferdinand13 wrote:I've been digging into this 'overbright polygons situation' and found out that simply adding roughness to any material - while using Octane's HDR environment - makes this issue pop up. No roughness, no problem. Of course there is the problem that I NEED roughness

Ahmet, do you know, what could cause this? I'm really getting nervous, as I've got a deadline approaching and I'll need v4's denoiser to get it done on time. Cheers!

Hi

To me that looks like a colorspace issue. You have to use ImageTexture node with Gamma 1 there, don't just drag an image because that creates a C4D bitmap with default Gamma at 2.2 and no way to change it. To be sure that everything is setup correctly use the HDRI preset from LV and if it still happens then it's probably a core issue or a regression of a UI bug with Texture import type parameter (I guess). Could be even the map itself.

Cheers
Milan

Hi Milan,

Thanks for the suggestion, but I'm quite sure that's not the issue. The texture is a Substance Shader, which renders absolutely fine when using Octane area lights - even super bright ones - or when using a white RGB environment. However, the second I switch from area lights to HDRI lighting (i.e. the Octane environment lighting) things go haywire.

I can reproduce this error on two vastly different machines. i'm surprised I'm the only one having this issue with v4. Could you check?

sdanaher wrote:

Ferdinand13 wrote:

Ferdinand13 wrote: I've been digging into this 'overbright polygons situation' and found out that simply adding roughness to any material - while using Octane's HDR environment - makes this issue pop up. No roughness, no problem. Of course there is the problem that I NEED roughness

If its a bug with the roughness param, try using a very fine bump instead?

Thanks for the suggested fix Sdanaher. But changing my workflow that way would become a real pain, especially since I'm using a Substance based workflow, so a working roughness channel is an absolute must. I mean, it should be working without problems. Can you reproduce this error?