Testing Beta 0.87b (SDK 1.20) **updated 04.10**

[centropolis]

Hello,

you have any suggestions for this error?

Testing Beta version 0.8.7b (SDK1.20)
Windows 8.1 preview
cinema 4D Studio R14.042

Many Thanks !

centropolis

[aoktar]

what kind of plugins is available on plugins folder?

look this:
http://render.otoy.com/manuals/Cinema4D/?page_id=651

[slash]

@centropolis - I noticed TurbulenceFD plugin causing this.

[Rudi]

Cinema R14, Carbon Scatter 2, nVidia GTX Titan, Octane Render 0.87b

################################################################################
Started logging on 06.10.13 21:22:53
################################################################################

OctaneRender version 1.20 (1200002)

CUDA error 1 on device 0: One or more of the parameters passed were not within an acceptable range of values.
-> Failed to bind texture to device memory (data8)
CUDA device 0: Failed to bind data texture 5 of context 0
CUDA error 1 on device 0: One or more of the parameters passed were not within an acceptable range of values.
-> Failed to bind texture to device memory (data8)
CUDA device 0: Failed to bind data texture 5 of context 0

[aoktar]

Cinema R14, Carbon Scatter 2, nVidia GTX Titan, Octane Render 0.87b

################################################################################
Started logging on 06.10.13 21:22:53
################################################################################

OctaneRender version 1.20 (1200002)

CUDA error 1 on device 0: One or more of the parameters passed were not within an acceptable range of values.
-> Failed to bind texture to device memory (data8)
CUDA device 0: Failed to bind data texture 5 of context 0
CUDA error 1 on device 0: One or more of the parameters passed were not within an acceptable range of values.
-> Failed to bind texture to device memory (data8)
CUDA device 0: Failed to bind data texture 5 of context 0

did you get a crash or only warning? What did you after this? Can you continue rendering with some revision?

[Rudi]

I had 3 different trees of Laubwerk. These are distributed via carbon scatter.
I could only render after I removed two trees. So practically only one instead of two or three species had.
Is this a bug? I don't know. Octane render maybe has problems with material from the Laubwerk. Can't be, that you can use only a tree. The store was covered so by the way, with 3700 MB!
Maybe memory problem? Compression or what because I know...

[kirbyzz]

my scene is growing and working is really hard on it currently because it´s super super slow... i mean changin tools, klicking checkboxen and working on geometrie and textures and lights and so on...

So i optimized it via xpresso for the function to deactivate all Cloners and converted all Boolean-Objects and so on .. now its a bit faster but working
is really really slow. But the scene is good optimized now.

i´m sure it comes from all octane-updatefunctions. update geometrie i have always off!
But if i deativate upfate for textures, prevs, light and cameras it´s not realy faster... i disabled all previous but it stays slow.

I kicked octane out of the plugindirectory and testet...everything fast and i could work...so it comes from octane.
May you optimize the update previews so it is possible to work inside c4d? Or to really deactivate them and to activate them if i want to rendern?
If i´m working i only need texture and lightupdate... if i want to render it can be slow..it´s ok..octane should render...but not if i want to work on the scene...for now i have to copy and paste everything in a new file ..make changes and put it back..in the current scene is working much to slow..

[aoktar]

@kirbyzz: are you working the scene that you showed to me? if you keep close Live viewer plugin will not check any updates on scene. Update geometry option is most dangerous option for very big scenes. It can trace everything on any little update and try to find needed updates. Some effectors/xpresso tags can affect mograph objects which has instances and can fire oftenly update calls. This can steal lot of cpu time.
But it should'nt be if you closed live vewer. Also when you disabled the "geometry updates" option.

[kirbyzz]

@kirbyzz: are you working the scene that you showed to me? if you keep close Live viewer plugin will not check any updates on scene. Update geometry option is most dangerous option for very big scenes. It can trace everything on any little update and try to find needed updates. Some effectors/xpresso tags can affect mograph objects which has instances and can fire oftenly update calls. This can steal lot of cpu time.
But it should'nt be if you closed live vewer. Also when you disabled the "geometry updates" option.

..you are right - i had the live viewer as tap. If i close the viewer/tab it´s faster. thanx

[kirbyzz]

ok..sometimes it works with disabeling all oct-updates and closing the liver-render-window but if i´m changing
between window to render and then go on working in cinema - cinema reacts very slow between camera moving, changin tools and klicks.

To deactivate octane for fluid working...i have to restart cinema and to deactivate everything in start or to remove the plugin while i´m working.
Its not only on big scenes .. now i have a smaller scene for building new objects and everything reacts slow to. Could you write an option to really deactivate it - so? While i´m working octane should not always listen to everything in the background ... i think he always tries to sniff out every klick...
That´s the same reason why i have to klick every Shortcut min. three times till tools were changed or someting react..... sometimes it worked and the shortcuts react very very bad from one moment to another...but all oct mats and everything is ready initialized..

An On/Off Button would be perfect.. i don´t know if this is so possible...