Issue with legends when printing/exporting image

Hi again,

I have spent over 30 minutes looking at discourse.pollination and discourse.ladybug, so apologies if this has been asked before, but I could not find anything related, apart from this.

When I try to save an image from Rhino - by either printing, or using the captureViewportTofile - the on screen legend does all sorts of funny things

  • printing in different locations
  • printing multiple legends
  • printing in various scales (I understand this has to do with the DPI)

If I keep the resolution as per viewport, the export is fine.

changing it to any different resolution seems to break everything.

Same thing also happens with any 2D legend from visualizationSet in LB.

I have had this issue for sometime but I kept ignoring it as I tend to have my legends as seperate object in my reports, but now my students have the same problem so I thought I should stop ignoring it. #

1 Like

note: this is happening on both R7 and R8. (images above are from R7)

Thank you, @byron! I remember someone else also reported this to me before but I forgot to document it.

@mingbo should be able to help!

Thanks @byron, I will investigate this issue today.

Hi @byron,

I am testing the legends with captureViewportTofile, and I cannot recrate the issue that adds multiple legends on the output image with custom resolutions. I am using Rhino 8, what version of the Rhino 8 were you testing?

In terms of the scaling issue, including the preview window on captureViewportTofile dialog, it will take me more time than I expected. I will keep you updated on this.

Thanks again for reporting this issue.

Hi @mingbo,

thanks for looking into this.
Apologies but it seems that Rhino 8 does not have this problem anymore. I thought it did as I had that a couple of weeks ago.

The problem appears only in Rhino 7 for me now.

sorry @mingbo for the wrong reporting

Justed tested both Rhino 8 and Rhino 7 to be sure.

  • Rhino 8 works fine
  • Rhino 7 has the weird behaviour when changing resolution
1 Like

No worries at all, I think this might be a bug on Rhino side and it is fixed in the recent Rhino 8 releases, and Rhino 7 won’t have the new fix.

1 Like