Monthly Archives: March 2018

Andrew Anagnost apology for AutoCAD 2019 rollout disaster

Autodesk CEO Andrew Anagnost has sent an email to customers affected by the AutoCAD 2019 rollout disaster that acted as a remote kill-switch for users of earlier releases of subscription software. The email’s subject is We Missed the Mark:

Image credit: R.K. McSwain

Readers of this blog will be aware that Andrew and I have fundamental disagreements on where he has taken the company, but credit where credit is due. An apology was appropriate in this case, and Andrew stepped up and made one.

He has also stated on Twitter that it won’t happen again. I don’t think such a guarantee is realistic, given that the nature of subscription software is to only work when it knows you’ve paid up. At least it demonstrates that the desire is there right at the top to try to prevent such debacles from occurring in future.

Autodesk watchers know that words mean little and actions are everything. I look forward to Andrew sharing news of the actions he’ll be taking to make good on his promise.

Ehlers Danlos Syndrome (EDS) awareness

This post has nothing to do with the usual subjects covered by this blog. It’s more personal than that. My niece Carrie and her two daughters have suffered, and continue to suffer, from a rare, painful and debilitating condition called Ehlers Danlos Syndrome (EDS). That suffering could have been reduced if there had been more knowledge of the condition among the medical profession.

I’m somewhat cynical about “awareness campaigns”, but this is different. This awareness can have a major beneficial impact on real people, if the awareness is among the people who can make a difference: medical professionals.

I’m asking you, kind reader of my blog, to forward this link to anybody you know in the medical profession. One day, they might come across somebody with this condition and have something lodged at the back of their minds; something to make them think, “Maybe it could be EDS? I’ll look that up.”

Here is Carrie’s story. This is a reprint of an article on page 22 of Arthritis Today magazine, Autumn 2018 edition.


EHLERS DANLOS SYNDROME – Diagnosis makes a difference

by Carrie Johnson

Some of us are naturally more flexible than others, or hypermobile as the medical people describe it. For many, being hypermobile is not a big deal and may even offer advantages in certain sports and careers. For others, these stretchy tissues can cause serious ongoing health challenges which are painful, unpredictable and sometimes disabling.
My younger daughter Cate hurts her joints very easily doing things other 6-year-olds take for granted. She’s dislocated her shoulder three times at rest. Her jaw is so loose that she struggles to speak clearly, and has been in speech therapy for years. Chewing a steak is out of the question!

My older daughter Lucy is fourteen and has spent the past year dealing with severe nerve pain triggered by a dislocation which tore her hip. She was sitting at the dinner table when it happened. Lucy was bedridden for more than four traumatic months before learning how to function with persistent and often intense pain. She missed nearly two-thirds of school last year.

I’ve always been bendy myself and had my fair share of painful joints and other problems. However, towards the end of my last pregnancy, I suddenly couldn’t weight bear because my hips were dislocating with every step. I’ve had several surgeries, but the repairs didn’t last. The pain and restrictions persist nearly seven years later, and now many other joints have joined the party.

Despite years of unexplained symptoms and endless medical appointments, it wasn’t until Cate was nearly five that we were all diagnosed with the hypermobile type of Ehlers Danlos Syndrome (EDS).

EDS is the name given to a group of genetic or inherited disorders which affect collagen, a vital building block in the connective tissue or “glue” which holds our bodies together. Although EDS is increasingly recognized as causing musculoskeletal pain, collagen is the most abundant protein in the body, meaning there is almost no limit to the places where issues can arise.

Poor eyesight, dental crowding, soft and fragile skin, excessive bleeding, digestive system issues, and autonomic dysfunction are just some of the problems my daughters and I deal with every day. Cate’s skin splits open easily, so a simple scratch will heal slowly and often leave a scar. Lucy recently had a spontaneous nosebleed so severe that blood streamed from her eyes and she bleed through a bath towel in fifteen minutes. In hot weather, if I stand up quickly I lose my vision, get very dizzy, and sometimes faint. To combat this, I am supposed to drink lots of water but I also have gastroparesis (stomach paralysis) and often can’t drink anything at all.

