Category Archives: Bricsys

Why every AutoCAD CAD Manager should have a copy of BricsCAD – part 2, 3D operations

This is the second post in this series where I explain why this statement holds true:

As a CAD Manager looking after AutoCAD users, or a power user looking after yourself, it’s worth your while to have a copy of BricsCAD handy.

This post is about using BricsCAD to do things to help out your AutoCAD users who are having problems with 3D operations. Why would you bother using BricsCAD to mess with AutoCAD 3D models? Because sometimes AutoCAD can’t do stuff with them, and BricsCAD can.

If you have a user who finally asks for help after fighting AutoCAD for ages trying to get an operation to work such as an awkward fillet, a self-intersecting extrusion or a direct edit that doesn’t want to move, you have a couple of options:

fight the same fight yourself in AutoCAD, eventually discover that the user was right, and then construct an excruciatingly awkward workaround; or
fire up BricsCAD and see if you can do it there. There’s a good chance it will. If it does, hand the DWG back to the user with a smug look on your face. If it doesn’t, construct an awkward workaround in BricsCAD, because it will almost certainly be faster than doing the same thing in AutoCAD. Direct editing of 3D solids is more flexible and easier in BricsCAD; the Quad Cursor helps a lot.

I’ve been writing a client-specific AutoCAD 3D training course recently, and going through the exercises I’ve developed has been instructive. I’ve lost count of the number of times I’ve thought, “Man, this would have been so much easier in BricsCAD.” That’s before we get to the 3D parametrics that BricsCAD has had for a while and which AutoCAD never will.

Why is BricsCAD so much better than AutoCAD at making 3D work well? Because it has to be. When you base your entire product line (including BIM, parametric 3D, sheet metal and a host of other uses covered by 3rd party developers) on a single DWG-based 3D engine, that engine has to be robust, powerful, efficient and fast.

It’s not as if Bricsys can say to somebody struggling with performing 3D operations in BricsCAD that they should be using Inventor or Revit instead. That cop-out is unavailable. It has to just work.

Fortunately, Bricsys has acquired a small group of genius-level experts in this area, and holds on to them rather than dumping them when they get too experienced. It shows. Overwhelmingly, it just works.

It will cost you a few minutes to download and install of an evaluation BricsCAD and confirm this for yourself. It’s well worth it.

There are exceptions, of course. Nothing is perfect, and you will come across the occasional glitch. But those exceptions are definitely rarer than in AutoCAD. My experience also tells me that if you report those exceptions, there’s an extremely good chance that they will be fixed, and quickly. Bricsys ain’t Autodesk.

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

2 Replies

Here’s a mega-tip with a lot of experience behind it:

As a CAD Manager looking after AutoCAD users, or a power user looking after yourself, it’s worth your while to have a copy of BricsCAD handy.

Why? There are too many reasons to fit in one blog post, so I’m going to do a mini-series. The first post is about using BricsCAD to fix up drawings that are giving your AutoCAD users problems.

One of the things that surprised me most when evaluating BricsCAD as a potential replacement for AutoCAD was that my expectations were wrong when it came to the reliability of opening DWGs. Over the years, I collected a variety of DWGs that gave various releases of AutoCAD some problems. Some of those problems occurred while performing some kind of editing or processing, while others prevented AutoCAD from opening the drawing at all. I was expecting BricsCAD to have all those problems, plus perhaps some additional incompatibilities of its own.

What happened was the opposite. I don’t think I came across a single drawing that AutoCAD could open but BricsCAD couldn’t. On the contrary, BricsCAD was much more forgiving than AutoCAD, breezing through the process of opening drawings that had problems that originated in AutoCAD. Maybe 80-90% of my “problem” drawings were problems for AutoCAD alone. In many cases an AUDIT in BricsCAD and a re-save was enough to make the problem go away in AutoCAD. In other cases I could use BricsCAD to recover the unrecoverable using the traditional methods of WBLOCK, saving as an earlier release, saving as DXF, binary search (I may do a later post on exactly what that means), and so on.

Note that you may be able to obtain similar results using other DWG-based products such as DraftSight, ZWCAD or even the free BricsCAD Shape. However, I don’t have the experience with those products to be able to confirm that. Autodesk’s DWG TrueView, being a cut-down AutoCAD, tends to have the same problems as AutoCAD.

One thing that was particularly pleasant about using BricsCAD to fix problem drawings was the speed at which it could be done, because of BricsCAD’s generally superior performance. Closing and opening AutoCAD is painfully slow these days as the bloat gets worse, so having a product that fires up quickly is very handy.

Also handy is the availability of tools within the product that make it easier to locate and fix problems. Of particular importance is the Drawing Explorer, which provides a consistent and efficient interface that provides access to over 20 different types of aspects of a drawing (e.g. layers, linetypes, text styles, etc.):

One example arose showing how useful this is, when my users were having an intermittent problem with some drawings locking up AutoCAD 2015 on open. Some trial and error made it possible to discover that the trigger for this was the existence of a text style (any text style) with a bigfont attached, where the bigfont SHX file did not exist. It was possible to fix this in an earlier or later AutoCAD release, which the users may or may not have available to them, by opening the drawing, using the STYLE command, then using that dialog box to go through each text style one at a time, looking for bigfonts.

It was much easier to quickly fire up BricsCAD, use the STYLE command which opens the Drawing Explorer in the Text Style section, and see all of the text styles laid out at once (see above). It was very efficient to quickly look for recalcitrant bigfonts and make them go away, or to see instantly that bigfonts weren’t the problem.

Similarly, the consistent, searchable and efficient interface of the BricsCAD Settings dialog makes it easy to check the values of any settings that you suspect may be triggering the problem in AutoCAD:

As a CAD Manager, it’s definitely worth your 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.

Once you’ve determined that it really is an invaluable tool to have around, the cost of entry is low enough to make it relatively easy to justify the investment. You won’t need to recover many drawings to get your money back.

More details of Bricsys 2018 in London

1 Reply

As I mentioned in March, this year’s Bricsys conference will be held in London (yes, the British one) on 23 and 24 October.

