OTOY Forums

ChrisVis wrote:Hey aoktar,

downloaded the repacked 0.6.5 and deleted previous installation completely, but getting the same hang up at start up. (and I don`t have Octane in the C4D start up layout anymore).
I see the C4D start up layout but cannot do anything, the mouse symbol is cycling forever, so I can only close C4D through the task manager.

Maybe my bugreport could give some info why it doesn`t work for me?

When I replace the c4dOctane folder with the 0.6.4. files it works again...

are you sure not files on c4d main folder also?
do you have new.c4d? remove also.
If don't work also can you remove oct.dat from cinema4d prefs folder

hi aoktar,

deleting oct.dat doesn`t change anything.
And no, I don`t have any octane files in the main C4D directory, only
CINEMA 4D 64 Bit.exe
CINEMA 4D.exe
libfftw3-3.dll
libfftw3f-3.dll
libfftw3l-3.dll

Where can I find the new.c4d?

ChrisVis wrote:hi aoktar,

deleting oct.dat doesn`t change anything.
And no, I don`t have any octane files in the main C4D directory, only
CINEMA 4D 64 Bit.exe
CINEMA 4D.exe
libfftw3-3.dll
libfftw3f-3.dll
libfftw3l-3.dll

Where can I find the new.c4d?

can you remove this dll's? you dont have new.c4d

About the clone object or instances issue: I tried to recreate it with a new scene, but could not get the same strange results that I have with the project I am working on. So I compared the project settings and found the problem that I wasn`t aware of.
It has to do with the detail level settings of the projects... somehow it was set to 25% instead of 100%, so the open GL preview and the Octane Live preview didn`t show up all instances, but the picture manager renderer always does.
See the pictures above, I did a small test scene with some lights that shows the issue. So it is not a bug but something that might be helpful for anybody else to be aware of when working with instances.

aoktar wrote:

ChrisVis wrote:hi aoktar,

deleting oct.dat doesn`t change anything.
And no, I don`t have any octane files in the main C4D directory, only
CINEMA 4D 64 Bit.exe
CINEMA 4D.exe
libfftw3-3.dll
libfftw3f-3.dll
libfftw3l-3.dll

Where can I find the new.c4d?

can you remove this dll's? you dont have new.c4d

Should I have new.c4d? Is it needed somehow?

Removed the dlls but still same problem, same when also removed oct.dat.
Seems like I don`t get it to work, anybody else with same problem?
I stay with 0.6.4. so far, seems to be more stable then 0.5.9 for now.
Hope you can find the problem.
Thanks for your support.

This is my bugReport that had generated by c4d.
I have crashed all version since 0.42
What is the problem?

Here is my feature request. To make possible to overwrite GPU priority settings for the render settings.
Now there is only one global priority setting which work for preview render and for final rendering in the picture browser. But I would like to have dwo different setups:
- for preview purposes - use one GPU, and let the other one work for smooth display
- for final render - use full power of both GPU's to render faster.
Here is screenshot how it could look like.

I'm not sure if this is good place to submit requests and/or bugs. Let me know if there is any special thread for it.

Version 0.6.6 crashes on me....0.6.4 works fine



win 7 64bit i7 16mb ram R13

cyartist wrote:Hi This is how to install on Windows

1. Delete all octane files from the Cinema root folder
2. Put the c4dOctane folder into the plugin folder
3. Make sure the 64 lib folder and 32 lib folders are in the c4dOctane folder

If you do this is should work fine.


There is no need to put any files in the root folder in the newer versions.
Only the 0.50 version use the root folder installs.

This is not the case for my install. If I do not have octane.dll & octane.dat in my C4D root folder then C4D will not start!

I have now got 0.5.9 & 0.6.4 working (not tried 0.6.5 yet) by doing everything above plus:

4. Copying octane.dll & octane.dat from my Libs64 folder into my C4d main folder.

Hope this helps others.

However, @aoktar the combed histogram problem that I reported and attached a file for in 0.5.7 is still there in 0.6.4!!! Data loss in the image file is not good. Sadly I'm going to have to go back to 0.5.0 until you can confirm this has been fixed so there is no data loss in the final render.

Beta 0.6.6 crashes Cinema 4D for me.

I deleted the old 0.6.4 folder from the Cinema 4D plugin folder and put in the new 0.6.6 folder.