Skip to main content

BricsCAD v15 for Architects

This week, for the first time, BricsCAD is released for the three major Operating Systems available: Windows, Linux and now also OSX. After getting rid of its IntelliCAD legacy, the Belgian company Bricsys retargeted BricsCAD as a DWG-compatible development platform for all kind of CAD uses: 2D drafting, 3D modelling and rendering, custom development, Mechanical Design and (a long time since the demise of the “Architecturals” module) now also for BIM Functionality.

Let’s start with that first: How does BricsCAD approach BIM?

From the Release notes: “Instead of creating a set of dedicated BIM primitives like walls, slabs, columns, etc..., each with their own restricted behavior and properties, we opted for offering maximum flexibility. Any 3D Solid can be used in a BIM model”

This is interesting and in line with the way freeform and modelling software approaches BIM: define any geometry and classify it afterwards (e.g. SketchUp, Rhinoceros).

BricsCAD is DWG based, but supports IFC import and export.

When you launch BricsCAD, you get a welcome screen, allowing you to start with a BIM template and set the intended units.

bricscad-1-2014-11-21-15-40.jpg

And than you can start modelling. There is no wall tool, no floor tool. Just geometric tools and operations.

I’ve use the first of the 3D Solids tools to draw the contour of a house, setting width and height along the way. Use the regular snapping and ortho modes as with any drawing or modelling operation.

bricscad-2-2014-11-21-15-40.jpg

In addition, there is a series of BIM-oriented modelling tools: BIMCONNECT (to solve corners between solids), BIMDRAG (like push-pull but oriented to adjust element positions and thicknesses), BIMINSERT (to insert doors or windows, which are stored in separate DWG files).

They are gathered on the BIM Toolbar.

BIMINSERT requires some further explanation though.

From the release notes: “Windows and Doors are native .dwg files which can be inserted in walls or slabs by the command BIMINSERT.

  • Using Dynamic UCS, a window will automatically align with the 3D Solid Face it is inserted on.
  • A 3D Solid in the window drawing on a layer named "BIM_SUBTRACT" will be used to automatically create an opening in the wall, keep the window in its position in the wall, and keep the opening associative with the window.
  • Optionally, the window drawing can contain 2D symbols.”

There are a few basic examples installed, but you have to ensure you work with the right units set up.

Oh, and here you have the OSX version by the way…

bricscad-3-2014-11-21-15-40.jpg

You can draw any shape you want to use as a Window or Door and by adding a custom “Void” geometry, it’ll make the required opening in its host wall or slab.

No Parametric Windows?

I remember that Architecturals and before that Triforma, used a parametric approach, where each window or door was created as a series of mostly geometric rules to fill in an opening with frames and glass panes. The approach in BricsCAD is closer to how you would work in SketchUp or even the way you create a custom Window in ArchiCAD by drawing slabs and other objects and having one or more slabs with the “WALLHOLE” or “WALLNICHE” ID to indicate voids.

But let’s not forget the major features aspects of BricsCAD

We already mentioned it is now fully cross-platform on the three major operating systems: MS Windows (32 and 64-bit), OS X (64-bit only) and Linux.

And is it a “real” Mac version?

I’ve dabbled a bit with the OSX Version and noticed it’s not Retina-ready (although it improved after using Retinizer), so icons and many dialogs look pixelated on a Retina-screen. Text in screen controls becomes sharp, but the Property Palette stays low-res.

