Tag Archives: DWG

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

2 Replies

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.

Why every AutoCAD CAD Manager should have a copy of BricsCAD – part 6, future proofing

2 Replies

This is the sixth and final 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 explains why adding a copy of BricsCAD to your stable of AutoCAD licenses is a good thing for your future and that of your company.

A CAD Management thing I did a few years ago was to examine the options for replacing AutoCAD and other Autodesk products. I was an AutoCAD loyalist (albeit a somewhat critical one) with over a quarter of a century invested in it. I was looking after the deeply entrenched and very heavily customised CAD environment of a major public utility company that had been using AutoCAD as its primary CAD system since the late 1980s. Hundreds of custom commands were in place and providing priceless productivity benefits. Hundreds of thousands of DWG files were on file, with thousands more coming through every month. The inertia behind AutoCAD was very, very strong. Looking outside the cage was a pretty radical step to take. What led me to that point?

  • Autodesk business policy. Autodesk has become increasingly anti-customer over the years in ways that will be familiar to all readers of this blog. I won’t rehash them here. This leads to…
  • Increasing costs. Autodesk software is expensive and getting more so. Autodesk has made no secret of its intention to move to an all-subscription (rental) model. This is an attempt to treble the ongoing income Autodesk receives, in return for doing as little as possible. Which leads to…
  • Lack of progress. It had become clear that the days of AutoCAD seriously improving from release to release were over, never to return. This isn’t because there is no room for improvement, it’s because Autodesk doesn’t want to improve AutoCAD. AutoCAD won’t be permitted to become too capable because that would just eat into sales of Autodesk’s other products. You’re not going to see 3D parametrics or sheet metal capabilities in AutoCAD: buy Inventor instead. You’re not going to see BIM capability: buy Revit. Beyond the internal competition issue, some years ago, Autodesk leadership lost interest in what it perceived to be an old-fashioned dead-end product. The income from AutoCAD customers is being diverted to fund purchase and/or development of more fashionable and interesting products.
  • Frustration with Autodesk’s Beta program. The goings-on within the Autodesk Beta program must remain private, so what I can say here is limited. I can say that I spent many years contributing large numbers of hours to that program in order to attempt to improve the product. As time went on, the positive results that emerged from that effort decreased; that much is no secret because it is apparent in the product. I felt I was fighting against Autodesk to try to improve the product, and losing. There were a few final incidents that persuaded me to stop bashing my head against that particular wall. I wasn’t the only one. I stuck it out for years longer than many very valuable people who had already given up before me.
  • Proxy server issues. Over the years, Autodesk’s habit of attempting to do sneaky things to access the Internet had caused a variety of problems in a secure proxy server environment. This caused several things not to work, and harmed performance severely in some places. As Autodesk’s developers turned over, things that worked in one release would not work in the next. Attempts to get this addressed as a support issue would result in the environment being blamed. These problems increased over the years as Autodesk threw in more and more connectivity-requiring features. There was a non-zero and ever-increasing possibility that one day, Autodesk would screw things up altogether and leave us with non-functioning software. That has already happened for some people, and although the stoppage has generally been temporary, it is important to have redundancy.
  • Poor performance. AutoCAD has been getting bigger and slower. Downloads are huge and Autodesk does its best to make them as difficult as possible. Installations take an age, as do uninstallations. Startup times are terrible and getting worse. My users were complaining – a lot – and there wasn’t much I could do about it.

That’s what moved me to take a very, very serious look at alternatives. Your motives may differ. Just the desire to have a Plan B in case of disaster might be enough.

If you don’t feel moved to investigate, you may eventually be faced with no option. Sooner or later, the person who holds the purse strings at your company may point to this year’s much bigger Autodesk invoice and ask, “What are we getting for this? How can we reduce our costs?” When that happens, you don’t want to be scrabbling round for answers before that invoice needs to be paid. Look into the options in advance. Are you really wedded to AutoCAD or are you actually tied to DWG?

Days of Future Past