Many health professionals appear reluctant to formally diagnose EDS, perhaps because it is considered rare and has no cure. Since hypermobility occurs on a spectrum, it can also be difficult to distinguish a flexible but otherwise healthy person from someone with EDS or a related disorder.

For my family though, our EDS diagnosis was the first positive step towards us taking back some control over our lives. Not only do we finally have an answer for all the things that were going wrong, but we are also able to meet others in the community with the same condition, and to seek treatments which have the best chance of improving our quality of life.

We see occupational therapists, pain specialists, and have a phenomenal physiotherapy team to help us build strength using techniques appropriate for our hypermobile joints. Now we know about EDS we avoid certain activities, and my daughters are very fortunate to have a wonderful paediatric rheumatologist to coordinate their care. Because of our diagnosis, we’ve been able to access some sources of assistance to help a little with the significant financial strain on our family.

Although it’s considered rare, some experts believe EDS and related hypermobility disorders may be underdiagnosed. Symptoms can vary dramatically, even within the same family.

Carrie’s story is all too familiar to me as a specialist clinician in this area of Medicine, but I suspect on reflection, colleagues will realize they too have patients with similar histories in whom the diagnosis has not been considered.” said Dr Alan Hakim, Consultant Rheumatologist and Clinical Lead of the Hypermobility Unit at London’s St John and St Elizabeth Hospital.

The value to individuals and families of a diagnosis, and our then ability to adapt and better treat them should not be underestimated. The challenge internationally is to both help non-specialists recognize these conditions, and to develop more multi-disciplinary teams with resources to support people like Carrie and her family.

For more information about hypermobility disorders and Ehlers Danlos Syndrome, visit the websites Hypermobility.org or www.ehlers-danlos.com.

Original article: https://www.arthritiswa.org.au/useruploads/files/arf5527-arthritistodaymagazineautumn2018.web.pdf

AutoCAD 2019 rollout disaster

If you’re an AutoCAD user, you may have been intrigued by the news about the new way Autodesk is bundling up AutoCAD 2019 with various verticals (perpetual license owners need not apply). This is Autodesk’s latest attempt to promote its subscription model and raise prices again. 7% this time, but much more to come. But never mind that, the main point is that you’re getting a whole lot of stuff, and who could say that’s not a good thing?

So it’s most unfortunate for Autodesk that the AutoCAD 2019 rollout has been an unmitigated disaster.

My own experiences in trying to download the product were sub-optimal, but I later learned that I was one of the lucky ones. Subscription users not only had problems with AutoCAD 2019, they found their AutoCAD 2018s were broken too, victims of an Autodesk licensing system meltdown. That’s right, the AutoCAD 2019 launch acted as a remote kill-switch for people’s production software.

Perpetual license users were fine, of course. Only subscription customers suffered. There’s a lesson there that should not go unnoticed.

Back to my own experiences, to begin with I couldn’t download AutoCAD 2019 anywhere, despite it being having been announced everywhere some hours earlier. Autodesk Account wasn’t showing 2019, but it was showing this:

The usual workaround method of downloading the free trial wasn’t any better; that was still on 2018. I even tried installing the execrable Autodesk desktop app (temporarily!), but there was no sign of AutoCAD 2019 there either.

I’ve never had any success using Autodesk’s AVA bot for any real questions, but there was a time when it served as a gateway to Akamai-free downloads, so I tried that. Unfortunately, AVA has been “improved” and that once-excellent feature is gone. I did try asking AVA for the download link to AutoCAD 2019, but that didn’t go well.

First attempt:

Second attempt:

I mentioned my difficulties on Twitter and a few hours later the long-suffering but always-professional @AutodeskHelp people offered this:

