OTOY Forums

Follow up:

Reinstalled Octane, Cinema 4D, and DDU Nvidia drivers.


Rendering works fine with only 1 GPU enabled. When i enable my secondary GPU, I get crashing.


Same error as above happens when I have an empty scene and hit render.

ndreimi wrote:Follow up:

Reinstalled Octane, Cinema 4D, and DDU Nvidia drivers.


Rendering works fine with only 1 GPU enabled. When i enable my secondary GPU, I get crashing.


Same error as above happens when I have an empty scene and hit render.

Better to look for issues on your GPU/PSU and drivers.

Hello Ahmet, Good work!

Just a note, for me in the latest plugin the Medium in the material doesn't work. Whatever I put in it, Absorpsion, Scattering, nothing works, it does'n even trigger a refresh in the viewport or the material. It happens in Diffuse and Universal materials. I've got latest drivers and all. No need for a scene, I suppose, it happens in a new scene with a new material. Could you please check if that's the case?

Thank you in advance!

KOD

Hi Ahmet, i get crushes every 3-10-20 frames at randome time on my new project. What could be the problem?
Scene with only x-particles objects: Particles, OVDBMeshers.
I sent the scene file to your pm. Simulation takes a long time. The scene contains 3 particle systems, each of which has its own catcher object.

OctaneLog, Octane BugReport, Cinema BugReport
https://yadi.sk/d/vjsolUAFaOMz9A

Hi Aoktar.

Me again. I think i found a small error, just wanted to clarify. I assume there has been a few things changed with color spaces/linear and the inclusion of ACES etc in latest Octane..
im on oct 2020 ( latest) - Mac osx.

1st issue.
The first thing i've found is with LUT's if im saving out an EXR( octane) layered file.. the out always seems to be removed when i bring it into After effects. looks fine in Picture viewer but its gone in AE. tried various combinations or color spaces ( linear/tonemapped) but no luck. Is it possible to fix?

2nd issue
the depth is now seemingly ignoring the tonemapped settings.. So its always full white 32bit. I can get the details out of it if AE is in 32 bit mode. but otherwise its blank. Which would be fine except we don't always won't to composite in 32 bit mode ( much slower) . It may just be linked to hte same problem as above. But the way it was working in 2019.1.2. was great.. ( in my view).. but happy to be corrected on that.

i'd include a file but this happens in any scene with any set up.. so theres no need to include a file.

thanks for your help!
btw.. native noise inclusion is amazing! very helpful!
R

Hi Ahmet, is there any information about my problem? I was forced to switch back to rs again in this project, because the octane was again inoperative.

divasoft wrote:Hi Ahmet, is there any information about my problem? I was forced to switch back to rs again in this project, because the octane was again inoperative.

It's holiday here and caching takes hours. No time for this.

aoktar wrote:

divasoft wrote:Hi Ahmet, is there any information about my problem? I was forced to switch back to rs again in this project, because the octane was again inoperative.

It's holiday here and caching takes hours. No time for this.

I was hoping you could extract some information from the error reports.

Interesting issue here, mix materials cause a crash when trying to wire another mix material into it. In fact it renders my project files (and all backups with no materials) unusable with 'incorrect file structure' message.

Octane Scatter display type "object" doesn't work.

Is there any way to save Octane Scatter settings, node tree as preset ?