More details have now been revealed on the Bricsys Conference page and tickets are now on sale. We now know:

- Venue: The Brewery, 52 Chiswell Street, London EC1Y 4SD, UK.
- Cost: €150, which is about US$180 (plus taxes in the EU, which you may be able to deduct). This is the early bird rate until 30 June.
- Speakers: Ten have been named so far, including big-name signing Heidi Hewett.

My attendance at the 2016 and 2017 conferences was well worthwhile, even coming from Australia. With the user/customer event now extending to two days rather than one, I expect this year’s event will be a step up from that. I’m hoping to attend this one too, in which case I will be happy to meet up with any of you.

bricsys,gent,london

Disclosure: Bricsys covered my travel expenses for the 2016 and 2017 conferences.

Steve’s BLADE presentation at the BricsCAD New Zealand and Australia Roadshow

3 Replies

Sofoco (Australia) and CAD Concepts (New Zealand) recently ran a series of seminars throughout Australasia demonstrating BricsCAD. I attended the last of these in Brisbane on April 19 and gave a presentation about BricsCAD’s LISP, with reference to AutoCAD compatibility and the tools available to CAD Managers and developers, including BLADE. The talk was aimed at anybody who is writing or maintaining LISP code for AutoCAD or BricsCAD.

I had the just-before-lunch slot, which is never desirable for a presenter. People are dozing off and/or bursting to go to the toilet, and time adjustments have to be made if earlier presentations run over. I started 10 minutes late and therefore had to remove the demonstration part of the presentation on the fly, but I had planned to allow for that eventuality. It’s been a while since I have presented like this before an audience so I was a bit rusty and it wasn’t as free-flowing as I would have liked. Too many ‘erms’!

Steve’s invisible accordion is impressively large

I did manage to keep the whole audience in their seats until the end, though, so that’s something. Maybe the fact that I was waving a sword around had something to do with it.

Here’s my video, which is 21 minutes long. The sound is a bit muffled and my accent is Australian, so you might want to turn on subtitles using the CC option in the YouTube player.

Disclosure: the organisers covered part of my expenses.

The game has changed – Robert Green migrates to BricsCAD

10 Replies

Is anybody left who still thinks BricsCAD isn’t a serious replacement for AutoCAD? If that’s you, perhaps the latest news might make you take it seriously. No, not the Heidi Hewett news. Even more recent news than that!

Robert Green, CAD Management guru, Cadalyst writer and consultant (not to mention a rather good guitarist) has been announced as the first Bricsys Certified Migration Consultant.

Image courtesy of Bricsys

Read all about what Robert has to say on this Bricsys blog post.

Anybody who has been reading this blog for the last few years will be surprised by none of what Robert has to say in that blog post. It’s not merely a repeat of what I’ve been saying for some time now, it’s all factually correct and easily verifiable by any competent CAD Manager.

I’ve been there and done that. I’ve gone through the process of taking a very complex custom AutoCAD environment, applying it to BricsCAD and giving it to my users. They loved it. No training was required to work as usual. Most things happened quicker, more conveniently, or both, starting right from the speedy installation. Once the product is in place and established, training can then be applied to take advantage of the places where BricsCAD is ahead of AutoCAD.

If you’re a CAD Manager where AutoCAD is used and you haven’t checked out BricsCAD yet, it’s about time you did.

This might come as a shock to those who see Autodesk domination of DWG CAD as a permanent fact of life, but the game has changed. AutoCAD’s stagnation and comments by senior figures show that the former flagship is clearly unloved by the powers within Autodesk. AutoCAD LT, even more so. An unimpressive AutoCAD 2019 shows that major improvements can no longer be expected in exchange for your ever-increasing annual payments, and with large numbers of people having been offloaded from the research and development teams, who would do it anyway? Meanwhile, BricsCAD development shoots ahead.

Thanks to decades of hostility towards customers that has only accelerated in recent years, Autodesk can’t even rely on customer loyalty for survival. When there’s a serious competitor that offers an easy migration path, the inertia that has kept Autodesk alive so far in the DWG space is no longer enough. The feeling among industry observers I meet is that Autodesk is in a decline of its own making. The only debate is whether that decline is temporary or terminal.

Back to Robert et al. Autodesk has lost many good people, and Bricsys is gaining them. The momentum is clearly with the Belgian company. Anybody want to run bets on who the next big name defector will be?

BricsCAD Shape for Mac

Leave a reply

BricsCAD Shape, the free DWG-based 3D direct modeling application from Bricsys, has now been released for macOS (formerly OS X). See my previous post on Shape for details of what it’s all about.

This is the same, just on a different OS. That’s because unlike Autodesk’s versions of its DWG products, the Bricsys versions are not cynically watered down for Apple users. Those users can now do full 3D conceptual modeling as part of a workflow that leads to full BIM (or simply view and edit DWG files if you’re not that ambitious), and without paying for the privilege.

It’s a proper free perpetual licence without usage restrictions, not a demo. You can’t get a perpetual license of DWG-editing software from Autodesk for any money, so by any measure Shape is a bargain.

The Bricsys blog post can be found here. The download page is here.

A Linux version of Shape is expected later.

IPoC interview – Heidi Hewett – part 3

2 Replies

Welcome to the first in this new series of interviews of Interesting People of CAD (IPoC).

First up, Heidi Hewett. Heidi has a long CAD history and is well known for being outstandingly good at her job. She made big news recently by shifting camps from Autodesk to Bricsys. Here is the third and final part of Heidi’s interview.

Steve: Did you go to Gent? What were your impressions of the people at Bricsys?

Heidi: Yes. After my initial discussion with Don Strimbu, he invited me to Gent to visit Bricsys headquarters and meet the team. While I wasn’t yet ready to give up my newly earned real estate license, who can turn down a trip to Europe? Don met me at Heathrow airport and accompanied me to Gent from there.

As soon as we arrived at the office, Don introduced me to Erik, Bricsys CEO, and other executive staff including Patrick, Mark, and Sander. I went into the office with Don every day that week as he arranged for me to meet and get product demonstrations from people across the organization. They were all incredibly welcoming and treated me as if I was already part of their team.

