OTOY Forums

Strange m... man mattafeller... Try to RTFM before insulting people.

Lol to RTFM? Thia stupid shit doesnt work that's what I'm saying. I want my money back. Btw Your PC specs are from a middle class cunt

Top class troll detected. Good luck, kid.

aLeXXtoR wrote:Top class troll detected. Good luck, kid.

+1 on this one.

The problem is not the software mattafeller...believe me.

Time after time Blender silently crashes when I render animation with sampled motion blur. Can't really say more details for now — if I catch the moment, I'll give more expanded feedback.

I have some crashing going on to... It seems it is scene specific. Not sure what I did to create this problem. Worked fine on earlier versions of the scene. I have a Titan card 6Gb (first edition). Blender hangs during viewport rendering for about 4 seconds before shutting down. I get these error messages (attached below). Can´t find error code 3... I first thought it was a graphics card error only, but could the TCP port have something to do with Octane server?

I reinstalled graphics drivers, but that did not help. What about Cuda drivers? I can´t find out if latest Cuda (6.5) was installed with the latest graphics driver. I know early versions of Octane demanded Cuda to be installed separately. Are you guys installing Cuda 6.5 separately or just running your latest graphics drivers?

I think I have a workaround for working on with the geometry and rendering in another scene, but it would be interesting if any one knows what this might be.

Thanks

::mb

Marten74
These are different errors.
TCP port error, as I wrote earlier - happens mostly due to the port is already occupied by other process. Most often it happens when you are trying to start the second instance of OctaneServer on the same machine - as the port is already used by running instance, the second start fails. This "extremely meaningful" ("no error" ) error description is returned by windows network stack, the Octane server just shows it to you unchanged.

But your second error is more interesting. Most likely it may mean that the GPU, which is used for displaying of the user interface (by OpenGL driver in this case, e.g. Blender uses OpenGL both for viewports and for user interface), is busy by some other things and does not respond for some time. So, after the timeout - the error is raised.
Most likely the GPU is used by CUDA rendering from inside of OctaneServer... This is why I always use the separate not expensive GPU for desktop only, never enabling it for CUDA rendering...

Ah, yes, the TCP message was "hiding" behind the code 3 one, and when I found it... Well... *no error*

I´ll see if another graphics card will help for handling the viewport will help. Have to read a bit about how that will work.

Thanks!

::mb

Hi are there any plans to get rid of the render server situation? The reason I ask is because it feels a bit cumbersome. Sometimes it works sometimes it doesn't. Most of the time octane server crashes when I try to render high poly scenes that work fine in standalone. Are there any other solutions in the works besides this one for Octane Blender?

The only way to get rid of Octane Server is to change Blender's GNU GPL license, which is probably never going to happen. This is the only way that Otoy can plugin to Blender and still have proprietary code.