Skip to main content
The connector isn’t just for sending — Load pulls a GingerBIM model back into your SketchUp or Rhino file. That closes the loop: work done in GingerBIM comes back into the native modelling tool, and the model on GingerBIM becomes the version everyone trusts.

​
Loading a model

  1. In the connector, choose Load.
  2. Pick the project, the model, and the version to load — the latest by default, or any earlier version.
  3. The connector bakes the model into your file. When a newer version is published later, the connector shows it, and you can load the update or switch versions at any time.
Components created in GingerBIM — including those generated with the parametric component generator — come back as native objects in SketchUp or Rhino, so you can keep modelling around them.
If you send and load the same model from the same file — say, a SketchUp file you publish from — loading doesn’t duplicate what you already have. The connector diffs against your file and pulls in only what was generated on GingerBIM.

​
GingerBIM as the source of truth

With send and load both available, a team can stop passing files around:
  • Different people work on different parts of the project in their own local files.
  • Everyone publishes their part to GingerBIM and loads the latest state of the rest.
  • The GingerBIM model is the single source of truth — versioned, with history — so there’s no “which file is current?” and no copy-paste merge errors.
Combined with GingerBIM’s own tools (property editing, schedules, drawings all working on the same live model), this keeps the whole team on one model without the hassle and risk of sending files to each other.