Here’s my suggestion. Examine the available alternatives to AutoCAD and the other Autodesk products you use. Do it sooner rather than later so you get the chance to determine the answers to non-trivial questions like these:

  • Capability. Does the alternative product do everything that AutoCAD does, that your users need it to do? Does it do other stuff that AutoCAD doesn’t that you might find useful? What’s the performance like? How does it work on the hardware you have? Does it have user interface elements that don’t just look good but work productively in practice?
  • Compatibility. You will almost certainly demand extremely good DWG compatibility, but this question goes well beyond that. Will your LISP work? How about DCL? ActiveX support? DOSLib? Other programming languages? Can you carry over your customisation files? Can you make the interface look the same? If you have custom toolbars, or ribbon, or even image menus, do they carry across? Can your users carry across their skills without downtime, extensive training and a productivity hit? Can AutoCAD and the potential replacement coexist without issues? Can you use a common set of custom support files pointed at by both products? Will it work well on your hardware?
  • Add-ons. If you’re using third party products on top of AutoCAD, or if you’re using an AutoCAD-based vertical, is that product or an equivalent available? Does it work well? What do the objects they create look like in plain AutoCAD? Can you round-trip through AutoCAD and back and retain your intelligence? You’re probably going to have to test this with evaluation software and your own data.
  • Licensing options. Is perpetual licensing available? Can you stick on a release for a few years and still purchase upgrades later? Has the company committed to providing you with licensing options or has it made noises about going all-rental? Is network licensing available? Does it coexist problem-free with Autodesk’s network licensing software?
  • Costs. Compare the likely costs for all your options over several years. You’re going to have to make some assumptions. It can be difficult to work out what they should be.
  • Track record. Has the company been around for a while? What reputation does it have? Does it treat its customers with respect? How good is the support?
  • Future prospects. Is the company likely to be around long-term? Is it actively developing the product you’re interested in? Is it innovating? Is it merely following AutoCAD at a distance or charging ahead? Is the product going to be limited by Autodesk-like internal competition?

I went through all of these questions and settled on BricsCAD as the best option in my company’s case. In fact, several aspects made it really the only viable option. The product impressed me with high performance, capabilities well beyond AutoCAD in several important areas, a very high degree of compatibility (particularly LISP but also other customisation files), the availability of perpetual licensing and much lower ongoing costs. The company impressed me with its honesty and attitude toward customers.

Most of all, I was won over because I could see that the product had a future. Subsequent improvements have only strengthened that view.

Obviously, you need to make your own judgement based on your own circumstances. I would suggest looking at all the options, including sticking with AutoCAD permanently, with or without subscription or maintenance. Maybe you can use my investigations as a starting point, but I encourage you to start investigating now rather than when you’re under time pressure and don’t have time to do a thorough job.

It will cost you a few minutes to download and install of an evaluation BricsCAD and start preparing for the possibility of a different future. Maybe it won’t turn out to be part of your company’s future, but it could still be part of your future.

Options are good. Learning is good. Best case scenario, your knowledge is going to save your company money and improve its productivity, and you will end up smelling of roses. Worst case scenario, you’re going to spend some very justifiable time doing something new, different and interesting. I recommend it.

Other posts in the Why every AutoCAD CAD Manager should have a copy of BricsCAD series:

Part 1, fixing drawings
Part 2, 3D operations
Part 3, parts on demand
Part 4, efficiency
Part 5, LISP

Why every AutoCAD CAD Manager should have a copy of BricsCAD – part 5, LISP

5 Replies

This is the fifth 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 BricsCAD being better than AutoCAD at the one thing that made AutoCAD win the race against its competitors back in the 80s – LISP. That is, AutoLISP (added fully to AutoCAD in Version 2.18) and Visual LISP (fully integrated with AutoCAD 2000).

