When I assign a material from the octanedb in blender then the name is OctaneDB Material.001
The Name of the Material in the OctaneDB is not reflected in any way.
Is this correct functionality?
I think this is quite confusing it would be much clearer if the OctaneDB Material Name would be used.
Material Name OctaneDB Material Import
-
linograndiotoy
- Posts: 1342
- Joined: Thu Feb 01, 2018 7:10 pm
Duplicate.
Last edited by linograndiotoy on Wed Feb 12, 2025 8:54 am, edited 1 time in total.
-
linograndiotoy
- Posts: 1342
- Joined: Thu Feb 01, 2018 7:10 pm
I agree, the material import workflow should be improved.
Currently, when importing a DB material, a new material is created (named "OctaneDB Material") and replaces the currently selected material in the slot. This process is destructive, as it removes the existing material instead of modifying it.
Proposed Solution:
Instead of replacing the material, copy the shading network into the currently selected material without creating a new one.
Optionally, rename the material to match the imported DB material name, if technically feasible.
Expected Benefits:
Prevents unintentional material loss.
Improves workflow efficiency by allowing users to retain existing material slots.
Enhances consistency in material naming.
We'll work on it. Thanks.
Currently, when importing a DB material, a new material is created (named "OctaneDB Material") and replaces the currently selected material in the slot. This process is destructive, as it removes the existing material instead of modifying it.
Proposed Solution:
Instead of replacing the material, copy the shading network into the currently selected material without creating a new one.
Optionally, rename the material to match the imported DB material name, if technically feasible.
Expected Benefits:
Prevents unintentional material loss.
Improves workflow efficiency by allowing users to retain existing material slots.
Enhances consistency in material naming.
We'll work on it. Thanks.