Without knowing anything about that log stuff: did you think about trying a new 391. driver? There have been some.useruser wrote:( nividia driver version 390.77, 2 GTX 980Ti )
Probably that helps.
Moderators: ChrisHekman, aoktar
Without knowing anything about that log stuff: did you think about trying a new 391. driver? There have been some.useruser wrote:( nividia driver version 390.77, 2 GTX 980Ti )
Are you aware of that you have ZERO of free vram. Remove redshift and try again.jmd wrote:Hi, I was using Red Shift but wanted to give Octane another try. Updated all of my NVIDIA drivers, and the most recent 3.08 Octane. Here is the issue I keep having which make it unusable.
Could you please explain crashes? Could you share any scene with steps to reproduce that crashes? For my side, plugin part is not less solid but new nvidia drivers are really bad.useruser wrote:it seems as if all 3.8-versions are not running as long the redshift-plugin is installed.
it works without any problems with octane R 3.07.
i uninstalled the redshift-plugin and now octane ( R 3.08RC-3) works again.
but a lot of crashes with older project. when i try to export to live-viewer octane crashes c4d ( render failure ) cant open the log-file because i have to quit c4d via taskmanager ( not responsive)
It's not a bug, you push the cpu to under very high amount calculation. Keep away is very cpu extensive calculation, go with small increments on value changes.offrench wrote:It seems I found a bug with Octane scatter in this release.
I am using a scatter on a small number of objects (35) on a terrain.
When I click on the keep away dial, C4d freezes and the CPU starts to work at 100% until I stop the task.