Despite appearances, this actually turned out to be helpful because by then the product trial download had been fixed and was offering 2019 rather than 2018. I still didn’t see a direct link and against my better judgement tolerated a very temporary installation of Autodesk’s nasty Akamai download manager. About 5 minutes into the download it said it was going to take about 9 hours so I went away and left it. I returned within the hour to find it was finished, so I have no idea how long it actually took. After immediately uninstalling all traces of Akamai and Autodesk desktop app, I was able to start my evaluation.

So how’s the product? Pretty much the same as 2018, except with a better drawing compare tool. Oh, and the icons are better. The first command I ran in the new release reminded me that some things never change. The ancient rectangular pickbox bug popped in to see me, just like an old friend.

I’ve been warmed by the familiar, comforting experience of this and various other early 90s-era bugs and limitations, where the easiest workaround is to use a competitor’s product to do those bits. More on that in a future post.

An hour or so into using the product saw it crash and burn for the first time:

Don’t take my word for it, though; here are some comments from various users, CAD Managers and long-term Autodesk fans, most of whom had a worse time of it than I did. It’s not just AutoCAD; LT and Navisworks are definitely affected and there may be others. Comments here have been reproduced from various sources under fair use; names have been removed to protect the innocent.

I think it is safe to say that Autodesk are having a very bad day. Account and activation issues, subscription access issues, forum login issues, kudos and comments blocked to some users…

I installed the brand new @Navisworks Manage 2019 last night, and this morning I get the “Your trial has expired” !!!

I can safely say that ‘unimpressed’ is my status right now with the licencing idiocy going on. Not only can I not get the 2019 version, but my 2018 version has stopped working too.

Looks like all subscription (not maintenance or legacy) software is affected this way: logging in and out as well as workarounds posted are not working. Now this is a good reason to abandon Autodesk subscription model.

Good news: Autodesk began rollout of 2019 licenses! Bad news: It might break your 2018 licenses.

Hard to imagine this rollout going any worse.
[Autodesk]”Hold my beer….”

2.5 days without AutoCAD available. I just wish Autodesk would have told us so I could have gone on vacation. Instead, I will have to work thru the weekend to make up lost time.

I love Autodesk and their software, but they have just ditched an entire generation of Autodesk ‘rockstars’ and their subscription portal isn’t working. It really doesn’t look good, does it?

my 2018 is hosed on 3 devices

Unfortunately the situation has lasted for nearly 24 hours and no work done. Can we send the bill to Autodesk?

so I thought I’d try and activate LT
LOL

Although some parts of this are supposedly fixed, it’s not over yet. As I type this, people are still reporting problems and Autodesk is still offering apologies:

Even now, AVA is still completely in the dark about the current release of Autodesk’s traditional flagship product.

It’s great to see users helping each other, though. You may find this Autodesk Forum post by Travis Nave useful as an interim workaround. Also, in a marvellous continuation of McNeel’s free service to the AutoCAD (and BricsCAD) LISP community, DOSLib has been made available for AutoCAD 2019 even before many people were even able to get hold of the software it runs on. That’s what I call service!

All in all, this has not the best start to AutoCAD’s brave new world of oneness. How did it go for you?

How to get your Wacom Graphire 4 tablet working in Windows 10

I’ve been setting up a new PC at home and one of the things I struggled with was getting my Wacom Graphire 4 tablet working. This isn’t a CAD tablet (remember those?); instead, I use its pressure-sensitive stylus for image creation and editing. Press harder and you get more ink. Turn the pen over and you automatically erase instead of drawing. Press the eraser harder and you get more erasing.

I use PaintShop Pro for my image work, by the way, not Photoshop. You can still buy and optionally upgrade PaintShop Pro perpetual licenses, which is how it should be. You’re probably aware that I don’t rent stuff unless there’s no realistic alternative.

According to the Wacom FAQ, I was severely out of luck.

What is the latest driver for the Graphire 3 & 4 (CTE) tablets?
The Graphire 3 & 4 CTE tablets made from 2003-2007 are no longer supported by Wacom and will not work with a current tablet driver. Below are links to the latest drivers available for these tablets.

