Category Archives: Win

Steve’s fencing year 2016

Leave a reply

Some of you may be aware I’m an active veteran fencer. I’ve been a bit quiet over the past month because I’ve been away, attending two major fencing tournaments. I’ll post some video later, but here are my national and international medal results this year:

Australian Fencing Circuit 1, Melbourne, Australia
  • Veteran Men’s Sabre – Bronze and 50+ Gold
Asian Masters / Oceania and AFC 3 Veterans, Perth, Australia
  • Asian Masters / Oceania Veteran / AFC3 Veteran Men’s Sabre (50+) – Gold
  • Asian Masters / Oceania Veteran / AFC3 Veteran Men’s Foil (50+) – Bronze
  • Asian Masters / Oceania Veteran Men’s Sabre Teams (Australia A) – Gold
  • Asian Masters / Oceania Veteran Men’s Foil Teams (Australia Green) – Bronze
Commonwealth Veteran Fencing Championships, Christchurch*, New Zealand
  • Men’s Sabre (50+) – Gold
  • Men’s Sabre Teams (Australia) – Gold
  • Men’s Foil Teams (Australia) – Gold


* I flew into Christchurch the day after the earthquake.

Australian Open and Veteran Fencing Championships**, Canberra, Australia
  • Open Men’s Sabre Teams (Western Australia) – Silver
  • Veteran Men’s Sabre – 50+ Gold
  • Veteran Men’s Foil – Silver and 50+ Gold
  • Veteran Sabre Teams (Western Australia – Captain) – Gold
  • Veteran Epee Teams (Western Australia – Captain) – Gold
  • Veteran Foil Teams (Western Australia – Captain) – Bronze

** At these Championships I fenced in 11 events and came away with 7 medals, which I believe is a men’s record for Australian events.

So among other things, I’m 50+ Sabre Champion of Australia, Oceania, Asia and the Commonwealth. The Western Australia Championships were also awarded a couple of weeks ago, where I won Veteran Championships in all three weapons and the Master-at-Arms (all-rounder) Championship. All-in-all, a pretty good year!

BricsCAD startup LISP bug fixed

Leave a reply

In my previous post I have a real problem with BricsCAD, I related my then-latest interaction with the Bricsys support system:

Steve Johnson
05-12-2016 05:30 UTC
I don’t know if this is a BricsCAD problem or a DOSLib one, so I am reporting it to both Bricsys and Dale at McNeel. I’m also not sure if this was happening in earlier versions.

If I load DOSLib during an S::STARTUP call and then use the (dos_msgbox) function later in that call, this fails the first time round because BricsCAD things the function is not defined. Opening a second drawing results in the call working as expected. I’ve chopped down our startup routine so you have an example.

; error : no function definition ; expected FUNCTION at [eval]

Awesome Bricsys Person
05-12-2016 12:32 UTC
Hi Steve,

There was a regression introduced in V17.1.10 that caused startup code to execute too early under certain conditions, before the lisp engine document context was properly initialized. This has been fixed now for the next update.

Steve Johnson
06-12-2016 02:43 UTC
I must say, the responses I’ve been getting to my support requests have been absolutely bloody brilliant. Cheers!

Let’s just finish the sequence, shall we?

Second Excellent Bricsys Person
13-12-2016 19:18 UTC
Hi Steve,

I have very good news. The fix is included in BricsCAD V17.1.11, available for download.
Thank you for your help.

Following a fast and straightforward download and install, I can confirm that the bug is fixed. The elapsed time from my bug report to the fix being publicly available and me being informed personally of the fact was 8.5 days. Note that this isn’t a workaround, patch or service pack, it’s a permanent fix that is now automatically in place for everybody who downloads the software.

Edit: the new version was actually released at 4 PM on 9 December, so it was less than 4.5 days from report to fix. Outstanding!

I should mention that I also received a prompt and relevant response from Dale at McNeel, despite the fact that the problem was nothing to do with him!

For somebody used to dealing with Autodesk, this is a breath of fresh air. Bricsys team, take a bow!

I have a real problem with BricsCAD

3 Replies

To be precise, I have a real problem with writing  about BricsCAD. I’ve written some pretty complimentary things about BricsCAD lately. In the interests of balance, I’ve been intending to write about some of the issues people can expect to deal with when moving from AutoCAD to BricsCAD. Such issues certainly exist. The problem I have with that is that the issues keep going away!

Here’s how it usually goes. I find a problem in BricsCAD. I submit a support request. Within hours, I get a meaningful response from a person who understands the issue. Within days, I’m informed it’s been fixed internally and the fix will be in the next update. Within a week or two, that update is released. I download and install the updated version. It’s basically a full reinstall, but all settings are seamlessly retained and it’s faster and less painful than an AutoCAD Service Pack installation. The whole thing from start of download to completion typically takes 5 or 6 minutes. The problem is gone, and I have nothing to write about!

