Tag Archives: BricsCAD

The BLADE video watchlist

I did my third and final (for now) BricsCAD Unplugged webcast about BLADE last Wednesday. Here’s the video:

Before I dig into DCL, I start with a brief description of an absolutely brilliant feature that was added to BLADE in V19. If you code in LISP, you’ll love this feature.

Then I move on to some ancient history. Did you know that we can thank the far-sightedness of some slightly renegade Autodesk OS/2 developers in the early 1990s for the dialog boxes we use today? Did you know that you could program dialog boxes for AutoCAD for Mac in 1993 but you can’t today? Can you spot the items of interest in the background?

The rest of the video is dedicated to describing DCL programming and debugging, and I explain how BLADE is the best tool for that job using examples.

If you want to watch all three of the BLADE videos in a row (that’s 1 hour 49 minutes of viewing), Matt Olding has created a YouTube playlist for this series.

It has been an absolute pleasure working with the Bricsys people in putting this series together. Torsten Moses has informed me about yet another bunch of enhancements that are coming very soon to BLADE, so maybe you haven’t heard the last from me on this subject on BricsCAD Unplugged.

More BLADE videos

As mentioned previously, In December I made a guest appearance on the BricsCAD Unplugged webcast series to discuss the LISP development environment, BLADE (YouTube link).

I made another appearance last week describing debugging using BLADE (YouTube link):

If you’re dealing with LISP code for AutoCAD and/or BricsCAD, you really should be doing it in BLADE. It’s the best development environment for AutoLISP/Visual LISP that you’re ever going to get.

I have another appearance scheduled for later today (13 February) in which among other LISPy things, I will be discussing using BLADE for DCL programming. Again, even if you’re AutoCAD-only, I believe this is worth a watch. BLADE is better for DCL programming, too.

Even if you’re AutoCAD-only and not a programmer, you might find my brief ancient history lesson of interest. Did you know that BricsCAD for Mac users can thank a far-sighted early 90s Autodesk OS/2 team for the dialog boxes they use today?

The BricsCAD Unplugged webcast broadcasts run on the Bricsys Facebook page and are then quickly transferred to YouTube. Today’s session will start at about UTC 14:15 (2:15 PM) on Wednesday, 13 February 2019 (click here for your local time)

Link

My Real World BricsCAD series of posts on the Bricsys blog continues with more from the in-depth interview at Schrack Seconet.

Part 1 | Part 2 | Part 3 | Part 4 | Part 5 | Part 6

 

I hope when people read these things they can see that I’m probing for problems, issues, difficulties, and so on. That’s the sort of thing that those people who are considering switching to BricsCAD are going to want to know about before diving in.

I’m grateful that Bricsys is OK with me covering their products like this on the Bricsys blog. Some CAD companies only allow super-positive things to ever be uttered about their products from their corporate sites. Bricsys is different.

Addendum – Why every AutoCAD CAD Manager should have a copy of BricsCAD – part 1, fixing drawings

This post is an addendum to a post from June, Why every AutoCAD CAD Manager should have a copy of BricsCAD – part 1, fixing drawings. This post provides new information about useful functionality added in V19 of BricsCAD that is useful for any CAD Manager or power user who ever has problem DWG files to deal with. Yes, even if your site is still purely AutoCAD-based.

In this post I’ll describe the (inspector) LISP function. This was added in the V18 cycle but was significantly enhanced in V19. It’s probably the most useful LISP function you’ve never heard of.

Although it’s LISP, that doesn’t mean you have to be a programmer to benefit from it. If you’re a non-programming CAD Manager or power user, you can use it to work out what’s going on within any DWG you’re having problems with. You can use it to discover information about objects in the drawing; not just conventional entities, but also blocks, tables, dictionaries and so on. It even works with custom data.

I gave a brief demonstration of (inspector) in the last BricsCAD Unplugged episode about BLADE. However, you don’t need to use BLADE; just enter (inspector) at the command prompt, select an object and you’ll be presented with a dialog like this:

These dialogs are modeless, and you can have as many displayed as you like; you’re not limited to one. This dialog displays the same data in three different ways. At the top, it’s shown in traditional LISP assoc form, and by playing with the Expand controls you can vary the way in which this is pretty-printed. The bottom left pane shows the data in DXF form, which is probably easiest to read if you’re a non-programmer. If you’re more of an ActiveX person or you prefer to see the properties described with words rather than numbers, you’ll prefer the display on the bottom right, which shows the COM properties for the object.

If you want to select another object to inspect without calling (inspector) again, just use the [ > > ] button.

The grayed-out lines indicate data that is considered read-only. It’s important to note that this doesn’t mean it’s impossible to change the data, merely that the ways in which that data can be changed within a program is restricted. Generally, it means you can’t change the ActiveX properties directly, but there are various other means that can be employed in many cases.

The lists are somewhat interactive; double-click on an entity name and you’ll be given another inspector window for that entity. You can burrow down through the drawing database in this way, looking for the source of your mystery DWG problem. If you’re using it while programming, you can use it to work out what set of circumstances is causing your code to trip up in certain drawings.

The (inspector) function has an optional argument, and what it will accept is very flexible. If you pass an entity name to it, you will get the data for that entity displayed. The same principle applies for various ActiveX objects: pass it a layer table object and the appropriate data will be displayed.

