OctaneRender™ Standalone v1.0 beta3.02a [obsolete]

[bepeg4d]

you are welcome
sorry for the mistake of the mac cuda version, you are right, it's 5.0.36
ciao beppe

[pixelrush]

Quadro windows drivers appear to have jumped cuda 4.2.
The previous one was 297.03 and is 4.1, the latest 305.93 is cuda 5.
What do Otoy suggest?

[abstrax]

Quadro windows drivers appear to have jumped cuda 4.2.
The previous one was 297.03 and is 4.1, the latest 305.93 is cuda 5.
What do Otoy suggest?

Sorry, I don't know which one you should use. I guess, I have to try out yourself. Any driver that works is a good driver.

Cheers,
Marcus

[roeland]

You can try driver version 301.42, get it from http://www.nvidia.com/Download/Find.aspx?lang=en-us.

--
Roeland

[pixelrush]

Yup but that's not a Quadro driver for Quadro cards
Is there anything specific in the latest Octane code relating to cuda versions or is it just a matter of finding a driver that works best regardless?

[abstrax]

Yup but that's not a Quadro driver for Quadro cards
Is there anything specific in the latest Octane code relating to cuda versions or is it just a matter of finding a driver that works best regardless?

No, there isn't anything specific, except that it must support CUDA 4.2 (or higher). That means a driver version of 301.32 or higher. 301.32 was the development driver released with the CUDA 4.2 toolkit.

Cheers,
Marcus

[pixelrush]

OK thank you in that case I'll have a try with Quadro 305.93 (cuda 5).

[grimm]

Yay!! This one worked. Except with the old test ocs files, although the benchmark ocs worked. Must be newer.

Which scenes did not work and how did they not work?

I think I spoke a bit too soon. The only ocs file I have gotten to work has been the benchmark. I tried all of the other demo files and they all would start to work for just a couple of seconds before stopping. The errors are the same as before, here is a sample:

Code: Select all

    -> Failed to unbind texture (data13)
CUDA error 700 on device 0: An exception occurred on the device while executing a kernel. The context cannot be used anymore and must be destroyed. All existing device memory allocations from this context are invalid and must be reconstructed.
    -> Failed to deallocate device memory
CUDA error 700 on device 0: An exception occurred on the device while executing a kernel. The context cannot be used anymore and must be destroyed. All existing device memory allocations from this context are invalid and must be reconstructed.
    -> Failed to unbind texture (data14)
CUDA error 700 on device 0: An exception occurred on the device while executing a kernel. The context cannot be used anymore and must be destroyed. All existing device memory allocations from this context are invalid and must be reconstructed.
    -> Failed to deallocate device memory
CUDA error 700 on device 0: An exception occurred on the device while executing a kernel. The context cannot be used anymore and must be destroyed. All existing device memory allocations from this context are invalid and must be reconstructed.
    -> Failed to unbind texture (data15)
CUDA error 700 on device 0: An exception occurred on the device while executing a kernel. The context cannot be used anymore and must be destroyed. All existing device memory allocations from this context are invalid and must be reconstructed.

I tried to load some obj files too and they crashed the kernel as well.

I did notice that this beta was less responsive than the previous versions on my single GPU system. Happy Jason, now I can have some fun with instancing.

Hmm, could you please be more specific? What does "less responsive" mean and against which version are you comparing?

I haven't been able to use Octane much this summer so I think it must have been 2.58 or thereabouts. "less responsive" is, when this version is working, things like button clicks take a second or two to register. Panning or rotating the camera is very slow and the rest of the interface is just not as snappy as it was before.

Thanks a lot for your feedback,
Marcus

No problem, I really like Octane and want to help as much as I am able.

The only differences that I can think of from then to now, besides the OS upgrade and the new version of Octane, is that I have changed my desktop environment to Cinnamon. Cinnamon is a fork of Gnome 3 that now uses a lot of graphic effects that might affect the GPU more than before? The only other thing is that I had to do is a link to the libGLEW library to get Octane to run. Even though I'm running Fedora 17 the libGLEW in the repository is only up to version 1.6. So I linked /lib64/libGLEW.so.1.7 to the 1.6 version. Sometimes this works, other times not. In any case it might be an issue?

Thanks,

Jason

[Tugpsx]

Thanks for new version. Will review for needed Exporter changes

[roeland]

I think I spoke a bit too soon. The only ocs file I have gotten to work has been the benchmark. I tried all of the other demo files and they all would start to work for just a couple of seconds before stopping. The errors are the same as before, here is a sample:

What is the first error shown?

I haven't been able to use Octane much this summer so I think it must have been 2.58 or thereabouts. "less responsive" is, when this version is working, things like button clicks take a second or two to register. Panning or rotating the camera is very slow and the rest of the interface is just not as snappy as it was before.

The only differences that I can think of from then to now, besides the OS upgrade and the new version of Octane, is that I have changed my desktop environment to Cinnamon. Cinnamon is a fork of Gnome 3 that now uses a lot of graphic effects that might affect the GPU more than before? The only other thing is that I had to do is a link to the libGLEW library to get Octane to run. Even though I'm running Fedora 17 the libGLEW in the repository is only up to version 1.6. So I linked /lib64/libGLEW.so.1.7 to the 1.6 version. Sometimes this works, other times not. In any case it might be an issue?

Maybe a graphical desktop indeed suffers more from running a CUDA application. Is it running much slower than with version 3.01? Were you using the PMC kernel back then? This kernel has less effect on the responsiveness of the desktop than the path tracing and direct lighting kernels.

We will try to remove the libGLEW dependency. I don't know if linking like this is a problem.

--
Roeland