Here’s the latest interaction. This is typical, and has been repeated many times:

Steve Johnson
05-12-2016 05:30 UTC
I don’t know if this is a BricsCAD problem or a DOSLib one, so I am reporting it to both Bricsys and Dale at McNeel. I’m also not sure if this was happening in earlier versions.

If I load DOSLib during an S::STARTUP call and then use the (dos_msgbox) function later in that call, this fails the first time round because BricsCAD things the function is not defined. Opening a second drawing results in the call working as expected. I’ve chopped down our startup routine so you have an example.

; error : no function definition ; expected FUNCTION at [eval]

Awesome Bricsys Person
05-12-2016 12:32 UTC
Hi Steve,

There was a regression introduced in V17.1.10 that caused startup code to execute too early under certain conditions, before the lisp engine document context was properly initialized. This has been fixed now for the next update.

Steve Johnson
06-12-2016 02:43 UTC
I must say, the responses I’ve been getting to my support requests have been absolutely bloody brilliant. Cheers!

 
Now, can you imagine the same scenario with Autodesk? I’m sure many of you have lived through it. First thing would be an automated response. A day or two later would be a confused support person coming up with totally unrelated links to Knowledgebase articles. A series of increasingly frustrating back-and-forth emails might go on for days or weeks until the Autodesk person finally plays their trump card, blaming the third-party routine (incorrectly) and/or stating that they don’t support users’ customization.

Such a problem would stay in AutoCAD indefinitely. Repeated reports, year after year, using subscription support and the forums and formal reporting mechanism in the Autodesk Beta program, would make no difference. Eventually I would give up and the problem would never get fixed. Again, this is typical, and has been repeated many times. This applies to bugs, incompatibilities, feature design, performance issues, user interface difficulties, documentation system idiocy, you name it. It’s massively frustrating and I know many very smart people who have given up even trying. The only exception is documentation content; that gets fixed as soon as possible, within the limitations imposed by Autodesk’s arcane systems.

The difference in attitude between Autodesk and Bricsys is glaring, stark, obvious. Autodesk pays lip service to providing customer service and software quality. Bricsys just gets on and does it.

So what’s actually new in BricsCAD V17?

4 Replies

A big problem I have in communicating the improvements to BricsCAD in V17 is that there are such a huge number of them. This isn’t an AutoCAD 201x-style touch-up masquerading as serious progress, this is a real  upgrade. You know, an AutoCAD V12-style upgrade that veteran AutoCAD users will remember from the good old days before Autodesk got bored and distracted. Dozens upon dozens of new features, improvements to existing features, performance improvements and bug fixes. Lots of stuff that’s genuinely useful.

I could write three posts a week on the changes and not be finished by this time next year. So I’m going to be lazy. I’ll pick out a few features for future posts but for the big picture I’ll point you to the official list. This isn’t a marketing document, it’s a technical list of terse descriptions of changes (to the Windows version only – remember BricsCAD supports Mac and Linux too), and it’s large. To give you some idea of the scale of changes, there are 3,200 words describing new V17 features, for example:

DMDISTANCE3D Specific measuring modes for cylinders, circles, and spheres have been introduced. Distance can be specified between boundaries (nearest points), central points or axes of the corresponding geometries.

 
There are 1,600 words describing improvements, such as:

IMAGEATTACH Multiple selection of images from a single folder is supported now so multiple images can be attached in one go. This is especially useful for images with geo-information attached.

 
There are 1,450 words describing fixes, like:

MATCHPROP When the source entity was non-annotative and the target annotative, the target undesiredly remained annotative.

 
There are 1,100 words describing API changes and fixes, e.g.:

BRX/LISP/SDS wcmatch() now supports the (undocumented) space character as a pattern key to match any contiguous sequence of whitespace characters (space, tab)

 
That last one is a fix for a bug that I reported in V16. Within ten days of submitting my report, I was informed directly by the developer that the fix had been done and would be available in V17. Here’s another one of mine:

BRX/LISP Improved sds_getFiled() / (getfiled) behavior during a Save operation when default filename argument is empty.

 
Elapsed time between my report and acknowledgement by the developer that a fix would be forthcoming? Just under 12 hours. Less than 3.5 hours after that, I was informed that the fix had been implemented. Hands up all those people who have had similar experiences with Autodesk?

Autodesk has some great documentation people

5 Replies

