It is not something designed to replace the current plugin shading workflow using the LW Octane nodes, to build new materials or to use the LocalDB as storage space for your presets.
Those bold parts I may not understand correctly, can you please confirm these below or explain more if I have misunderstood any of them?
-as it is possible to edit the Octane materials in Octane node tree inside LW, why cannot I build new materials as well? Or do I need to always start with some existing one? Even then I can edit the material i.e. also remove pretty much everything and then save it with different name which is in practice the same as making new, right?
-as it is possible to save the LiveDB materials - edited on unedited - to LocalDB, isn't that exactly way to use them again i.e. making 'presets' of them? Right?
-and it is possible to use LiveDB and LW Octane materials in same scene or object, of course not in same surface, right?
If those are all possible then I will be very happy and of course even without those this is really great feature
Thank you again Juanjo!
Intel Core i7 [email protected]
(6-core), 32GB RAM, Nvidia Geforce GTX 690(2 GPU), Geforce Titan Black, Win 10/64 Pro
Latest daily build Octane3 LW plugin (no network rendering
Octane-supported software: Lightwave 2015.3, HDR Light Studio 5 (via LW)