failed to initialise CUDA driver API

[sjogren]

Hey! I have to agree that Octane for Modo and Modo is a bit fragile! I never got it to work properly and have not had time to debug so I have not used Octane in a long time!

I also got another problem when I installed Octane for Modo that made Modo freeze in 1 to 2 seconds in every thing I did, I got Modo to work after a lot of uninstallations and reinstallations of plugins and drivers but I dare not to install Octane for Modo again right now. However, I do not think this needs to be a Octane error, start thinking if my video card / OpenGL is broken? Does anyone recognize this behavior or know how to test and figure out what might be wrong, I want to start use Octane again...

/niklas

[face_off]

I also got another problem when I installed Octane for Modo that made Modo freeze in 1 to 2 seconds in every thing I did, I got Modo to work after a lot of uninstallations and reinstallations of plugins and drivers but I dare not to install Octane for Modo again right now. However, I do not think this needs to be a Octane error, start thinking if my video card / OpenGL is broken? Does anyone recognize this behavior or know how to test and figure out what might be wrong, I want to start use Octane again...

Your NVidia driver version looks fine.

You should be able to safely install the latest release. When you do, delete you Modo801.CFG, in case there was something there upsetting things. I have seen a couple of plugin conflicts - and this is generally because when you access your plugin channels through the API and another plugin has added channels prior to your plugin, if you do not access your channels in the correct way Modo will crash. I am 99.9 percent certain the Octane plugin is doing things the right way - but I cannot be certain about other plugins. I have heard reports of conflicts with some other plugins and have reported then to the relevant Modo people, and they are in the process of investigating.

So - if you have issues - disable all plugins except Octane. If it runs fine - enable other plugins until you find the culprit and let me know which plugin is causing the conflict and I will start the process of tracking down the issue.

Paul

[sjogren]

Hello, did some testing and found these kits/plugins that conflicts with Octane!
Mootzoid emReader (latest version) http://www.mootzoid.com/
Mootzoid emPolygonizer5 (latest version) http://www.mootzoid.com/
UnrealShader (latest version) Link to Modo forum
V-Ray for Modo (latest BETA version)

then I think I found a pretty solid Nvidia driver, got everything to work and I think I have the situation/computer under control, don't dare to change too much now...

/Niklas

[face_off]

UnrealShader (latest version) Link to Modo forum

Hi Niklas. I just installed this plugin, and couldn't find any issues running it with Octane. What specific conflict are you getting pls?

Paul

[sjogren]

I get:
CUDA error 999 on device -1: An unknown internal error occurred.
-> failed to initialise CUDA driver API

/Niklas

[face_off]

Hi Niklas - have you tried deleting Modo801.cfg? (You will need to re-authenticate the Octane plugin if you do this).

Do you get the error if the UnrealShader plugin is installed - or do you need to add an unreal material in order to generate the Cuda error?

What Nvidia driver version are you using pls? I assume it is not the version in your signature, because the latest release of the Octane plugin requires at least version 344.x.

Do you have a separate graphics card as your Window display adapter, or are you using a single card for for Octane rendering and as the Windows display adapter?

Thanks

Paul

[sjogren]

hi there.
I got it to work after a lot of re-installing drivers and cleaning, no error with UnrealShader and my computer works great!
As I wrote earlier, I think it is/was something with my graphics card, also installed Asus GPU tweak and got the feeling that my video card became a lot more stable (my speculation)? I had a lot of strange OpenGL things previously, but not right now with Nvidia driver 347.52!

V-Ray and Mootzoid plugins still give me the error!

I had deleted my Modo801.cfg. Do it all the time to have a clean Modo, personal settings on a separate .cfg.
Sorry but I dont remember witch driver I had earlier, been alot of changing versions lately (troubleshooting), but I could run Octane for Modo with it!
I have a single cards, looking in to to buy a new one, but need tips and investigate which one!

Thanks a lot for your effort...
/Niklas

[face_off]

I have emailed Mootzoid to try to get a copy of their plugins so I can take a closer look.

Paul

[face_off]

V-Ray and Mootzoid plugins still give me the error!

I installed Mootzoid emReader, started Modo, added a cube, opened the Octane Viewport - and everything was fine. Is there something specific I need to do to get the conflict?

Thanks

Paul