Direct access is provided to various useful things from within BLADE using the pull-down menu Lisp+DCL > Browse DWG Database:

If you pick Browse Text Styles, you’ll see something like this:

Double-click on one of the text style items in the left pane and you will get this:

As you can see, this is very handy for tracking down issues both while programming and when diagnosing DWG problems.

Finally, I should note that there is potential for the inspector to provide even more power in future. Bricsys LISP guru Torsten Moses is investigating the possibility of allowing the inspector to modify data, not just inspect it. There’s potential danger there, but if Torsten can make that work safely then that would be another invaluable tool for any DWG-based CAD Manager.

As I stated in my original post, it’s definitely worth a CAD Manager’s while to do the quick download and install of an evaluation BricsCAD. My experience in dealing with Bricsys is that requests for extensions for evaluation purposes are usually accepted, so you probably won’t have to give up your valuable tool as soon as your 30 days are up.

Video – who is that masked man?

Last night I made another guest appearance on the BricsCAD Unplugged webcast series. This time I was discussing the LISP development environment, BLADE. Here’s the video:

Bonus points will be awarded for identifying three items of interest in the background. No, not counting my dog Sunday asleep at lower left.

Despite going way over time, there was still nowhere near enough opportunity to describe the full LISPy awesomeness that BLADE represents. I am therefore scheduled to return for another two or three episodes beginning in February. In those, I’ll be doing more of a step-by-step demonstration rather than the overview and V19 new feature description I did in this episode. If you have any particular requests for what you want covered, please comment on this post.

I also showed how the tools in BLADE (e.g. the (inspector) function) are still worth having for any DWG-based CAD Manager or power user, even if you’re not a full-on LISP programmer. If you have to work out what’s going on with dodgy DWG files, you’ll want to have (inspector) in your set of tools.

The BricsCAD Unplugged webcast broadcasts run on the Bricsys Facebook page and are then quickly transferred to YouTube. This was the last episode for 2018 because of Christmas and New Year.

Wielding BLADE on BricsCAD Unplugged

In September I was the special guest on the BricsCAD Unplugged episode BricsCAD Unplugged – Steve Johnson 5 surprises moving to BricsCAD. Next Wednesday I will return, this time to wield BLADE, the best thing to happen to CAD LISP in nearly 20 years. I’ll be introducing it and demonstrating a few things, including the new features that came with V19.

These live broadcasts are run on the Bricsys Facebook page and are then quickly transferred to YouTube. This broadcast will start at UTC 15:00 (3 PM) on Wednesday, 19 December 2018. Here’s that time in a few handy time zones:

Location Zone Time
San Francisco PST 07:00
Minneapolis CST 09:00
New York EST 10:00
London GMT 15:00
Brussels CET 16:00
Moscow MSK 18:00
Mumbai IST 20:30
Perth AWST 23:00

BricsCAD V19 promo pricing ends 15 December

I’ve previously explained the changes to BricsCAD pricing that came in with V19, and showed how the prices for new purchases would rise when the promotional period ends.

Upgrading now requires All-In. Problem?

One change I failed to point out, but which was mentioned by a commenter, was that for customers not already on the All-In Maintenance program, they needed to sign up for one year’s All-In in addition to paying the upgrade fee. This meant the upgrade fee was significantly greater than in previous years because customers were effectively paying for two upgrades (e.g. V18 to V19 as an upgrade, plus V19 to V20 covered by All-In).

Although this still represented good value compared with the competition and recent BricsCAD upgrades have proven to be well worth the money, there was still a ‘sticker shock’ effect associated with this double payment, and people who budgeted for upgrades based on previous pricing found themselves in a bind. There were complaints from customers and partners. For Bricsys, accustomed to being the good guys in terms of CAD pricing and licensing fairness, this was an unusual situation.

Fixing the problem

On 16 November, Bricsys responded to this feedback by introducing significantly reduced prices in this scenario, and committing to making good with those customers who already paid the higher prices. How significantly reduced? About half. To give you an idea, an upgrade of BricsCAD Pro V18 to V19 (and later to V20 thanks to All-In) is about US$425 or €400.

I don’t see much to complain about there. It’s great to see a company that actually listens to its customers and acts accordingly, even when doing so costs real money.

However, it’s important to note that this lower upgrade pricing only applies during the promotional period that had already been announced for new license pricing. That period ends on 15 December (i.e. prices go up from 16 December). To make things very plain, at the time of writing:

BricsCAD promotional pricing for both upgrades and new purchases will end in two days.

This only affects on-demand upgraders

None of the above has any effect on customers who were already on the All-In program. That program has always represented the best value way of keeping BricsCAD up to date; I recommend getting on it and staying on it. You can of course hop off it in the future if Bricsys one day fails to keep you happy with its upgrades. Although you’re effectively paying for upgrades in advance it’s still a perpetual license system, which gives you the ability to keep playing even when you stop paying.

There is also the option of the rarely-used subscription (rental) pricing for those cases where licenses are not needed long-term or need to be assigned to a specific project. Regular readers of this blog will be familiar with my thoughts on that licensing model. If you need it, fine. If you don’t, you shouldn’t be strong-armed into adopting it.

Perspective

