Where exactly is this Proxy Hell?

progeCAD IntelliCADApplication Programming Interface, AutoCAD, Autodesk, CAD and CAM, Computer-aided design, DWG, progeCAD

This article was posted originally over 4 years ago and the situation has not gotten any better. In fact, we are starting to hear from a few folks who are experiencing circumstances similar to those examined in the following article.

Rogue Software, or, software that is made to impede your ability to freely move your design drawings from one CAD software companies products to another, is quite simply in my opinion bordering on anti-competitive. Your choice? Take your data and go to another vendor for the Tools you use every day. Quit investing in the kind of software that is so selfish that it essentially ruins DWG drawings, specifically products from Autodesk, and often third party developers who have partake of this scheme to control the design future of all who use the software, I believe they need to be investigated by legal authorities to understand how the monopolization of CAD has been brought about, and is going to get a lot worse as the transition to cloud computing begins appearing. If I were responsible for the future of my architectural firm, or my companies design tools, I would be careful about heading down that path.

Scenario: Working on a large design project for a swimming pool complex and tasked with defining the locker rooms layout. Working with a large AEC firm with requirements t

Fun at a waterpark in a wave poolImage via Wikipedia

o use AutoCAD drawings to complete the project. AEC firm agrees to supply base drawings showing walls, doors, plumbing, etc. for the design. Monday morning, ready to tackle the job and get rolling, expected to have the design finalized by Friday. Project is tight but we think we can get it done with the help of the original design drawings. until we try and open them using AutoCAD. The drawings load fine but there are no walls, doors, or anything we can use to complete our design. What is going on? A call to the AEC firm tells us that they are not using AutoCAD but one of the vertical products Autodesk sells. A check on pricing shows us that the $4000 we already paid for each license of AutoCAD is not going to cover, no even close, the extra we will need to pay to be able to even view these drawings. ARGH. Only choice is to request an extension from the design group and redraw the walls, doors, plumbing, etc. from scratch adding about a week onto the length of our job and eating all our profits.

What this company just discovered is the little known secret Autodesk has been sliding under the carpet as they are out promoting their wiz bang vertical applications and their API’s such as ARX and Virtual LISP. Now, with the release of AutoCAD 2010, the problem is not isolated to those using their vertical applications such as MDT, ADT, or Civil 3D but the problem of proxy hell obects (what Autodesk benignly calls “Custom Objects”) has crept into the main stream. Many entity types you can define now in 2010 are now custom objects and subject to the non-display on product other than those they were created with.
Why do you think Autodesk has taken this route of requiring the original application be installed to be able to view and work with these proxy objects? They had every opportunity to create their API in a way that did not create anything custom but worked with original AutoCAD entities as defined in the DWG drawing file. Evidence of this is available in third party applications developed before ARX was released. See Ketiv’s ARCHT product created before ARX was invented. It had the ability to define a wall as a wall, to allow you to stretch, copy, move, etc every entity it created without the need to worry about vendors and customers downstream being able to open, edit, and save the drawings it created as everything was a standard AutoCAD entity. Why indeed…
Only one reason comes to mind when explaining the need for proxy hell objects… Greed. The ability to lock all your customers into using your products, and your products alone. By not publishing the underlying code to your custom objects you can essentially lock any ve
Greed album coverImage via Wikipedia

ndors out of displaying those objects and require all your customers to come to you, regardless of price, and sell them your solution without any other source of software. Brilliant marketing, and really, not a bad gamble considering NO ONE talks about it. I have seen little or no information at all from our vaunted CAD press that addresses this problem.

So is it just a problem for me? Apparently not, as there are those out there who have come to us for a solution. progeSOFT built converters into progeCAD starting with the 2007 version which will convert the proxy hell objects for MDT and ADT. Thus, those opening one of these mutated DWGs will see the proxies converted to blocks so you can at least see the objects albeit not edit them natively unless you wish to explode the blocks.
So, three cheers for Autodesk on their quest to force their customers on the continuous upgrade to oblivion path. What was once a minor problem for some has become a major problem for almost all with the release of 2010 and guess what, the only way to change the non-competitive behavior is with your feet. Walk away and find a compatible solution from a vendor who still looks out after customers first, the stock holders never.

Free 30-day trial of progeCAD 2010 Professional: Click Here to download…

Enhanced by Zemanta
Full Free 30-day trial of progeCAD Professional, the Proven Replacement for AutoCAD and AutoCAD LT, Download Now!:

Click Here to download your 30-day trial
Or
use a macintosh?, Click Here for a test drive of an “AutoCAD like” software for your Mac!