If you’re a good AutoCAD CAD Manager, you’ll already know the reasons LISP is an extremely important tool, so I won’t cover them here. I may explain those reasons in a later post, but that would distract us from the main point. Why is having a copy of BricsCAD useful to a CAD Manager?

  • BLADE. I’ve covered the BricsCAD LISP Advanced Development Environment in various posts already, and I intend to go into greater detail in future posts. There are enough advantages over VLIDE to warrant an entire series of posts. This is simply the biggest advance for CAD LISP in 20 years; if you’re doing any reasonably complex development in LISP and you’re not BLADE, you’re wasting time and money.
  • Performance. Because BricsCAD’s LISP engine is much more modern than AutoCAD’s, the performance is much greater. In my experience, it’s about three times as fast. Some function calls are as much as 30 times as fast. If you have a user who’s complaining that your routine is taking an age to process in AutoCAD, try it in BricsCAD instead. I once saved a user half an hour in processing time for one polyline by using BricsCAD. Another aspect that will benefit you when programming and testing is BricsCAD’s generally superior performance. Got nothing running and want to get programming in the next 5 seconds? Fire up BricsCAD. Want to do a complex process on a big drawing that makes AutoCAD run out of RAM? Try it in BricsCAD.
  • Licensing. While you’re developing in BricsCAD, you’re not using up an expensive AutoCAD license. You’re using a cheaper (or even free, while you’re evaluating it) BricsCAD license. Also, it’s a perpetual license so if you ever stop paying, you can keep developing as long as you like. Oh, and it’s not going to flake out on you on those days where Autodesk’s subscription licensing server has a meltdown.
  • Extra functionality. BricsCAD’s LISP has the AutoLISP and Visual LISP functions and then some. Some of the DOSLib functions are available without even needing DOSLib, but if you need the full set of DOSLib functions they can be loaded, as per AutoCAD. A range of extended functions are available with the vle- prefix, and the LISP Developer Support Package documents these and provides the source code so you can also use them in AutoCAD.
  • Platform independence. AutoCAD for Mac has severely restricted LISP capabilities, making it unsuitable for use in a professional, efficient custom environment. BricsCAD for Mac and BricsCAD for Linux both provide practically identical functionality to the Windows version. Yes, BricsCAD for Mac really is significantly more AutoCAD-compatible than AutoCAD for Mac.

I do my LISP development in BricsCAD these days, and can attest that it’s well worth the investment in time to get the hang of BLADE.

It will cost you a few minutes to download and install of an evaluation BricsCAD and check out the LISP situation for yourself.

Edit: it’s not just LISP. See James Maeding’s comment below about .NET, too.

Why every AutoCAD CAD Manager should have a copy of BricsCAD – part 4, efficiency

2 Replies

This is the fourth 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 BricsCAD being more efficient than AutoCAD for some of the things a CAD Manager might need to do. What do I mean?

  • BricsCAD starts up and closes down faster than AutoCAD, much faster in some environments. If your AutoCAD starts up slow (e.g. in some secure proxy server environments), pretty much any job you need to do to a user’s drawing that involves getting in, doing something quick, saving and getting out again is likely to be finished in BricsCAD before AutoCAD is even open.
  • If you perform a more complex operation on behalf of a user that is likely to take a while, there’s a better-than-even chance that BricsCAD will do it quicker than AutoCAD. In some cases it will do it much quicker (e.g. drawing compare).
  • BricsCAD tends to be able to cope with large drawings while using less memory than AutoCAD. If you have a user with a huge drawing who can’t work with it any more in AutoCAD and you need to split, purge or simplify it before it is usable, the very process of doing that in AutoCAD can itself be unworkably slow. Try the same thing in BricsCAD and there’s a good chance you’ll get the job done in a fraction of the time and without the same level of frustration.
  • If you perform a batch process that operaties on a set of drawings, under most circumstances it will be finished in BricsCAD well before the same thing is done in AutoCAD. Maybe this means you can process a set of drawings over lunch rather than wasting all afternoon on them or waiting until home time before setting the batch going. Plus you’re occupying a cheap BricsCAD license rather than an expensive AutoCAD one. Also, because BricsCAD uses much less RAM than AutoCAD while running, you can run your batch processes on that old PC sitting in the corner rather than having your top user sitting around watching your top spec PC grind away.
  • Certain user interface structures in BricsCAD are much more logically arranged and efficient to use than the AutoCAD equivalents. For example, if you have a drawing with an obscure setting that needs changing, unless you have an impeccable memory, you’ll find that setting much more quickly using the BricsCAD Settings command.

