Version 2.24.1-R3 (06.10.2015) - obsolete stable

[aoktar]

Thank you aoktar for this quick release,
i just have small problem after i install the update like every time i get this error on mac OS X do you have any idea way?? see the attachment please

you're welcome Ata. what happens after deactivate from otoy account section? it may require this after some updates.

[albehany]

Thank you aoktar for this quick release,
i just have small problem after i install the update like every time i get this error on mac OS X do you have any idea way?? see the attachment please

you're welcome Ata. what happens after deactivate from otoy account section? it may require this after some updates.

yes this fix my problem thank you.

[Ron]

Hi Ahmet,

had a plugin crash several times while exporting an animated ORBX. Crash report attached.
It crashes allways at the very end of the process at 99%. In this version of plugin the LV gets active and is rendering all frames automatically when the export process starts. That didn't happen in 2.23.X.
Tried to stop that but couldn't.
Is there any setting that avoids getting the LV active while exporting ORBX?

_BugReport.txt

(259.59 KiB) Downloaded 266 times

[_Fertig]

Hi,

I'm experiencing crashes since the last two releases ( R6025 - pure virtual function call). I cant reproduce the crash on purpose, I have the feeling it sometimes comes up when reloading the live viewer, but as I said, it might also just crash out of the blue. I managed to get a bug report yesterday, usually I have to kill Cinema after the crash and I don't even get the report. Is there anything I can do to narrow down the possible cause or find out if its octane at all?

The same error message apparently appears with some older network rendering issue and displacement nodes. I can rule these out, as I neither have network rendering enabled, nor am I using displacement on this file.

Thanks,
Lukas

[aoktar]

Hi Ahmet,

had a plugin crash several times while exporting an animated ORBX. Crash report attached.
It crashes allways at the very end of the process at 99%. In this version of plugin the LV gets active and is rendering all frames automatically when the export process starts. That didn't happen in 2.23.X.
Tried to stop that but couldn't.
Is there any setting that avoids getting the LV active while exporting ORBX?

_BugReport.txt

Is it happening on same scene? Maybe too big for orbx format.

[aoktar]

Hi,

I'm experiencing crashes since the last two releases ( R6025 - pure virtual function call). I cant reproduce the crash on purpose, I have the feeling it sometimes comes up when reloading the live viewer, but as I said, it might also just crash out of the blue. I managed to get a bug report yesterday, usually I have to kill Cinema after the crash and I don't even get the report. Is there anything I can do to narrow down the possible cause or find out if its octane at all?

The same error message apparently appears with some older network rendering issue and displacement nodes. I can rule these out, as I neither have network rendering enabled, nor am I using displacement on this file.

Thanks,
Lukas

You can give me more info about your scenes, better to send me a scene to reproduce here. Bugreport seems like not related with issue which you said. At least give me much better info about content of your scenes. How much objects, cloners, generators are used? What do you see on on-screen info of LV?

Also, if you notified that there is some differences between last versions and older. Biggest is "auto mode" on LV. Do you know what you should aware of while it's active?

[FelipeCortes]

issue:
animating "visible in render" for objects, in the LiveViewer works ok , but animated on the picture viewer work in the next frame. problem encountered several versions ago , in 2 similar PC

Win 8.1 gtx970 r16.050 tanks.

[aoktar]

issue:
animating "visible in render" for objects, in the LiveViewer works ok , but animated on the picture viewer work in the next frame. problem encountered several versions ago , in 2 similar PC

Win 8.1 gtx970 r16.050 tanks.

Every animated object requires a object tag. Or use "auto detect" or "All movable" option. Also read manual and see tutorial videos why we put a object tag.

[dotcommer]

Thank you aoktar for this quick release,
i just have small problem after i install the update like every time i get this error on mac OS X do you have any idea way?? see the attachment please

This is also happening to me. I finally got a chance to upgrade my plugin and stand-alone versions, and now when I open them, I get this message saying they're activated on another computer (but its the same computer!). Do I need to deactivate both licenses from Otoy website and wait 30 min, before reentering them? That seems really silly. Why do I need to do that? Is this new plugin having trouble identifying my machine?

[raincity]

Aoktar thank you for all your hard work on Octane.

Unfortunately, when I upgraded to 2.24.0 from 2.23.2-r6.2 the octane materials (diffuse, specular, glossy) no longer show up in the materials palette. They show up as empty boxes instead of showing the material on a sphere. When I apply to an object, the object turns black and nothing renders. I have since downgraded back to 2.23.2 and the materials are back to working fine.

I am on a recent iMac running c4d r16.050.