Before I post in the bug reports forum I have a dim recollection of it being a current issue with octane rather than the plugin but I can't find the info anywhere.
Rendering textures with network nodes produces incorrect colours, half the image is a slightly different tone or sometimes a completely different colour. Seems mostly to occur when using a texture into 2nd node such as Multiply, Colour Correct, Mix etc.
currently using R19.053, OSX 10.11.6, octane 3.08-Test6.1, the network nodes are running on Windows.
Wrong colour when network rendering
Moderators: ChrisHekman, aoktar
Windows 10 - 64GB RAM - Cinema 4D R20 - RTX 2070 x3
Hi sdanaher,
check if the Minimize net traffic option is enabled in the Kernel panel, and if yes, try with the option disabled.
ciao beppe
check if the Minimize net traffic option is enabled in the Kernel panel, and if yes, try with the option disabled.
ciao beppe
thanks beppe I will give that a try (its currently on).
Windows 10 - 64GB RAM - Cinema 4D R20 - RTX 2070 x3
Hmm, something odd is going on. While unchecking 'Minimise net traffic' made sure the entire frame is rendered the same, its not actually rendering the correct colour. The first pass is correct then when it next updates the colour changes. In my test scene for example it removes the effect of a Multiply node acting on a texture and an RGB spectrum node. It renders the normal texture colour instead.
Windows 10 - 64GB RAM - Cinema 4D R20 - RTX 2070 x3
Hi sdanaher.
yes, confirmed, there is definitely an issue with net render in v3.08t6 SDK, and mapping nodes.
We need to wait for a new 3.08 SDK.
ciao beppe
yes, confirmed, there is definitely an issue with net render in v3.08t6 SDK, and mapping nodes.
We need to wait for a new 3.08 SDK.
ciao beppe
OK, thanks. 3.08 looks like a great update though, very impressed. Back down to 3.07 for the time being for me though.
Windows 10 - 64GB RAM - Cinema 4D R20 - RTX 2070 x3
-
northalex78
- Posts: 56
- Joined: Tue Nov 30, 2021 12:33 pm
I am getting this same issue in 2026.3 (1.9.3), Mac M4 Max master and PC slave with 2x 4090s.
Was there ever a definitive solve for this, as "minimize net traffic" doesn't seem to help in my case.
Was there ever a definitive solve for this, as "minimize net traffic" doesn't seem to help in my case.
Hi,
This issue was related to a very old version of OctaneRender.
Could you share more info on the issue you are having, maybe with some screenshots?
ciao,
Beppe
This issue was related to a very old version of OctaneRender.
Could you share more info on the issue you are having, maybe with some screenshots?
ciao,
Beppe
-
northalex78
- Posts: 56
- Joined: Tue Nov 30, 2021 12:33 pm
I have filed a ticked but I've not had a response yet, and we're coming up to 24hrs so I assume some time zone must have seen it.
I can't find much about this error online, the particular combination of keywords is not making search easy. "render, network, patches" turns up a lot of wrong results.
Ticket contains output of nvidia-smi and output from the node. All versions (Mac, PC, Slave) are current 2026.3. So unless it's nvidia driver, I am not sure why the patches are so bad.
Moving over solely to PC, the image comes out fine. Rendering solely on Mac, fine (but very slow). Neither of those is really a practical option in a Mac-based studio. We need network rendering working invisibly and seamlessly.
Thanks
I can't find much about this error online, the particular combination of keywords is not making search easy. "render, network, patches" turns up a lot of wrong results.
Ticket contains output of nvidia-smi and output from the node. All versions (Mac, PC, Slave) are current 2026.3. So unless it's nvidia driver, I am not sure why the patches are so bad.
Moving over solely to PC, the image comes out fine. Rendering solely on Mac, fine (but very slow). Neither of those is really a practical option in a Mac-based studio. We need network rendering working invisibly and seamlessly.
Thanks
Ok, I'm going to answer you to the ticket during my day.
ciao,
Beppe
ciao,
Beppe