As I mentioned in my last post, this series is all based on stuff I’ve done in real life as a CAD Manager for a primarily AutoCAD-using company. Feel free to add your comments with your own experiences, even if they differ from mine.

It will cost you a few minutes to download and install of an evaluation BricsCAD and check out the performance and efficiency for yourself.

Why every AutoCAD CAD Manager should have a copy of BricsCAD – part 3, parts on demand

1 Reply

This is the third 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 as a mechanical and structural parts library for your AutoCAD users. As I mentioned in my last post in this series, I was writing a client-specific AutoCAD 3D training course recently. To demonstrate the concept of revolving profiles, and also to compare and contrast different styles of solid creation, I wanted to use a ball bearing as an example. The easiest way for me to get hold of an accurate example ball bearing model was to fire up BricsCAD (a few seconds) and select the part from the Standard Parts panel (a few more seconds).

It gets inserted as a block. After explosion to reduce it to 3D solids, I could then slice it in either BricsCAD or AutoCAD to form the basis for my example. I could save it at any stage in BricsCAD and open it in AutoCAD to continue to work on it seamlessly. What I can’t do is simply copy and paste from one application to another; you do need to save the DWG. You can then open it in AutoCAD or access the blocks using AutoCAD’s DesignCenter palette; if you’re doing this a lot you might want to point DesignCenter to a scratch DWG you keep handy for this sort of parts exchange.

There are currently 13 sets of standards:

Although you may already have your own parts library, having access to a wider range of international standards may prove useful. Aussie steel sections? Go for your life, mate.

Just how much stuff is available? A lot. Each of the sets of standards has multiple sections, each section has many parts, and many of the parts have many sizes. Depending on the part, other parameters (such as bolt length) may also be available for a given size.

Here’s the full Standard Parts panel in action, in this case selecting a nut.

BricsCAD Pro and Platinum have 3D parametrics built in (and given the minor extra cost I’d suggest going for Platinum), so it’s quite feasible to use it as the basis for your own 3D parts library. If you’ve built up a few 2D dynamic blocks in AutoCAD, you’ll be quite capable of doing the same thing in 3D in BricsCAD. The methods are different but straightforward enough to teach yourself.

As pointed out in a comment by James Maeding, you can set up a network license or two and install BricsCAD on everybody’s PC, giving everybody access to the goodies without excessive cost. Bear in mind that like Autodesk, Bricsys charges a premium for a network license over a standalone one. Unlike rent-or-go-forth Autodesk, Bricsys allows you to have a perpetual license and the total cost of ownership is substantially lower.

By the way, this series isn’t theoretical, it’s all based on stuff I’ve tried out in the real world. For example, the network license software will happily coexist with Autodesk’s network license software on the same license server. The services ignore each other; no clash, no problem. My experience is that it works just fine on a virtual server.

It will cost you a few minutes to download and install of an evaluation BricsCAD and check out the included parts content for yourself.

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

2 Replies

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:

  1. fight the same fight yourself in AutoCAD, eventually discover that the user was right, and then construct an excruciatingly awkward workaround; or
  2. 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.

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.

BricsCAD Shape – can a free DWG product be a BIM game-changer?

6 Replies

At the Bricsys 2017 Conference in Paris, one of the biggest surprises was the announcement of BricsCAD Shape. This product was demonstrated live, very impressively, in pre-release form. As I live-tweeted at the time, the demo jock was able to create a pretty decent architectural model in minutes, from scratch, very easily. That product has now been released.

What is BricsCAD Shape?

Shape is a 3D direct modeling application. At the core, it’s a simplified BricsCAD BIM. That means it’s small, fast, stable and it uses 2018 DWG as its native format. These are all good things. It’s obviously aimed at the AEC market, but there’s nothing to stop anyone using it for anything. Use it as a lightweight DWG viewer/editor if you like.

As you can see, it has a very simple, clean, cut-down interface. That dude is French Architect Jean Nouvel, by the way. He’s a block; you can erase him. He doesn’t appear in DWG files from other sources you open in Shape.

