Qonic September Release Notes

Release Notes
1

Hi there!

It’s been a busy few weeks, after receiving the openBIM Award in Berlin for Qonic Intelligence, and now we’re back with a new release packed with improvements. This update brings smoother modelling, smarter coordination and a stronger connection with Revit.

Want to see it in practice? Check out this month’s release video:

Interoperability

  • Bidirectional link with Revit: You can now send changes made in Qonic back to your original Revit file. The bidirectional link ensures you don’t have to duplicate work and keep both tools in sync.

Group 581
Group 581768×400 65.8 KB

  • BuildingSMART validation improved: IFC exports now run through stronger checks to improve compliance.
  • IFC export now gives correct file names: Exported IFC files will automatically be named correctly.
  • SketchUp import: Bad links in SketchUp files are now automatically ignored.

Modelling

  • Resizing windows and doors: You can now stretch windows and doors directly in the model by grabbing the side face of the frame or mullion. The surrounding context updates automatically.
  • Replace with Layer: Now works across multiple models, so you can make bulk changes in one go.
  • Strip to Core: Also supports multi-model workflows, letting you simplify several models at once.
  • Connected Move: Move connected elements across multiple models in one operation.
  • Spaces: Spaces can now be visualised and used directly for calculations.

Coordination

  • Grids in 3D: Grids embedded in imported models are now visible in 3D and can be used directly for snapping.

Group 580
Group 580768×400 81.4 KB

  • Issues: Issue management has been further improved for better workflows.
  • World position for issues: Each issue now contains its world position for more precise coordination.

API & Integration

  • Assign multiple classification codes: The Public API now allows assigning multiple codes at once.
  • Property modification with addOrUpdate: Update or create properties in one step through the API.
  • Model import through API: Import models directly into Qonic using the Public API.
  • bSDD properties: bSDD class properties are now supported.

Platform & User Interface

  • Inspect panel improvements: You can now edit or remove a single relation value.
  • iPhone scaling: The interface now scales better on iPhone screens.

Bug Fixes

  • Wildcard search: Now case-sensitive.

  • Revit plugin: Fixed version check, upload timeout, and compound wall conversion.

  • Undo stack: Correctly tracks floor section selections; wording changed to “subtract” instead of difference.

  • UI consistency: Generate sections button hidden in read-only or public mode.

  • Type assignment: Removed unnecessary assembly check when assigning types.

  • Browse-Codification: Parent validation improved.

  • Revit updates: Descriptions of personal changes now display correctly.

  • API stability: Fixed potential crash when deleting multiple models at once.

  • Browse issues: Fixed duplicates in multi-model setups, improved wildcard speed, and corrected handling of name & description fields.

  • Inspect panel: You can now edit or remove a single relation value.

  • UI scaling: Interface now scales better on iPhone.

  • Split product relations: Prevented elements from being copied to opening relations.

  • Batch highlight: Exceptions are now replaced with warnings.

  • Username now correctly set from Auth0

  • Version dialog now calls process modifications correctly

Looking ahead

Our focus this month: less rework, smoother teamwork and faster modelling. Qonic is here to rethink how BIM should feel: lighter, easier and always improving with monthly updates.
Everything in this release is ready for you at app.qonic.com.

Your feedback makes a real difference, so keep sharing how Qonic fits into your workflow.

If you’d like to see Qonic live in action, join our webinar on Wednesday 22 October, an event by AI in AEC, where Aaron Perry will show how you open complex models in seconds, how you fix data right in your browser and collaborate with unlimited users.

See you next month!

2

Awesome stuff, as always! What does a door or window family turn into, after it’s been stretched in Qonic and synced back to Revit? I imagine stretching might easily conflict with constraints defined in the Revit family, so it would seem difficult to turn in back into an instance of the original family definition.

1 Like
3

Thanks! Great question @Michael_Hasse and you’re absolutely right that this is a tricky part of Revit interoperability.

When a door or window is stretched in Qonic, we try to keep the original Revit family wherever possible. However, if the geometric change goes beyond what the original family allows (for example, if the family has constraints or formulas that would be violated by the new size), Qonic will automatically create a new Revit family type based on that instance.

So in short:

  • If the change fits within the family’s allowed parameters, the same Revit family is retained and only the instance parameters are updated.

  • If the change alters the geometry beyond those limits, Qonic generates a new family specific to that object, so the original family remains untouched and consistent for other instances.

This ensures you can safely edit and sync without breaking constraints or dependencies in Revit. Feel free to put it to the test yourself! We look forward to your findings and any further feedback on our bidirectional sync.

4

Thanks @Barbra , that’s very impressive. I currently don’t have access to Revit, but look forward to test it the next chance i get.

1 Like