Bear in mind that with all this talk of rising prices, a little perspective is useful. Based on currently-available pricing, the 3-year cost of BricsCAD Pro including All-In in the USA is $1615, compared with $4605 for AutoCAD on subscription. At the end of the 3 years, you will have a perpetual license of the then-current version of BricsCAD Pro, or you will have nothing at all if you had spent 2.85 times as much to rent AutoCAD.

If you look beyond 3 years (and some customers of mine have AutoCAD licenses ten times that age) then the difference in the value proposition between the products becomes even more dramatic. You’re all smart people with calculators and spreadsheets, so I invite you to do your own comparisons.

Reminder: if you want to get the absolute best value for money from a BricsCAD purchase, remember to do it on or before 15 December. If you do decide to buy, and also want to support this blog, then please use this link to do so:

Bricsys Store

Disclosure: this is a sponsored link. If you buy a Bricsys product using this link, I get part of the proceeds. However, this will not have any effect on the editorial content of this blog. I don’t expect to be able to retire on the proceeds from this link (if any) and I will continue to write what I honestly think about the CAD products and policies of all companies, as I see fit.

DOSLib goes open source

What’s DOSLib?

DOSLib is a free library of LISP functions that adds a lot of functionality to AutoLISP/Visual LISP/BricsCAD LISP. It makes a lot of programming tasks a lot easier, because instead of writing a bunch of code to do tricky stuff, you can just load the library and call a ready-made (dos_xxx) function. There are hundreds of functions that cover the following areas (taken from the McNeel Wiki):

  • Drives – Check for drives, change between drives, and check available disk space.
  • Paths – Manipulate path specifications.
  • Folders – Create, rename, remove, select, and change folders. Return special operating system folders.
  • Files – Copy, delete, move, rename, and select files; get directory listings, search and find multiple instances of files, and change file attributes.
  • Print – Get and set default printers, and spool print files.
  • Configuration – Manipulate Windows-style initialization (INI) files, and access the Windows Registry.
  • Processes – Run operating system commands or other programs.
  • Interface – Get strings, integers, reals, and lists from the user. Display Windows message boxes, progress meters, and splash screens.
  • Strings – Tokenize strings, extract characters, find characters, insert, remove, and replace characters, and trim characters.
  • Math – Trigonometric calculations, vector manipulation, statistical analysis, and more.
  • CAD – Save all and close all open files. Preview drawings and list xrefs.
  • System – Get system information, sort lists, change the system date and time, manipulate the keyboard, and play sounds.

Why would a CAD LISP programmer use it?

There are many DOSLib functions that would be difficult to write purely in LISP and quite a few that would be impossible. So for those people who want to code for AutoCAD and BricsCAD without the bother of learning ARX/BRX and dealing with the associated compiler requirements, DOSLib has been a godsend. It’s worth noting that some of the DOSLib functions have been added to BricsCAD’s LISP engine, so depending on the function you use, you may not even need to load the DOSLib library.

Do impressive-looking stuff without writing much code. You might call it being lazy. I call it being efficient.

A history of dependability

DOSLib has been around for many years. It is currently supported on AutoCAD 2013 and later and BricsCAD Pro V13 and later, but earlier versions have supported AutoCAD releases dating back to 1992! Dale Fugier at Robert McNeel and Associates has been providing outstanding service in developing DOSLib and keeping it up to date. For nothing!

So developers have been able to take advantage of the DOSLib functionality all that time, and Dale has always come up with the goods in terms of updates to work on new releases of AutoCAD and BricsCAD. However, you may have had a nagging doubt about writing code that relies on a third party, or as a CAD Manager relying on such code, no matter how rock-solid reliable that party has proven in the past.

That nagging doubt can now be put to bed, because Dale has announced that DOSLib has been made open source under the very open and simple MIT license. The GitHub DOSLib page has the source, with compilation and other relevant information.

All good news

Dale has also stated that he intends to continue to provide compiled binaries for the foreseeable future, so don’t worry about having to mess with compilers. Even if a meteor happens to land on McNeel headquarters, it’s a pretty safe bet that somebody in the AutoCAD/BricsCAD development community will, after a suitable period of mourning, step forward to compile the code for new AutoCAD/BricsCAD releases when required.

The availability of the source code also opens the door for DWG-based applications (other than BricsCAD) to attempt to provide a higher level of LISP compatibility, to the extent of supporting (dos_xxx) function calls. That means you, the CAD LISP programmer, will have a wider potential audience for any code you write that uses DOSLib functions.

Finally, if you’re an ARX/BRX developer who wants to do something similar to something in a DOSLib function, you now have some handy sample code.

So this is all good news, and yet another example of Dale and McNeel doing the right thing by the CAD community.

BricsCAD V19 – pricing changes explained

The BricsCAD V19 release has not only given us a new software release (an excellent one – and I’ll be writing about that later), it’s also given us a new Bricsys website and a new pricing structure. In some cases prices are actually slightly lower, but in the vast majority of cases the movement is up. The price movement varies by product, market and currency, and depends largely on whether you choose to opt for All-in Maintenance. The aim of this post is to clarify exactly what has happened to Bricsys prices.

One significant change across the board is the way All-in Maintenance is priced. It was previously a fixed amount (e.g. US$220) to pre-emptively keep up to date with each of the three BricsCAD types (Classic, Pro and Platinum). Now it’s a percentage (e.g. 30%), which means All-in is now cheaper than it was for Classic users and more expensive for everyone else.

