ViewCaptureToFile / ScreenCaptureToFile mismatch

unhandled

#1

Hi all,

I’ve created a custom display mode, which also looks like this in my viewport:

The output I get by performing “ViewCaptureToFile” is somehow different, much darker:

By doing ScreenCaptureToFile, the result is however accurate:

Can somebody explain me why that difference occurs? Am I putting some settings wrong? Does this have to deal with shading/lighting/environnements stuff? I’m pretty confused about all possible Display Modes options…

Many thanks in advance!


#3

If you post your file it would probably help the big brains diagnose the issue.


#4

Hi, makes sense…

Please find attached the sample file + display mode export:

ViewCaptureToFile_issue.3dm (296.0 KB)
Pen_PRINT.ini (11.4 KB)


#5

@nathanletwory, @stevebaer. Are you the people to whose attention this should be brought ?


(Nathan 'jesterKing' Letwory) #6

@AlW this topic is already assigned to @jeff


#7

OK. Sorry.


#8

Hi,

Any news/update on that topic?
It seems the issue still occurs (Rhino 6 SR13 2019-2-4).

ScreenCaptureToFile:

ViewCaptureToFile:


(Jeff Lasor) #11

@jeffoulet

Sorry for the hold up, I’ll take a look at this today.

Thanks,
-Jeff


(Jeff Lasor) #12

The problem is easily reproducible here…and I’m seeing it with both versions of the capture command not just one.

It’s been written up: https://mcneel.myjetbrains.com/youtrack/issue/RH-50740

Thanks,
-Jeff


(Jeff Lasor) #13

Note: It has something to do with, and is related to the “Transparency” setting for the Object Color & Material usage.

-J


(Jeff Lasor) #14

I also just realized that you said “ScreenCaptureToFile” and not “ViewCaptureToFile”… Obviously ScreenCapture is going produce the correct results…all it does is snapshot the contents of the window… The ViewCaptureToXXX commands are lot more involved, and a lot more going on under the hood…which obviously is where the problem lies…and is why it happens in both ViewCaptureToFile and ViewCaptureToClipboard.

-J


(Jeff Lasor) #15

@jeffoulet Fixed!


#16

Hi Jeff,

Thank you!
I assume the fix will be shipped with the next release candidate?