https://www.indigorenderer.com/forum/
https://www.indigorenderer.com/forum/viewtopic.php?f=10&t=15688
another nice joke... but this is reality:
i didnt save it, just made cube, started ipr and tweak the materials.pixie wrote: ↑Sun Sep 06, 2020 4:35 amDo you mind sharing the scene?wob wrote: ↑Sun Sep 06, 2020 3:08 ami 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
Alright, can you drop the snarky attitude towards long-time users? Thanks...
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?wob wrote: ↑Sun Sep 06, 2020 7:24 am
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
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 itwob wrote: ↑Sun Sep 06, 2020 7:26 ami didnt save it, just made cube, started ipr and tweak the materials.pixie wrote: ↑Sun Sep 06, 2020 4:35 amDo you mind sharing the scene?wob wrote: ↑Sun Sep 06, 2020 3:08 am
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
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.wob wrote: ↑Sun Sep 06, 2020 7:24 amanother 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
wob wrote: ↑Sun Sep 06, 2020 3:17 amnice joke
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).
no, no... even half functional gpu ipr much better then full working cpu ipr only
Thank you for the info.
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 wrote: ↑Mon Sep 07, 2020 4:16 amThank 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.
Ok, I found the problem. Please be specific... It only happens on the one machine with 2 logical processors, right?wob wrote: ↑Mon Sep 07, 2020 4:43 amno-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 absolutely shure this problem appears on pentium g4400, celeron g3900 / g3930 (both 2 cores / 2 threads processors)fused wrote: ↑Mon Sep 07, 2020 5:45 amOk, I found the problem. Please be specific... It only happens on the one machine with 2 logical processors, right?wob wrote: ↑Mon Sep 07, 2020 4:43 amno-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).
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.fused wrote: ↑Mon Sep 07, 2020 5:45 amOk, I found the problem. Please be specific... It only happens on the one machine with 2 logical processors, right?wob wrote: ↑Mon Sep 07, 2020 4:43 amno-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).
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'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.wob wrote: ↑Mon Sep 07, 2020 7:11 ami 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).