It is a cross-platform application and it doesn’t use the typical OSX styles. This is not a hindrance in using the software, but it might be a disappointment to Mac lovers. I consider myself a moderate Mac lover and I fully understand their use of a cross-platform interface library (wxWidgets), which renders native controls and integrates fairly well, but it is not Mac-like interface you get in the end (so no integration with Notification center.

When comparing both (the Windows version running inside Windows 8.1 in Parallels and the OSX version running in Yosemite), I didn’t see many differences, apart from the OS-style borders and buttons, as shown above.

Price point

It’s low price has always been a major asset to sell the software.

  • Classic is targeted at AutoCAD LT: 2D Drafting, for less than half the price of LT
  • Pro is oriented as an extensible platform for custom development with special focus on 3D, rendering and plugins.
  • Platinum is the full suite, with additional assembly modelling, sheet metal design and BIM features. Still at a price point below AutoCAD LT

DWG Compatibility

Initially, BricsCAD was targeted as an AutoCAD replacement, but the last few years have shown much more dedication to become a platform on itself: compatible with DWG, but more and more focusing on delivering features that are required for end users.

Developer Friendly

To be honest, one of the biggest approaches to growth for Autodesk has been its extensibility: Lisp, DCL, macro’s, VBA, .NET, C++, COM… You name it, AutoCAD has it. And BricsCAD (well, primarily the Windows version) delivers a complete developers solution: source-compatibility with ARX (the AutoCAD Extension API), LISP.

If you are still accustomed to VBA, beware that it is only available for the Windows 32-bit version. This is said to be a Visual Basic for Applications limitation, although Office for Mac has been able to circumvent this somehow.

And they license this freely to everyone who registers as a developer.

And… Belgian quality

Bricsys is based in Ghent (Belgium) and while they have programmers in other parts of the world too, they keep their Belgian roots. This was the team that once developed Triforma on top of MicroStation, which was later sold to Bentley.

More info on https://www.bricsys.com/en_INTL/bricscad/

Comments

Popular posts from this blog

Improve usage of BIM during early design phases

When I was collecting ideas for a book chapter on BIM (that seemed to never have emerged after that), I collected 10 ideas, which I believe still reflect good recommendations to improve the usage of BIM during the early design phases. These ideas are related to BIM software, but you can apply them in any flavor, as long as you can model with Building Elements, Spaces and have control over representation. Introduction This article gives an overview of several recommendations and tips, to better apply BIM applications and BIM methodologies, in the context of the early design phases. Many of these tips are applicable in any BIM application and they are based on experience gathered from teaching, researching and using BIM software. Sometimes they could help software developers to improve the workflow of their particular BIM implementation. Tip 1 : Gradually increase the amount of information In the early design phases, the architect makes assumptions and lays out the main design in...

Getting BIM data into Unity (Part 9 - using IfcConvert)

This is part 9 of a series of posts about getting BIM data into Unity. In this post, we’ll discuss the IfcConvert utility from the IfcOpenShell Open Source IFC Library to preprocess an IFC model for integration with Unity. This is (finally?) again a coding post, with some scripts which are shared to build upon. Conversion of IFC into Unity-friendly formats The strategy with this approach is that you preprocess the IFC-file into more manageable formats for Unity integration. Most Web-platforms do some sort of pre-processing anyway, so what you see in your browsers is almost never an IFC-file, but an optimised Mesh-based geometric representation. However, it wouldn’t be BIM-related if we’d limit ourselves to the geometry, so we will parse the model information as well, albeit using another, pre-processed file. IFC to Wavefront OBJ I used a test IFC-model and used the IfcConvert-utility converted it into OBJ en XML formats. The default way to use it is very simple: ...

Getting BIM data into Unity (Part 8 - Strategies to tackle IFC)

This is part 8 of a series of posts about getting BIM data into Unity. In this post, we’ll discuss IFC as a transfer format towards Unity. As with the previous post, this is not a coding post, although hints and examples are provided. Open BIM and IFC Everybody who ever met me or heard me present on a conference or BIM-lecture will not be surprised to hear that I’m a strong believer in the Industry Foundation Classes (IFC), an open standard, with already two versions published as an ISO standard, being IFC2x2 and IFC4 (but surprisingly not IFC2x3 which is widely used). In the ideal world, this would be the format to use to transfer BIM data into another environment, such as Unity. So what are our options? Looking in the Unity Asset Store Assimp is a library which supports multiple formats, including IFC. https://assetstore.unity.com/packages/tools/modeling/trilib-unity-model-loader-package-91777   I did a few attempts, but alas without any success. It is po...