another very old "classic" problem of indigo. alpha channels work very very very bad: CLOUDS_ALPHA_TROUBLE.jpg it depends too much on GPU Max Ray Depth parameter. In complex scenes this problem appears up to 10 (!) GPU Max Ray Depth (10 MRD - it means long rendering time). And you never know when i...

yonosoy wrote: ↑

Wed Sep 16, 2020 12:57 pm

Thank you!

Waiting for code in the absorption ans SSS definition, the inclusion of mie cumulus as phase function, the inclusion of maximum extincion coefficient value, ...

Thanks again.

I have added a ticket for that, will happen eventually. I really have to do some work on 3ds max now

Indigo for Cinema 4D 4.4.13.1 R20 version supported: R20.059 R21 version supported: R21.207 S22 version supported: S22.118 R23 version supported: R23.008 Windows: Indigo Renderer: indigo-for-cinema-4d-4.4.13.1-installer.exe - Includes installers for R12 - R19 indigo-for-cinema-4d-R20-4.4.13.1-insta...

Ilay wrote: ↑

Mon Sep 14, 2020 6:09 am

Thank you for reply. Will wait

Seems to work ok. Soon.

Ilay wrote: ↑

Mon Sep 14, 2020 2:51 am

Hello
fused, CIndigo does not support scene-nodes?

Not for the moment, I'm afraid.

wob wrote: ↑

Sat Sep 12, 2020 8:08 am

this element of large scene guaranteed crashes with new 4.4.12-4.4.13 cindigo exporter:

ocean.zip

exports fine only with 4.4.10

Thank you, I'm looking into it.

Indigo for Cinema 4D 4.4.13 R20 version supported: R20.059 R21 version supported: R21.207 S22 version supported: S22.118 R23 version supported: R23.008 Windows: Indigo Renderer: indigo-for-cinema-4d-4.4.13-installer.exe - Includes installers for R12 - R19 indigo-for-cinema-4d-R20-4.4.13-installer.e...

do you mean groupaffinity error bug? where can i download fixed updated beta (preferably with standalone?) It will be in the next release. 4.4.13. :) what's about new 4.4.10 bug with network rendering, when network client guaranteed crashes with more then 1 gpu? I don't know anything about that bug...

Bug is fixed.

edit: please be calm in here

no-no, SetThreadGroupAffinity error appears ONLY in gpu mode with MORE thn 2 cards (3 or more). 1 and 2 cards work fine. i think this is some sort of opencl threads synchronization error but i'm not sure because i dont know much about opencl programming (i have only nvidia cards, have no amd gpus)....

i tested it on asus z270p + celeron g3900, msi z390 mortar + intel core i7 9700f, and that screenshot from asus z270h strix gaming board + intel pentium g4400 cpu, all platforms windows 10 pro 1909, 24 gb ram Thank you for the info. Does CPU rendering work for you? Or do you get the same error abou...

wob wrote: ↑

Sun Sep 06, 2020 7:24 am

Clipboard01.jpg

Thank you for reporting this bug.

It's entirely unrelated to GPU rendering. Does CPU rendering work for you?

I'd be interested to know you system specs, CPU(s?) especially.

This is the reason why I feel GPU should not be an option for IPR right now, until Indigo core fully supports it.

Indigo for Cinema 4D 4.4.12.1 R20 version supported: R20.059 R21 version supported: R21.207 S22 version supported: S22.118 Windows: Indigo Renderer: indigo-for-cinema-4d-4.4.12.1-installer.exe - Includes installers for R12 - R19 indigo-for-cinema-4d-R20-4.4.12.1-installer.exe - Includes installers ...

Funny, we were just discussing that.

It's a new bug added in 4.4.12, I think. Will hopefully be fixed soon.

(it happens when you add an object that is larger than the original scene bounds)