OctaneRender™ 2019.1 Tweet

[Elvissuperstar007]

you have the wrong Motion vector

[BCres]

Yeah, sadly I'm seeing the network rendering issue as well. Goes away once I stop the remote machine.

Here's a pic:

Octane 2019.1 network rendering.JPG

I did want to say, however, how great the work of the developers has been on this release, including Ahmet for the wonderful C4D plugin. The improvements to the denoiser (which was already great), along with the new upscaler AI, the flawless commandline rendering, not to mention the look, keep this my favorite render engine.

Thank you, Otoy developers.

[coilbook]

Otoy, can you do an emergency patch release for just network rendering bug? This is a commercial release and it is not working. We cannot got back to 2018.1 because of textures. We are stuck with no way to render at this point. Please help

[Raoul]

Otoy, can you do an emergency patch release for just network rendering bug? This is a commercial release and it is not working. We cannot got back to 2018.1 because of textures. We are stuck with no way to render at this point. Please help

I just wanted to second this request. Network render absolutely crucial for us to continue work. It was working fine on the previous ( non stable) release of 2019 but we've been locked out of that version for some strange reason. ( Mac/C4D)

Could you please prioritise getting the network bug fixed asap or at least let us back into the last version of 2019 with working network render. Could you also give us a rough ETA of how long these fixes will take?

Thanks for the hard work.

[natemac00]

Bikram (OTOY, Inc.)
Sep 24, 23:12 UTC

Hi Nate,

Thank you so much for your email and reporting this issue on our forums page.

Our senior Core team is aware of this issue and they are already looking into it.
In the meantime, would you please revert into stable 2018?

Thank you for your patience.

Kind Regards

Bikram
Octane Support

[funk]

BUG: Glossy material with specular set to 0 creates incorrect sheen

1. Load the attached ocs and render the material
NOTE: Sheen is incorrect
2. Change specular to 0.001
NOTE: Sheen is now correct

glossy_spec_0_bad_sheen.png

[haze]

Apologies for the network rendering problems. We identified a significant defect and have been working for several days already to fix it as soon as possible. I will come back to you in a few hours with an ETA.

[funk]

BUG: Dielectric 1/IOR Map doesnt work if albedo is not black

1. Load the ocs
2. render the material
3. move dielectric 1/ior map... nothing happens
4. make albedo black (0,0,0)
5. move dielectric 1/ior map... now it works

It seems the "dielectric IOR" value is being used if albedo isnt black. Dielectric 1/IOR map (when connected) should always override the dielectric IOR value.

EDIT: This works in 2018.1, but got broken in 2019.1

dielectric_ior_broken_with_non_black_albedo.png

[wallace]

BUG: Glossy material with specular set to 0 creates incorrect sheen

BUG: Dielectric 1/IOR Map doesnt work if albedo is not black

I have fixed them both, and the fix will be in the next revision.

[funk]

Thanks Wallace