The most heavily commented post on this blog is AutoCAD 2013 – An Autodesk Help writer responds, featuring Dieter Schlaepfer‘s response to posts and comments here about AutoCAD 2013’s Help. I don’t always agree with Dieter but I respect him enormously, and not just because he was brave enough to stick his head above the parapet in a hostile environment. Dieter is a principal technical writer at Autodesk with many years’ experience and is therefore responsible for large amounts of documentation content. You’ve almost certainly read his work.

I’ve been critical of AutoCAD’s Help system since it was broken in 2011, and I make no apologies for that. The Help system sucked then, it sucked even worse in 2013, and it continues to suck badly in 2017. None of that’s Dieter’s fault. It’s the Help engine that’s at fault, or to be more accurate the Help engines, because the online and offline engines still both suck in various ways. Clearly there’s someone important at Autodesk satisfied with the ongoing Help engine awfulness, but that’s not Dieter. He’s responsible for content, not the engine. Content isn’t the problem. The content is actually very good, and gradually improving as Dieter finds ways to do so. It’s just that the system for accessing that content is so terrible that not many people get to read much of it these days, which is a crying shame.

I digress. Dieter’s awesome.

Also awesome is Lee Ambrosius, who does a great job with developer documentation. That job’s less visible, but still very important and performed to an excellent standard. Lee is very technically knowledgeable and understands users, developers and their documentation requirements. Within the confines of the systems he’s forced to work with, Lee has done the very best job it would be possible for anyone to do.

Everybody knows Lynn Allen, of course. Not just an entertaining and engaging presenter at AU and a thousand smaller gatherings, she has been producing beautifully prepared tips-and-tricks and what’s-new articles, posts and documents for so long she must surely have been a toddler when she started. The value of Lynn to Autodesk and its customers is hard to calculate, but is clearly immense.

Last but not least, Heidi Hewett has done an exemplary job for many years in producing preview guides, posts and other documents. You don’t get to see some of them because they are confined to pre-release testers, but I assure you that they are done to the same high standard as the ones that go public.

The work of our illustrious foursome and other talented writers can be found on the AutoCAD Blog and I’m sure my readers will find something of use there.

BricsCAD V17 – the best AutoCAD upgrade in years?

10 Replies

I’ve been evaluating BricsCAD for a few years now, and have been looking at it pretty seriously as a DWG-based LISP-compatible AutoCAD alternative for a year or so. A couple of weeks ago, I flew to Munich for the Bricsys International Conference (at Bricsys’ expense – see the Legal page for disclosure) where I learned quite a few things I had failed to notice during my own evaluation of V17. As you may have noticed, I can be pretty hard-bitten and cynical about what CAD companies have to say about their products, but I came back impressed.

The conference and the product itself are not free of flaws, but I have to say the progress Bricsys has shown in developing the BricsCAD product is really quite astonishing. The rate at which serious, worthwhile-to-customers improvements have been made to BricsCAD over the last few releases is huge. Some of it’s just catching up with existing AutoCAD features, but most of it is going beyond what Autodesk has done. Overall, Bricsys lately has outstripped Autodesk’s efforts in improving its DWG-based flagship CAD product to such a degree that it’s frankly embarrassing for the much larger corporation.

I grabbed Bricsys CEO Erik De Keyser for a brief chat at the end of the conference. I told him that while there were still important areas that need addressing, nevertheless if Autodesk had shipped a new release with a quarter of the improvements that Bricsys managed with V17, it would still have been the best AutoCAD upgrade in fifteen years. Yes, the gap in progress from Autodesk to Bricsys really is that big.

The difference appears to be one of attitude. The Bricsys development team (many were there in Munich to speak to) is focused, motivated and enabled. For Bricsys, BricsCAD really is the flagship product. That’s where all the effort goes; everything goes into the DWG-based product. High-performance 2D drafting, user interface innovation, parametric 3D models, IFC-certified BIM, sheet metal, everything. You would think this would lead to massive bloat, but somehow it doesn’t; the product remains small and fast.

For Autodesk, the emphasis has been elsewhere for some years now. The rate per release of worthwhile AutoCAD improvements, never stellar since the 12-month release cycle was adopted, has been trending downwards since AutoCAD 2010 and has slowed to a trickle. Autodesk is happy to accept the income from AutoCAD customers and use it to develop a hundred trendier products, neglecting the foundation on which the company was built. That’s relying on inertia, and there’s a big question mark over how sustainable that is.

Here’s a 5-minute YouTube marketing video outlining some of the changes. If you have a bit longer, here’s a 37-minute YouTube video of the new features from head of development Hans de Backer. The presentation lacks sparkle (no insult to Hans, but he’s no Lynn Allen) but the substance is there. Note that Hans was demonstrating live to the full conference using a pre-release product, including opening a huge drawing, which surely deserves marks for bravery! As a bonus, you can just about see Owen Wengerd and myself in the bottom left corner.

