Yep, we have the first implementation @StefanW did of the OIDN for viewport 
But keep in mind that it only works when you use CPU as render device, if you use GPU (no matter if itās Nvidia or AMD) it does not work Iām afraid.
OIDN for viewport will be awesome. I definitely prefer OIDN over Optix in terms of IQ. I suspect on a modern CPU it wonāt be that much slower than Optix, but Iāll be interested to benchmark it once itās committed.
Also, it looks like with the change @brecht is doing, it will part of the render process as well, which is really nice.
Well, I can say that while itās fast, in a 2990WX is not as fast as Optix in a GTX1080 (which is not an RTX card), but I donāt know if that can be optimized and improved, I have no idea
Iāll have to do some benchmarking among my systems to get a sense of how OIDN scales with multicore. Maybe it works better with high frequency and fewer cores? I would be nice if the performance could be optimized, but the best solution is an OpenCL denoiser or OIDN adapted to work with OpenCL so that it would be fast on any OpenCL GPU.
Oddly enough, I found a post you made back in January asking a similar thing about RadeonProRender
Yep, but people that tested it told me that the results were far from optimal compared to Optix Denoiser and OIDN, Iām not sure about itās current status or results.
AMD RDNA 2 looks like it will be very fast and will include hardware ray tracing. Whatās not known yet is the software side. Iām hoping that they realize the importance of ray tracing beyond video games and provide a solid OpenCL-based denoiser (and render acceleration). However, it might be proprietary like Optix. I guess weāll find out in September.
The denoiser doesnāt work with the raytracking part of the hardware, the RTX cores, but with the AI part of it, the Tensor Cores, I imagine RDNA2 will also include some AI/ML oriented hardware.
Yep, weāll find out when RDNA2 is released
where can i find this file?
non RTX cards are already supported in 2.90 and 2.91, no need for you to modify any file
I use Gtx1080 + Gtx1070 together as CUDA devices on same pc. I tried my gpus as Optix devices and rendered ok with no difference in rendertime, say one given image 3 minutesā¦
And now that we can use Gtx gpu as Optix devices, what if I buy one Rtx 2060Super and try to render as Optix devices Gtx + Gtx + Rtx? The 2060S will benefit from its tension cores in that mix?
The 2060S will use the RT cores, yes. Those are not the same thing as the tensor cores, btw. Tensor cores are not used in Cycles that I know of, with the possible exception of the OptiX denoiser.
well Iām trying for the past hour already to get my 1080ti to work with 2070 super, all I get is Blender unresponsive or crash to desktop or some error code.
You should use the latest drivers, and right now better if you use Blender 2.92, are you using those two?
Yeah. Did clean drivers install, restart, and tried with 2.92 and the experimental builds. Are you saying that you have managed to make rtx and gtx card to work at the same time?
In the past, yes, GTX970 + RTX2080Ti, Iāll test later with 2.92 and tell you something
I just tested, the same GTX970 + RTX2080Ti, no problem at all, it worked fine, 2.92.
ok, I donāt know whatās different thenā¦ I tried CUDA, Optix, no dice. Even with default cube render preview didnāt load up.
Do both GPUs work one by one?
If itās unresponsive it might just be loading some stuff. It tells you something something āloading, might take a few minutesā - if thatās whatās happening, you really just have to wait for a few minutes during which Blender goes unresponsive. This is a one-time situation though. Once you waited through this, it will work quicker after.
That doesnāt, however, explain the crashes youāre getting. :-/
Lol wut. So with the latest versions of and especially Optix, 2070 super and 1080ti should work together? Waiting is not the issue. Thereās straight out crash to desktop or errorcode āinvalid ā¦ā Using newest game ready drivers. Both cards are even from MSI 