Windows 8, Windows 7, Vista & XP Download Here
Mac 10.8, 10.7 & 10.6 Download Here

Not one to give up so easily, I tried a variety of drivers for my tablet (model CTE-440). They were either blocked from installation by Windows 10×64, or in the best case scenario failed to provide any functionality other than acting as a basic mouse. The tablet failed to appear as a WinTab device, so I couldn’t configure PaintShop Pro to use its pressure-sensitivity, defeating the object of having the thing in the first place.

So I did what I thought was best and put the tablet out on the verge with the other junk awaiting council collection and investigated a replacement. Not from Wacom, obviously! I don’t want to reward a company for abandoning its products. I was checking out Huion tablets, which are so much cheaper than Wacom’s that it’s probably worth taking a punt and buying one anyway.

But then the stubborn streak in me (have you noticed?) kicked back in and I had one last go. A bit more in-depth Googling led me to this page. This is an old, non-maintained, leftover page from Wacom Europe. Let’s hope it stays there. On that page I found the driver I needed: DRIVER 5.30-3 RC FOR WINDOWS 8, WINDOWS 7, VISTA, AND XP. The direct link to the driver installation executable (cons530-3_int.exe) is:

http://downloadeu.wacom.com/pub/WINDOWS/cons530-3_int.exe

I retrieved my tablet from the junk pile, installed that driver, cleaned off my tablet while my system rebooted, plugged it in and away I went! In PaintShop Pro 2018, the setting is found at File > Preferences > General Program Preferences in the Miscellaneous section.

Wacom’s FAQ gave me a bum steer. Yes, the driver I used isn’t supported in Windows 10 and it isn’t current, but I don’t care. It works just fine and means my perfectly good as-new tablet isn’t landfill. Wacom needs to do better both in terms of supporting its hardware with current drivers and providing more useful information to its customers.

Video – 3Dconnexion fine tuning in BricsCAD and BricsCAD Shape

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

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!

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.

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

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”

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.

  1. Start up BricsCAD V18.2 or later and start BLADE using either the BLADE or VLIDE command.
  2. Open a LISP file in BLADE so you can check the effects of the changes we’re going to make.
  3. Use Preferences > Show preference dialog…
  4. In the Preferences & Settings dialog, pick the Styles tab and the Lexer Styles sub-tab.
  5. I’m perfectly happy with Courier New 10, but if you want the VLIDE look, change 1 – Default text to Fixedsys 11.
  6. 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.
  7. Click next to 5 – String and change the Fore Color to magenta (255,0,255).
  8. Click next to 7 – Operator and change the Fore Color to red (255,0,0).
  9. 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.
  10. 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.
  11. 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).
  12. 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:

  1. Line numbers  – View > Margins, Show line number margin
  2. 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.
  3. Edge marker (that vertical line on the right indicating 80 character width) – View > Edge marker > Type, No background.
  4. Indentation guides (those vertical lines that show you what your code is lining up with) – Tabs and EOL > Indentation, Show indentation guides.
  5. 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.

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

That should do it. Happy BLADEwork!

Autodesk contemplates Bentley-style licensing

Some of you may have received an invitation from Autodesk to provide survey feedback. This hints at a possible move towards time based licensing (e.g. hourly), and asks what kind of tools you will need to handle that. Sometimes these questions lead to nothing, other times they are a precursor to inevitable change (desirable or not). If it’s the latter, I can only surmise that Autodesk is concerned that its customers haven’t been thoroughly peed off by anything new in a while and is investigating novel and interesting ways to annoy them.

Ask a Bentley customer what annoys them most about dealing with the company and odds are you’ll be told that it’s the time-based licensing system introduced to SELECT customers a few years ago. Tales abound of rip-off calculations, huge unexpected end-of-period bills, companies being billed for impossible numbers of hours, and so on. Some customers even went as far as calling the system a scam or a fraud.

Some of the worst excesses of SELECT are apparently now fixed, but this system is still unpopular with many customers. So I guess it’s only natural for Autodesk to examine moving in that direction.