OTOY Forums

mattfrodsham wrote:Let me clean my plugin folder up and do some tests later today, I'll let you know if I find out what causes it or if it continues after removing everything

ok, i can test if you let me know the your list

Ahmet I have still no success to get .79B to work.

I copied the whole C4D folder, deleted all not-C4D based files (plugins, scripts, browser content) until it was like pure install.
Then I installed 0.79B. The effect was the same as written in the PM: octane failed to show the complete geometry, lacking most of it. .76 is still working good, but I need some of the new features as rendering 16/32 floating images from picture viewer.
I did not switch on the update geometries option because the scene nearly couldn't be handled anymore. Every click on an option takes up to a minute till it responses. Under this circumstances I tried different priorities of the device, I have one card for all, wich does not change the slow reaction. Btw: I had this two wired responses since 0.77.
So it does not depend on any installed plugins. What else can I try?

dinf wrote:Ahmet I have still no success to get .79B to work.

I copied the whole C4D folder, deleted all not-C4D based files (plugins, scripts, browser content) until it was like pure install.
Then I installed 0.79B. The effect was the same as written in the PM: octane failed to show the complete geometry, lacking most of it. .76 is still working good, but I need some of the new features as rendering 16/32 floating images from picture viewer.
I did not switch on the update geometries option because the scene nearly couldn't be handled anymore. Every click on an option takes up to a minute till it responses. Under this circumstances I tried different priorities of the device, I have one card for all, wich does not change the slow reaction. Btw: I had this two wired responses since 0.77.
So it does not depend on any installed plugins. What else can I try?

Hi,
0.79B has lot of internal changes. You can think as a testing release.
Because of this somethings can has problem. Also i have found a problem with render instances and zero scale while update geometries is activated in rendering.
I'm working on this. I hope to fix lot of things and release soon(in 1-2 days)

aoktar wrote:

mattfrodsham wrote:Let me clean my plugin folder up and do some tests later today, I'll let you know if I find out what causes it or if it continues after removing everything

ok, i can test if you let me know the your list

To confirm my render queue crashes after the first job even with no other plugins in my folder

aoktar wrote:

dinf wrote:Ahmet I have still no success to get .79B to work.

I copied the whole C4D folder, deleted all not-C4D based files (plugins, scripts, browser content) until it was like pure install.
Then I installed 0.79B. The effect was the same as written in the PM: octane failed to show the complete geometry, lacking most of it. .76 is still working good, but I need some of the new features as rendering 16/32 floating images from picture viewer.
I did not switch on the update geometries option because the scene nearly couldn't be handled anymore. Every click on an option takes up to a minute till it responses. Under this circumstances I tried different priorities of the device, I have one card for all, wich does not change the slow reaction. Btw: I had this two wired responses since 0.77.
So it does not depend on any installed plugins. What else can I try?

Hi,
0.79B has lot of internal changes. You can think as a testing release.
Because of this somethings can has problem. Also i have found a problem with render instances and zero scale while update geometries is activated in rendering.
I'm working on this. I hope to fix lot of things and release soon(in 1-2 days)

I'm looking forward to it!

In my case Hot4D crashed Octane. I removed the plugin and it crashed again, until i realised that i had to delete the dll files of hot4d from the root folder too!

No crashes here now since 6 days using 079b!

The only thing (I think) that I left were the vray libs in the C4D application package necessary for the plugin to run. I don't have hot4d,

For reference my usual list is:

ChamferMaker
CADeformerPack
Flatten
KyamaSlide
SteadyBake
True Symmetry
Vray

But none are in use in the scenes that crash, and I already tried removing them from my plugins folder. Maybe that info helps?

mattfrodsham wrote:The only thing (I think) that I left were the vray libs in the C4D application package necessary for the plugin to run. I don't have hot4d,

But none are in use in the scenes that crash, and I already tried removing them from my plugins folder. Maybe that info helps?

to loading any confusing plugin that is enough to crash.

FYI: there are no left DLLs in my test-installation.
I'll try the render queue crash wich I had also later on with the clean Cinema version.

Ahmet, I am trying to get a round IES spotlight to work in the plugin. I know it was possible in the standalone, http://www.youtube.com/watch?v=Tedj2lEK ... B&index=12 is this working in the plugin?