OctaneRender™ Standalone 2.14

A forum where development builds are posted for testing by the community.
Forum rules
NOTE: The software in this forum is not %100 reliable, they are development builds and are meant for testing by experienced octane users. If you are a new octane user, we recommend to use the current stable release from the 'Commercial Product News & Releases' forum.
Post Reply
User avatar (Default)
thefishnut
Licensed Customer
Posts: 64
Joined: Thu Aug 23, 2012 12:08 pm
Location: Australia

Unfortunately I've another crash today :(
Likewise, this is a reoccurring crash that has caused me to loose a lot of work many times. :x
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.
Win 8 64 | 2 x Geforce GTX780 6gb | i7 4790k | 32GB
Top
User avatar
Dmi3ryd
Licensed Customer
Posts: 233
Joined: Mon Feb 25, 2013 1:31 pm
Location: Russia
Contact:
Contact 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?
Win 8.1/64 | Geforce GTX780TI | Core I7 970 | 24GB
Top
User avatar (Default)
thefishnut
Licensed Customer
Posts: 64
Joined: Thu Aug 23, 2012 12:08 pm
Location: Australia

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.
Attachments
error crash octane.jpg
Win 8 64 | 2 x Geforce GTX780 6gb | i7 4790k | 32GB
Top
User avatar
grimm
Licensed Customer
Posts: 1332
Joined: Wed Jan 27, 2010 8:11 pm
Location: Spokane, Washington, USA

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.
Linux Mint 21.3 x64 | Nvidia GTX 980 4GB (displays) RTX 2070 8GB| Intel I7 5820K 3.8 Ghz | 32Gb Memory | Nvidia Driver 535.171
Top
User avatar
ff7darkcloud
Licensed Customer
Posts: 73
Joined: Sun Mar 18, 2012 11:20 pm
Location: Fairfax, VA, USA

I think you clicked and disconnected the node while it was rendering? That causes me crashes too.
( PC ) Win10 x64 | 2xRTX2080TI | ASUS Rampage VI Extreme | i9-7900x | 32GB | 1600W
( Laptop ) Win10 x64 | RTX2080Max-Q | Lenovo Legion Y740 | i7-9750H | 32GB - Octane Standalone Win 10/ Sketchup 2019

PORTFOLIO: https://renderspace.wixsite.com/portfolio
Top
User avatar (Default)
manalokos
Licensed Customer
Posts: 441
Joined: Fri Nov 18, 2011 4:43 pm

On the "render imported animation" script "skip existing image file" option doesn't work.
Top
User avatar
aLeXXtoR
Licensed Customer
Posts: 294
Joined: Sat Oct 29, 2011 5:38 pm
Location: Russia, St. Ptetersburg
Contact:
Contact aLeXXtoR

manalokos wrote:On the "render imported animation" script "skip existing image file" option doesn't work.
There's more! :) And there's a fix already posted.
Win 10 Pro 64bit | GeForce RTX 2070 SUPER 8Gb | AMD Ryzen 7 3700X | 32GB RAM
WebSite
Showreel
Top
User avatar
stratified
OctaneRender Team
Posts: 945
Joined: Wed Aug 15, 2012 6:32 am
Location: Auckland, New Zealand

grimm wrote: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
Top
User avatar
grimm
Licensed Customer
Posts: 1332
Joined: Wed Jan 27, 2010 8:11 pm
Location: Spokane, Washington, USA

Thanks Thomas,

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

Jason
Linux Mint 21.3 x64 | Nvidia GTX 980 4GB (displays) RTX 2070 8GB| Intel I7 5820K 3.8 Ghz | 32Gb Memory | Nvidia Driver 535.171
Top
User avatar
stratified
OctaneRender Team
Posts: 945
Joined: Wed Aug 15, 2012 6:32 am
Location: Auckland, New Zealand

thefishnut wrote: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.
ff7darkcloud wrote: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
Top
Post Reply

Return to “Development Build Releases”