Hi,

Well, as you can see there are no problems with the materials in this scene once configured. The only problem is that of course the exterior package doesn't allow to see the internal money object if it is opaque, so in this scene I've made it near transparent. Attached you have the scene ...

Hmm, so do you say that Houdini crash just after trying to import a LiveDB material using the "import" option as you can see in the attached image? Sorry, but here this feature seems to work fine. What plugin version are you using?

Thanks,
-Juanjo

sorry for late response, but I am using the ...

Hi,

If you get purple materials, that means that the object doesn't have a material assigned, or it is not valid. The materials are assigned at OBJ level using the Material parameter, or at the SOP level using the Material SOP (that configures the shop_materialpath primitive attribute). The ...

Hi,

Sorry, it is Monday here, so I've just seen this post after the weekend. Here the LiveDB feature seems to work fine. What Octane plugin version are you using? If possible try the latest one released 2018.1.0.7

The problem can be related for example to the LiveDB textures path, that you must ...

I can't import anything from local/live db, if I import from LiveDB the tab closes and nothing happens/ is imported into Houdini...
On the other hand if I import my own textures from LocalDB the whole Houdini program just closes...?
Handful of problems and I can't understand why, I'd love some ...

If I try to import a material from LocalDB, as soon as I press Import, Houdini crashes without error message.

I may just be new to the render setup process, but I have a stack of money geometry with materials that I created inside material context, but when I IPR render the model is fully purple without any materials... How can I fix this?
Could someone explain me the basic process so I don't keep running ...

On my other RBD scene, I still can't get it to render with IPR, it still just closes the program altogether.

Hi,

What Octane plugin version are you using? The CUDA 999 error was always related to a problem with the NVIDIA drivers or to trying to use the latest NVIDIA drivers with an older Octane build.

The latest 2018.1.0.7 build just released (or the current 4.02.1.0 build) should work without problems ...

Hi,

What Octane plugin version are you using? The CUDA 999 error was always related to a problem with the NVIDIA drivers or to trying to use the latest NVIDIA drivers with an older Octane build.

The latest 2018.1.0.7 build just released (or the current 4.02.1.0 build) should work without problems ...