WIP: MaterialX addon #104594
No reviewers
Labels
No Label
Interest
Animation & Rigging
Interest
Blender Cloud
Interest
Collada
Interest
Core
Interest
Documentation
Interest
Eevee & Viewport
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
Import and Export
Interest
Modeling
Interest
Modifiers
Interest
Nodes & Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds, Tests & Devices
Interest
Python API
Interest
Rendering & Cycles
Interest
Sculpt, Paint & Texture
Interest
Translations
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Meta
Good First Issue
Meta
Papercut
Module
Add-ons (BF-Blender)
Module
Add-ons (Community)
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
4 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender-addons#104594
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "BogdanNagirniak/blender-addons:materialx-addon"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Purpose
This PR continues implementation of https://archive.blender.org/developer/D16044
As part of Hydra Render engine we are providing MaterialX Blender addon.
Features
Notes
New addon is in TESTING status.
How it works
When addon starts, it generates python code with MaterialX nodes. Generated
*.py
files are lay in<user addons dir>/materialx_data/materialx_nodes
.Screenshots
List of new MaterialX nodes in Shader editor
Tools for Import/Export
.mtlx
file:Exported
.mtlx
to Shader editor:The design of this is different than we agreed on, so I'm confused about what the plan is here? Is this really meant as the implementation we ship with Blender?
I guess my main comment is on the mechanism of generating the .py files for materialx nodes. Why are they generated on the user side and not something done once.
@ -0,0 +1,93 @@
<?xml version="1.0"?>
Why are these node defs being included?
I've been attempting to try out this addon but have been running into errors registering the nodes:
ValueError: register_class(...): already registered as a subclass 'MxNode_STD_convert'
. Perhaps there's a mismatch between the materialx version I'm using and what this addon supports? What version are you testing it with?Sorry, this PR has to be closed. MaterialX is going to be supported natively by Blender. Here is PR blender/blender#111765 which converts Blender material nodes to MaterialX, which is going to be merged.
Pull request closed