OTOY Forums

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:
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?

sdanaher wrote:I have an activation error.

I've updated my licenses to v4 online. Installed v4 and launched R20 but get "render thread failed: Octane is not activated". The Activate button in Octane Settings does nothing.

I tried installing V4 standalone and that works fine. Any ideas Ahmet?

I'm having this issue as well, did you get a solution?

UPDATE: Just figured it out for me, there was an additinal R20 file in the plugin folder "c4doctane-r20-demo.xlib" that you need to remove as well.

Do you have more information on the Substance integration?

"Native Substance PBR Texture Integration: OctaneRender 4 now provides Substance PBR texture integration in DCC tools such as C4D"

Hi natemac00,

Check out the step by step guide I put online yesterday:

viewtopic.php?f=30&t=69712&p=351437#p351437

I think that's what's in the bag for now.

Hi aoktar,

Can you send the new HELP MANUAL about PDF to me?

I want to watch the help to study.

Thanks for your help.

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?

Just bumping this one again. Would be great, if someone has an idea what could cause/fix this. Thanks a lot!

natemac00 wrote:

sdanaher wrote:I have an activation error.

I've updated my licenses to v4 online. Installed v4 and launched R20 but get "render thread failed: Octane is not activated". The Activate button in Octane Settings does nothing.

I tried installing V4 standalone and that works fine. Any ideas Ahmet?

I'm having this issue as well, did you get a solution?

UPDATE: Just figured it out for me, there was an additinal R20 file in the plugin folder "c4doctane-r20-demo.xlib" that you need to remove as well.

Yes, you're right. It's a new file that caught me out till I checked the folder again.

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

hey guys, everything seems to be working fine but motion blur. I had a scene with VERY little camera movement that when camera motion blur was active, the camera was REALLY far away and the next frames were all blurry as shit. turning cam motion blur off fixed it for one frame but then it went crazy again. motion blur completely off is the only thing that fixed it

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