Several things about the office environment got my attention. The first was that nearly all the conference rooms were empty. And it was very quiet. People were sitting at their computers working, not sitting in meetings! They’re a team of dedicated people that know what they need to do and how to get it done. But they also know how to have fun.

A chiming sound ringing through the quiet office indicates an important event. One afternoon it signalled everyone to meet in the kitchen for Portuguese wine and cheese tasting hosted by Carlos, who was visiting from his office in Portugal. Each Friday at lunch the chime reminds everyone to head to Pinocchio’s for weekly pizza and wine. And I heard rumor that company hardware policy enables employees to keep their old computers when it’s time to upgrade. In exchange, the employee leaves a few bottles of wine in the community kitchen, which, coincidentally is right next to the rec room with ping pong table.

Steve: How about Gent itself?

Heidi: When I wasn’t in the office, I was exploring Gent and nearby Bruges, with my gracious hosts from Bricsys. It’s a beautiful city with so much to see. I look forward to the opportunity to return!

Steve: How have your former colleagues reacted to your move? Have they been supportive? How about the reaction form the CAD community in general?

When I decided to join Bricsys after all my years of working on and promoting AutoCAD, I was a little concerned about the reaction I’d get from the AutoCAD community, whether internal or external to Autodesk. But my concerns were unfounded. Immediately following the announcement that I joined Bricsys and for at least a week following it, I was bombarded with responses through social media and direct messaging. Names were scrolling by so fast that I couldn’t keep up. Former colleagues and customers that I haven’t talked to in decades as well as those I worked with just a few months ago. Many names I’ve never seen but suspect they belong to AutoCAD users somewhere around the world that have attended my presentations or read my posts.

I was truly touched by the kind words of respect for my past achievements and the enthusiastic support for my new endeavors. It made me realize this global CAD community is incredibly small and tight. And, even if we’re developing or using different CAD software, we have the same goal… to design amazing things. I’m proud to be part of it.

Steve: I’m sure you’re deeply immersed in learning everything you can about BricsCAD and related products. What has surprised you most so far about the software?

Heidi: It’s a little surprising how much there is to learn about a product that feels so familiar to me. I’m confident that I can jump in and immediately start using BricsCAD the same way I use AutoCAD. That’s reassuring but it’s not enough. The challenge for me, as it is for most CAD users, is to push beyond the old and familiar ways of doing things to take advantage of the software’s most powerful functionality. What I found most surprising about BricsCAD, is that it allows me to create 3D solid models in a way that’s intuitive and familiar yet with more intelligence than I thought possible in a DWG-based drawing.

Steve: What are you most looking forward to in your new role?

Heidi: When I met with Erik and team at the end of my week in Gent, he asked if/how I wanted to work with Bricsys. He knew that my career had been headed in a different direction, away from CAD, so he left it up to me to decide if I wanted to work part-time, full-time, consulting, whatever. After what I’d seen and experienced at Bricsys, I knew I couldn’t be any less than fully committed! There’s just too much to show and talk about and demo and teach.

I can’t come up with a single thing that I’m most looking forward to. That’s what attracted me to this role. What I’m most looking forward to are the Endless Possibilities.

IPoC interview – Heidi Hewett – part 1
IPoC interview – Heidi Hewett – part 2

IPoC interview – Heidi Hewett – part 2

Leave a reply

Welcome to the first in this new series of interviews of Interesting People of CAD (IPoC).

Steve: Did you have much involvement with AUGI?

Heidi: I haven’t had a lot of involvement with AUGI aside from presenting at CAD Camps they hosted almost a decade ago. I thought they were great events and was sorry to see them fade away.

Steve: What do you think the benefits have been for Autodesk in helping to support AUGI over the years?

Heidi: While I haven’t had a lot of experience working with AUGI, I think any opportunity a company has to get closer to their customers is worth pursuing.

Steve: How much presenting did you do at events like AU and others? Did you enjoy that?

Heidi: During the first half of my career at Autodesk I did a lot presenting at AU, CAD Camps and many other events. My kids were young then. As they got older, I didn’t want to miss all the big things in their lives. So, while I was always willing to travel to events, I didn’t seek them out. Instead, I did more webcasts and limited most of my travel to train-the-trainer events. I especially enjoyed the train-the-trainer events because I felt like I was sharing my knowledge globally without spending all my time on airplanes. Instead, I traveled to a few Autodesk sites in Europe or Asia to train a group of employees and partners from various countries in that region. Then, they would take what they learned, and the materials I provided, back to their countries where they could present it to customers in their local languages.

Steve: You and Lynn Allen worked closely together for many years, right?

Heidi: Yes, I met Lynn soon after she started at Autodesk. She was in the Training department and I wanted to join their team. That’s where we first worked together and became friends almost a quarter of a century ago. I think she’ll back me up when I say we were both 5 years old at the time!

Since then our paths have crossed many times. Each year when I was ready to present the newest AutoCAD functionality, first to employees, I reached out to Lynn so that I could schedule my training session around her busy travel schedule. And, as she was traveling the world, receiving more presentation requests than she could schedule, she referred the AutoCAD ones she couldn’t cover to me. On more than one occasion I’d be at some international event and a customer would bring Lynn’s Tips and Tricks book to me for an autograph, thinking I was her. Or they’d insist that they met me at that same event several years before even though I’d never been there before. Being mistaken as Lynn Allen is certainly flattering!

Steve: It’s kind of bizarre that such a successful team was thought to be no longer required. Do you have any idea what was behind that?

Heidi: I don’t have any insight on the thinking behind it. But, I try to believe things happen for a reason. I wasn’t sure what that reason was, until now… and I’m thrilled!

Steve: You’ve now joined Autodesk competitor Bricsys, which is something of a coup for them. Who contacted you initially? Was it Erik [De Keyser, Bricsys CEO]?

