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

Stuck in wireframe mode

asked 2015-05-14 08:47:29 -0500

eloneill's avatar

updated 2015-08-07 14:34:19 -0500

I'm working in Sketchup and I just did an intersect/match (I think the match caused the blowup), and now my model is stuck in wireframe mode. None of the "render by" mode buttons do anything.

I shouldn't have to backtrack far as I've been saving regularly, but it would be nice to know why this blew up, because I'm going to have to intersect and match again after I redo the changes...

Here's a copy of the osm file:

edit retag flag offensive close merge delete



Using the Ruby Console gives the following error:

for #<Sketchup::Face:0x00000015b12f78>, #<Sketchup::Face:0x00000015551300>
DrawingInterface.create_from_entity:  create_model_object failed
Error: #<NoMethodError: undefined method `name' for nil:NilClass>

The following previous questions may help:

MatthewSteen's avatar MatthewSteen  ( 2015-05-14 08:55:15 -0500 )edit

4 Answers

Sort by ยป oldest newest most voted

answered 2015-05-14 09:28:34 -0500

SketchUp isn't reliable at creating surface intersections. The current version of the surface matching measure has an option to intersect surfaces. Try using this in the OpenStudio application described in this post.

As for what to do in SketchUp when you get an error (stuck in wireframe), you should close the model without saving changes, or if you do save changes, use "SaveAs" so you can leave the original version of the model untouched.

edit flag offensive delete link more

answered 2015-05-14 11:51:51 -0500

updated 2015-05-14 11:53:24 -0500

If you run the intersect faces or match faces scripts and then observe that Sketchup gets stuck in wireframe mode, this is a sign that the script has failed. Then typically the window with the log messages will also be empty.

In this case I solved the problem by reloading the original osm file, inspecting the geometry for errors (which sometimes are only visible, if the 3D view is zoomed to a very high degree: e.g. there may be gaps between adjacent walls/ceilings, small missing faces, or superfluous tiny faces, duplicate tiny faces, possibly generated from intersection algorithm).

Finding geometry errors is facilitated, if the geometry is built incrementally, i.e. adding elements step by step and doing surface intersection and matching after every step.

If no geometry errors can be found and the intersection algorithm still fails, it is still possible to create the intersections as well as the surface matching manually. This is facilitated by assigning appropriate surface names to corresponding surfaces (front/back, A/B).

edit flag offensive delete link more

answered 2015-05-14 09:50:08 -0500

updated 2015-06-15 10:33:05 -0500

I also had a similar problem. I just simply save openstudio or idf and reload it. After that surfaces are ok.

edit flag offensive delete link more

answered 2015-08-06 09:27:56 -0500

NickC's avatar

I recently had a similar issue (stuck in wire frame after using the 'move' command on some fenestration). This link helped me get the offending surfaces removed and was fairly painless. From your comment, it looks like you may have already identified the issue in the Ruby console.

Best, Nick

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools


Asked: 2015-05-14 08:47:29 -0500

Seen: 1,322 times

Last updated: Aug 06 '15