Question-and-Answer Resource for the Building Energy Modeling Community
Get started with the Help page
Ask Your Question

Revision history [back]

Julian's advise is good. Linking to a SketchUp file can be problematic, so it is better to work with an OSM and and use the "Open OpenStudio Model" directly.

More generally whenever you see surfaces as white, or that don't show up in the "OpenStudio Inspector" when you selected, then the OpenStudio model is not properly synchronized with the active SketchUp model. This can also create issues changing render modes. I would follow these steps when this happens.

  1. Save your OSM file as a new name to avoid overwriting your original file that may not have any issues
  2. Quit and restart SketchUp (don't open the new file yet)
  3. Go to the "Plugins" menu and then under "OpenStudio User Scripts/Reports" look for "OSM Diagnostic Script"
  4. Now browse to the new file you saved in step 1. and click ok.
  5. There are two options for removing objects with errors or warnings. The defaults of "true" and "false" are fine, but if you have lost of tiny surfaces you want to remove then setting both to true may be good

At this point the script will run, and will open your ruby console. The script will report out results of some basic testing for problematic objects such as surfaces with out a parent space, or surfaces without 3 vertices, it will look for surfaces with duplicate geometry within the same surface group. If it finds any issues it will save a copy of your file with "diagnostic" at the end of the name, leaving your original file untouched. Now you can open the resulting model through the traditional method using the "Open OpenStudio Model" button.

Note: one thing the script doesn't currently do is remove orphan sub-surfaces. These can result if you deleted a base surface but somehow not the subsurface. There is a dedicated user script for this under "Add or Alter Model Elements" section of the user scripts/Remove Orphan SubSurfaces". This script is also good for files that won't even open in the plugin. That was what it was originally developed for.