Heidi: Ironically, the first contact I had about Bricsys was from Lynn Allen. Not because she was working for them. But because Vince Aman (formerly from Autodesk, now working for Bricsys) had been trying to reach me through LinkedIn. I was attending a real estate class at the time, in preparation for what I thought was my next career. I received a text from Lynn telling me to check my LinkedIn messages. After speaking to Vince, briefly, I reached out to Don Strimbu, VP of Communications at Bricsys. I’ve known Don since my first years at Autodesk and wanted to hear about his experience at Bricsys.

IPoC interview – Heidi Hewett – part 1
IPoC interview – Heidi Hewett – part 3

IPoC interview – Heidi Hewett – part 1

Leave a reply

Welcome to the first in this new series of interviews of Interesting People of CAD (IPoC).

Steve: You’ve been doing this a long time, but was there a pre-CAD part of your career? What did you do before Autodesk?

Heidi: I didn’t have much of a pre-CAD career. I started college at Colorado State University as a Computer Science major. One day I stopped by the Industrial Design lab to meet one of my friends. He was taking a drafting class and had just been introduced to AutoCAD. He wanted me to see it. Using a stylus, he drew an ellipse on the tablet (not today’s kind of tablet, of course). The ellipse appeared in green on the monochrome monitor… like magic! That’s all it took. I was hooked! I realized I didn’t want to program computers, I wanted to draw with them. So, I checked around to see what majors would best let me combine my interest in math with my interest in AutoCAD. The next semester I transferred to the University of Colorado for Architectural Engineering.

After graduating, I moved from Colorado to California to take an engineering position with an MEP firm in San Francisco. They worked exclusively on drafting boards and I soon realized that what I enjoyed most about my engineering education wasn’t engineering, it was using AutoCAD! Within the first year I managed to convince my boss that we needed AutoCAD (I was a horrible manual drafter)! While working with a local reseller to set up our new CAD lab, I learned that the company that makes AutoCAD was located right across the Golden Gate Bridge, in Sausalito. Less than a year later, I was walking down the hall at Marinship Way, passing people like John Walker and Amar Hanspal (my hiring manager). I was in awe that I actually worked there.

Steve: You were with Autodesk for 26 years, right? Were you a Technical Marketing Manager all that time, or did you start at Autodesk with something else?

Heidi: I started in Product Support, as a support technician answering calls from resellers. It wasn’t a good fit for me. Nobody ever calls product support (at any company) to talk about how much they love their product. They only call when there’s a problem and they need help. And, most of the questions weren’t about how to use the software. They were about how to configure plotters and digitizers. I loved AutoCAD and wanted to share my knowledge about how cool it was. So, aside from my first few years in Product Support, my career at Autodesk was focused on educating users on what they could do with AutoCAD. My titles included Illustrator (back when we had printed manuals), Training Specialist, Marketing Support Engineer, Senior Applications Engineer, and Technical Marketing Manager.

Steve: What did a Technical Marketing Manager do, exactly?

Heidi: It’s kind of funny, Technical Marketing Manager was my title for more than half my career, but it was probably the least descriptive of what I did. I was technical and worked under the Marketing organization. But I did the same thing in that role that I did in all my previous roles aside from Product Support. I was a Learner and a Trainer. I worked with the AutoCAD development team to learn what was coming in the next release of AutoCAD. Then I created documents and videos such as the Preview Guides and Launch Demo Videos to help educate Autodesk employees, partners, and customers on the new functionality. Regardless of my official title, it was the perfect job for me because I got show people how cool the software was.

Steve: What did you enjoy most about that job?

Heidi: There were many things I enjoyed about the job so it’s hard to narrow down. I enjoyed working directly with the development team to be one of the first people on the planet to understand and use the newest AutoCAD functionality. And I enjoyed travelling around the world to share what I learned with our partners and customers.

Steve: I’ve noticed that your written materials always show a very high standard of clarity and correctness. What would you put that down to?

Heidi: That’s quite a compliment and I appreciate the acknowledgement.

I graduated from college without having taken a single English class. Back then it wasn’t required for Engineering majors and I was thrilled because I hated to write. As I got further into my career, I realized how crucial writing skills were, even for a math-minded person. That was around the same time I realized my true passions were around training and education. So, after a little research I found two relevant graduate programs at the University of Colorado, Denver. One was a Master in Technical Communication (so I could finally learn to write) and the other was a Master in Information and Learning Technologies. I couldn’t decide between them, so I did both! Having two young children and a full-time job with a lot of travel, it took me almost 7 years to graduate but it was worth it! The technical communication skills that I learned gave me the confidence to write publicly and I launched my original AutoCAD Insider blog, as one of my class assignments.

Steve: Would you say you’re obsessive about the quality of what you put out?

Heidi: Yes, I’m definitely obsessive about what I produce. There are many times I wish I wasn’t because it can be time-consuming. But, if I make a statement (written or oral) I want to know that what I’m saying is accurate to the absolute best of my ability. A perfect example is one of my first blog posts for Bricsys. It started as a quick and simple post about installing the trial version. How complicated could that be, right? But for me it’s not just writing about what I see, it’s understanding it. Writing that simple little blog post produced a string of emails between myself and the BricsCAD development team. Most of the information I learned didn’t make it into the blog post but it helped me fully understand and believe what I was writing.

The greatest value I get from writing is learning. If I want to learn something, I write about it. Because, until I can clearly explain it to someone else, I probably don’t really understand it myself. My first and best experience with the value of writing was when I wrote about sheet sets for AutoCAD. It was such a new, big, and overwhelming topic that I just couldn’t grasp it. Not after discussing with members of the development team and not after trying it for myself. The only way I could fully understand and communicate sheet set functionality was to write about it step-by-step. And so, Sheets Happened!

IPoC interview – Heidi Hewett – part 2
IPoC interview – Heidi Hewett – part 3

Steve at the BricsCAD New Zealand and Australia Roadshow

Leave a reply

Sofoco (Australia) and CAD Concepts (New Zealand) are currently running a series of seminars throughout Australasia demonstrating BricsCAD.

Here are the dates and locations:

Auckland – 9 April 2018, Jet Park Hotel and Conference Centre
Christchurch – 11 April 2018, Christchurch Community House
Melbourne – 17 April 2018, Airport Motel and Convention Centre
Sydney – 18 April 2018, Stamford Plaza Sydney Airport
Brisbane – 19 April 2018, Royal on the Park