I’ll be going into more detail on BricsCAD V17 pros and cons later (yes, there are cons), but for now here’s the press release and here’s where you can download the product for evaluation. It’s a straightforward download of a 234 MB MSI file and the install takes just over a minute. That in itself is a breath of fresh air for people who are used to hanging around, waiting for AutoCAD downloads and installs to finish.

The best thing about AutoCAD 2017.1 is…

Leave a reply

…the fact that one of the Express Tools finally got an update. Not just a minor maintenance tickle or mere absorption into the core code, either. A real update, resulting in not only bug fixes but genuinely useful improvements in functionality.

A little background on Express Tools might help put this into context. The history goes back to 1992 and AutoCAD Release 12. In addition to an impressively full set of paper manuals, people with Release 12 (great value at US$500 to upgrade from any earlier release) obtained a Bonus CD containing 2605 files of free add-on goodness. Fonts, LISP, DOS and Unix utilities, sample drawings, demos, all sorts of stuff. Remember that just popping on the web to grab that sort of thing wasn’t really an option at the time, so this CD was quite a big deal.

autocadrelease12bonuscdcase

Release 13 didn’t have an equivalent CD (although it had many other things – most of them bugs), but with Release 14 in 1997 there was a concerted effort to add extra value. A program was put in place to produce a set of bonus stuff, partially developed by external parties. Unlike the Release 12 material, the Release 14 Bonus Tools were (kind of) incorporated into the main product, although they remained unsupported:

Although we put a great deal of effort into making sure the Bonus Tools are free of problems, they are not officially supported by Autodesk. We do not guarantee that the results are 100% error free.
 
To use the bonus tools, choose the Full installation option or select Bonus and Batch Plotting during a custom installation. The installation program places the bonus files in the BONUS\CADTOOLS directory and puts that directory in the Support File Search Path. The installation program also appends your ACADR14.LSP and ACAD.MNL files to ensure the proper loading of the bonus support file AC_BONUS.LSP and menu file AC_BONUS.MNU.

A lot of the things we now take for granted in AutoCAD were born as a result of this initiative. With AutoCAD 2000, Bonus Tools were renamed as Express Tools and some R14 Bonus Tools were removed while others were added to the core product. Several more features were added to an already handy collection, including TXT2MTXT:

autocad2000txt2mtxthelp

The history of Express Tools has been less illustrious since that high point. Autodesk made an ill-advised attempt to make money from them by removing them from AutoCAD 2000i and 2002 and first of all making them available only to VIP/Subscription (now called maintenance) customers as a carrot, then offering them for sale as AutoCAD Express Tools, Vol 1-9. That little business venture was always doomed to fail, and you can still find many sets of instructions allowing people with AutoCAD 2000 to carry across their Express Tools to 2000i and 2002.

Since then, other than some commands being absorbed into the core, it has been “maintenance mode” for Express Tools. This means the code just gets recompiled when necessary and very little actual maintenance goes on. As a result, some 20th Century bugs live on to this day.

Enough history! So what is this best thing? As a byproduct of improvements to PDFImport, the TXT2MTXT command was redone. Not much about this gets mentioned in the readme, but a whole bunch of very good things happened to this seemingly simple command (main source AutoCAD 2017.1 Preview Guide):

  • You can select Mtext objects in addition to Text objects.
  • A Settings option on the Command line displays the Text to MText Settings dialog. In the past you had to press Enter at the start of the command to see the dialog box.
  • Character codes translate correctly between Text and Mtext (e.g. text underlining appeared as %%U when converted to Mtext).
  • The “Select objects” prompt adheres to standard error checking and messaging. For example, objects on locked layers are filtered from the selection set.
  • Justification (Top left, Top center, Top right) is inferred for the Mtext object being created based on the positioning of the text objects in the drawing instead of always using Top left justification. When no justification can be logically inferred, it defaults to top-left.
  • Numbered and lettered list formatting is inferred when the word-wrap text box is checked. If a line starts with one or two characters followed by a period and up to 10 spaces, list formatting will be applied automatically.
  • The top-down sorting order is relative to the current UCS and sorting is left-to-right when text objects are collinear. When multiple text objects are collinear, they are treated as if on the same line with a space between them.
  • A new Settings option enables you to force uniform line spacing or maintain existing line spacing.
  • Various bugs are fixed that caused unexpected results when in a non-WCS UCS.
  • An option was added to the Settings dialog box to not combine selection into a single mtext objects (converts text object to mtext without combining).

That last item alone could be a huge time-saver. If you need to convert 100 text items to mtext (e.g. for background masking reasons), you can now use the command once rather than 100 times. Sure, there are LISP routines to do this (I’ve written some myself), but incorporating it into the core product makes things easier for large numbers of people.

