This can be super important for understand overall design moves by our design partners. We’re trying to standardize on Rhino internally, but are finding we have to launch SketchUp to view their files properly.
Rhino file size
A SketchUp file size of 109MB balloons to 1.4GB when imported into a clean Rhino file. I believe the SketchUp file makes heavy use of blocks (or similar). What are we missing?
One thing I noticed on RH-65306 is that you have the import set to trimmed planes. That could have a very serious impact on the size of the Rhino file. You’re making polysurfaces out of each SketchUp mesh. Unless you have a specific reason where you need the polysurfaces instead of the mesh, choose mesh. When I open your .skp file with the radio set to mesh and immediately save the file as a 3dm, it’s 68Mb.
I just got to thinking that importing as meshes may make the texture coordinates (TCs) better. At least the TCs that are in the file will end up on the mesh in Rhino. When you pick trimmed planes all of that information in the SketchUp file is not even used. TCs in SketchUp (SU) are tricky though and I plan on having someone much smarter than me look at the code that converts them from SU to Rhino.
It looks like importing your file as meshes did not have an impact on the texture coordinates. I’m working with someone who knows that stuff well to, hopefully, get that fixed up.
We seem to be having some more success on the texture issue being resolved when importing as a mesh.
Also very happy the filesize is more manageable.
Now we just need to get the team used to working with mesh editing.
