Qubu Studio

Appearance

Importing, exporting, and project files ​

TODO screenshot: show the main menu import/export area or import modal, with the supported file actions and key modal fields highlighted.

Importing ​

Use Main menu → Import.

Supported import sources ​

  • OBJ for geometry
  • GeoJSON for site boundary input

Import modal fields ​

Use as ​

  • Surroundings
  • Site boundary

GeoJSON is forced to Site boundary.

File Units ​

  • Meters [m]
  • Centimeters [cm]
  • Millimeters [mm]

Set this to match the source file exactly.

Up Orientation ​

  • Y
  • Z

Set this to match the source authoring tool.

Facade Reflectance ​

Available for surroundings import. Sets the starting reflectance used in daylighting.

Import rules to remember ​

  • Stop running algorithms before importing new geometry.
  • Only OBJ and JSON files are accepted by the import flow.
  • Imported OBJ data can become either surroundings or site boundary.
  • Boundary import mistakes affect every downstream stage.

Exporting ​

Use Main menu → Export.

Export as OBJ ​

Exports the scene geometry as OBJ.

Export as IFC ​

Exports geometry as IFC.

Export reports as JSON ​

Exports project info, zone parameters, zone reports, costs, section reports, floor reports, apartment mix, and parking-related values as JSON.

Screenshot ​

Saves a viewport screenshot.

Qubu project file ​

Use Save, Save As..., and Open... from the main menu, or use the keyboard shortcuts.

The project file is the Qubu save file for restoring:

  • project parameters,
  • boundary,
  • surroundings,
  • informed spaces,
  • sections,
  • reports,
  • visualizations,
  • and generation-related state.

Technical facts useful to users:

  • the save format is versioned,
  • it uses the qubu file magic internally,
  • incompatible versions can fail to open in older or newer builds.

If you want a portable deliverable for other tools, use export formats instead of the project file.