bitsquid/bitsquid-blender-tools
bitsquid/bitsquid-blender-tools
1
Fork 0
Code Issues 4 Pull requests Projects Releases Wiki Activity
Var Dump: 
dumpVar: only available in dev mode
Mailing List

Tracking issue to implement export functionality for material shader nodes #1

New issue
Open
opened 2021-04-04 21:14:06 +02:00 by lschwiderski · 2 comments
lschwiderski commented 2021-04-04 21:14:06 +02:00 (Migrated from gitlab.com)
Copy link

Bitsquid's Flow features similar functionality to Blender's shader nodes for complex material setups.
It would be nice to find a way to export Blender's system into data compatible that Bitsquid can compile.

Bitsquid's Flow features similar functionality to Blender's shader nodes for complex material setups. It would be nice to find a way to export Blender's system into data compatible that Bitsquid can compile.
lschwiderski commented 2021-04-04 21:20:49 +02:00 (Migrated from gitlab.com)
Copy link

The first step will likely be analyzing the materials from the Vermintide 2 SDK, as these represent the functionality behind the current (crude) template.
While it might be possible to just create some approximate translations (e.g. "if material has diffuse map, write to base color"), ideally, we would be able to replicate those base materials within Blender for everyone to import and build a pipeline that correctly exports those into the same .material file we manually create right now.

The first step will likely be analyzing the materials from the Vermintide 2 SDK, as these represent the functionality behind the current (crude) template. While it might be possible to just create some approximate translations (e.g. "if material has diffuse map, write to base color"), ideally, we would be able to replicate those base materials within Blender for everyone to import _and_ build a pipeline that correctly exports those into the same `.material` file we manually create right now.
lschwiderski commented 2021-04-04 21:24:45 +02:00 (Migrated from gitlab.com)
Copy link

changed title from Tracking issue to implement export functionality for material shder nodes to Tracking issue to implement export functionality for material sh{+a+}der nodes

changed title from **Tracking issue to implement export functionality for material shder nodes** to **Tracking issue to implement export functionality for material sh{+a+}der nodes**
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
master
feature/bsi
No results found.
Labels
Clear labels   
bug

   
docs

   
enhancement

   
feature

   
tracking
No labels
bug
docs
enhancement
feature
tracking
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: bitsquid/bitsquid-blender-tools#1
No description provided.
Delete branch "%!s()"

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?