Each seminar is in two parts. The morning session is for leaders and decision makers and the the afternoon is less structured and goes into more details, with informal discussions, questions and answers and one-on-one sessions. There will be many short presentations from various presenters to demonstrate the different things that BricsCAD is capable of, with or without third party add-ons.

I’ll be travelling to the Brisbane show. I’ll be there for the whole day but will be doing a brief presentation about BricsCAD’s LISP, with reference to AutoCAD compatibility and the tools available to CAD Managers and developers, including BLADE.

I have experience not only in developing using LISP in AutoCAD and BricsCAD, but also in transitioning from one to the other in a comprehensively modified custom environment. I hope to be of some assistance to CAD Managers and users who are considering such a move. I believe there are still seats available.

Disclosure: the organisers will be covering part of my expenses.

Heidi Hewett – Autodesk loses, Bricsys gains

2 Replies

The most excellent Heidi Hewett was, bafflingly, one of the big-name casualties in Autodesk’s latest experience cull. What was already a big loss to Autodesk has been compounded by her arrival at Autodesk’s most significant AutoCAD competitor, Bricsys.

Heidi has accepted a position as User Success Manager with the Belgian company. I don’t blame her. Bricsys is where the action is. Here’s her opening salvo:

For well over a decade, the world was told that the .dwg file format is not suitable for advanced design workflows. It can’t be used for mechanical design, and it certainly can’t be used for BIM. Bricsys has shown that this old belief is simply not true. The .dwg file format is alive and well and kicking serious butt. I am looking forward to helping Bricsys take .dwg to new, previously unimagined levels, and I’m excited to be part of the team that is doing this for our users.

Is it just me, or does Heidi look more relaxed in her Bricsys photo than she ever did in her Autodesk ones?

Photo credit: Bricsys

Here’s Heidi’s first Bricsys blog post. Can you feel her genuine excitement? Maybe she’s just happy that she’s going to have masses of real improvements to write about, rather than having to stretch out an ever-shrinking set of new AutoCAD features each year.

Given Heidi’s outstanding contribution to assisting CAD users over many years, I’m very happy that she is now going to be able to continue that work. I suspect she’s going to be very busy!

Autodesk loses, Bricsys gains. Big time. What on earth was Autodesk thinking?

Video – 3Dconnexion fine tuning in BricsCAD and BricsCAD Shape

3 Replies

The second video in the cad nauseam YouTube channel is more typical than the first in that it’s a tips and tricks video. In this case it only applies to BricsCAD and Shape users, but future videos will provide information for AutoCAD and other DWG-based CAD applications.

Bricsys 2018 comes to London

Leave a reply

I’ve had the pleasure of attending the Bricsys Conference in 2016 (Munich) and 2017 (Paris). This year’s conference will be in another great European city, London, on 23 and 24 October.

Other details have not yet been revealed, but will be posted on the Bricsys Conference page as time goes on. You can sign up on that page for email notifications.

This is a great opportunity for British companies looking at reducing costs and improving efficiency in their CAD and BIM operations to get an idea of what BricsCAD and related applications can do. If you’re further afield, it’s still worth the effort. I was certainly blown away by what I learned at my first conference, and I’d already been evaluating the product for a couple of years before that. It was well worth the journey from Australia.

Disclosure: Bricsys covered my travel expenses for the 2016 and 2017 conferences.

Rock on, Robert Green!

1 Reply

I’d like to offer my congratulations to Robert Green on his landmark of 400 issues of the CAD Manager’s Newsletter. There’s a interview with Robert here.

As a fellow CAD Manager and Cadalyst contributor, I’ve admired Robert’s work for many years. I finally got to meet Robert last year at the Bricsys Conference 2017 in Paris, and it was a pleasure.

Legends on stage – Robert being interviewed by Don Strimbu at Bricsys 2017

Robert, R.K. McSwain and Steve enjoy lunch at the Carrousel du Louvre

No pictures! R.K. McSwain, Nancy Johnson and Robert

Robert rocks out

Some of you will already be aware that Robert is a seriously good guitarist, and he did not disappoint at the after-conference party. I look forward to seeing Robert again, and to reading many more of his insightful articles.

CAD Panacea tip – startup files in BricsCAD

3 Replies

One of the things that might initially baffle a CAD Manager or power user when investigating switching from AutoCAD to BricsCAD is how to set up the startup routines. Head over to CAD Panacea for R.K. McSwain’s concise, handy description of how to do it.

Due to BricsCAD’s high level of compatibility, you can maintain a common folder or set of folders containing LISP and other custom files for both applications. That way, you don’t need to do double maintenance during the transition period. I’ve done this successfully in a highly complex custom environment. Some code and other adjustments were required in places, but all but a handful of my hundreds of AutoCAD LISP files worked as-is in BricsCAD with zero effort.

Having added your AutoCAD custom folder(s) to BricsCAD’s search path, I suggest you make a common startup LISP file (e.g. rename your old acaddoc.lsp to something like CADStartupDoc.lsp) and have tiny stub startup LISP files for each application (acaddoc.lsp and on_doc_load.lsp) that each loads the common startup file.

acaddoc.lsp contents:
(load "CADStartupDoc")

on_doc_load.lsp contents:
(load "CADStartupDoc")

You can add error checking and messaging if you like, but if you have control of your environment you probably won’t even need that. If you find you do need any application-specific code, you can just add it or load it from the acaddoc.lsp or on_doc_load.lsp stubs as appropriate.

BLADE – putting things back to “normal”

2 Replies

Disclaimer: I’m making money using BLADE. I’m using it on a paying project right now (well, not while I’m typing this, but you get the idea). I’m developing a routine to automate a massively repetitive task for one of my AutoCAD-using clients, and I’m developing it in BricsCAD and BLADE rather than AutoCAD and VLIDE.

