Can’t recall that this has been as bad as in the current build.
Raytracing is completely hogging the entire computer for the time of the render (and, btw, it starts from scratch for any viewport capture).
Computer becomes sluggish, almost unusable, until render finishes.
Rhino 6 (6.23.20055.11282, 2020-02-24)
AMD Radeon Pro Vega 48 (8GB)
When you start a new viewport capture do you use the dashed command, and does the panel on the left change size? If it does the viewport will change size, which triggers a restart. Changed size also means differences between vp and capture settings.
Further there has between 6.21 and 6.22 only one fix for Raytraced, nothing else has changed since.
Tried now and yes, this helps. Rendering is now done on CPU, using all cores. Computer stays responsive.
So it seems the issue is with Rhino’s usage of the GPU?
Is the dev. team aware of it and is there any solution being worked on?
I am using the exact VP size. I noticed that the “Transparent Background” might be the reason. Even if there is no actual transparent background (e.g. entire image is filled with objects), this does seem to trigger a re-rendering of the scene.
In any case, would be very desirable for this not to happen.
This is a common problem when using GPU-based rendering when using the only GPU on your machine can do this. The best I can advise is to use CPU on the viewport and GPU for when you want to do an actual render.
If there is any setting different in the view capture dialog from what you have in the regular settings there will be a complete rererender.
Don’t use the Intel one, that is in my experience worse than the Radeon Pro. That said I don’t have much experience with neither the Intel GPU nor the AMD GPU on OpenCL on the Mac, so can’t really say one way ore another.