If you’re doing a -_ViewCaptureToFile (or Clipboard) while the Raytraced viewport still has work to do it is going to affect the render speed. If I set Raytraced viewport to render 10 samples, then -_ViewCaptureToFile with 1000 samples takes about the same time as Raytraced viewport with 1000 samples.
I tried by pausing the raytraced viewport, and also setting sampling to low number so in background, still having problem with the output speed…
Below is with sampling set to 1 in viewport then ViewCaptureToFile.
3min on the viewport for 1000sampling… (18:53->18:56)
You are on a high-dpi screen right? In that case you probably see that the viewport renders at a lower resolution (larger pixel size). Capturing will ignore the pixel size, but render to the actual resolution. This will take longer.
Yes I’m on high-dpi screen 4K on 15inch, but viewport size seems same as the rendered image with ViewCaptureToFile since using display viewport dimensions(2958x1628)
The attached ViewCaptureToFile output is captured after doing 350 sampling in viewport and setting same 350 as capture option for number of passes.
Tried with 351 right after, and again slow compared to the viewport…
Not sure what I’m missing.
Actually crashed after fiddling some more…
Crashdump also attached.
It may impact performance for all sessions - each view and running capture is a session conducting a render. The more you stress your GPU the more you notice it in overall performance across running sessions.
I have now looked at your crashdump, it looks like a crash with setting colors to the image. This crash happens during fiddling with the settings for ViewCaptureToFile, but you haven’t pressed OK yet. Correct?