The idea is to do most of your work with the 18 buttons in this mini-ribbon/monster toolbar thing:

For less common operations, there is a set of pull-down menus. Although it’s hidden by default, you can even turn on a command line (Shift+F2) that will be very familiar to AutoCAD and BricsCAD users. Try to do without it; you will then discover how the excellent Quad Cursor interface (inherited from BricsCAD) uses AI technology to save you time and clicks.

How do I get it?

Click this link, enter your email address (no, they won’t sell it to spammers), and download away. Unlike Autodesk downloads, there are no nasty Akamai download managers to contend with, no multi-stage install processes, no massively bloated files, just a straightforward download of a 212 MB MSI installer. Time to download for me on ADSL2 was 2m 56s. The install time, including user interactions was 36s. Time for the first startup, including online registration, was 15s. That got me to the startup screen. The time for the first drawing startup was another 10s.

You can be using Shape in under 4 minutes. That is, you could be using it yourself in less time than it takes to read what I have to say about it.

How is it licensed? How much is it?

It’s a perpetual license, and it’s free. Bricsys has stated that it will always be free. Not much to complain about there.

So what’s in it for Bricsys?

The problem Bricsys faces in churning over large numbers of Autodesk’s disgruntled customer base is not the products. The products are fine. BricsCAD is notably superior to AutoCAD in a bunch of significant ways (while remaining inferior in a handful of less important ways), and costs a fraction as much.

No, the problem Bricsys faces is in persuading large numbers of people to try its products. Shape is an attempt to make that happen. It’s an ice-breaker in a way that goes beyond the usual 30-day free trial product.

There’s hardly any bar to entry; anybody with an email address can own it with zero investment. The interface has been kept very simple and there are a whole bunch of bite-size tutorial videos that demonstrate how to do things. If this product can create a buzz and get people to use a Bricsys product, half the battle is won. The models it creates are ready to be easily taken to the next stage using the full, paid product, BricsCAD BIM.

It’s not SketchUp
There are superficial similarities between Shape and the discarded-by-Google product, Trimble SketchUp.

However, there are very significant differences. SketchUp Free is a cloud-based product that works inside your browser (the paid product is currently a desktop product). Shape is a standalone application that does not require the Internet. SketchUp has its own file formats; getting those models into CAD or BIM is fraught. Shape is not just using industry-standard DWG file format, it’s a proper, efficient, accurate CAD application. Because it’s a cut-down version of what Bricsys is hoping you will use to fully develop the models later, there is no translation. The model you build in Shape opens directly in BricsCAD BIM where automatic classification of building elements can take place.

BricsCAD Shape. It’s free, it’s easy, it’s DWG, it’s CAD, it’s 3D, and it’s a pathway to BIM. It could change the game. I have no way of predicting whether that will happen. But if it does, it’ll be another kick in the guts for a dormant Autodesk that has largely given up on improving its products.

AutoCAD 2018 – why did the DWG format change?

105 Replies

In my review of AutoCAD 2018, I had this to say about AutoCAD 2018’s changed DWG format:

Why does AutoCAD 2018 need a new DWG format? It probably doesn’t. The 2013 DWG format is capable of holding pretty much anything you want… Although Autodesk cites performance reasons with certain drawings, I strongly suspect the new DWG format was introduced purely to make life difficult for competitors, and to encourage wavering customers to stay with Autodesk for fear of losing compatibility. In other words, it seems likely this is an anti-competitive change rather than a technical one.

In a recent blog post, highly respected Swiss-based Autodesk development and research person Kean Walmsley had this to say on that subject:

The main reason for the break in compatibility is some longer-term work that’s going on inside the AutoCAD codebase. For now this is really only surfacing in small ways – I expect it’s contributing some performance benefits, for instance – but the work is absolutely critical to the long-term viability of the product.

Kean’s a straight-shooter and I’m always ready to be corrected if it can be shown that I’m wrong. So I would be interested to learn more detail about this long-term work that’s critical to the long-term viability of the product. It might be good news for customers or really terrible news. If the groundwork is being laid for a file format that’s more heavily cloud-reliant or subject to continuous change, say, that would be an absolute tragedy for customers.

