ScreenCaptureToClipboard Raytraced/Cycles Problem

Hello everyone,

I recently moved from Rhino 6 Win on Parallels to Rhino 6 Mac and couldn’t be happier. Thanks for the great work!

I just found a small annoying problem. If I let a Raytraced/Cycles view render for a while (e.g. sample 50) and then try to ScreenCaptureToClipboard, it refreshes the view and the capture is very low quality (sample 1).

But ScreenCaptureToFile works correctly, and captures the viewport in high quality (e.g. sample 50).

Any help?

Hi Pablo - I’m able to reproduce that on my Rhino 6 Mac here. It doesn’t happen on the WIP of Rhino 7 for Mac, though. I can’t find any relevant entries in the bug-tracking system and so I’m not sure what was changed. Perhaps @nathanletwory knows more…
Thank you for reporting.

BTW, just curious, what makes you use the ScreenCapture* commands over the ViewCapture* commands?

Hi Wim,
Thanks for your answer, I am just trying to make a quick capture of what I see on my screen. The ViewCapture* will start a new render if raytraced is selected, so then I have to wait for the render to finish.

So what I do is a screenshot (cmd-alt-shift-4), but its a little bit messy…

Hi Pablo - I think that the recommended workflow here is to set the Samples setting low in Preferences > Cycles and then, when you need a rendering, use the dashed version _-ViewCaptureToFile with samples set to your needed level.

@wim it sounds like the ScreenCapture* commands need some fixing to not trigger restarts of Raytraced - it’d do so for any engine integrating with the realtime RDK. Maybe you can create a YT item for that? Thanks!

@nathanletwory - I could do that, but the things is … this works as it should (i.e. without restart of Raytraced) on Rhino 7. So something already has been fixed. Are you saying that this fix should be ported to Rhino 6? I couldn’t find a YT for that fix and was wondering if you knew more about it…

Hmm, dunno. It is not something Raytraced itself can fix, it is the underlying pipeline through which a restart is signalled. Lots of changes already have happened in v7. It would be nice if the command didn’t trigger a restart in v6, though. It’d be for the ScreenCapture* and/or display pipeline devs to figure out what is happening there.

Hmmm… this is rather frustrating. It’s intermittent on the Mac, both RH6 and RH7.
@pablo2 - do you also see that ScreenCaptureToClipboard sometimes works just fine?

I just tried ScreenCaptureToClipboard a bunch of times and yes I got it working a couple of times. It seems completely random. Just using the keyboard and repeating the command, it works sometimes and fail most of the time.

Im on RH6 6.16

Thanks - I’ve filed this as RH-54443.

Hi Pablo - the developers looked at that issue and decided that it would be too much trouble to try to fix this. The recommended workflow is to either use the platform-specific way to capture the screen (on Mac the CmdAltShift4 combination that you provided above) or the Rhino ViewCapture* commands.

I think you probably mean CmdShift4
I personally prefer CmdShift5 which has more options - and also remembers the last used capture (or video) window :sunglasses:


1 Like

Hey Wim, thanks for the follow up.

I just found out by accident that I can just CmdC the viewport and paste it as an image in photoshop or in any app that support images! It works fine with cycles too…

It’s mentioned in the help, but I never bothered to look:


There’s also ViewCaptureToFile. Maybe that is an alternative …

What’s better with that command:
You can choose whatever pixel dimensions you want, it doesn’t belong to the actual screen size … :wink:

Oh wow, I didn’t know that :open_mouth: