OTOY Forums

I get this message in the log and dont know what it means:

Started logging on 08/16/18 19:01:21

OctaneRender 4.00 RC1 (4000011)

Tried to access pin via an invalid index 7
Tried to access null node pin
Tried to access pin via an invalid index 7
Tried to access null node pin
Can not connect node 'Material out' (NT_OUT_MATERIAL, 000002B2783944D0) to static pin 'unknown' (P_UNKNOWN, type PT_UNKNOWN) of node '' (NT_UNKNOWN, 00007FF888C319E0)

Win10, 2x 1080ti, c4d r19 studio

y81r wrote:I get this message in the log and dont know what it means:

Started logging on 08/16/18 19:01:21

OctaneRender 4.00 RC1 (4000011)

Tried to access pin via an invalid index 7
Tried to access null node pin
Tried to access pin via an invalid index 7
Tried to access null node pin
Can not connect node 'Material out' (NT_OUT_MATERIAL, 000002B2783944D0) to static pin 'unknown' (P_UNKNOWN, type PT_UNKNOWN) of node '' (NT_UNKNOWN, 00007FF888C319E0)

Win10, 2x 1080ti, c4d r19 studio

It's not having effect for giving any problems. Just It's trying to access something is not valid. Do you have any problems on rendering?

Very often I get the message: render failure

This usually happens when I try to create a new material

Then i get this in the Log:


Started logging on 16.08.18 23:01:17

OctaneRender 4.00 RC1 (4000011)

Tried to access pin via an invalid index 7
Tried to access null node pin
Tried to access pin via an invalid index 7
Tried to access null node pin
Can't connect node 'Material out' (NT_OUT_MATERIAL, 00000182F20DB6B0) to static pin 'unknown' (P_UNKNOWN, type PT_UNKNOWN) of node '' (NT_UNKNOWN, 00007FF8B94B19E0)
CUDA error 700 on device 1: an illegal memory access was encountered
-> kernel execution failed(kernel25)
CUDA error 700 on device 1: an illegal memory access was encountered
-> failed to launch kernel(kernel34)
device 1: path tracing kernel failed
CUDA error 700 on device 1: an illegal memory access was encountered
-> failed to unload module
CUDA error 700 on device 1: an illegal memory access was encountered
-> failed to create link
device 1: failed to create OSL compile context:

device 1: failed to compile module 1
CUDA error 700 on device 0: an illegal memory access was encountered
-> failed to launch kernel(kernel26)
device 0: path tracing kernel failed


At first render freez and LV look like this:
download/file.php?mode=view&id=69392

After resend LV shows this:
download/file.php?mode=view&id=69393

aoktar wrote:

Weezer wrote:For me, Octane/C4D has never been stable on MacOS. Ever.

V3? V4?

And which renderer stable for you? You may have some chronic issues on your setup. I'd be happy to check your system by remote connection. Even though that It's not my work part.

Hi, thanks Ahmet. I'd really like to get it sorted – I'm sure other Mac users are having similar issues. I'm on a mid-2010 Mac Pro with a GTX980Ti. Everything else about the system runs fine. I get very few crashes form other apps. I've had issues with both v3.x and 4.x – the latest build of 4.0 crashes instantly so I can't really test that.

I can spend some time with 3.08.3 and get some crash logs and find situations that cause instability. Only today it cashed and took my whole system down (but I did have Hearthstone running, so I was probably stressing the GPU to much!). Let me see how this version behaves.

I am looking through the patch notes, so I apologize in advance if I missed it, but is Light Linking in this build?

I can't seem to find any settings through C4D, Octane, or Octane tags.

Thanks for the update though! I am running tests with the AI Lights and the Denoiser, everything is working great so far!

-Inky

aoktar wrote:

Inky wrote:I am looking through the patch notes, so I apologize in advance if I missed it, but is Light Linking in this build?

I can't seem to find any settings through C4D, Octane, or Octane tags.

Thanks for the update though! I am running tests with the AI Lights and the Denoiser, everything is working great so far!

-Inky

Thank you! That was my bad, it wasn't totally straightforward. This is great! Very much appreciate this feature!

Hi all.

Thank you very much for reporting bugs and crashes. We are trying to release RC2 today with a bunch of bug fixes that should hopefully help with stability. The crash/issues we have identified so far are:

- Fixed in RC2: Denoising fails if used on a CPU without AVX instructions. On OSX this causes Octane to not even start even if you re not using the denoiser.
- Fixed in RC2: Geometry updates fail in scenes without instances.
- Fixed in RC2: Networking rendering crashes if no AI lights are being used.
- Currently working on: The denoiser fails at specific resolutions.
- In the C4D plugin, the scene update can hang sometimes. We fixed a few bugs in that area before RC1 got released, but haven't been able to reproduce this problem with RC1 anymore. If you still experience hangs during the scene update, please send us a scene plus instructions how to reproduce the hang.

There have been a bunch of other bug fixes during the last couple of days and we hope to get to a stable version 4 in the next few weeks. Well, as soon as possible. For version 4 we are currently focusing on stability. We are also working on render performance and hope to get those changes finished next week, but after that it will only be bug-fixing until we reach a stable version.

XB1 was released in March, why does it take so long to stabilize version 4? Well, that's how long it usually takes to really finish something and that's usually hidden, but was more visible this time since we released a very early preview with XB1 which was nowhere finished yet.

Thank you all for your patience.

Hi!
RC version crashes if denoiser is enabled. Crash always occur when denoising starts.
Testscene with nothing but a cube and denoise enabled - attached debug log.
Win10 C4D R19 GTX 1080ti driver ver: 388.19

Hey,

unfortunately Cinema4d crashes on startup for me as well with v4.0-RC1.1

V4 XB3-r1 and 3.08 versions are working quite well.

Thats my computer setup:
Windows 10 Pro Version 1803
i7 7820X CPU
3x1080 ti GPUs (Nvidia driver 398.82)
128GB Ram
Octane C4D Plugin v4.0-RC1.1
Cinema 4D R19 R19.068 (Build RB245443)
see Bugreport file attached.

On a side-note I got the feeling that since my last c4d R19 update everything is a little more unstable - like perfectly working scenes before the cinema4d update are crashing pretty fast randomly and indepent from octane. gotta investigate that further...

Let me know if you want to know anything else!


v4.0-RC1.0 (thats what it reads in the LiveViewer Window) is working on another machine of mine running Cinema4d R18.057 as expected, but I had little time to test so far.

Cheers and many thanks in advance!
michi