Indigo for Cinema 4D 4.4.12.1

[fused]

Bug is fixed.

edit: please be calm in here

[wob]

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 8 threads only (i imagine, good minded man will not use server's xeon / threadripper configurations for multipurpose home render systems).

I'm pretty sure that once had problems with indigo not recognizing my gfx card, but I'm also pretty sure that once I got it figured out and drivers sorted out all was working well. If you go to benchmarks you'll see tons of multiple gpu configuration, and it seem that you are the first having problems. So don't be so hasty in blaming indigo, namely when people are trying to see what is the problem you're having.

indigo has system requirements:

Windows:
64-bit x86 CPU with SSE4

https://www.indigorenderer.com/document ... quirements

not a single word about count of cores for similar count of gpus.

[wob]

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?

[fused]

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, did you describe it anywhere?

[wob]

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, did you describe it anywhere?

i wrote about it to ono's mailbox here: if you run network slave with 2 gpus (4.4.10), it crashes after "starting rendering thread". 4.4.9 network slave works good. 4.4.10 network slave works only with 1 gpu (nvidia, windows). i think this problem appears with new opencl 4.4.10 tweaks. 4.4.10 network slave crashes with any scene (simple cube + sky for example).

another (smaller) network render trouble: rendering process on master doesnt stop on halt spp limit reached because master freezes in pause mode (4.4.8 or 4.4.7 innovation) on rendering end and nework slave doesnt recognize this render end on master - it "thinks" master still works. it's normal for single frame renders, but not suitable for animations (last frame gets much more spp than previous frames).