OctaneRender™ Standalone 2.14 Tweet

[thefishnut]

Unfortunately I've another crash today

Likewise, this is a reoccurring crash that has caused me to loose a lot of work many times.
As far as I can tell it occurs when clicking in repetition on areas around the node view port and render screen, while rendering. This has happened many times, and in two different ways, sometimes octane simply crashes with a warning box saying the program has stopped working. Other times it appears with a red error box indicating the path of the 2.14 octane .exe and that it has crashed.
Unfortunately this is a hard to describe and hard to reproduce error, but it is occurring within all the betas constantly, forcing me to work with the 2.06 version.

[Dmi3ryd]

thefishnut it is very intresting version.

First I think that I've problem with my video card (Asus 780 TI Docu2). But I remember that this broblem didn't appear in earlier versions of octander render.

Second may be file have broken geometry. But in this situation modo - octane plugin working very well.

I can share personal project but I didn't think that problem at current actane file.

P.S.
Dear developers, what do you think?

[thefishnut]

Occurred again, this time there was not an excessive amount of mouse clicks, so my previous post may be incorrect. I simple clicked between the multiply texture and the mix texture, right on the connecting cord, once, and I received this error. This has occurred many times now.

[grimm]

Up, up out of the murky depths the old bug has resurfaced again. On Linux if I select the maximise pane button for the render viewport it locks Octane up and I have to kill it. I tested it on several ocs files and they all lock up. Even if you don't load a file and just have started Octane fresh.

[ff7darkcloud]

I think you clicked and disconnected the node while it was rendering? That causes me crashes too.

[manalokos]

On the "render imported animation" script "skip existing image file" option doesn't work.

[aLeXXtoR]

On the "render imported animation" script "skip existing image file" option doesn't work.

There's more! And there's a fix already posted.

[stratified]

Up, up out of the murky depths the old bug has resurfaced again. On Linux if I select the maximise pane button for the render viewport it locks Octane up and I have to kill it. I tested it on several ocs files and they all lock up. Even if you don't load a file and just have started Octane fresh.

Yes, I can confirm this on Linux. It does seem that it only happens with the OpenGL viewport. You can work around it by choosing the software viewport in the application preferences. We will look into this.

cheers,
Thomas

[grimm]

Thanks Thomas,

I keep forgetting about that option, as I never change it.

Jason

[stratified]

Occurred again, this time there was not an excessive amount of mouse clicks, so my previous post may be incorrect. I simple clicked between the multiply texture and the mix texture, right on the connecting cord, once, and I received this error. This has occurred many times now.

I think you clicked and disconnected the node while it was rendering? That causes me crashes too.

Thanks for the bug reports. The crash will be fixed in the 2.15 release.

cheers,
Thomas