You’ll also note that the rarely-used subscription (rental) pricing is now much easier to find on the web site. The annual cost equates to about 40% of the cost of a perpetual license.

Those 30% and 40% figures look high, but remember that they’re a percentage of much smaller sums than you get with Autodesk. For example, the difference between buying BricsCAD Pro with and without All-in is US$255. Going Subscription (rental) for a year is $488. For comparison, keeping an old perpetual AutoCAD license up to date is in the region of US$500+ (it varies considerably under different circumstances) and the current annual AutoCAD subscription cost in the USA is US$1575 (bear in mind that this now includes access to various AutoCAD-based verticals).

Let’s compare the BricsCAD prices before and after these changes. First, US$ prices without All-in. Note that none of these prices include taxes.

US$ BricsCAD Classic BricsCAD Pro BricsCAD Platinum BricsCAD BIM BricsCAD Mechanical
V18 590 750 1110 1760 1630
V19 590 770 1110 1720 1630

As you can see, there is very little price movement at all here. Note that these V19 prices are promotional, which means they won’t stay at this level for ever. (Edit: the promotional prices apply until 16 December 2018).

The Euro prices have moved up a little more:

Euro BricsCAD Classic BricsCAD Pro BricsCAD Platinum BricsCAD BIM BricsCAD Mechanical
V18 480 640 990 1540 1440
V19 525 725 1050 1590 1500

A more useful comparison can be made by comparing the prices including All-in, because (temporary conditions excepted) this is the cheapest way of keeping up to date, and the way I’d usually recommend paying for BricsCAD. I’ve included the post-promotion prices here so you can get an idea of the total movement.

US$ BricsCAD Classic BricsCAD Pro BricsCAD Platinum BricsCAD BIM BricsCAD Mechanical
V18 810 970 1330 2100 1940
V19 (Promotion) 781 1025 1470 2275 2155
V19 (Standard) 825 1105 1560 2405 2275

Here’s the same thing in Euros:

Euro BricsCAD Classic BricsCAD Pro BricsCAD Platinum BricsCAD BIM BricsCAD Mechanical
V18 680 840 1190 1840 1720
V19 (Promotion) 701 965 1391 2115 1995
V19 (Standard) 760 1040 1475 2275 2145

The upshot is that for most customers, buying and maintaining the low-end Classic product is slightly cheaper than it was, but as you move up the product range, the price increases start to bite. However, the total cost of ownership is still significantly lower than AutoCAD. The following table shows the total licensing costs over several time periods, assuming no price increases from anybody. Yes, I know that’s not a reasonable assumption, but at least it precludes guesswork! The ongoing annual All-in price is assumed to be 30% of the non-promotional product cost.

US$ 1 Year 3 Year 5 Year 10 Year
BricsCAD Classic (All-in) 781 1276 1771 3009
BricsCAD Pro (All-in) 1025 1688 2351 4009
BricsCAD Platinum (All-in) 1470 2406 3342 5682
BricsCAD Classic (Subscription) 312 936 1560 3120
BricsCAD Pro (Subscription) 410 1230 2050 4100
BricsCAD Platinum (Subscription) 588 1764 2940 5880
AutoCAD (subscription) 1575 4725 7875 15750
AutoCAD LT* (subscription) 390 1170 1950 3900

* Note that I have included AutoCAD LT here for comparison even though it is a significantly less capable product than BricsCAD Classic, which has 3D and full LISP capabilities.

In addition, BricsCAD Platinum plus Sheet Metal is now called BricsCAD Mechanical, with the price including All-in going from US$1940 to US$2155 ($2275 after promotion). Euro prices go from €1720 to €1995 (€2145 after promotion). Similarly, BricsCAD Platinum plus BIM is now called BricsCAD BIM, with the price including All-in going from US$2100 to US$2275 ($2405 after promotion). Euro prices go from €1840 to €2115 (€2275 after promotion).

It’s worth noting that the price of Communicator, the Bricsys format translator, has dropped slightly in most cases despite providing more format translation options.

If you intend buying a Bricsys product and also want to support this blog, then please use this link:

Bricsys Store

Disclosure: this is a sponsored link. If you buy a Bricsys product using this link, I get part of the proceeds. However, this will not have any effect on the editorial content of this blog. I don’t expect to be able to retire on the proceeds from this link (if any) and I will continue to write what I honestly think about the CAD products and policies of all companies, as I see fit.

BricsCAD price rise imminent

BricsCAD V19, which is expected to be released within days, will bring with it new, higher pricing. It still won’t be anything like Autodesk-level high, of course, but will be a bit higher than it was.

Bricsys is currently offering new buyers of V18 an automatic upgrade to V19 (the serial number will just work for both). What this means is that you don’t need to pay for All-in Maintenance to keep up to date in the first year. You’re therefore saving twice: by avoiding the price hike and by not needing to add about US$220 for All-in. You can add All-in later, or optionally pay for upgrades as you see fit. If you do decide to upgrade later, you will be expected to sign up for All-in at that time, so there will be a catch-up cost associated with that.

Upshot: if you’re going to buy new BricsCAD licenses, be quick. Do it now. Next week might be too late.


If you intend doing this and also want to support this blog, then please use this link:

Bricsys Store

Disclosure: this is a sponsored link. If you buy a Bricsys product using this link, I get part of the proceeds. However, this will not have any effect on the editorial content of this blog. I don’t expect to be able to retire on the proceeds from this link (if any) and I will continue to write what I honestly think about the CAD products and policies of all companies, as I see fit.

