Feature request: node editor filter

[alexos]

Hello,

I would find it rather useful if we had a filter in the node editor that hides all the non-compatible nodes. I know one can simply type "Octane" in the search box, but there are a few native math and info nodes that actually do work, and I'd like to see those too. Am I getting too picky/spoiled?

(credit for the original idea goes to Andrew, btw)

ADP.

[juanjgon]

In the materials you can only use the Octane native nodes, it is easy ... it is true that you can rasterize the LW procedurals to use it in the shaders, but none of the LW nodes (for example the math nodes) are going to work in the materials.

In the render target node editor you can use LW nodes without problems, for example as you say the math nodes, but the render target is precomputed before init the rendering, so again you can't use materials or other nodes that should work at render time.

-Juanjo

[3dreamstudios]

Hello,

I would find it rather useful if we had a filter in the node editor that hides all the non-compatible nodes. I know one can simply type "Octane" in the search box, but there are a few native math and info nodes that actually do work, and I'd like to see those too. Am I getting too picky/spoiled?

(credit for the original idea goes to Andrew, btw)

ADP.

I would agree this would be nice...not sure how cleaned up it would get since as Juan says some of the nodes can be used in different parts of Octane. Procedural and such.

But by his answer I'm not sure he understood what you were asking. I'm not even sure how he would pull it off but would be nice since we have moved to an Octane workflow and don't need to see anything unrelated to Octane in the node tree options.

[juanjgon]

But by his answer I'm not sure he understood what you were asking. I'm not even sure how he would pull it off but would be nice since we have moved to an Octane workflow and don't need to see anything unrelated to Octane in the node tree options.

I think that this feature is not possible currently with the LightWave SDK, but I will investigate it.

-Juanjo

[3dreamstudios]

But by his answer I'm not sure he understood what you were asking. I'm not even sure how he would pull it off but would be nice since we have moved to an Octane workflow and don't need to see anything unrelated to Octane in the node tree options.

I think that this feature is not possible currently with the LightWave SDK, but I will investigate it.

-Juanjo

Thank you sir! Who knows what you may find...could be a stumper though!

[alexos]

I was dreading the "not possible with the current SDK" reply. Forgive me for taking this to a probably ridiculous limit, but I thought that if you can do a separate colour picker (jovian, picky before it) with its own interface, perhaps you could do a separate, Octane-only node editor? Don't kill me!

ADP.