i dont know why, but this small funny element of the large scene guaranteed crashes cindigo 4.4.13.1 (before bulding phase), but renders fine with 4.4.12: Clipboard01.jpg c4d scene file (tested with s22 and r23): indigo_crasher.zip I looked into it and made a new build, replacing the 4.4.13.1 build...

i tested just now multi-gpu 4.4.13 fix (for 2 cores CPU), and can say, indigo can render picture with 3 gpu and one 2 core processor now (pentium g4400). but gpu utilization with 3 gpu cards is lower (cpu utilization is 100%), than with 2 cards (cpu utilization is 85-90%). i'm afraid, system with 4...

i dont know why, but this small funny element of the large scene guaranteed crashes cindigo 4.4.13.1 (before bulding phase), but renders fine with 4.4.12:
c4d scene file (tested with s22 and r23):

i tested just now multi-gpu 4.4.13 fix (for 2 cores CPU), and can say, indigo can render picture with 3 gpu and one 2 core processor now (pentium g4400). but gpu utilization with 3 gpu cards is lower (cpu utilization is 100%), than with 2 cards (cpu utilization is 85-90%). i'm afraid, system with 4 ...

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...

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...

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 it...

very nice. still waiting for scatter.

this element of large scene guaranteed crashes with new 4.4.12-4.4.13 cindigo exporter:
exports fine only with 4.4.10

* Updated to Indigo 4.4.13 SDK.

very nice! what's about standalone 4.4.13?

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...

fused wrote: ↑

Mon Sep 07, 2020 8:23 am

Bug is fixed.

edit: please be calm in here

do you mean groupaffinity error bug? where can i download fixed updated beta (preferably with standalone?)

what's about new 4.4.10 bug with network rendering, when network client guaranteed crashes with more then 1 gpu?

i have expirience of rendering with redshift, octane and thea renders on this platforms (up to 6 cards) and it works fine. it's not a good idea, very bad idea to use one cpu core / thread for controlling every single gpu because many motherboards can support up to 12 pcie cards and even i7-9700 has...

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)....

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)....