OctaneRender® beta 2.43 (lin/mac/win) [OBSOLETE]

[abstrax]

Question for the Tech Godz...
At the moment I am running 32 bit vista, w/ geforce vso 9600 (I need to upgrade to a new 4xx or 5xx card badly)... if I upgrade to 64bit windows 7, how much of a gains will I see in regards to Octane? Load higher res meshes?

Thanks in advance for all of your time and knowledge.

Cheers,
Happy Rendering...

Andy

The preparation of the geometry is done on CPU using RAM. If you have more than 2GB of RAM and want to process larger meshes, 64bit Windows definitely helps. Of course it doesn't affect render speed or available VRAM on the graphics card.

Cheers,
Marcus

[abstrax]

I would like to see an alpha channel to work in direct light.

The CUDA compiler used too much memory and crashed when had this option enabled for the direct lighting kernel. We only way to solve that problem was to take out the option. I'm currently trying out a few things that might help, but I don't know yet.

Cheers,
Marcus

[abstrax]

Hmm, maybe it helps to completely delete the directory /ust/local/cuda and then reinstall (in that order)
- the latest NVIDIA driver (http://www.nvidia.com/object/quadro-mac ... river.html)
- the CUDA 3.2 toolkit (http://developer.nvidia.com/object/cuda ... html#MacOS)
- the CUDA 3.2 driver (http://www.nvidia.com/object/macosx-cud ... river.html)
?

Or just wait for the CUDA 3.0 releases, which I'm currently preparing and which will be available in 2-3 hours.

Cheers,
Marcus

unfortunately it's exactly what i've done.
i've spend all the morning uninstalling and reinstalling but nada
the bad news is that i've the same issue of matej and i can't go back to cuda 3.0 with osx 10.6.6. the problem for me is in the new drivers for the GTX 285 mac, i can't find a way to deinstall it.
i've installed the 243 cuda 3.0 on the PC and i like it very much but my workflow is broken. i'm very sad, this is the first time that i can't run octane on my macpro
ciao beppe

Ok, let's investigate this problem a bit further:

- Do other pre-beta 2.4x releases work?
- What is displayed in the status bar of the render view port?
- What is displayed in the device status dialog (File -> Account Preferences -> CUDA Devices)?

Cheers,
Marcus

[Timmaigh]

I just tried new 2.4.3 and want to say thank you for highlightning selected materials on the meshnode. Its great! Finally i can actually use pre-made material nodes on more complex scenes...

[teecee2107]

I just tried new 2.4.3 and want to say thank you for highlightning selected materials on the meshnode. Its great!

+1

[bepeg4d]

hi marcus,
finally i've found the solution
as i suspected the problems come out from the latest graphic drivers from nvidia, i've reinstalled the osx 10.6.6 combo update without uninstalling cuda 3.2.
doing so i've overwriting the graphic drivers with the apple's one and now octane works perfectly
i think that it must to be said in the realize note, at least for the gtx 285 owners
ciao beppe

[abstrax]

hi marcus,
finally i've found the solution
as i suspected the problems come out from the latest graphic drivers from nvidia, i've reinstalled the osx 10.6.6 combo update without uninstalling cuda 3.2.
doing so i've overwriting the graphic drivers with the apple's one and now octane works perfectly
i think that it must to be said in the realize note, at least for the gtx 285 owners
ciao beppe

Ok. Could you please post the versions of
- the NVIDIA graphics driver
- the NVIDIA CUDA driver
- the NVIDIA CUDA toolkit
that makes it work again?

Thanks,
Marcus

[bepeg4d]

surely:
the cuda toolkit and drivers are the same:
cudatoolkit_3.2.17_macos.pkg
devdriver_3.2.17_macos.dmg
for the graphic drivers I attached two screenshots of the cuda control panel
ciao beppe

[necko77]

I just tried new 2.4.3 and want to say thank you for highlightning selected materials on the meshnode. Its great!

+1

+1

[matej]

Code: Select all

 the launch timed out and was terminated.

I'm experiencing the same thing. Octane (cuda30) crashing when pathtracing on higher resolutions.

I guess a possible solution would be to render from the command line, but unfortunately this way you loose the ability to tonemap. And re-rendering multiple times just for different tonemaping is a big waste of resources.