Indigo for Cinema 4D 4.4.12.1

[wob]

nice joke at first indigo must support more then 2 gpus )

Not sure what you mean - Indigo supports as many as you want and since 4.4.10 has near-perfect scaling on NVIDIA GPUs (there was a bug slowing it down before).

another nice joke... but this is reality:

tested with 3 1070, 3 1060, 4 1060, 5 1060, 5 1070 etc... the same result

417.22 - 452.06 nvidia drivers / studio, gaming / the same result - on any windows pc. only 2 cards really supported (4.4.5 - 4.4.10)

p.s. it was my advice here to fix nvidia gpu scaling because it was very ugly when 2 gtx gpus render scene slower then one

[wob]

Well, I cannot reproduce your problem wob

i created cube, created new material, add it to cube (irp didnt update new material on cube), then create another (second) indigo's material, and try to change color in fristly created material. so, material preview (ball) didnt change color, and cube in ipr screen also didnt change color to new color. so i got 3 different colors - on cinema 4d viewport, on indigo ipr and on material preview for the one object with one material).

Do you mind sharing the scene?

i didnt save it, just made cube, started ipr and tweak the materials.

[Oscar J]

another nice joke... but this is reality:

Alright, can you drop the snarky attitude towards long-time users? Thanks...

Clipboard01.jpg

tested with 3 1070, 3 1060, 4 1060, 5 1060, 5 1070 etc... the same result

417.22 - 452.06 nvidia drivers / studio, gaming / the same result - on any windows pc. only 2 cards really supported (4.4.5 - 4.4.10)

p.s. it was my advice here to fix nvidia gpu scaling because it was very ugly when 2 gtx gpus render scene slower then one

Other users have been running multi GPU setups fine, and going by your post history this is the first time you're reporting this bug. How do you expect developers to fix issues you aren't reporting?

[pixie]

i created cube, created new material, add it to cube (irp didnt update new material on cube), then create another (second) indigo's material, and try to change color in fristly created material. so, material preview (ball) didnt change color, and cube in ipr screen also didnt change color to new color. so i got 3 different colors - on cinema 4d viewport, on indigo ipr and on material preview for the one object with one material).

Do you mind sharing the scene?

i didnt save it, just made cube, started ipr and tweak the materials.

As I've told you, I cannot reproduce it. If you do the same perhaps on your part it will behave the same and then you can share it

[pixie]

nice joke at first indigo must support more then 2 gpus )

Not sure what you mean - Indigo supports as many as you want and since 4.4.10 has near-perfect scaling on NVIDIA GPUs (there was a bug slowing it down before).

another nice joke... but this is reality:

Clipboard01.jpg

tested with 3 1070, 3 1060, 4 1060, 5 1060, 5 1070 etc... the same result

417.22 - 452.06 nvidia drivers / studio, gaming / the same result - on any windows pc. only 2 cards really supported (4.4.5 - 4.4.10)

p.s. it was my advice here to fix nvidia gpu scaling because it was very ugly when 2 gtx gpus render scene slower then one

Well my suggestion would be to do a clean install with the latest nvidia drivers, and do not forget that your scene is always bound by the slowest card, meaning if you have 3 cards with 8gb and one with 3gb the scene will have to fit in only 3gb and perhaps you're slowest card can also hinder it too. And don't always assume that indigo is to blame, indigo cannot assert for each and every motherboard+gfx card configuration out there, so when you're amongst the few complaining about this issue, then perhaps, the joke is on you.

[fused]

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

[fused]

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.

[pavoda]

It is time to realtime rendering on GPU and new RTX 30..It will be so fast and confortable if Indigo can realtime building scene like on CPU. I hope it will be soon.

nice joke at first indigo must support more then 2 gpus ) and you will get around 2-4 minutes per frame with complex (more thn 100 mln polys / more thn 1000 objects) 1440p scene with 8 new rtx3080.

p.s. just 2.5x of speed up, compare with 1080

Clipboard01.jpg

but you can use unreal or blender eevee with its ugly realtime screen space reflections, gi and ao now without rtx (i m not sure about unreal + rtx speed on complex scenes, small scenes renders fine with rtx).

I mean realtime rendering for preview, not for final image..work well now for cpu, but it is not very fast.

[wob]

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

no, no... even half functional gpu ipr much better then full working cpu ipr only

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

[fused]

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 about SetThreadGroupAffinity? You should, as it's not related to GPU rendering at all.

Also, are you running any third party tools that do anything to process priority, cpu affinity, or anything like that? If yes, please try running Indigo without those.

[wob]

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 about SetThreadGroupAffinity? You should, as it's not related to GPU rendering at all.

Also, are you running any third party tools that do anything to process priority, cpu affinity, or anything like that? If yes, please try running Indigo without those.

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

[fused]

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

Ok, I found the problem. Please be specific... It only happens on the one machine with 2 logical processors, right?

It's not a problem on the others?

P.s.

If you are still experiencing less than ideal scaling with multiple GPUs, have you considered your CPU may be the bottleneck?

[wob]

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

Ok, I found the problem. Please be specific... It only happens on the one machine with 2 logical processors, right?

It's not a problem on the others?

P.s.

If you are still experiencing less than ideal scaling with multiple GPUs, have you considered your CPU may be the bottleneck?

i absolutely shure this problem appears on pentium g4400, celeron g3900 / g3930 (both 2 cores / 2 threads processors)

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

[wob]

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

Ok, I found the problem. Please be specific... It only happens on the one machine with 2 logical processors, right?

It's not a problem on the others?

P.s.

If you are still experiencing less than ideal scaling with multiple GPUs, have you considered your CPU may be the bottleneck?

do you assign one core to one card or one thead to one card? do i need to use icore i3 (2 core / 4 threads) or icore i5 (4 core / 4 threads) to run rendering with 4 cards? better, find the way to ideal scale gpu's count without linking to count of core / threads. it's posible because another renders can do it.

[pixie]

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.