Hello,
On Mac OS X, where can I find the octane logs?
I keep getting an error warning when trying to start up Octane in MODO.
Both licences are active so I am kind of stumped as to whats going on.
I've also attached a screenshot of my CUDA driver version.
Any suggestions would be great.
Thanks
Octane logs Mac OS X
Moderator: face_off
If you go to OctaneRender->OctaneRender Setup Window, it's the little '>_' button on the top toolbar of that panel.
Paul
Paul
Win7/Win10/Mavericks/Mint 17 - GTX550Ti/GT640M
Octane Plugin Support : Poser, ArchiCAD, Revit, Inventor, AutoCAD, Rhino, Modo, Nuke
Pls read before submitting a support question
Octane Plugin Support : Poser, ArchiCAD, Revit, Inventor, AutoCAD, Rhino, Modo, Nuke
Pls read before submitting a support question
- macreation
- Posts: 8
- Joined: Sun Apr 25, 2010 11:22 am
Thanks Paul.
Just had a look
Got this message.
Started logging on 17.02.15 08:57:20
OctaneRender version 2.16 (2160000)
CUDA error 300 on device 0: The device kernel source was invalid.
-> failed to bind device to current thread
device 0: failed to initialize resources
CUDA error 300 on device 0: The device kernel source was invalid.
-> failed to bind device to current thread
device 0: failed to initialize resources
CUDA error 300 on device 0: The device kernel source was invalid.
-> failed to bind device to current thread
device 0: failed to initialize resources
CUDA error 300 on device 0: The device kernel source was invalid.
-> failed to bind device to current thread
device 0: failed to initialize resources
Do you know what Error 300 could mean?
Octane was working fine 2 weeks ago.
Just had a look
Got this message.
Started logging on 17.02.15 08:57:20
OctaneRender version 2.16 (2160000)
CUDA error 300 on device 0: The device kernel source was invalid.
-> failed to bind device to current thread
device 0: failed to initialize resources
CUDA error 300 on device 0: The device kernel source was invalid.
-> failed to bind device to current thread
device 0: failed to initialize resources
CUDA error 300 on device 0: The device kernel source was invalid.
-> failed to bind device to current thread
device 0: failed to initialize resources
CUDA error 300 on device 0: The device kernel source was invalid.
-> failed to bind device to current thread
device 0: failed to initialize resources
Do you know what Error 300 could mean?
Octane was working fine 2 weeks ago.
Hi
I have not seen error 300 before. Have you updated anything since the plugin was last working? Does Octane Standalone render OK? What graphics card do you have? Have you tried rebooting and trying again?
Paul
I have not seen error 300 before. Have you updated anything since the plugin was last working? Does Octane Standalone render OK? What graphics card do you have? Have you tried rebooting and trying again?
Paul
Win7/Win10/Mavericks/Mint 17 - GTX550Ti/GT640M
Octane Plugin Support : Poser, ArchiCAD, Revit, Inventor, AutoCAD, Rhino, Modo, Nuke
Pls read before submitting a support question
Octane Plugin Support : Poser, ArchiCAD, Revit, Inventor, AutoCAD, Rhino, Modo, Nuke
Pls read before submitting a support question
- macreation
- Posts: 8
- Joined: Sun Apr 25, 2010 11:22 am
Running a GTX 970 unflashed in a mac.
Deactivated and reactivated the licences.
Rebooted.
Standalone is not working either. Its saying Graphics Card failed.
I might try an older version of cuda. See if it makes a difference.
Deactivated and reactivated the licences.
Rebooted.
Standalone is not working either. Its saying Graphics Card failed.
I might try an older version of cuda. See if it makes a difference.
Win7/Win10/Mavericks/Mint 17 - GTX550Ti/GT640M
Octane Plugin Support : Poser, ArchiCAD, Revit, Inventor, AutoCAD, Rhino, Modo, Nuke
Pls read before submitting a support question
Octane Plugin Support : Poser, ArchiCAD, Revit, Inventor, AutoCAD, Rhino, Modo, Nuke
Pls read before submitting a support question
- macreation
- Posts: 8
- Joined: Sun Apr 25, 2010 11:22 am
Solved.
There was another NVidia driver for newer maxwell based Cards (6.5.46). It wasn't coming up in the system preferences for some reason.
There was another NVidia driver for newer maxwell based Cards (6.5.46). It wasn't coming up in the system preferences for some reason.