Page 2 of 2

Re: Indigo Dev Update Q4 2020

Posted: Sun Nov 08, 2020 11:41 am
by mpro31
Hi fused, that's great news for the future of Indigo, I wish Metal performs better that OpenCL in MacOS, especially with the newly released AMD rx 6000 series.

I would like to ask you also, if you have any other plans feature-wise to share with us. Projection lighting for example is a feature I would like to see in Indigo, or this is a matter of plugin development?

Re: Indigo Dev Update Q4 2020

Posted: Mon Nov 09, 2020 2:30 am
by fused
mpro31 wrote:
Sun Nov 08, 2020 11:41 am
Hi fused, that's great news for the future of Indigo, I wish Metal performs better that OpenCL in MacOS, especially with the newly released AMD rx 6000 series.
Hi mpro31,

the thing with all these different compute APIs is, that they will all roughly run at the same speed, internally they all use the same compiler, output the same bytecode which then runs on the same hardware. So don't expect Metal to run any faster than OpenCL. :)

What Metal allows us to do, though, is to tap in to hardware accelerated ray tracing. Which should result in increased performance on devices that support it.
mpro31 wrote:
Sun Nov 08, 2020 11:41 am
I would like to ask you also, if you have any other plans feature-wise to share with us. Projection lighting for example is a feature I would like to see in Indigo, or this is a matter of plugin development?
I'd say that is a core feature of Indigo, and I'm wondering if it can't already be done with a texture in the emission channel and a fitting IES file. Maybe...

Although it would be nice if Indigo could do that without the need for an IES.

edit: I tried, that doesn't work :) it would be a nice addition

Re: Indigo Dev Update Q4 2020

Posted: Mon Nov 09, 2020 3:43 am
by mpro31
thanks for the reply fused,
the issue with lower opencl performance in macOS compared to Windows (-40% speed) isn't a matter of opencl drivers?

also glad to read about for the projection lighting feature note :D

Re: Indigo Dev Update Q4 2020

Posted: Mon Nov 09, 2020 4:32 am
by fused
mpro31 wrote:
Mon Nov 09, 2020 3:43 am
thanks for the reply fused,
the issue with lower opencl performance in macOS compared to Windows (-40% speed) isn't a matter of opencl drivers?
I wasn't aware of this. In Indigo, compared to running on Windows through bootcamp?

My statement was more about the theoretical.

But I'm also seeing some difference in Cuda performance between Windows and Linux, so I shouldn't be too surprised. :)

Re: Indigo Dev Update Q4 2020

Posted: Mon Nov 09, 2020 7:26 am
by mpro31
Exactly, compared to your benchmark page, Windows/ bootcamp results are on track, while macOS is lower, but my system is old (nvida 980) and drivers may be the issue

Re: Indigo Dev Update Q4 2020

Posted: Mon Nov 09, 2020 10:49 am
by ErichBoehm
I think this tech is very neat, but it would be very helpful to see some UI change, such as an "undo/redo" buttons and a "history" window like Photoshop. Hope everyone is staying safe.

Re: Indigo Dev Update Q4 2020

Posted: Thu Nov 12, 2020 7:07 am
by Lal-O
fused wrote:
Fri Nov 06, 2020 1:19 pm
Lal-O wrote:
Fri Nov 06, 2020 1:04 pm
Will it be possible to use CPU and GPU for rendering at the same time? :D . ( I hope is not a silly question :? )
Not at all :)
It came up in our discussion, but I can't really give you an answer on that, for now.
Thx for the reply fused :D

Honestly, i think it would be a great move to be able to render using CPU+GPU, everything here is about speed (Indigo already has the quality :wink: ). Look at Lumion, its render quality is not even close to indigo and is very popular (i don't like it much by the way :P ).
Most of the greatest rendering engines (except Maxwell Render) are using Hybrid rendering methods to improve rendering times...Vray does, Thea Render does, Why not indigo? :wink:. I mean,we have the best render engine, right? Sooo... Just sayin' :D

Re: Indigo Dev Update Q4 2020

Posted: Mon Nov 16, 2020 6:10 am
by schwungsau
did you ask vray and thea user if they actually using cpu or GPU ? adding CPU gives only 20% more speed with 10 core i9, in most scenes even less. unless you 64 core threadripper. using moth makes scene laggy too.

i prefer to 2:30 minutes for print rendering and have a "workable" computer then have the rendering done 15 minutes earlier.

Re: Indigo Dev Update Q4 2020

Posted: Tue Nov 17, 2020 3:17 am
by Zom-B
schwungsau wrote:
Mon Nov 16, 2020 6:10 am
did you ask vray and thea user if they actually using cpu or GPU ? adding CPU gives only 20% more speed with 10 core i9, in most scenes even less. unless you 64 core threadripper. using moth makes scene laggy too.

i prefer to 2:30 minutes for print rendering and have a "workable" computer then have the rendering done 15 minutes earlier.
Its start to be interesting for animations, since extra 20% of speed in a movie that would render for 2 weeks is saving 3days.
And my Threadripper gets very competitive to the GPU if you start rendering foliage scenes where a very high raydepth is needed...

Re: Indigo Dev Update Q4 2020

Posted: Mon Nov 23, 2020 11:37 pm
by Life
Proposal ,Add the function of automatically saving IGI.

Re: Indigo Dev Update Q4 2020

Posted: Tue Nov 24, 2020 12:32 am
by Zom-B
Life wrote:
Mon Nov 23, 2020 11:37 pm
Proposal ,Add the function of automatically saving IGI.
This is available since Indigo v1.
What 3D app do you work in, maybe somebody can guide you to the right checkbox :)

Re: Indigo Dev Update Q4 2020

Posted: Sat Nov 28, 2020 10:20 pm
by fourzeronine
Any chance in looking at integrating USD Hydra Render Delegate? Would be nice way to have Maya and Houdini support. ;)