My Bricsys 2018 – getting there

Last month I attended my third annual Bricsys conference. Following on from Munich and Paris, this year’s event was held in London. (For those who remember M’s cheesy hit Pop Musik from 1979, you will notice that Bricsys is holding these events in reverse order, and the next event should therefore be held in New York).

Before we get to the conference itself, I should point out that I preceded it by pinging around Europe doing other Bricsys-related things. I had a couple of days in Berlin with BLADE creator Torsten Moses, preparing our upcoming presentation on BricsCAD’s VLIDE-beating IDE.

We retired to a church building in a forest just outside Berlin and spent a very long day thrashing out a series of demonstrations, down to the last click and keystroke.

Then I shot over to Vienna for another couple of days, where I interviewed the good people at Schrack Seconet about their experiences with their 101 licenses of BricsCAD.

Look out for that when it’s published on the Bricsys Blog in the forthcoming Real World BricsCAD series.

I spent a couple of days in the English countryside rehearsing and preparing for the BLADE presentation, and took this photo which I inserted into my PowerPoint at the last minute.

THE BLADE at Reading Abbey – modernity towers over the ruins of what was once magnificent

Once in London and checked into the hotel, I visited the Bricsys 2018 venue, The Brewery.

It was interesting to check out the preparation that goes into running an event like this. Here, the AV people were testing the individual elements of the huge screen.

Then it was back to the hotel bar where I caught up with lots of old friends, many of whom I knew from previous Autodesk and Bricsys events. In addition to big CAD names like Ralph Grabowski, Randall Newton, R.K. McSwain, Robert Green, Owen Wengerd, Don Strimbu and several Bricsys high-ups, it was great to finally meet the amazing LISP talent Lee Mac.

Steve and a few of the former Autodesk people

It was particularly pleasant to meet up again with the fabulous and talented IPoCs Lynn Allen and Heidi Hewett, who I last met in person at the AutoCAD 2010 launch in San Francisco. The networking that goes on at these events can be just as educational as the presentations, and I certainly learned a few things over a Leffe or two.

Lynn loves Leffes

A dinner for (mostly) press people also proved educational. Despite knowing that some big announcement had been made to the Bricsys employees, we were still none the wiser about exactly what that announcement was. We know now, of course, but right then we were still in the dark.

One thing that was different for me this year is that quite a few people approached me to thank me for my writings on this blog. It was amazing for me to be standing next to somebody way more famous than me, and have people want to shake my hand. Although I found it odd, it’s also gratifying. Thank you to those people who took time out to say that they appreciate what I do.

In the next post in this series, I’ll describe day 1, where the shock announcement was made, and where a user group was born.

Other views on the Hexagon/Bricsys acquisition

I’ve made a couple of posts on this subject, but so have several others who might have different perspectives. This post is merely an accumulation of links to those other sources.

There was also extensive live commentary on Twitter using the #Bricsys2018 hashtag.

Image source: Bricsys

I expect to add to this post over time rather than making a new one. If you have any suggestions for other links to include, please comment below.

Hexagon acquiring Bricsys – what does it mean for the future?

As reported earlier, Swedish Hexagon AB has acquired Bricsys. It goes without saying that this was the big talking point among everyone at Bricsys 2018.

Surprise!

This announcement was a big surprise to almost everyone at the conference. Hexagon has been working very closely with Bricsys for nearly two years, so if someone was going to buy Bricsys then Hexagon would have been my first guess, but the fact that it was happening at all came straight out of the blue.

Most Bricsys employees in London only found out about the acquisition at a meeting in the hotel on the eve of the conference. Ably shepherded away from the area by legendary CAD figure Don Strimbu, I was unable to hear the announcement. I did hear the applause that followed it, though.

Gatekeeper Don and his ironic jacket

Fear, uncertainty and doubt

FUD often accompanies big change, so it’s no surprise that over the two days that followed the official announcement, I was asked by quite a few people what I thought of the news. My response went something like this:

I don’t know yet. It could be very good for Bricsys.

Erik De Keyser’s announcement that he’s staying around was welcomed, but there were still some concerns expressed. For example, an employee had been through something similar elsewhere and the company that took over proceeded to slice through half of the workforce. A partner feared that Hexagon only wanted to use BricsCAD as an engine to run CADWorx and that progress in other areas would be limited.

Answering questions

I was able to attend the press event and was able to ask some questions of Hexagon PPM Executive Vice President Rick Allen and Bricsys CEO Erik De Keyser.

Rick Allen and Erik De Keyser answer press questions

One question I asked of Rick went something like this:

Bricsys operates very differently to most companies. Is that going to change?

The response was interesting and instructive:

I don’t like fixing things that aren’t broken.

That’s reassuring, as were responses from Rick to other questions. He clearly understands CAD and what customers want. He and Autodesk have history, and he knows how they operate. He knows about the widespread customer dissatisfaction with Autodesk, he understands the reasons for it, and he plans to take ruthless advantage of it. He understands BricsCAD and the advantages it offers to AutoCAD customers who convert.

I had a chance to talk further with Rick at the after-event party. That was also very instructive. Rick “gets it”. Rick clearly understands very well that he’s bought an absolute diamond of a company. The port of the huge CADWorx suite to BricsCAD has given Hexagon a thorough insight into the quality of the people there and the software they write. I came away convinced that he really isn’t going to break it.