I can simply develop faster in the more modern environment, and BricsCAD’s significantly quicker start-up time helps with that. So does the fact that the routine runs several times faster in BricsCAD, making testing the large data sets much more efficient. I’m getting paid on results and not by the hour, so using BLADE is putting cash straight into my pocket while giving me more time to walk my dog.

Using BLADE in production, I’m discovering a few bugs, quirks and things I don’t like. That’s totally understandable with a new feature of this level of complexity and functionality. Where I think it makes sense, I’m submitting problem reports or feature requests to Bricsys. I’m sure Bricsys already has a bunch of these from other developers, so they’ll be very busy for a while. From past experience, I know my reports will be taken seriously and acted on appropriately in a timely manner, if it’s feasible to do so. Your LISP IDE feedback won’t be ignored for decades by Bricsys.

One of the things Torsten Moses mentioned to me that didn’t make it into the published interview was that many developers are very conservative. There’s some truth in that. I’m missing certain keystrokes, for example: 1978-era WordStar Ctrl-Y to delete a line, anyone? It’s a reasonable expectation that as more VLIDE users migrate to BLADE, many requests will come in for VLIDE-like things. I’m told that some of these things will be provided in coming months.

In the meantime, there are things we conservative developers can do to make ourselves feel more at home. One of these is to configure the editor appearance. Here’s the VLIDE editor:

Here’s the BLADE equivalent:

One of the great things about BLADE is how configurable it is, and I know Torsten’s working right now on making it even more so. Configurations are stored in the Registry in a version-independent location (HKCU\Software\Bricsys\BricsCAD\VLispDbgEditor). These can be exported and imported directly or via BLADE, so multiple complete setups and configurations can be managed.

In this post, I’m going to be going through the process of configuring BLADE’s editor appearance to make it look more like VLIDE. I’m not suggesting that’s necessary or even a good idea in most cases, but if you really want to do it, here’s how.

Note: before you do all this manually, please note that at the end of this post I will provide a configuration file that will do it for you.

Start up BricsCAD V18.2 or later and start BLADE using either the BLADE or VLIDE command.
Open a LISP file in BLADE so you can check the effects of the changes we’re going to make.
Use Preferences > Show preference dialog…
In the Preferences & Settings dialog, pick the Styles tab and the Lexer Styles sub-tab.
I’m perfectly happy with Courier New 10, but if you want the VLIDE look, change 1 – Default text to Fixedsys 11.
Click next to 3 – Comment, turn on the Background color toggle and change the Back Color to mid-grey (192,192,192) and Fore Color to dark magenta (128,0,128). You’ll need to specify that RGB value in the lower right corner and use Add to Custom Colors to do this.
Click next to 5 – String and change the Fore Color to magenta (255,0,255).
Click next to 7 – Operator and change the Fore Color to red (255,0,0).
The 8 – Keyword 1 setting should already be blue as in VLIDE. If you want system constants such as T, nil and pi to also be that shade of blue then change 9 – Keyword 2 accordingly. Personally, I prefer a different shade so they stand out. Mid-dark cyan (0,128,192) works well.
I like the pale grey background in BLADE that helps identify the current line. If you don’t, click next to 8 – Caret colour and turn off the Background color toggle.
Switch to the Editor Colors sub-tab, click next to 5 – Selection colour and change the Back Color to a custom mid-blue (0,120,215).
While you’re in the Editor Colors sub-tab, there are a few other non-VLIDE things you can play with. 1 – Brace hilight and 2 – Brace mismatch are dynamically applied to matching and non-matching parentheses respectively. I like my Brace hilight setting to be plum and bold (turn on the Attributes toggle to enable this):

I like my non-matching setting to be white on red (the inverse of a normal parenthesis so it shows up):

Changing all that should give you something that looks like this. Familiar enough?
There are several things in the above image that might be unfamiliar but which I suggest you leave turned on because they’re useful. If you really insist, here are the locations for these settings in the Preferences & Settings dialog:

