OctaneRender™ 2019.1.3

[vijay]

As far as my tests it works well

It seems to only work correctly for "Mesh UV" projection (which you are using). My example is using an "XYZ to UVW" projection.

I just tried changing yours to "box" projection and see similar problems. It almost looks like incorrect vertex normals are being created?

Auto bump currently works only if the mesh is UV mapped. I'm fixing it now. Sorry.

[funk]

Auto bump currently works only if the mesh is UV mapped. I'm fixing it now. Sorry.

Thanks Vijay

[funk]

Crash using vertex displacement mixer

1. Load the orbx
2. Right click the diffuse material > render

Octane crashes to the desktop

[linograndiotoy]

Using a normal or a bump map with the Toon Material doesn't work properly anymore (no bump or normal effect shows up). I think it never worked in 2019.x.

CelBump.JPG

It works fine in 2018.

CelBump_02.JPG

Toon_Normal_Bump_issue.orbx

Thanks!

[wallace]

Using a normal or a bump map with the Toon Material doesn't work properly anymore (no bump or normal effect shows up). I think it never worked in 2019.x.

Thanks!

Thanks for the report, this will be fixed in the next revision.

[funk]

I'm seeing some artifacts in this specular material, which don't happen in 2018.1.3

bad_glass.png

[linograndiotoy]

I'm seeing some artifacts in this specular material, which don't happen in 2018.1.3

bad_glass.png

Hi! It looks like a value of 1.0001 is triggering the issue. It's ok as the value is >= 1.00049.

[funk]

I'm seeing some artifacts in this specular material, which don't happen in 2018.1.3

bad_glass.png

Hi! It looks like a value of 1.0001 is triggering the issue. It's ok as the value is >= 1.00049.

Yes its only happening on smaller values. The modo plugin seems to be generating these values for its "on the fly" conversions in some cases.

Anyway, since its working correctly in 2018, it should be fixed in 2019.

[BCres]

Is there a CPU "old generation: limitation on this release? Here is my situation.

My main system with a 2080ti and new core i7 works great. Also, working with it is my slave machine with a 1080ti and 980ti. Everything works fine. The older system cpu is a Q9450 Core 2 quad. But it works great as a slave system.

But if I take an orbx file to the slave (and I am taking a small one). Start my second license of Octane standalone on it. The program starts up fine, loads the file, but as soon as I try to render the scene, the program just disappears to the desktop. No errors or anything.

So why can't the second machine handle the simplest little orbx files? Everything about the prefernces shows it's ready and using both GPUS.

Again, this slave works fine as a support to the main when I'm working. I just can't use the standalone version on it.

[wallace]

I'm seeing some artifacts in this specular material, which don't happen in 2018.1.3

bad_glass.png

Hi! It looks like a value of 1.0001 is triggering the issue. It's ok as the value is >= 1.00049.

Yes its only happening on smaller values. The modo plugin seems to be generating these values for its "on the fly" conversions in some cases.

Anyway, since its working correctly in 2018, it should be fixed in 2019.

No worries, I'll fix this for the next release.