It would not be a bad idea for Autodesk to go through all of the Express Tools looking for similar bug fixes and improvement opportunities. Instead of occasional ad-hoc drip-by-drip adoption of an Express Tool or two into the core, I propose that a special project be undertaken to go through the whole lot, fixing and improving them all. Once done, add them all to the supported functionality of the product, along with any related functionality that makes itself apparent during the overhaul.

Such a project strikes me as something relatively easy to do that would go down very well among customers. Or how about some totally new stuff? Express Tools 2018 – The Next Generation?

How to download Autodesk software without the Akamai download manager

4 Replies

Note: this post is now out of date. AVA no longer provides the facility mentioned here. Instead, it tries (and fails) to be clever.

For reasons beyond my understanding, Autodesk chooses to make life difficult for customers and prospective customers who want to download its products by imposing the use of a download manager (DLM) by Akamai. You really don’t want to let such a thing loose on your system even if it works, for reasons that have been explained in previous posts.

Until a couple of years ago, Autodesk allowed prospective customers to get at a direct download link after jumping through a few hoops and ignoring a bunch of bullshit warnings, but in recent times even that small measure of semi-decency has been removed. It became impossible for anyone who couldn’t or wouldn’t use the Akamai DLM to try out Autodesk’s products! Here’s what you get these days; there is no direct browser download option to be found, just a downloader stub you’re expected to install and give open slather on your system. Don’t.

autodeskdemodownload-2016

Yes, I know this is marketing lunacy, and several years ago I made Autodesk very aware of this via direct email contact. Still, Autodesk remains determined to hamper itself in this way and there seemed to be no prospect of a solution. The old loophole of using an unsupported browser (e.g. Opera) was closed off a while ago.

But wait! There’s an answer! While researching something unrelated, I came across a reference to the Autodesk Virtual Agent and had a look at it. Lo and behold, that contains a bunch of straightforward DLM-free links to the Autodesk product range!

autodeskvirtualagent

Click on Download Links, burrow down to find your product and direct links to the installers are right there! Use your plain browser, a DLM built into your browser, or a DLM of your choice. Easy! Straightforward! Amazing! Unfortunately, this facility only appears to be available in English.

To sum up, if you want to download an English-language Autodesk product in a straightforward manner:

Here’s the link! (link removed as it is now broken)

Congratulations to Ed Martin, who won the selfie contest with this entry:

1. This is Don Strimbu – a tricky angle on the picture, but his smile gives it away
2. He’s famous for the drawing of a nozzle – a fire hose nozzle to be precise – that he drew in 1984
3. Don used block scaling to simulate a 3D effect on the text, knurling, and fins
4. Autodesk used the drawing in its promotional material starting with an ad in the September 1984 issue of Scientific American
5. Don is now promoting products from Bricsys, notably their BricsCAD product
6. Wow, I really don’t know how long it took him, and it would be cheating to ask him … so I’ll guess. 18 hours?

Some clarifications:

1. Indeed it is Don. It was a privilege to meet him at the recent Bricsys International Conference in Munich, among other notables.

2. Correct, NOZZLE.DWG (we were all upper case 8.3 filenames at the time) which is quite possibly the most famous AutoCAD drawing of all time. It was the first complicated drawing ever done with AutoCAD, and was done in 1983 (not 1984), according to John Walker. See The Autodesk File for more information.

nozzle

3. Yes, it was block scaling. In addition to the 3D effect, the thing Don came up with that amazed John Walker was using negative scale factors to achieve the equivalent of the MIRROR command. That command didn’t exist at the time, along with object snap and a bunch of other things it would be difficult to imagine life without these days.

4. Yes, it was also on Autodesk’s Task Force Tips’ letterhead for a while…

5. Yes, Don and former Autodesk Senior Vice President Dr. Malcolm Davies (also at Munich) are important figures at Techevate, enthusiastic promoters of BricsCAD in the USA.

6. 18 hours is a bit off. How about 400 40?

I remember using NOZZLE.DWG as a benchmark for comparing AutoCAD hardware back in the 80s. Open the drawing, enter REGEN and see how long it takes to get a command prompt back again. As every single zoom or pan required a regeneration back then, regen time was very important. I remember an HP Vectra taking 17 seconds and an NEC APC III taking 19. An IBM PC without math co-processor took much longer; 2 minutes 39 rings a bell, but I’m not certain. These days, it’s so fast it’s hardly measurable.

Anyway, I look forward to seeing what Ed has to say in this blog’s first ever guest posting. Could be anything!

Props to Autodesk for supporting education

5 Replies

I have to raise a glass to Autodesk for supporting students and educators by making its software available free. Further props are due for removing the virus-like educational watermark.

