Also it only happens in Cycles render engine not Eevee.
Yeah I also dont have it, but some others had it on nvidia gpus aswell and on AMD its definitely awell, so if you want to know make sure you did turn on AGX as viewtransform.
So, is this a bug? Who’ll file the report?
AGX is on by default.
Hmm
I treid your file and did not have the problem.
So looking at the settings found that the problem is only when Denoise is turned off (I have denoise turned off in my startup file.)
Try turning off denoise and see if you get the problem.
This gets even more weird!
Also I have found that with final render if denoise is turned off then the problem is still there after render (does not “flip” to correct after render).
Render finished NO denoising.
In my startup file I had denoising turned off in viewport and on in render, which is why it was fixing the problem at the end of render.
So it looks like denoising was the missing calculation. Denoising fixes it.
Try turning off de-noising and tell us if you get the problem.
Cool, you nailed it. ![]()
I always turn on denoise for viewport & render anyway.
Unfortunately I hate the blotchy de-noising in viewport.
![]()
It is still a weird problem.
I get the same problem with AGX in all the versions I have when denoising is TURNED OFF (4.2, 4.3 and 4.4)
Nvidia 3060
Secrop wanted to take a look, but otherwise…its there, its definitely reproducable, it smells like a bug it looks like a bug…
Maybe some hardware models dont have it in some cases, but that can have quite some reasons from drivers to the specific implementation and doesnt change that other models have it.
Someone should file a bug report.
It definitely looks like a bug!!
But I think it has not much to do with Cycles kernel, but with some library it is using (i.e. the denoiser or oiio)…![]()
I still don’t know which (didn’t had so much time to dig into it)… and I might also be wrong…
I’ll start a new ‘issue’ tomorrow, if by then no one else have this reported. … i’m too tired right now, to do it properly.
Yeah, I wont report it, I think its better if someone where it doesnt work in 4.3 is posting it. So… ![]()






