27.17 Asset Library
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)
if there is any octane material in the .blend files which is put into the user asset library folder, when this asset is inserted into a new blender file, when turn to octane engine and click the render preview button, Blender will crash immediately
Supermicro 4028GR TR2|Intel xeon E5 2697 V3| windows 10| revit 2019 |Titan V+ Quadro GV100+RTX 2080 Ti
The issue is still there for the new version of 28.4,
when an object is octane material applied in blender octane edition, it can be opened if directly from blender and correctly rendered in octane.
but when it is put into an asset library in a drive path, then from the asset browser to be inserted into a new scene, when you turn on the view of octane render, blender will Crash.
when an object is octane material applied in blender octane edition, it can be opened if directly from blender and correctly rendered in octane.
but when it is put into an asset library in a drive path, then from the asset browser to be inserted into a new scene, when you turn on the view of octane render, blender will Crash.
Supermicro 4028GR TR2|Intel xeon E5 2697 V3| windows 10| revit 2019 |Titan V+ Quadro GV100+RTX 2080 Ti
I found another bug, I believe which is related or rather the reason of this one.
if we want to append an octane material from an existing blender file, if this existing material have an image map,
after the imported material applied in the new file, and turn on the octane's preview, the blender will crash.
In one word if we try to import an octane image, blender will crash...
here is a simplest sample: a cube with an octane material, if you want to import the material to a new blender file, crashing...
if we want to append an octane material from an existing blender file, if this existing material have an image map,
after the imported material applied in the new file, and turn on the octane's preview, the blender will crash.
In one word if we try to import an octane image, blender will crash...
here is a simplest sample: a cube with an octane material, if you want to import the material to a new blender file, crashing...
Supermicro 4028GR TR2|Intel xeon E5 2697 V3| windows 10| revit 2019 |Titan V+ Quadro GV100+RTX 2080 Ti
-
linograndiotoy
- Posts: 1354
- Joined: Thu Feb 01, 2018 7:10 pm
I'll test this in the new addon version currently in development.
unfortunately, the issue is still there in both most recently versions of 28.12 and 29.4.
though I found a possible solution for this issue, I guess.
I found if import the assets after the kernel is switched to octane, it will not crash,
it will crash when switch from other kernels to octane.
so if start a new project, we need to use the option of start an octane project instead of simply new a project to enable the asset lib.
I guess there is just "null pointer" issues in C++
btw, as a user of 7 years of octane render, I am really feel frustrated,
together with the geometry node issue(also still unresolved, for a year?),
We, your users, are just ignored
though I found a possible solution for this issue, I guess.
I found if import the assets after the kernel is switched to octane, it will not crash,
it will crash when switch from other kernels to octane.
so if start a new project, we need to use the option of start an octane project instead of simply new a project to enable the asset lib.
I guess there is just "null pointer" issues in C++
btw, as a user of 7 years of octane render, I am really feel frustrated,
together with the geometry node issue(also still unresolved, for a year?),
We, your users, are just ignored
Supermicro 4028GR TR2|Intel xeon E5 2697 V3| windows 10| revit 2019 |Titan V+ Quadro GV100+RTX 2080 Ti
-
linograndiotoy
- Posts: 1354
- Joined: Thu Feb 01, 2018 7:10 pm
I've tested your asset in the latest version and I can add the material to my scenes with no issues:
https://www.dropbox.com/scl/fi/9ybv9qh0 ... tqj57&dl=0
Can you please make a video or describe the exact steps to reproduce the problem? Thanks!
https://www.dropbox.com/scl/fi/9ybv9qh0 ... tqj57&dl=0
Can you please make a video or describe the exact steps to reproduce the problem? Thanks!
-
linograndiotoy
- Posts: 1354
- Joined: Thu Feb 01, 2018 7:10 pm
About the geometry node issue, can you please point me to the thread describing the problem? Thanks.
I found it. I'm going to paste the same answer here:
That's not a bug but an Octane limitation. Octane shading system can only deal with max 2 vertex color maps per object. Again, it's a limitation that should be solved in the engine, not a specific Blender issue.
I found it. I'm going to paste the same answer here:
That's not a bug but an Octane limitation. Octane shading system can only deal with max 2 vertex color maps per object. Again, it's a limitation that should be solved in the engine, not a specific Blender issue.