OTOY Forums

face_off wrote:Hi Niklas - I cannot help you unless you answer my question from above...

Sorry...
unfortunately it's the same error with these versions too!
/Niklas

If Octane Standalone 2.06 and 2.10 is also producing error 999's, then it is most likely a hardware error. For some people, UNDERCLOCKING their card will fix this. Also worth checking the card temperature with CPU-Z. I take it you only have a single card?

Paul

I just noticed that the plugin works fine in Modo 701 sp5 64 bit?

Yes, its a single card, temperature is around 48 Celsius and 118 Fahrenheit?
/Niklas

I just noticed that the plugin works fine in Modo 701 sp5 64 bit?

Does it render OK on 701? If Octane Standalone is producing Cuda error 999's - I cannot see of the Modo plugin would render without errors.

Paul

Now I'm embarrassed, sorry for messing it up...
Standalone works just fine, I Missed "standalone" in today's stress!
All versions of the plugin does not work anymore in 801!
/Niklas

All versions of the plugin does not work anymore in 801!

Can you pls delete your Modo801.cfg file and try again. You will need to re-authenticate the plugin. This should fix your problem.

Paul

Hello
I found the problem, it was not the .cfg file (that one gets deleted first when you troubleshoot something)...
But I started to look more at my other plugins! I had the v-ray beta installed and if I disabled it everything works,
my card shows up again and no more errors (I'm happy)!
let me know if you want to look into it some more and if I can help you with anything?

Thanks...
/Niklas

Hello.
I've got a new conflict between two plugins, this one is emPolygonizer5 for Modo - http://www.mootzoid.com/plugin/empolygonizer5!
I get this error, see below, in Octane for Modo if I have empolygonizer5 active but Octane works fine if I disable empolygonizer5? I have also written to him in other forums, if something can be done about it!

Started logging on 12.11.14 00:35:25
OctaneRender version 2.12.1 (2120001)
CUDA error 999 on device 4294967295: An unknown internal error occurred.
-> failed to initialise CUDA driver API
No interface with that address found. -> Not changing current daemon scan interface.

Best
/ Niklas

sjogren wrote:Hello.
I've got a new conflict between two plugins, this one is emPolygonizer5 for Modo - http://www.mootzoid.com/plugin/empolygonizer5!
I get this error, see below, in Octane for Modo if I have empolygonizer5 active but Octane works fine if I disable empolygonizer5? I have also written to him in other forums, if something can be done about it!

Started logging on 12.11.14 00:35:25
OctaneRender version 2.12.1 (2120001)
CUDA error 999 on device 4294967295: An unknown internal error occurred.
-> failed to initialise CUDA driver API
No interface with that address found. -> Not changing current daemon scan interface.

Best
/ Niklas

Try a different graphics driver. Usually it should be ok to have multiple modules accessing CUDA and until recently nobody reported this issue. -> My guess is currently that one of the latest NVIDIA graphics drivers introduced this problem.

I had exactly the same problem! Disabling Vray fixed It.(thank you, you saved me hours of research and reinstalling drivers and plugins) I must add that I had another problem like this one on my other computer (where I installed the demo of Octane) and got the Error 500 log message.

I'm also running Octane for lightwave on the same machine and never had a glitch, so It seems to me that the Modo/Octane plugin is a tad "sensitive" to say the least.