OTOY Forums

Guy_frog,
İ don't understand you here. Issue cannot be related with my plugin. Could you attach a bugreport? And what's highest amount of free vram with a smaller resolution which is not crashing?

aoktar wrote:

Raoul wrote:Hi, some great features in this release.
Unfortunately I'm getting a lot of freezes in Cinema with this latest version ( hadn't tried earlier versions of 2018) . Almost always when I'm adjusting materials.. node editor or just the normal material editor.
Need to force quit C4D, so don't get logs. Also nothing shows in the octane log if i have that open during the freeze.
I don't have this problem with V4 .. only with 2018.

Any thoughts?

Extra info:
Mac Pro MacOS Sierra.
C4d R19.068
gtx1080ti

Did you keep "synchronisation with geo updates=OFF" in settings?

Hey thanks for the reply. Yes, I have Sync with Geo updates turned OFF.. i.e. NO tick in that box.
Any other settings i should look at? seems to be related to generating material preview updates etc.

aoktar wrote:Guy_frog,
İ don't understand you here. Issue cannot be related with my plugin. Could you attach a bugreport? And what's highest amount of free vram with a smaller resolution which is not crashing?

Hi Aoktar,
Sorry, but C4D doesn't create BugReports file for this crash. The smaller resolution which is not crashing is 5700x5700 pixels. For this resolution, during render Vram is 1.099Gb/7.563Gb/11Gb (Used/Free/Total). Above 5700x5700 pixels and up to 6000x6000 pixels resolution, C4D freezes at the end of rendering and still unable to save the image. Above 6000x6000 , C4d crash and closes by itself at the end of rendering.

I'm having the same issue as Raoul. I had mentioned it on the mograph slack a few days ago. I turned off the sync on geo updates and it now crashes a lot less, but still does it fairly often. It does always seem to be either when working with materials or updating the scene. I tried checking the log after restarting C4D but I guess it doesn't get saved (it was empty).

C4D R20
2018.1.3 (had same issues with all 2018 versions)
Mac OS High Sierra 10.13.6
CUDA 410.130 (newer version gives render errors)

Joey

wafflelad wrote:I'm having the same issue as Raoul. I had mentioned it on the mograph slack a few days ago. I turned off the sync on geo updates and it now crashes a lot less, but still does it fairly often. It does always seem to be either when working with materials or updating the scene. I tried checking the log after restarting C4D but I guess it doesn't get saved (it was empty).

C4D R20
2018.1.3 (had same issues with all 2018 versions)
Mac OS High Sierra 10.13.6
CUDA 410.130 (newer version gives render errors)

Joey

you can grab bugreport.zip and send. Also activate log outputs from settings/other and send "c4doctanelog.txt".

Raoul wrote:Hi, some great features in this release.
Unfortunately I'm getting a lot of freezes in Cinema with this latest version ( hadn't tried earlier versions of 2018) . Almost always when I'm adjusting materials.. node editor or just the normal material editor.
Need to force quit C4D, so don't get logs. Also nothing shows in the octane log if i have that open during the freeze.
I don't have this problem with V4 .. only with 2018.

Any thoughts?

Extra info:
Mac Pro MacOS Sierra.
C4d R19.068
gtx1080ti

Hi Raoul have you seen this topic?
viewtopic.php?f=30&t=71514

[/quote]you can grab bugreport.zip and send. Also activate log outputs from settings/other and send "c4doctanelog.txt".[/quote]

Oh, that helps. I just got a full crash while loading an image into a material (not the usual freeze). The logs are attached.

Joey

DWAA/DWAB EXR implementations don't seem to be working yet. We've trying to render out DWAB at the moment but After Effects is saying they are Zip16 and they are much bigger files than we would expect to get from DWAB.

chrisbrearley wrote:DWAA/DWAB EXR implementations don't seem to be working yet. We've trying to render out DWAB at the moment but After Effects is saying they are Zip16 and they are much bigger files than we would expect to get from DWAB.

You need to use the EXR(octane) setting for the compressions to work on passes.

First project using Octane AND C4D (normally maya guy)....

I'm running into issues with the Cryptomatte output going into Nuke. When I apply the cryptomatte node in Nuke to break out my objects and then comp them back together, I notice some fringing in the alpha. I fiddled around with unpremultiply in the Cryptomatte node in Nuke but it doesn't seem to help. I premultiplied each one before I merged and the same thing. I then tried using the Take System inside of C4D to try to help me out but I noticed in one of the takes, I see a black fringe in the Crypomatte object pass in the Octane Live Viewer. I'm wondering if something is wrong with the crypomatte functionality. I've tried various OctaneEXR compressors (RLE, ZIPS, DAWA, etc).






Separate issue... I figured since my cryptomatte passes weren't working as I would have thought, I tried the old Render Layer ID passes. When bringing those into nuke, I noticed the colors were muted.. (eg, not 255, 0, 0 for red). When I shuffled the Red to Alpha, the alpha was not at 100% black and white. I tried using a Grade node to boost the gamma on the Alpha but then I saw artifacts starting to appear in areas where it shouldn't. Is there something I should be doing differently?