Crystal ball time

So, what will happen? Here are my best guesses, any of which could easily be proven wrong:

  • Bricsys will go on creating software as it did before.
  • There won’t be sackings. I expect an expansion of staff numbers rather than a reduction.
  • I don’t expect Hexagon to interfere too much in the software creation and improvement side of things, and any contributions are likely to be financial and beneficial.
  • Hexagon is a much bigger company than Autodesk. It will use its marketing power and widespread office network to increase sales world-wide, but particularly in the US. How this pans out for existing resellers is yet to be negotiated.
  • Hexagon is going to go after Autodesk customers. Hard. Not just AutoCAD customers, either, although in the BIM area it says it expects to win business more from the existing large untapped market than from existing Revit customers.
  • Autodesk is likely to get litigious. (Martyn Day: “This means war”). Hexagon is ready for this. (Rick Allen: “We went into this with our eyes open”). From the little I know, I suspect Autodesk will lose badly and go home with its tail between its legs.
  • Hexagon isn’t going to use BricsCAD purely as an engine to run CADWorx, because that would be stupid. In Hexagon’s best interests for BricsCAD use to become more widespread. It’s much easier to sell a suite of applications to a corporate client when it’s based on a commonly-used base rather than something few people have heard of. By dramatically expanding BricsCAD sales, Hexagon will win not only pure income but also the confidence of the market.
  • Prices? Who knows. It’s commonly held among industry observers that BricsCAD is too cheap for its own good. Maybe prices will creep up, but there’s a long way to go before they approach Autodesk levels.
  • Hexagon isn’t going to rename BricsCAD. Yes, I know Intergraph isn’t called Intergraph any more, but this is different. If you’re going to knock over a long-standing near-monopoly in the DWG world, you’re going to need a name with a long-standing history in that space and an excellent reputation among an important core of influencers. Starting again with a new name would make life more difficult than it needs to be. (This is the prediction I’m least confident about).

If I were asked now what I thought of the acquisition, I would modify my response somewhat:

I think it will be very good for Bricsys. Very bad for Autodesk, too.

The CAD world is in for a shake-up.

Hexagon acquires Bricsys

The acquisition of Bricsys by Intergraph-acquirer Hexagon AB was just announced at the Bricsys 2018 conference in London. That means that BricsCAD is part of an organisation with 2017 sales of €3,470 million – significantly larger than Autodesk.

This follows on from Hexagon’s previous close relationship with Bricsys that led to its CADWorx series of AutoCAD-based products also being available on the BricsCAD platform.

Hexagon Executive VP Rick Allen took the stage to explain his enthusiasm for the BricsCAD product, noting many of the strong points that will be no news to regular readers of this blog. Interestingly, he was not shy of pointing out the various technical and policy areas where Bricsys is strong and Autodesk is weak. That included the ongoing availability of perpetual licenses.

Erik De Keyser announced that he’s not going anywhere following the Hexagon acquisition, which was greeted with applause.

Interesting days lie ahead for Bricsys now it has a parent that’s more powerful than Autodesk.

A & B Tip 9 – drilling holes 3 – counterbores

In this series of posts, I’ll be providing tips that show how to do something in both AutoCAD and BricsCAD, hence A & B.

The Series

The idea behind this series is to provide useful information for several sorts of reader:

  1. AutoCAD users.
  2. BricsCAD users.
  3. People in the process of transitioning from AutoCAD to BricsCAD and who need to know what to do differently (if anything).
  4. People considering transitioning from AutoCAD to BricsCAD and who want to know about the differences and similarities.

Counterbored holes

This post continues to explain more about how to put holes in your 3D models. In this post I’ll be describing how to construct counterbored holes. Hint: the most efficient method is described last.

I’m going to start with this model and use different methods to create three counterbored diameter 10 holes that go through the block, each with a diameter 20 x 18 deep counterbore. I’ve placed circles of diameter 10 and 20 in place to indicate where the holes are going to go, and in some cases to act as the basis for extrusion.

If you’re unsure about how to locate these circles in exactly the right spots in 3D space, see my earlier drilling holes posts, part 1 and part 2.

Extruding circles

Assuming we have appropriate circles to work with, we can extrude them to create cylinders, then subtract them. This works in basically the same in both AutoCAD and BricsCAD, but there are differences:

AutoCAD BricsCAD
Invoke the EXTRUDE command:
Invoke the EXTRUDE command:
Select the inner circle and press Enter to complete the selection process:
Select the inner circle and press Enter to complete the selection process:
Move your cursor down and click when the extrusion goes beyond the bottom of the block:
Enter a negative number that equals or exceeds 100 (the thickness of the block):
If you just pick a point as per AutoCAD, the extrusion will go up rather than down. It’s also possible to point to the direction and amount to extrude by using the Direction subcommand and picking two points, for example a top and bottom corner of the solid.
Repeat the above process for the second circle, but this time specify an extrusion height of 18 while the cursor is located such that the extrusion is going down rather than up:
Repeat the above process for the second circle, but this time specify an extrusion height of -18. It has to be negative, otherwise the extrusion will go up even if you’re pointing down (unlike AutoCAD).

We’ll subtract these cylinders later.

Drawing cylinders