Autodesk is clearly manoeuvring customers into a position of maximum tie-in using various nefarious means, and if the DWG format change is part of that then it’s to be condemned. Maybe further information would help alleviate such concerns. Kean can’t provide that information, and neither can the selected bloggers who were given some insight under NDA last week, but I’m sure someone at Autodesk could. That is, if there really is nothing to worry about.

Kean also had this to say:

AutoCAD continues to be a core part of Autodesk’s business – and it continues to receive significant investment in terms of development resources – but don’t expect that to translate to buckets of shiny new features: AutoCAD’s feature maturity means the investment is rightly being focused in other areas (at least for now).

This had me wondering if Kean mistyped “immaturity”, because almost every AutoCAD feature from the last decade was released immature and only the lucky few eventually got finished. There’s a huge mass of outstanding work left to do in AutoCAD just to bring its existing half-baked features up to scratch, practically all of which could be done without disrupting customers with a new DWG format.

As for the feature set itself being mature, I can’t agree with that, either. Maybe it’s considered mature within Autodesk because of defeatist thinking about what’s possible with DWG-based CAD software? Kean’s comments seem to reinforce that impression. From where I’m standing, the lack of progress in recent AutoCAD releases demonstrates a severe lack of imagination and hunger to improve the product, not any inherent natural plateau in CAD development.

I believe this because Autodesk’s keener competitors have shown that no such plateau exists. Bricsys has proven that it’s very possible to improve an AutoCAD-like DWG-based product out of sight with genuinely useful and productive new features, and they can do it without changing the DWG format. Incidentally, my preliminary tests indicate BricsCAD V17 opens and saves DWG significantly faster than AutoCAD 2018, again without the need for a new format. More on that in a later post.

Back to Kean:

This is a tricky balance – and could easily be interpreted as a big company not caring about (some of) its users and only being interested in milking its cash-cow – but the work happening behind the scenes is significant and I believe will ultimately prove to be of real value to our customers.

Real value? History has taught me to be dubious about that. Many things that Autodesk promotes as being of value to customers turn out to be of net negative value. Time will tell with this one.

Sorry, but I really don’t believe that Autodesk cares about AutoCAD and its users as anything but an income source. I know there are still honest, hardworking, enthusiastic people within Autodesk (like Kean) who want to improve the product on behalf of customers. Good luck to those people, because their efforts are being stymied by management. The results we’re seeing out here in customer land are dismal, and no matter what spin is put on that, it must be disheartening.

Autodesk people, caring about users? Sure. Autodesk, the public listed company, as directed from the top? Nope. Autodesk’s actions and inactions tell me otherwise. Zero cares are given. No words can fix that, no matter who they come from.

AutoCAD really is being treated as a cash cow; hang one of those bells around its neck and be done with it.


(Original image: Daniel Schwen)

The biggest DWG file I’ve ever seen

14 Replies

Today, I tried to investigate a DWG file that one of my users couldn’t open. It wouldn’t open for me on an old 1 GB PC. Trying a PC with 4 GB didn’t help, and neither did experimenting with various releases of AutoCAD. Depending on the release, AutoCAD would either try to open the drawing and eventually die with an out of memory error, or would instantly inform me that the drawing was too big to open. I don’t have access to a 64-bit version of AutoCAD (which might possibly be able to open this monster on a PC with more than 4 GB of RAM), so the drawing is effectively useless.

The drawing is 242 MB (254,145,119 bytes), which I’m pretty sure is the largest drawing I’ve ever encountered. Based on a plot of a previous revision of the the drawing, it should be about 200 to 300 KB, i.e. one thousandth of the size it is. Looking at other oversized drawings from the same company shows that they are large because they contain lots of invisible proxy objects from a third party add-on or vertical variant of AutoCAD. Wblock will dramatically shrink such drawings, but care needs to be taken to ensure it’s not stripping out anything that might possibly be needed.

What is the biggest drawing you have ever come across? Did you discover what was making it so huge?