A further program that Autodesk supports is the FIRST robotics competition series, helping to develop young people into technology leaders; a member of my family has benefited directly from that.

Credit where credit is due, Autodesk deserves praise for supporting education. Of course, Autodesk will ultimately benefit from this support, but there’s nothing wrong with that. Doing good and being smart are not mutually exclusive.

Battle of the Bullshit part 4 – Bentley tells the truth

3 Replies

Behold, the latest episode in the Autodesk versus Bentley PR battle over perpetual licenses versus rental!

Bentley has issued a response to Autodesk’s response to Bentley’s response to Autodesk’s move to all-rental software. This is entitled Bentley Responds to Autodesk – You Have a Choice. I have already dissected Bentley’s and Autodesk’s previous responses and found neither of them entirely truthful.

So, how does the latest effort from Bentley shape up? Very well. It’s pretty much spot-on for accuracy. There’s nothing that could be described as disingenuous, misleading, or even exaggerated. I encourage you to read it and make up your own mind.

Bentley PR also invited me in on a press conference call, having first invited my questions. Although I was unable to take part in that call, I have listened to a recording of the event and that was similarly free of issues. The Bentley executives were understandably presenting Autodesk’s licensing strategy in a negative way and their own in a positive way, but didn’t have to resort to anything underhand in order to do so. The facts were enough.

Here’s something I wrote in an earlier post:

Raise your game, people; we’re not all stupid out here. If you can’t support your argument with the truth, then your argument isn’t a good one and you need to rethink it.

I’m happy to report that Bentley has  raised its game and in my view it is winning this PR battle because it can  support its argument with the truth. It will be interesting to see if Autodesk is capable of the same.

AutoCAD 2017 Feature – Share Design View

2 Replies

An interesting new feature of AutoCAD 2017 is Share Design View, which is invoked using the leftmost button on the A360 Ribbon tab or the ONLINEDESIGNSHARE command. The idea behind this command is to create a web-published snapshot of your drawing that can be accessed by anyone with a browser (they’ll need a fairly recent one).

This command works as advertised and provides another option to allow limited access to your design information without providing access to your DWG files. It creates a web page containing a view of your drawing and lets you have the URL (link) so you can access it. You can then share this URL with anyone you want to share the design with. They just follow the URL and can view the design using the Autodesk A360 Viewer (no download required).

Heidi Hewett wrote a fuller description of how it works on the AutoCAD blog that would be pointless to reproduce here.

One caveat: although Autodesk describes the design’s location as secure and anonymous, it’s important to understand that it’s an open location. Anybody with that URL has access to that page. Although the URL is long, complex and probably unguessable, if you email somebody that URL and they start an email forward/reply chain that ends up with other people, all of those people can also access that page and you might never know about it. Also, the index that Autodesk must maintain for all of these pages would be a prime target for hackers looking to steal design content, at which point “secure and anonymous” will be meaningless.

So maybe don’t use this method to share your nuclear plant designs. Also, rescind any sensitive designs as soon as access is no longer needed, in order to limit the exposure time (see About Conferring with Clients and Colleagues Online). The URL stays active for 30 days unless you rescind it earlier.

Autodesk is to be commended for providing this feature and documenting it well and honestly. There is little evidence of the misleading hype about security that tainted Autodesk’s DWF marketing back in the day. Here’s a Cloud-based feature that adds value to AutoCAD with little or no downside. Just be aware of its semi-open nature and use it appropriately.

Note: this feature requires A360 to be selected during installation or deployment creation (which it is by default). If A360 is not installed, the Share Design View button will be greyed out. The command will still exist and will attempt to connect to A360 but will then fail with a Service Unavailable message.

Shout out to Robert McNeel & Associates

4 Replies

Let’s start the rebirth of this blog on a positive note. I’d like to express my gratitude to Robert McNeel & Associates for what must surely be the most outstanding example of long-term customer service in the CAD industry.

These days, McNeel is best known for the 3D modelling software Rhino. I have heard good things about this product, but have never used it. However, I am a long-term user of another McNeel product, DOSLib. This is an extensive set of functions that adds greatly to the functionality of AutoLISP. It all works very well and has saved me many hours of work that I would have spent reproducing that functionality. Of course, many LISP programmers could write functions to calculate a cube root, or read a text file, or display a date in whatever format you like, or copy files, or generate a GUID, or toggle the Caps Lock status, or display an HTML file, or return a list of OLE objects in the drawing, or display a multi-select file dialog, or return a list of Windows printers, or a hundred other handy things. The point is, they don’t have to because all that has been done for them and handed over for nothing.

The documentation is straightforward and accurate, and is provided in the form of a good old-fashioned local CHM file. This Help system may be unfashionable, but it remains infinitely superior to the still-awful system that paying AutoCAD customers have had to put up with for the last few years.