You can draw cylinders to subtract without needing construction circles. In this case one of the circles is just used to help locate the cylinder center point, but you can use other methods that involve no construction geometry instead, as explained in my first drilling holes post.

AutoCAD BricsCAD
Invoke the CYLINDER command (Solid, not Surface):
Invoke the CYLINDER command (Solids, not Meshes):
Locate the center of the cylinder, in this case using the center object snap:
Locate the center of the cylinder, in this case using the center entity snap:
Enter a radius of 5:
Enter a radius of 5:
Move your cursor down and click when the extrusion goes beyond the bottom of the block:
Move your cursor down and click when the extrusion goes beyond the bottom of the block:
Repeat the above process for the second cylinder, but this time specify a height of 18 while the cursor is located such that the extrusion is going down rather than up:
Repeat the above process for the second cylinder, but this time specify a height of -18:

Subtracting the cylinders

We can subtract all four cylinders at once to create two of the counterbored holes. This process is the same in both applications.

AutoCAD BricsCAD
Invoke the SUBTRACT command:
Invoke the SUBTRACT command:
Select the main solid as the object to subtract from and press Enter to complete that selection. Then select the cylinders to remove. This is easiest with an implied window. Pick a corner point containing no objects, starting on the left. Then pick the opposite corner to the right.
Press Enter to complete that selection and the command.
Select the main solid as the object to subtract from and press Enter to complete that selection. Then select the cylinders to remove. This is easiest with an implied window. Pick a corner point containing no objects, starting on the left. Then pick the opposite corner to the right.
Press Enter to complete that selection and the command.
End result:
End result:

Note that the first method replaces the circles with cylinders. The second method only uses the circles to help locate the center; they don’t really need to be there at all and are ignored.

Presspulling or Push/pulling

As described before, planar objects such as circles can be extruded by presspulling them. We’ll use that method to create the third counterbored hole. In this case, the operations differ somewhat between AutoCAD and BricsCAD.

AutoCAD BricsCAD
Hold down Ctrl+Shift+E to turn on dynamic presspull mode, hover over the space between the two circles and pick:
Hover over the inner circle. You should see the Quad Cursor appear, suggesting a push/pull operation. Pick the icon to accept that operation:
Now you can release Ctrl_Shift+E. Move your cursor down and enter 18:
Move your cursor down beyond the bottom of the block and pick.

Note the on-screen reminder that you can hit the Ctrl key to switch between several different types of push/pull operations. We can ignore this because in this case we want to use the default. However, it’s worth noting that this feature exists because it’s very handy.
Hold down Ctrl+Shift+E to turn on dynamic presspull mode, hover over the inside of the inner circle and pick. Release Ctrl+Shift+E, move your cursor down beyond the bottom of the block and pick:
Hover over the outer circle and pick the push/pull icon on the Quad Cursor. You could enter a height of -18, but in this case there’s a handy nearby hole counterbored to the correct depth and we can just pick the center of that instead:
In the AutoCAD presspull end result, the circles are left behind so if you don’t want them you will need to erase them.
Note also that your UCS origin is changed by this operation even if dynamic UCS is turned off. To restore it, use UCS Previous or use the UCS menu under the ViewCube to change it to World or any other named UCS:
In the BricsCAD push/pull end result, the circles are converted to holes so no more action is required. No UCS restoration is necessary.

Summary

Assuming you have construction circles in place, presspulling is the most efficient of the three methods in AutoCAD, even allowing for the tidy-up required at the end.

BricsCAD’s Quad-based push/pull operation is the most efficient method of the lot. Hover, pick, pick and hover, pick, pick is enough to create a counterbored hole.

Next: countersunk holes.

My Real World BricsCAD series is coming soon on the Bricsys blog

In February, my first Bricsys blog post appeared:

Inside Bricsys: Interviewing the creator of BLADE – the new Visual LISP IDE in BricsCAD V18.2

This was an amalgamation of my two similarly named posts on this blog where I interviewed BricsCAD’s Torsten Moses about BLADE, the LISP IDE that arrived with BricsCAD V18.2.

Today marked my first original-material post on the Bricsys blog:

Real World BricsCAD Series Coming Soon

I encourage you to hop over to the Bricsys blog to check it out. I’ve been interviewing real people about their use of BricsCAD and will be reporting what they have to say.

Disclosure: Bricsys is paying me to interview these people and produce these pieces.

Bricsys is not, however, paying me to sugar-coat anything. I’m being left alone to interview who I like and write it up as I see fit. A quote from today’s post will give you some idea of what’s in store:

The posts in this series aren’t going to be your average corporate-waffle puff-pieces. I mean, who reads those things anyway?

If you have used BricsCAD and are willing to be featured in this series, I would love to hear from you. Please contact me using this form and I will be in touch. In addition to the interviews in the pipeline, I have already had my first response to this invitation. A site in Austria with 70 users and lots of custom programming sounds like something I can get my teeth into.

Video – Steve on BricsCAD Unplugged

Following on from Lynn Allen and Robert Green’s guest appearances on the BricsCAD Unplugged webcast a couple of weeks ago, this time it was my turn.

Last night (my time) I was the special guest on the episode BricsCAD Unplugged – Steve Johnson 5 surprises moving to BricsCAD. I’m introduced at 2:12 and appear at 3:30. Here’s the full video:

In this week’s episode, you’ll witness:

  • Me discussing the five biggest things that pleasantly surprised me about BricsCAD. (I have more than five, but time was limited).
  • Don Strimbu bribing me with drinks containers.
  • An actual printed copy of Cadalyst magazine from 1995, complete with my old column Bug Watch (1995-2008).
  • The excellent euphemism, “You’re generally pretty conservative in terms of your praise.”
  • Don throwing me a curveball by introducing my points out of order!
  • The announcement that I’ll be at Bricsys 2018 in London and possibly participating in the BLADE session.
  • Me saying, “No. I’m wrong.”
  • Me drinking a glass of wine (parental guidance advised – alcohol consumption depicted). If you care, it’s a Shiraz (that’s Syrah if you’re American) from South Australia’s Limestone Coast region.
  • Total lack of coordination from everyone in raising our drinks at the end.

Thank you to the Bricsys crew for the invitation, it was a blast! If you ever want me on again, I’ll be happy to oblige.

For future reference, these live broadcasts run on the Bricsys Facebook page and are then quickly transferred to YouTube.

Mac users rejoice – at long last, a LISP IDE comes to OS X

CAD’s best LISP development environment has come to the best “AutoCAD for Mac”. It should come as no surprise to anyone that this has occurred without Autodesk’s involvement.

What’s happened?

With the release of BricsCAD (Mac) V18.2 (currently V18.2.23-1 to be precise), BLADE (BricsCAD’s much-superior equivalent to VLIDE) has been added to BricsCAD

See here for the release notes and here to download. Make sure you select the Mac version:

Significance

This is pretty significant for anybody serious about using DWG-based CAD on the Mac. AutoCAD without LISP is hardly worthy of the name, which is why I’ve never been keen on AutoCAD LT from the moment LISP was yanked out of it just before release in the early 90s. There has never been an integrated development environment for AutoCAD for Mac (either in the first iteration in the 1990s or the second attempt in the 2010s) and I think I can safely predict that there’s never going to be one. I expect AutoCAD for Mac’s LISP to remain forever in 1990 mode.

Compatibility

One problem a small number of users may face when developing for Mac with BLADE is that of downward compatibility. In case you’re wondering, BricsCAD (Mac) to AutoCAD for Mac is very much a downward direction, particularly in the area of LISP. The LISP in AutoCAD for Mac is famously half-baked with large portions of functionality missing, including no ability to control dialog boxes. BricsCAD (Mac)’s LISP is very much more capable, so while compatibility between AutoCAD for Windows and BricsCAD (Mac) is strong, you can’t say the same for LISP compatibility between AutoCAD for Windows and AutoCAD for Mac.

Half of the stuff you write for AutoCAD in Windows is just going to fail when you try to run it in AutoCAD for Mac. Much more of it is going to work in BricsCAD (Mac). While you can now write, debug and run your LISP code efficiently in BricsCAD (Mac) and it’s practically guaranteed to run just fine in AutoCAD and BricsCAD for Windows, it will be very easy to write stuff in BricsCAD (Mac) that doesn’t work in AutoCAD for Mac. Of course, the same downward compatibility problem applies to writing stuff in AutoCAD for Windows using VLIDE.

If you’ve moved on completely from AutoCAD for Mac to BricsCAD (Mac), that’s not going to be a problem. Bircsys building a notably better product that’s significantly more compatible with the main game is not something anybody could reasonably condemn. However, but it’s something to bear in mind if you are hoping to write code that runs on both AutoCAD and BricsCAD for Mac.

Summary

That caveat aside, it’s all good news for Mac CAD users. You already had a product available that would run a much higher percentage of the huge library of LISP out there than AutoCAD for Mac would. For the first time in history, you now also have access to a professional LISP development tool. Lucky for you, it’s the best such tool on the market.

Where on Earth is Lynn Allen going?

Well, this is a fun video for CAD geeks. The third in the BricsCAD Unplugged series of weekly webcasts, this one promotes the Bricsys 2018 conference which will be held on 23 and 24 October in London.

These live broadcasts run on the Bricsys Facebook page and are then quickly transferred to YouTube.

This one is interesting because of the people in it and some interesting news. It features Bricsys regulars Don Strimbu, Heidi Hewett, Vince Aman and Matt Olding, but also a couple of special guests. First on the scene is Robert Green (see 4:57) but the real surprise comes at 9:23 when somebody who may be familiar to you appeared in the bottom right corner:

The fun part comes when Lynn is “persuaded” with the promise of beer to turn up in London. Lynn won’t be going to AU this year (“My invitation must have got lost in the mail!”), along with quite a few others. So if you’re going to Vegas you’ll have to put up with somebody slightly less popular on stage instead.

So Bricsys 2018 in London is where all the cool people will be. Lynn and Heidi will be there and Robert will be rocking out with the Bricsys band. I might not be lead-guitarist-cool but I’ll be there too. What is said in the video about Bricsys conferences being great for meeting people is very true. Everybody’s approachable, right up to Bricsys CEO Erik De Keyser, so come up and say hello.

If you want to join us, sign up here. At the time of writing, there are just a few hours until the end of Early Bird pricing on the tickets.

Did I mention it’s being held in a brewery?

Oh, and there’s some CAD stuff.*

Here’s the full video:

* The CAD stuff alone made the Bricsys Conferences well worth attending for me in past years.