SketchUp Import Issue - Textures and File Size

We’re running into similar issues noted in this previous post: Import SketchUp file bugs

Texture Scaling
SketchUp files imported with textures do not preserve texture scaling in Rhino

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?

I logged these issues as:

  • RH-65305 SketchUp Import: Incorrect texture mapping scale
  • RH-65306 SketchUp Import: Rhino file size gets extremely large

These issues are not publicly visible, I’m just providing the numbers for our internal reference.

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.


1 Like

Opening as meshes will also significantly cut the time it takes to open a SketchUp file.

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.


1 Like

We’ll give that a look. Thank you!

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.

Coming back to this old thread now that we’re migrating to Rhino 8.

If you import as a mesh, and you chose not to join faces at import, it fixes the texture scaling issue. However, this still results in a long file import time (15+ minutes), an enormous file size that is essentially unusable due to all the separate faces, and very slow viewport performance (5 minutes to move from wireframe to rendered mode).

What are are looking for is a clean way to work with other consultants in SketchUp but we are in Rhino. I am curious if we are missing something.

Shane -

I am taking a look at your files here. I will start with some benchmarks to get some good baselines.

At this point you are not missing anything, as the geomtry doesmove back and forth. The problem of course is the different representations in each product.

Sketchup uses a lightweight Ngon geometry. It can be quite efficient, although limited in form.

In Rhino we have two options that are not as efficient. Although can be used in advanced forms.

It is navigating between these two that we need to decide what we can do.