For those investigating alternatives to AutoCAD for whatever reason, the availability of DOSLib for Bricscad may help make that particular alternative a more attractive proposition.

Despite McNeel and Autodesk breaking ties many years ago, McNeel’s Dale Fugier has continued to provide, maintain and improve DOSLib. What’s more, DOSLib has remained totally free of charge and ad-free throughout its history, which dates back to 1992! Sometimes, there really is such a thing as a free lunch.

So here’s a big raised glass to Dale and Robert McNeel. Thank you for the many years of outstanding customer service in exchange for nothing but good feelings. Long may you prosper!

Disclaimer: I have no pecuniary relationship with McNeel; no money has ever changed hands in either direction. This post is totally unsolicited; I hope it comes as a pleasant surprise to McNeel.

AutoCAD 2013 Help shock – it no longer sucks

18 Replies

Some months ago, I gave Autodesk several damn good (and thoroughly well-deserved) thrashings over its hopelessly inadequate AutoCAD 2013 Help system. When Autodesk’s Dieter Schlaepfer responded and asked for feedback, he sure got it. There are 142 comments on that one post to date, most of them leaving nobody under any illusions about how short of the mark the new system was.

There is now an updated version of the AutoCAD 2013 Help system. It has been an interminably long time coming, a fact made far worse by Autodesk’s stubborn refusal to provide a CHM stopgap (which could have easily been done on the ship date with minimal resources if the will had been there), but at least an update is here now. Is it any good, though?

I’ve seen fit to give the online version of the updated system a few minutes of my time and I have to say that it’s now way, way better than it was before. In a remarkable turnaround from current standard Autodesk practice, it would appear that customer feedback has not just been listened to, but actually acted on. Honest! Search results make sense. Performance is generally way better than I expected from an online system. There are links to useful things like lists of commands. Things like forward/back mouse buttons work as expected. Various things I expected to suck, simply didn’t. Huh? What’s going on here?

It’s not all brilliant. There are occasional unexpected pauses, but not to excess. A Douglas Adams fan (Dieter?) is clearly responsible for The Hitchhiker’s Guide to AutoCAD. It’s fun, but I’m not convinced it’s particularly useful. The layout is confusing and the content has me somewhat baffled. Is DRAWORDER really one of the first things a beginner needs to know about AutoCAD? Or were there 41 things in someone’s list and that one was thrown in there to make the number up to 42?

That aside, this thing is looking good. Unlike the last effort, I don’t think it deserves Total Existence Failure. But does it just look good in comparison with what went before? Have I been so shocked by apparent adequacy that I have missed some glaring problem? You tell me. Please, give it a fair go and report back on what you think.

If you want to try the offline version, here it is. It’s not immediately obvious, but you’ll need to uninstall the old one first before the new one will install, don’t bother. It’s still the horrible old thing. See I was wrong about AutoCAD 2013 Help, it still sucks for what I think about that.

AutoCAD 2013 – Help improved in one area

2 Replies

There’s one important area in which AutoCAD 2013’s Help shines when compared with its immediate predecessors. If you’re a Visual LISP user, you’ll be pleased to know that if you select a function name in the editor (e.g. (vla-get-ActiveDocument)) and hit Ctrl+F1, this now takes you to the appropriate page in the ActiveX and VBA Reference, as it should. In AutoCAD 2011 you just got a cryptic message or a 404 error, depending on the context. In AutoCAD 2012, you were just taken to the front page of Help and expected to find it yourself. Props to Autodesk for fixing this problem.

As a bonus, the reference you’re taken to is still a CHM so it works nicely. The Search tab doesn’t work in Windows 7, but that applies to all CHM Help and it’s Microsoft’s fault, not Autodesk’s. The structured contents and index are fully functional, which makes the whole thing usable even without the search facility.

Australian Fencing Championship 2011

3 Replies

I have been away in Sydney for a while, attending the Australian Fencing Championships. I fenced in five events with uneven success (I came 52nd out of 70 in the Open Foil, for example), but a few things made me happy. First, I was able to fence for Western Australia in the Team Foil event as captain of the WA ‘B’ team, which put up a decent performance in going down to a strong ACT ‘A’ team. Next, I came 6th in the Veteran Foil; down from last year’s 2nd, but quite respectable given the strength of the field.

The event I was really concentrating on, the one in which I most wanted to do well, was the Veteran Sabre. I fenced pretty well through the pools and direct elimination bouts and got through to the final. There, I faced an opponent who had beaten everybody else that day, and I had trouble maintaining the same level of performance. Who would come through to be crowned national champion for 2011? Watch the video (YouTube, 3:02 long) of the Veteran Men’s Sabre Final to find out:

