2D of 3D scanned 2M poly mesh

[Holo]

@wim and @pascal
Hi guys, are there any fast ways to make a 2D image of a scanned mesh?
I have gotten descent results by reducing it to 90% and using a modified technical display mode with no hidden lines and a custom material + custom ambient light:

I’m working on helping out the Viking Museum to document their scans. And we’d prefer to not jump through too many loops to get a good result.

Current issues I meet now is:

• Technical display mode takes long to calculate even on a 200K model.
• Technical data is recreated on file open, it appears to not save this with the model and that makes opening the file very slow. This is a bummer if we use the technical display mode in a layout.
• If I annotate the mesh model and then run Unweld on it (as an example) then the annotations are all over the place since I guess Rhino makes new vertices and messes up the old list of vertcies, so now the annotations snaps to the wrong vertices.
• If I use make2D instead then I get a different result that doesn’t look as good:
  
  
  
  Is there a chance Make2D in the future could reuse the technical data from technical display mode in some way?
  And 3D PDF’s has a 2D mode that is instant, as it uses a simple shader that could be good enough in many situations, could Rhino get something like that that doesn’t require any calculations for the technical display modes? If so we could probably use the original 2M scan and it would be a huge time saver.

Another thing: Rhino needs an to be able to save the custom and altered displaymodes used in layouts, as depending on custom display modes is a huge culprit when customers are working on multiple machines IF (when…) the display mode used is not installed.

Thanks for taking the time to read this.

[pascal (Pascal Golay)]

Hi Jorgen - I guess these would be questions for @GregArden and @jeff - I see one or two things that could make but track items, but more generally, those devs will surely have more useful things to say.

-Pascal

[Holo]

Oh, and two more things when printing to PDF:
Rhino needs to remember the DPI setting for the layout! Please look into this! Or at least lower the default dpi to 300. 600 dpi at A0 is slow, makes huge files etc.

And I still see odd miss alignments between the detail and the annotations in the layout when I use the Rhino PDF printer:

But this doesn’t happen if I export the layout to PDF from the “save pull down menu”:

And there the default dpi is 300…