OTOY Forums

Just updated both C4D and Octane and the node list on the left side disappears when I drag around or click something in the node editor.
Any Idea what could be the cause for that?

R26.107 + 2021.1.5-(R4), Studio Driver 472.84.
Win 10 21H2


Edit:
Nvm, it was a "Auto Hide Menu" thing that was on by default in the Node Editor Settings.

zomtech wrote:Just updated both C4D and Octane and the node list on the left side disappears when I drag around or click something in the node editor.
Any Idea what could be the cause for that?

R26.107 + 2021.1.5-(R4), Studio Driver 472.84.
Win 10 21H2


Edit:
Nvm, it was a "Auto Hide Menu" thing that was on by default in the Node Editor Settings.

Yes your "auto hide" option.

lightborne wrote:I am having an issue with the Scatter object after upgrading from 2021.1.4-(R4) to 2021.1.5-(R4)

I have a .abc animation inside an Octane Scatter object but the render looks very different. Cinema 4D R26.0.14

I saw in the release notes "Fix: orientation problems with scatter object" What exactly was the fix and how can I fix this issue? Thank you!!!

Adobe_After_Effects_2022_-_Untitled_Project.aep__768.jpg

It was a change to calculate the scatter object's matrix from the hierarchy. Check the PSR of the related object group

Hello!
After migration to c4d r26, getting following bugreport while working with some scenes with active live viewer just in a minutes after start. (2021.1.5-R3 and 2021.1.5-R4 tested)
Works again for a minutes after restarting cinema4d.
What could be wrong?
Have never been used FumeFX on my machine.
Thank you.

Started logging on 03.07.22 01:00:00

OctaneRender Enterprise 2021.1.5 (11000500)

VRAM used/free/max:0Kb/11Gb/11Gb Out-of-core used:0Kb RAM used:9.844Gb total:31.94Gb OpenGL free/total:0/0
FumeFx library initialisation error!
--------------------------- EXPORT LOG ---------------------------
Export materials time= 6.803 ms
Collect objects time= 13.209 ms
Mesh creation time = 57.748 ms.
Api update time: 12.043 ms.
VRAM used/free/max:631Mb/7.993Gb/11Gb Out-of-core used:0Kb RAM used:10.576Gb total:31.94Gb OpenGL free/total:0/0
CUDA error 700 on device 0: an illegal memory access was encountered
-> failed to wait for event
device 0: path tracing kernel failed
MB:0/0 ST/MOV:0/193 Nodes:408 Tris:268k DispTris:0 Hairs:0 Meshes:210
Textures Grey8/16:0/0 Rgb32/64:0/0
CUDA error 700 on device 1: an illegal memory access was encountered
-> failed to copy memory to device.
device 1: failed to upload samples

Octane is freeze for some seconds if texture mix slider is moving to 1. It works fine until we not move it to 1.
It is caused by Invert node between texture and specular input.

EDIT : Something is really bad with this build because connecting new texture or OSL nodes to Material Inputs and disabling/enabling texture nodes if there is other node between them like mix, multiply etc. takes many seconds too !

EDIT2 : this is caused by the new NVIDIA studio driver 516.59. Returning to 512.96 at everything works fine. It seems that Octane Core needs to be updated or driver is buggy. There is big CPU lag while reconecting texture/OSL nodes.


---

Is there chance to add "external" in OSL Projection node like it is in regular OSL Texture node ? Since custom OSL directiories doesn't work.

SSmolak wrote:Octane is freeze for some seconds if texture mix slider is moving to 1. It works fine until we not move it to 1.

mix_freeze.jpg

It is caused by Invert node between texture and specular input.

EDIT : Something is really bad with this build because connecting new texture or OSL nodes to Material Inputs and disabling/enabling texture nodes if there is other node between them like mix, multiply etc. takes many seconds too !

EDIT2 : this is caused by the new NVIDIA studio driver 516.59. Returning to 512.96 at everything works fine. It seems that Octane Core needs to be updated or driver is buggy. There is big CPU lag while reconecting texture/OSL nodes.


---

Is there chance to add "external" in OSL Projection node like it is in regular OSL Texture node ? Since custom OSL directiories doesn't work.

There's not any differences since latest builds and this build to cause this. Compare it with a video! Which version is good for you show me? Also I'll be away for a while for vacation. I may not help much in this period.

aoktar wrote:
There's not any differences since latest builds and this build to cause this. Compare it with a video! Which version is good for you show me? Also I'll be away for a while for vacation. I may not help much in this period.

Yes, as I said in edited post this is caused by the new Nvidia Studio driver - Octane works fine using old 512.96 driver version. I reported it here : viewtopic.php?f=12&t=80056

This is cool and all - but I'musing the 2022 plugin - surely if you did this work on that - why do 2 alongside each other???!

I believe the Distorted Mesh UV projection has been broken since R3.

I open the same file with R2 and the material works

protokol wrote:I believe the Distorted Mesh UV projection has been broken since R3.

I open the same file with R2 and the material works

It looks like working. Can you send a sample to show what's not working for your opinion?