I’m on the left. If a red light goes on, I’ve hit him. If he hits me, it’s a green light. If both lights go on, we’ve both hit each other within 120 milliseconds and the referee awards the hit based on right-of-way rules. Veteran direct elimination bouts are fought until one fencer scores ten hits. Link to results.

The best feature ever added to AutoCAD is…

4 Replies

…LISP. I have now closed the What are the best features ever added to AutoCAD? poll, and the winner is AutoLISP/Visual LISP, by a long, long way. I don’t always agree with the majority view expressed in the polls here, but in this case I wholeheartedly agree. Adding LISP was the biggest and best thing that ever happened to AutoCAD. Autodesk owes an enormous debt of gratitude to John Walker for incorporating the work of David Betz, who was of course standing on the shoulders of John McCarthy. It’s a crying shame that Autodesk has been so terribly neglectful of Visual LISP for over a decade.

Here are your top ten “best ever” AutoCAD features:

  • AutoLISP / Visual LISP (32%)
  • Paper / Model Space / Layouts (21%)
  • Xrefs (20%)
  • Copy / Paste between drawings (19%)
  • Dynamic Blocks (16%)
  • Object Snaps (15%)
  • Layer Visibility per Viewport (12%)
  • Undo (12%)
  • Grips (12%)
  • AutoSnap (9%)

Something interesting I noticed is the age of these features:

  • AutoLISP / Visual LISP – 1985 (significantly improved 1999)
  • Paper / Model Space / Layouts – 1990 (significantly improved 1999)
  • Xrefs – 1990
  • Copy / Paste between drawings – 1991
  • Dynamic Blocks – 2005
  • Object Snaps – 1984
  • Layer Visibility per Viewport – 1990 (improved 2008)
  • Undo – 1986
  • Grips – 1992
  • AutoSnap – 1992

The youngest feature here is 6 years old, the oldest is 27. The average top-ten AutoCAD feature is over 20 years old. What does that tell you?

(so (long (and (thanks (for (all (the (parentheses))))))))

1 Reply

A few days ago, John McCarthy died at the age of 84. He didn’t make a fortune selling gadgets, he just profoundly affected the world of computing. He will be remembered mainly as the father of LISP, without which it is quite possible that AutoCAD and Autodesk would not have survived beyond the 80s. However, his original thinking went well beyond the development of a language. For example, 50 years ago he came up with an idea that is very relevant to what we are actively discussing today:

In 1961, he was the first to publicly suggest (in a speech given to celebrate MIT’s centennial) that computer time-sharing technology might lead to a future in which computing power and even specific applications could be sold through the utility business model (like water or electricity). This idea of a computer or information utility was very popular in the late 1960s, but faded by the mid-1990s. However, since 2000, the idea has resurfaced in new forms (see application service provider, grid computing, and cloud computing.)

(Credit: Wikipedia)

Back to LISP, I still use John’s antique language today. It’s still the best language choice for the vast majority of the development I do. Thanks, John.

Best and worst AutoCAD features ever – polls

3 Replies

Using your suggestions and a few of my own, I have added two polls for you to select what are, in your opinion, the best and worst features ever added to AutoCAD. To help us find The Answer, there are 42 items in each poll, from which you can choose up to three.

A few items (e.g. Action Recorder) made it into both lists, while several items in the ‘worst’ list (e.g. 2012 Array, Ribbon, Annotative Scaling) were suggested multiple times. It will be interesting to see how the poll results pan out.

What are the best and worst features ever added to AutoCAD?

Audience participation time, I think. A comment on one of AutoCAD 2012’s new features recently set me thinking about what were the worst features ever introduced to AutoCAD. That in turn got me thinking about what were the best.

I’ll keep my opinions to myself for a while, as I’d like your input and don’t want to influence it. Please add a comment with your list of what you consider the best three features ever added to AutoCAD and the worst three. If you can’t think of three of each, you can submit less, but please don’t submit more. By all means discuss at length the things you love or loathe, but make it clear what you’re submitting by using a clear format like this (meaningless examples only):

Best:
1. Content Explorer
2. Online Help
3. Nudge

Worst:
1. AutoLISP
2. Transparent zoom and pan
3. Paper/model space

What do the words “feature”, “best” and “worst” mean? I’ll leave that for you to decide for yourself. You might consider “worst” to be something that’s a bad idea, poorly implemented, slow, inefficient, poorly documented, bloated, buggy, half-baked in the short or long term, clueless in some other way, or some or all of the above. It’s up to you.

When I have enough submissions, I’ll collate the most popular (and unpopular) features into a pair of polls for you all to vote on. Have fun!

Edit: I have now added the polls and closed comments on this post.