Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Option to run the addon in arbitrary Node Trees #166

Open
Labels
enhancementNew feature or request
@Dereuz24

Description

Hi there,

Thanks a lot for creating this tool, it's simply amazing. I've tried plenty of methods to backup and run my nodes but this is the most convenient so far, much more than Libraries in terms of ease of use

I was wondering if it would be possible to enable the addon in something like Malt?

https://github.com/bnpr/Malt

This is the render framework created by one of the guys that is working in the current NPR implementation at the Blender Foundation.

It is a fully open alternate rendering engine that allows you to do pretty much anything under the sun if you find time to implement it yourself. I'm not that technical but the node trees do get incredibly complex

Taking a look at the output of the scripts and given that these can be run on vanilla render, I was wondering if it would be possible to use this tool to collect the same information on node location, connected sockets and values?

Unfortunately there won't be a way to replace something like malt in a long time given the approach the NPR prototype is taking so working without a proper node library has become very cumbersome.

And if this approach works, could this be enabled in any node tree? Even if there's no official support it could help to have the addon offer the option and then the users would individually fix the small quirks that each of their requirements have

For example, one of the things I was told about Malt is that the nodes and connections can be restored but it seems that Malt Node maintains an internal ID for each node and that ID points to the real socket inputs for that Node, it does not store socket's value together with the node. Not sure why it is designed in that way, so you should be able to restore the ID, but can't restore the data referenced by that ID

I have no idea on how to get around something like that... but maybe you have a better idea on how to go about something like this and if it's even possible to achieve, because I imagine if the nodes are there and can be read a script can be created even if the addon or custom nodes are not known in advance

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Projects

    No projects

    Milestone

    No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

        AltStyle によって変換されたページ (->オリジナル) /