When I change to display mode raytracing, after patiently waiting for it to complete the 1000 cycles, a bit of the viewport looks like this:
If change something that forces a rerender (slight view move, turn on/off some layer) the view rerenders, but after 1000 passes it looks like this:
This happens whether the NVIDIA GeForce is on or not.
(by the way is there a way that you don’t have to click the bottom left to switch to NVIDIA?)
@nathanletwory is this for you?
Thanks, N
When you make the change does the view get blurry like that from the start, or only at the very end? I don’t see that behavior here. A quick guess would be maybe you have focal blur on?
Not sure what you mean by this. The only way to switch is through Tools > Options > Cycles, and after that by toggling the viewport away from Raytraced and back.
they are talking about when you click the label and it toggles showing what cycles is rendering with, and I guess they misinterpreted that as indicating a switch from cpu to gpu
I see. Indeed clicking the Raytraced name only toggles showing what the current render device is.
Yes, that was my misunderstanding. Thanks.
When I first change to DisplayMode Raytracing, the image gradually progresses in definition with each sample until 1000.
After completion of the 1000 samples, if, for example, I turn off a layer, rhino starts rerendering and gets to the state that is shown almost immediately (by the way the whole image is like that not only the detail), and does not progress anymore. However, the count of samples continues until 1000.
I need to go back to other DisplayMode and back to Raytracing for getting the definition.
No focal blur. And it would be visible also on the first pass, wouldn’t it?
side note: I updated two days ago the GPU drivers. Right now while raytracing is running, the computer fans are very audible, and if I type options nothing happens. I have to escape to do other commands, but it is not practical, of course, because it is extremely slow.
I tried with a small file,
After first pass of 1000 samples
and after turning off the blue layer and another 1000 samples
here’s the file
230308 Bug R7 Raytracing second pass fail.3dm (1.1 MB)
Thanks, N
I will check the file soon. In the meantime does this happen in Rhino 8 as well?
I am unable to reproduce result you are seeing.
The blotchy result look like a denoiser ran on a very grainy result. Did you use a denoiser?
I’ll install the denoisers to see what happens.
Addendum. I did install all three denoisers, and it looks like you have the Intel denoiser enabled.
If you disable it you’ll see that Raytraced keeps on refining. There is something wrong with the denoiser. But if you disable it, and enable for instance for a moment the Nvidia denoiser and disable it again then enabling the Intel denoiser again will show the expected result.
I hardly ever turn on denoisers, especially not in Raytraced, as that consumes unnecessary computation power while rendering IMO.
That is one for @DavidEranen as Raytraced doesn’t do anything with the post effect pipeline and denoisers other than providing the pixels.
@nathanletwory
I see, thanks. Yes, it seems that the Intel denoiser takes the initial very grainy image and stays there (the second time around). But on my side it happens also with the NVIDIA denoiser, I didn’t try the AMD.
My follow-up question is: is it normal that the final result of that small model takes 01:47 to complete 1000 samples, and the result is still rather grainy, especially in the darker areas?
Thanks, N
This is due to all lighting in these areas being indirect lighting.
FWIW Rhino 8 renders this much faster.
I think I know what’s causing this issue, and we are currently working on fixing it. I will let you know when we make some progress.
-David
Hi @nsgma,
Please try out the latest Rhino 8 release candidate (Rhino 8.6, released 12 hours ago) and let me know if it fixes the issue.
Help → Check for updates… → Update frequency: Service Release Candidate. Press Check Now.
-David
