[ababak]

Introducing the internal node-based architecture will allow future node support in compatible plugins. In the beginning the plugins should just silently translate the exisiting material setup to internal node-based format but as this evolves it will be possible to build material node chains in compatible applications (Maya, Blender, etc.).

The possibilities are endless — from reusing file texture nodes or color slots in different BSDFs to building complicated procedural textures or making an easy mix of different materials.

What do you think?

[Hervé]

I don't like Node based things... this is why I stopped using Realflow.. hehe

but don't worry about me, I am old.. so yes the future might be in that direction..

[ababak]

I don't like Node based things... this is why I stopped using Realflow.. hehe

but don't worry about me, I am old.. so yes the future might be in that direction..

The way it's done in Blender seems pretty though out. You have the basic control just using the property sheets, if you don't want to get under the hood.

If Maxwell's internal architecture would use nodes, the same could be done in all plugins. Current interface is preserved but plugins get the ability to translate native (under-the-hood) node graphs right into Maxwell's ones. Hope this makes sense.

[sirdan]

Would that fix the kind of crippled node workflow for the Max Slate Editor in the near future?

In general nodes are more suiteable for my way of working with complex hierarchies.

[seghier]

what i hate in octane and the new versions of 3dsmax is nodes
but i hope maxell have feature to mix different materials and create more complex procedurals textures ; so nodes in maxwell material editor will be good but not in studio

[jfrancis]

"Substances?"