See attachments.
https://dl.dropboxusercontent.com/u/276 ... blem.blend
V3 serious shading issues
Forum rules
Before posting a bug report, please check the following:
1. That the issue has not already been disclosed
2. That the issue is specific to this plugin, and not Octane in general (Try reproducing it in Standalone)
Bugs related to the Octane Engine itself should be posted into the Standalone Support sub-forum.
All bug reports should include the information below, along with a detailed description of the issue and steps to reproduce it.
A. Operating System, including version (i.e. Win 7, OSX 10.11.2, Ubuntu 14.04, etc.)
B. Graphics Card(s) model (i.e. GTX 580 - 3GB, TITAN, etc.)
C. RAM Capacity (i.e. 6 GB)
D. Nvidia driver version (i.e. 7.50, 7.5.22)
E. OctaneRender Standalone version, if installed (i.e. 2.24.2, 2.23, etc.)
F. OctaneRender plugin version (i.e. v2.25 - 2.21)
G. Host application version, including build number if available (i.e. 3ds Max 2016 Build 18.0)
Before posting a bug report, please check the following:
1. That the issue has not already been disclosed
2. That the issue is specific to this plugin, and not Octane in general (Try reproducing it in Standalone)
Bugs related to the Octane Engine itself should be posted into the Standalone Support sub-forum.
All bug reports should include the information below, along with a detailed description of the issue and steps to reproduce it.
A. Operating System, including version (i.e. Win 7, OSX 10.11.2, Ubuntu 14.04, etc.)
B. Graphics Card(s) model (i.e. GTX 580 - 3GB, TITAN, etc.)
C. RAM Capacity (i.e. 6 GB)
D. Nvidia driver version (i.e. 7.50, 7.5.22)
E. OctaneRender Standalone version, if installed (i.e. 2.24.2, 2.23, etc.)
F. OctaneRender plugin version (i.e. v2.25 - 2.21)
G. Host application version, including build number if available (i.e. 3ds Max 2016 Build 18.0)
And here is the exact same mesh exported as OBJ and rendered in Octane Standalone. Expected results achieved. So the issue here appears to be that Octane for Blender does not read the mesh normals. Hopefully this is a trivial thing to correct.
Hi adamnerva,
Looks like you have rounded corners turned on in the Octane plugin render you posted.
Jason
Looks like you have rounded corners turned on in the Octane plugin render you posted.
Jason
Linux Mint 21.3 x64 | Nvidia GTX 980 4GB (displays) RTX 2070 8GB| Intel I7 5820K 3.8 Ghz | 32Gb Memory | Nvidia Driver 535.171
OK, the problem is definately that Octane for Blender cannot read vertex normals. New test file attached. This is a beveled cube with custom vertex normals.
https://dl.dropboxusercontent.com/u/276 ... Norm.blend
I consider this a pretty big bug that kills my workflow. I hope it can be addressed.
https://dl.dropboxusercontent.com/u/276 ... Norm.blend
I consider this a pretty big bug that kills my workflow. I hope it can be addressed.
This is the same in V2.x
Maybe Octane does not properly interprets edge creases.
Anyway adding Egde Split modifier solves the issue.
Maybe Octane does not properly interprets edge creases.
Anyway adding Egde Split modifier solves the issue.
CPU – i9 13900KF, 128GB RAM, GPU – RTX 4090
System – Windows 11
My Behance portfolio, Blender plugin FB support group
System – Windows 11
My Behance portfolio, Blender plugin FB support group
Unfortunately, no, the edge split modifier does not solve the issue. Blender has support for custom vertex normals, which I make use of in my second example scene. The vertex normals are face area weighted. The edge split modifier cannot fix this, nor can it fix imported CAD models with very precise vertex normals.J.C wrote:This is the same in V2.x
Maybe Octane does not properly interprets edge creases.
Anyway adding Egde Split modifier solves the issue.
Blender supports vertex normals. Octane standalone supports vertex normals. And Octane for Modo supports vertex normals. It was actually a huge surprise to me that Octane for Blender doesn't even have this very basic feature.