OctaneRender™ Standalone v1.0 RC 3 (obsolete)

[abstrax]

Here's the output of deviceQuery, the utility to find your CUDA capable devices that comes with the CUDA SDK. This confirms that there's no reason Octane doesn't find any CUDA devices...
Still no further ideas on what else to try from across the Tasman? Might this perhaps be the time to take this to a support email rather than a public forum? This obviously is a problem that is not affecting any other users at present.

I also checked which modules are being used by Octane and by the deviceQuery task that successfully sees my GPU. Interesting things I found there:

• Octane appears to make use of OpenCL as well as CUDA libraries (!).

• There appears to be one small difference in which libraries are used: Octane loads /usr/local/cuda/lib/libcuda.dylib, this is not loaded by the CUDA SDK samples. Conversely, libcudart.dylib is not loaded by Octane but used by the SDK samples. Perhaps there's a versioning problem there?

• CUDA framework, libcuda_295.10.20.dylib, libgpucomp.dylib are identical in both processes

...

Hmm, I really don't know what's going on here. Could you try to launch Octane from the terminal (the executable is of course hidden inside the bundle)? Does it give any error messages?

Btw, the OpenCL part must have been pulled in by the CUDa driver (libcuda.dylib). And we don't use the CUDA runtime library.

Thanks,
Marus

[balt]

Hi and thanks for giving this a think...

I have now upgraded to Mountain Lion and the now Octane 1.0 RC 3 does indeed see the GT330M card. But as soon as I attempt to render anything, nothing appears in the viewport and underneath the viewport the text (in red) appears:

0 Textures, 0 Tris, 0 Meshes, GeForce GT 330M (failed), /511/511 MB

This happens regardless of whether I add an empty material and try to render that, or whether I open a scene which previously rendered fine (and still does on the windows machine).

Starting octane from the command line produces this:

Unicorn:MacOS balt$ ./octane
2012-11-17 15:47:43.912 octane[3929:707] invalid drawable

Then adding a specular material and clicking on it to render it and this appears:

CUDA error 2 on device 0: The API was unable to allocate enough memory to perform the requested operation.
-> Failed to bind device to current thread

Memory blowout... but on a sample material scene?

Cheers

- Balt

[pixelrush]

>512mb vram
Sorry I should have also included that with the 48 cores when I said this card is not really suitable for Octane...

[merid888]

hi roeland i have a problem with the 1.0 RC3, i add image, when i do click into material picking mode don't appear selected the object, nothing happen
regards

[ROUBAL]

@merid888 :

Make sure that the corresponding node icone is not disabled on the left of the graph editor screen.

[sternbach]

Otoy never sleeps and...
a software never is final...

Fixed

A software which claims to be final is outdated...

[carbon]

please, any news about medium priority? it is going to be in final release? or it will be disabled forever?

[abstrax]

Hi and thanks for giving this a think...

I have now upgraded to Mountain Lion and the now Octane 1.0 RC 3 does indeed see the GT330M card. But as soon as I attempt to render anything, nothing appears in the viewport and underneath the viewport the text (in red) appears:

0 Textures, 0 Tris, 0 Meshes, GeForce GT 330M (failed), /511/511 MB

This happens regardless of whether I add an empty material and try to render that, or whether I open a scene which previously rendered fine (and still does on the windows machine).

Starting octane from the command line produces this:

Unicorn:MacOS balt$ ./octane
2012-11-17 15:47:43.912 octane[3929:707] invalid drawable

Then adding a specular material and clicking on it to render it and this appears:

CUDA error 2 on device 0: The API was unable to allocate enough memory to perform the requested operation.
-> Failed to bind device to current thread

Memory blowout... but on a sample material scene?

Cheers

- Balt

Hi Balt,

thanks for trying. Although the GPU is fairly weak and only useable for small scenes, it should work. The error message indicates that there is some incompatibility between Octane and the CUDA driver or the CUDA driver and the graphics driver. Which CUDA driver did you install?

Cheers,
Marcus

[icelaglace]

Balt
I did try Octane using Mountain Lion on my GT 650M & It does work if you clean up your CUDA drivers completely if you used Lion then install the very latest one CUDA 5 version. The only change is Mountain Lion support and you need it to make Octane Render to work on your computer.

Also, do you have the Intel dedicated GPU in your computer that switches depending of the performance/battery (Check on Power settings if you have something about graphic card switching)
Cheers.

[balt]

Hi guys,

I have CUDA 5.0.37 running, that's the latest drivers according to the CUDA system preferences applet, and it's a minor revision higher than the latest downloadable driver from the nvidia website (they offer 5.0.36).

Cheers

- Balt