Applying Materials to Nulls OK in Octane?
Moderators: ChrisHekman, aoktar
It is quite common in Cinema to apply a material to a parent null, and have that null send down the material to its children (unless they have their own materials assigned, of course.) However, I have noticed that this method doesn't work reliably in Octane, particularly with SubD objects. I can get around that, but I noticed in my most recent crash that Octane was complaining it could not get a null with the material. Is this considered bad practice in Octane?
CaseLabs Mercury S8 / ASUS Z10PE-D8 WS / Crucial 64GB 2133 DDR4 / 2 XEON E5-2687W v3 3.1 GHz / EVGA 1600 P2 / 2 EVGA RTX 2080Ti FTW3 Hybrid/ Cinema 4D
Is it fast? Oh, yeah!
Is it fast? Oh, yeah!
Yes. it counts until reach another materials overwrite on child objects. If you post a sample we can see. It's better to posting just some words.
Octane For Cinema 4D developer / 3d generalist
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
Thanks, Aoktar. What does this error mean?
Started logging on 31.08.15 10:31:10
OctaneRender 2.24 (2240000)
Scene created in plugin version 2232006
Tried to access null item
Tried to access null item
Started logging on 31.08.15 10:31:10
OctaneRender 2.24 (2240000)
Scene created in plugin version 2232006
Tried to access null item
Tried to access null item
CaseLabs Mercury S8 / ASUS Z10PE-D8 WS / Crucial 64GB 2133 DDR4 / 2 XEON E5-2687W v3 3.1 GHz / EVGA 1600 P2 / 2 EVGA RTX 2080Ti FTW3 Hybrid/ Cinema 4D
Is it fast? Oh, yeah!
Is it fast? Oh, yeah!
It show plugin is trying to set an undefined pin. But this is not a critical problem to give a Cuda error. You should find a line which contains "Cuda error......".jayroth wrote:Thanks, Aoktar. What does this error mean?
Started logging on 31.08.15 10:31:10
OctaneRender 2.24 (2240000)
Scene created in plugin version 2232006
Tried to access null item
Tried to access null item
Octane For Cinema 4D developer / 3d generalist
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
Thanks, Aoktar. As I said, this issue is causing Cinema to hang, and since Octane does not write out a log, when I restart Cinema, there is no information to recover
The only option I see to write out a log is if you can see the log in the log view. Is there an option somewhere to have Octane write out and amend the log to a text file on a frame by frame basis? That could really help to track down these errors. I am really dead in the water right now...

The only option I see to write out a log is if you can see the log in the log view. Is there an option somewhere to have Octane write out and amend the log to a text file on a frame by frame basis? That could really help to track down these errors. I am really dead in the water right now...
CaseLabs Mercury S8 / ASUS Z10PE-D8 WS / Crucial 64GB 2133 DDR4 / 2 XEON E5-2687W v3 3.1 GHz / EVGA 1600 P2 / 2 EVGA RTX 2080Ti FTW3 Hybrid/ Cinema 4D
Is it fast? Oh, yeah!
Is it fast? Oh, yeah!
You can but will not help to find i suppose. Best to watch vram and triangle counts in LV. Anyway copy this "octane_log_flags.txt" to Cinema4D.exe's place. And run and watch resulting "octane_log.txt".
- Attachments
-
- octane_log_flags.txt
- (62 Bytes) Downloaded 119 times
Octane For Cinema 4D developer / 3d generalist
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
Thanks, I will do that. Also, what does this mean:
Could not load 'C:\Users\<me>\Dropbox\Cinema 4D Files\<Project>\tex\263742_4d47604d5ca7c830d1fe368209719e62.png:rgba'.
I have no such texture that is in my scene, or that directory (I replaced the items in the <> as they are not relevant information here). Is this a texture that Octane created? Should I be concerned with this at all?
Could not load 'C:\Users\<me>\Dropbox\Cinema 4D Files\<Project>\tex\263742_4d47604d5ca7c830d1fe368209719e62.png:rgba'.
I have no such texture that is in my scene, or that directory (I replaced the items in the <> as they are not relevant information here). Is this a texture that Octane created? Should I be concerned with this at all?
CaseLabs Mercury S8 / ASUS Z10PE-D8 WS / Crucial 64GB 2133 DDR4 / 2 XEON E5-2687W v3 3.1 GHz / EVGA 1600 P2 / 2 EVGA RTX 2080Ti FTW3 Hybrid/ Cinema 4D
Is it fast? Oh, yeah!
Is it fast? Oh, yeah!