Line numbers – View > Margins, Show line number margin
Marker margin – View > Margins, Show marker margin. If this is turned off, bookmarks show up using the settings under Styles > Editor Colors > 13 – Bookmark marker.
Edge marker (that vertical line on the right indicating 80 character width) – View > Edge marker > Type, No background.
Indentation guides (those vertical lines that show you what your code is lining up with) – Tabs and EOL > Indentation, Show indentation guides.
Code folding margin (the margin on the left that allows you to collapse functions, etc. – Folding and Wrapping > Show code folding margin.

Unlike VLIDE, the default in BLADE is to use spaces for indentation, not tabs. As I don’t know of any LISP developer who uses tabs except by accident, this is a much more sensible default. But if you really want to use tabs, turn it on using Preferences > Use tabs and set the width to the VLIDE default of 8 in Preferences > Set tab width.

If you’ve left opening parentheses on previous lines and have indented the following code as usual, then as you go on to finish off the code with closing parentheses, in BLADE a single backspace will take you back your indent width (2 spaces by default) rather than a single space as in VLIDE. If your coding finger can’t get used to this keystroke-saving feature, you can turn this off with Preferences > Backspace unindents.

Having done all that, and having arranged the rest of the interface to your needs (overall window size, pane and field widths, etc.), make sure you save it! It’s as simple as Preferences > Save preferences, but it’s not done automatically. If you want to keep a safe copy of your settings, you can do so with Preferences > Save preferences to file. This simply exports the relevant part of the registry to a .reg file of your choice. This is a text file you can hack about with at your leisure (using BLADE if you like!), and you can even make files that represent subsets of your preferences.

For example, I’ve removed all but the style settings from a .reg file I exported. I’ve uploaded it renamed as a .txt file because .reg files are considered dangerous by browsers, etc.

If you want to use this to give BLADE that old familiar VLIDE look, here are the steps.

Download SteveVLIDE-likeBLADEStyleSettings.reg.txt.
Rename the file to remove the .txt extension so it becomes SteveVLIDE-likeBLADEStyleSettings.reg.
In BLADE, use Preferences > Load Config from File
Close BLADE and BricsCAD.
Restart BricsCAD and BLADE.

That should do it. Happy BLADEwork!

Interviewing the creator of BLADE – CAD’s best LISP IDE – part 2

2 Replies

This post continues my interview with Torsten Moses about BLADE, the new LISP IDE that arrived with BricsCAD V18.2. See here for post 1.

Steve: I’ve noted before that BricsCAD execution of AutoLISP and Visual LISP is several times faster than AutoCAD’s. How does the new technology affect that performance?

Torsten: All the new BLADE-related stuff doesn’t really affect normal LISP execution outside the IDE and debugger. The connection is made by a few callbacks, which take zero time in normal processing. Therefore there is also no chance of breaking things. The BLADE implementation is very safe, and performance remains high for normal usage. For the debugger and the synchronization, it is all home-brewed stuff, optimized for best performance even when debugging, and minimum system and LISP memory usage.

In the course of implementing the debugger and internal versus external synchronization, I also removed most emulations and implemented that as core OpenLisp functionality. That has the side-effect that the (repeat), (foreach) and (vlax-for) functions now run about five times faster at the loop construction. So rather than slowing things down, creating BLADE has actually speeded things up!

Steve: Will the Mac and Linux versions also get this feature?

Torsten: Yes, it is fully compatible. This is due to the implementations of WxWidgets and my own stuff. I have already verified BLADE running under Linux. There are no differences; even the implementation code has no Windows-specific stuff.

Steve: Can you give a simple example of the workflow of a debugging session?

Torsten: First, don’t pre-load any LISP file into BricsCAD. Such code loaded outside the debugger is fully functional, but it can’t be used for debugging. The special connection between internal and external representation is only established when loading the LISP code under a debug state.

Next, in BLADE open an existing FAS or VLX project, and/or a “Named Session”, or simply any LISP file you want to start debugging with.

Now you can select Start Debugging from menu or toolbar, or hit the F8 hotkey. The special Debug Toolbar will appear. You can either activate AutoBreak, which stops at first executable code, or activate the LISP source where you want to start debugging and place some breakpoints.

Then load the dedicated LISP file, either by the normal Load into BricsCAD function, or from the Load button in the Debug Toolbar. Now that loaded code is debug-enabled and you will see the file and debug-enabled functions in the two right tabs.

When the debugger halts at the first breakpoint, all debug-step modes are enabled in the toolbar, and you have all the usual debug step modes. More than in AutoCAD’s VLIDE, actually. You can set the watches (observed and tracked variables) as “Data Break Point” by activating the checkbox. Then, whenever that value changes, the debugger also stops automatically at the related LISP statement.

Steve: What if your code calls code in other files you haven’t loaded?

Torsten: Don’t worry about that. The debugger recognizes this and will ask to load the related LISP file on-demand. In normal LISP, you would get an unknown function error but the debugger catches this upfront. In fact, this is one of the high-end features – only load the primary LISP file, any further debugging into other files resolves by loading during the debugging session. This is very handy for dealing with complex apps – there’s no need to preload any other LISP source. I’m sure you’ve experienced Murphy’s Law, where the particular function you need is the one that’s not loaded. You won’t have that problem in BLADE.

Steve: Where to from here? Is this job done or is there still room for improvement?

Torsten: As BLADE is still a very young product, there is definitely a lot more to come. So far, the main target was to provide good debugging features, and a somewhat reasonable handling of projects, but not so much focusing on plain editor capabilities.

My to-do list still has a number of major key features to be implemented. We want to add a hotkey editor, because every developer loves his own keystrokes and learning others is a nightmare! We also want cross-reference checking on a per-file and per-session basis, mainly for bigger LISP applications.

Then, over time, the editor capabilities will be extended and improved, providing more features. One example is to provide an editor tooltip that shows a function signature and short help when hovering over a LISP function name.

And of course, I’m aware that when people start using this in production, a lot of feedback will arrive from developers in the form of wishes, hints for improvements and bug reports. It’s very likely there will be many wishes to implement several details to make BLADE resemble AutoCAD’s VLIDE more closely. This could be a bit difficult sometimes, and is also not the main target. I hope that developers will be open to a slightly different workflow, given the big advantages they get in return.

In general we are very open to developer ideas, needs and requirements, as we are with BricsCAD itself. In the end, it’s the developer who needs to work with BLADE, as easily and productively as possible. Even the initial release of BLADE is based on important feedback from beta testers such as Martin Drese (CAD Wiesel).

Steve: I can certainly attest to how well you respond to feedback. I’ve seen bugs I’ve reported fixed in a very short timeframe.

Torsten, thank you for your time. This has been very illuminating.

This interview is also available in one post on the Bricsys blog.

Interviewing the creator of BLADE – CAD’s best LISP IDE – part 1

1 Reply

Easily the most impressive new feature of BricsCAD V18.2 is the new Visual LISP IDE, BLADE (BricsCAD LISP Advanced Development Environment). The lack of any LISP IDE has been a BricsCAD stumbling block for a while, dissuading CAD Managers from adopting BricsCAD to replace their stagnant and increasingly expensive AutoCADs.

As I will relate elsewhere, Bricsys has not just caught up with Autodesk here, but has shot so far ahead it’s unlikely to ever be caught. BricsCAD’s BLADE is so superior to AutoCAD’s VLIDE in so many ways there’s really no comparison.

Yet it remains highly compatible. I have personal experience in making large amounts of AutoCAD LISP code (literally hundreds of routines) work in BricsCAD. That experience tells me that the vast majority of code will work just fine (and much faster) in BricsCAD. A tiny proportion of LISP or DCL code may need adjustment before it will work perfectly on both platforms, and that’s one reason an IDE that works within BricsCAD was an important step that Bricsys needed to take.

I had the chance to see this IDE privately in then-unnamed pre-release form when I attended the Bricsys Conference 2017 in Paris. I was surprised and delighted at the functionality demonstrated by its creator, Torsten Moses. I recently had the chance to interview Torsten about his creation.

Steve: I understand it was difficult to create a LISP IDE for BricsCAD because of the way BricsCAD’s LISP works. Can you explain that?

Torsten: BricsCAD LISP uses the OpenLisp core system, from French developer Christian Jullien. This is the only LISP engine still under development; the others I found stopped development in the mid-90s.

OpenLisp is a very modern implementation, not comparable to the old XLisp dialect used by AutoLISP. Even object-oriented features are supported. Therefore the internal representation of LISP expressions is different from the textual representation as seen in a LISP file.

Steve: So the AutoLISP code I write isn’t the code that BricsCAD executes?

Torsten: That’s right. A number of typical AutoLISP constructions were implemented by a kind of emulation, which drives the internal versus textual representation differences even further. That makes it a major challenge to synchronize the internal OpenLisp expression execution with the related textual representation in order to provide any debugging functionality.

Besides the plain technical details, which seemed to be virtually unresolvable, there was the expected heavy effort to implement a full-blown GUI. This was not just a plain editor, but the entire IDE GUI. It would have been a disaster, a major disgrace, if we had provided a VLIDE that was just up to AutoCAD standards. That was great in its time, but it’s 20 years later now. The idea of creating a LISP IDE for BricsCAD seemed so filled with difficulties that we put it off for a long time.

Steve: How did you finally manage to overcome these difficulties?

Torsten: First, it was a pure coincidence. [laughs] By luck, I discovered a hidden detail in OpenLisp – any LISP symbol (and expressions are a kind of anonymous symbols) can hold unlimited, attached custom data, very similar to XData in DWG database objects. I even knew about that for many years, but never worked out the shortcut to ‘misuse’ this for the LISP expression execution to editor and debugger bidirectional connection. Some initial quick tests showed that this approach was very suitable.

By another coincidence, I discovered that WxWidgets (our cross-platform system, not only for GUI) already includes support for the famous Scintilla editor, an OpenSource editor engine, widely used by many editors. WxWidgets even provides two levels of wrappers – a plain, core wrapper, and a high-level wrapper class system. This fits perfectly into the WxWidgets logic.

But still, that is only plain editor support – not a GUI. Then I found a very suitable, extensible editor and GUI implementation, based on that WxWidgets Scintilla system – as Open Source under the WxWidgets license. Hence, we are allowed to use that source code in a commercial application. That editor is called wxStEdit.

I verified that this source was suitable for our LISP IDE, and put in a lot of extra work to extend it. wxStEdit development finished in around 2008, and it still was compiling and working mostly fine. Nevertheless, in the course of extending that GUI, I found and fixed a lot of defects at all related levels (Scintilla, WxWidgets Scintilla wrapper and wxStEdit).

So it was this set of coincidences that suddenly opened both wings of a big gate!

See here for part 2 of this interview.

This interview is also available in one post on the Bricsys blog.

Bricsys shows Autodesk how to do mid-term updates – again!

5 Replies

BricsCAD V18.2 for Windows is out. The new stuff in this mid-term update is again showing up Autodesk’s lack of progress with its once-flagship product, AutoCAD. I’m sure Autodesk would love customers to accept that there’s only so much anyone can do with a DWG-based CAD product once it reaches a certain level of maturity. Customers should get used to nothing of significance being added year after year. Diminishing returns, and all that. Pay to continue using the product, but don’t expect it to get better.

What a shame for Autodesk, then, that Bricsys exists. By consistently providing a raft of significant improvements with each full and mid-term release, Bricsys shows up that idea as nonsense. It’s perfectly possible to keep improving CAD at a very rapid rate, particularly if you’re not worried about competing with other products in your range. There’s a reason AutoCAD’s parametrics are restricted to 2D, and BricsCAD’s 3D parametrics in a DWG product proves that the reason isn’t technical. It’s strategic. Also strategic is cutting the guts out of an already much-weakened AutoCAD team, because you would really prefer your customers to be using your trendier and/or more expensive products.

I should point out that BricsCAD V18 customers who have a perpetual license, even without maintenance, will be receiving V18.2 with all its improvements free of charge. Contrast that with Autodesk, which is, despicably, withholding even bug fixes from selected customers. Autodesk’s attitude to customers who aren’t constantly paying up front is one of utter contempt. Autodesk feels entitled to your money; Bricsys wants to earn it.

So what’s Bricsys done to earn your money with BricsCAD V18.2?

Mostly, it’s lots of relatively small-sounding things that add up to significant productivity enhancements. There are several items that are playing catch-up to AutoCAD, such as long-overdue in-place text editing. There are big performance improvements in drawings with PDF underlays due to a smart multi-resolution cache mechanism. The 3D-to-2D generation mechanism has also been significantly sped up. Constraints (2D and 3D, unlike AutoCAD) are easier to create. Several 3D direct modeling operations have been made easier. That also helps with sheet metal design, which has seen other improvements.

In Bricsys BIM V18.2, a lot of smarts have been added. The mechanism for converting CAD models (including those made in BricsCAD Shape) to BIM models, BIMIFY, already did some fascinatingly clever things, but that’s been improved further particularly in the areas of structural member and room recognition. For those of us in Australia, support for our steel sections is very welcome.

For me, that’s not the big news. Oh, no. The big news for me is a thing called BLADE – the BricsCAD LISP Advanced Development Environment.

If you’re a CAD Manager or in-house developer and you’ve been waiting until BricsCAD had VLIDE, wait no longer. But this isn’t just catch-up. This is a big leapfrog over Autodesk’s sadly neglected IDE for CAD’s primary user programming language. There’s so much good stuff in BLADE that I can’t hope to do it justice here, so I will be covering it extensively in future posts. For now, here’s a statement for you:

If you program in AutoLISP or Visual LISP, you should be doing it in BLADE.

It’s that good. Really. Watch this space for details.

The download is small, the install is fast, it won’t harm your AutoCAD installation, and you can evaluate it free for 30 days. Links:

Gallery – Gent visit 2017 – Sights

Leave a reply

Here are some pictures of some sights I saw in Gent (Ghent) and Brussels during my visit attending the Bricsys Insights press event in April 2017. I published some of these photos at the time but had to remove the post due to technical difficulties I was having with WordPress galleries.

I agree with Serge Jonnaert in Why every Architect should Visit Gent, except I wouldn’t limit it to architects. It’s a very lovely place, well worth a visit by anyone.