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

[pixelrush]

A small bug re exceeding vram size when changing image resolution.
Previously I reported a crash for this condition and suggested some better error handling was needed.
I note now it says 'Failed to Allocate GPU Mesh Object. Please reduce scene complexity' when this is encountered however from that moment the render is hung at the previous res and with the vram showing the mem occupied by the new image setting but not the geometry. Then its not possible to change the resolution (you would of course like to change to something smaller)...perhaps it is not possible to go back once the vram is over allocated? although before it just gave a black screen and a strangely fast render speed until you reduced it...

I also note that it seems to take a very long time with a big mesh to display the image in the viewport when first clicking on the node to get it rendering. perhaps it needs a 'loading and confirming license' message in place of the hourglass icon

[abstrax]

A small bug re exceeding vram size when changing image resolution with an already large mesh.
previously I reported a crash for this condition and suggested some better error handling was needed.
I note now it says 'Failed to Allocate GPU Mesh Object. Please reduce scene complexity' when this is encountered however from that moment the render is hung at the previous res and with the vram showing the mem occupied by the new setting but not the geometry. It is not possible to change the resolution (you would of course like to change to something smaller)...perhaps it is not possible to go back once the vram is over allocated?

I also note that it seems to take a very long time to display the image in the viewport when first clicking on the node to get it rendering. perhaps it needs a 'loading and confirming license' message or a hourglass icon

The first time you click on a mesh node and Octane starts rendering, the whole CUDA system is initialised, all the geometry, textures and other stuff are uploaded. And that takes time. We will improve this area (including the first point and the error handling), when we do the rewrite of the multi-GPU layer. It's not a trivial fix you can just "tack on" unfortunately.

Cheers,
Marcus

[pixelrush]

There seems to be a new bug or perhaps two to do with rendering near 8000px.
I am getting renders at 7000x7000 and a bit over (<7125x7125) but not 8000x 8000
either crashes outright or in the case of 8000x4000 it displays but 8192x4000 shows all white.
I 'm sure this has worked before - I have the vram for it
I suspect the film is maxing out at 1024mb vram used now??

[abstrax]

There seems to be a new bug or perhaps two to do with rendering near 8000px.
I am getting renders at 7000x7000 and a bit over but not 8000x 8000
either crashes outright or shows all white.
8000x4000 displays but 8192x4000 is all white
I 'm sure this has worked before - I have the vram for it
I suspect the film is maxing out at 1024mb vram used now??

Hmm, actually we haven't changed anything in that area. It could be CUDA 3.2 that causes trouble here or some other change. I will investigate next week. Thanks for the feedback.

Cheers,
Marcus

[Elvio]

Hey Radiance!!! Is possible to add image sequence in the next release? It would be great because when you are using like a tv display, there is no need to export the obj every time, only the cam.

Congrats by the 2.43 version, it´s really really stable, im doing a short movie about drugs, it´s a documentary, I will post it here soon.

[SamCameron]

Please, add clip texture feature, is really important.

[abstrax]

Please, add clip texture feature, is really important.

What exactly do you mean? That textures are not wrapped at the borders? Why exactly is it important and which colour should be used outside of the (0,1) UV range?

Cheers,
Marcus

[thwak]

Marcus,

Have been playing on my Win32 side (XP) with 2.42 (CUDA 3.0) and it has been great. 2.42 still runs great. 2.43 won't start.

I get the splash screen and then the error message "Unable to determine network type..." which I always got for 2.42 as well. I click OK on the error message and it and the splash screen go away (as it also does for 2.42). And then.... Nothing. 2.43 won't start.

Tried upgrading to 266.58 but didn't solve anything. 2.42 continues to run great. 2.43 won't start.

I double checked that I am using the CUDA 3.0 versions of both.

What changed between the two versions that might cause this?

Any ideas?

[abstrax]

Marcus,

Have been playing on my Win32 side (XP) with 2.42 (CUDA 3.0) and it has been great. 2.42 still runs great. 2.43 won't start.

I get the splash screen and then the error message "Unable to determine network type..." which I always got for 2.42 as well. I click OK on the error message and it and the splash screen go away (as it also does for 2.42). And then.... Nothing. 2.43 won't start.

Tried upgrading to 266.58 but didn't solve anything. 2.42 continues to run great. 2.43 won't start.

I double checked that I am using the CUDA 3.0 versions of both.

What changed between the two versions that might cause this?

Any ideas?

I sent you a PM. I hope we can solve this problem

Cheers,
Marcus

[yoyoz]

hi Marcus,

the attached object still makes Octane crash at load time. I know this is bad geometry, but no reason for executing an illegal instruction

Code: Select all

lionel@pc-lionel:/opt/OctaneRender$ ./octane 
ERROR: Program executed illegal instruction.. terminating

Cheers,
Lionel