"material not found: Tweet

[rohandalvi]

Hi,

"material not found: /materials/octane_vopnet1"?

I keep running into this issue. Signing out and in to the license manager solves the issue but I don’t want to keep doing that all the time. A more permanent solution would be most welcome.

[lionlee19]

I have the same problem

[BK]

Hi Rohan & Lionlee19,

Thanks for the reminder.

It seems this issue mostly happens if we use the assets from the Test Geometries. Please try avoiding using these assets in the scene and see if the error appears.
We reached out to SideFX devs a while ago and perhaps will get this issue resolved in future releases.

Cheers

[Terryvfx]

Hi,

"material not found: /materials/octane_vopnet1"?

I keep running into this issue. Signing out and in to the license manager solves the issue but I don’t want to keep doing that all the time. A more permanent solution would be most welcome.

I'm actually impressed you found that work-around, I just re-start Houdini and hope for the best, needless to say this is happening to me as well I hope this issue can be resolved in the near future, thanks.

[HandcraftedMedia]

Same thing is happening to me. Not with test geometry but my own stuff.
DO not have that issue in 19.5.403, just in .493

[BK]

Same thing is happening to me. Not with test geometry but my own stuff.
DO not have that issue in 19.5.403, just in .493

Hi HandcraftedMedia,

Would you please share your scene via PM including the Motion blur issue?

Cheers

[peteg]

This seems to be happening when a non-Octane material assignment is made first. It also occurs if a node tree with a non-Octane material assignment is already selected when opening an existing scene.

[Terryvfx]

This seems to be happening when a non-Octane material assignment is made first. It also occurs if a node chain with a non-Octane material assignment is already selected when opening an existing scene.

Nice finding! this correlates with what we already knew about the bug showing if you had a test geometry in the scene.

@BK Does this help you whatsoever to solve the issue or is this something you already knew?

[BK]

This seems to be happening when a non-Octane material assignment is made first. It also occurs if a node chain with a non-Octane material assignment is already selected when opening an existing scene.

Nice finding! this correlates with what we already knew about the bug showing if you had a test geometry in the scene.

@BK Does this help you whatsoever to solve the issue or is this something you already knew?

Hi Terry,

Thanks so much.
Previously, the bug happened randomly with test geometries..
mmm.. need to try with the non-octane material because with Principle shaders seem to work fine.

And thanks to one of your scenes helping us to reproduce it precisely.
We are collecting some info, to resubmit a request for side fx devs to help debug!

Hope we can get this fixed asap!

cheers

[peteg]

This seems to be happening when a non-Octane material assignment is made first. It also occurs if a node chain with a non-Octane material assignment is already selected when opening an existing scene.

Nice finding! this correlates with what we already knew about the bug showing if you had a test geometry in the scene.

@BK Does this help you whatsoever to solve the issue or is this something you already knew?

Hi Terry,

Thanks so much.
Previously, the bug happened randomly with test geometries..
mmm.. need to try with the non-octane material because with Principle shaders seem to work fine.

And thanks to one of your scenes helping us to reproduce it precisely.
We are collecting some info, to resubmit a request for side fx devs to help debug!

Hope we can get this fixed asap!

cheers

As long as Octane was started in the viewport first (no material assignment required) the material not found error didn't show up when I tested.

I tested with the Principled Shader and Matx Subnet, same issue with both if a non-octane material is assigned before octane has been initiated.