Anuncios

The Autodesk Community Forums has a new look. Read more about what's changed on the Community Announcements board.

AutoCAD 2010 - 2016 Comparison

wispoxy
Advisor

AutoCAD 2010 - 2016 Comparison

wispoxy
Advisor
Advisor

Just look at how much Autodesk has done for us.

 

2010

  • 2D parametrics - Geometric and Dimensional Constraints
  • Super commands - Attach, Adjust, Clip, MeasureGeom, Ulayers, TextEdit
  • MeasureGeom
  • segment editing - hold down Ctrl during scale, rotate, move
  • SECTIONPLANE, SECTIONPLANEJOG, SECTIONPLANETOBLOCK, SECTIONPLANESETTINGS
  • Parameters Manager
  • mtext grips added triangle grips for editing

2011

  • Grid - lines in 2D
  • Ribbon updates, added 3D Basic WS
  • Grip added to polyline
  • Selection cycling enhancement  -  SC toggle at bottom of screen
  • Multifunctional grips
  • SelectSimilar command added, HideObjects, Unhide,
  • AddSelected command added
  • HideObjects command added
  • IsolateObjects, UnisolateObjects
  • 3D object snaps

2012

  • Autocomplete command
  • VpControl viewport controls - navigation, views and visual styles on screen
  • Ribbon sizing - three minimized settings
  • mtext background remembers last used fill color and offset
  • grip with lengthen option
  • grips are multi-functional for more objects - arcs, assoc arrays, dims, elliptical arcs, lines, mleaders, 3d faces edges vertices
  • Associative Arrays, grips editing
  • Blend - connects two objects using a spline
  • Extend works with Splines, Fillet works with Splines
  • Support for multiple paths for PMP, PC3, CTB, STB files
  • Snap can be set to work only while in a command, SnapMode sysvar
  • Drawing Views - 2D drawing views from 3D model and 1st or 3rd angle projection Base View
  • 3D editing - ChamferEdge and FilletEdge added Loop option
  • 3D editing - OffsetEdge
  • MeshCap has options added
  • Point Clouds enhanced

2013

  • drawing views additions, create details and sections
  • Properties - shows realtime previews for colors, lineweights, lintypes, transparency, layers
  • Array - displays contextual tab, uses default values to show instant previews
  • Offset has preview before picking
  • Polylines - reversed plines with varying widths handled with new sysvar PlineReverseWidths

2014

  • command line - spell checking, synonyms, block names, layer names, hatch name, visual styles, dim style
  • autocorrect - after three misspellings the word is added
  • autocorrect - after three misspellings the word is added
  • type at command line to change layer, text style, dim style, visual style
  • type at command line with hatch name to start hatch command
  • type at the command line with a block name and the insert command will start
  • mid string search at command line
  • Drawing Tabs - tabs displayed for each drawing
  • Chamfer command closes polylines
  • Filleting polylines will close polylines
  • Layers - merge selected layers in layer manager (LAYERDLGMODE must equal 1)
  • Xref layer names are not shown in the properties palette
  • Xrefs can be selected in quantities and the path or xref type changed in-mass

2015

  • User interaction - Start, Help Find tool, Dark theme, Ribbon gallery, Improved graphics, Lasso selection, Command preview, Resizable modelspace viewports
  • Design - Point cloud manager, Cropping, and object snaps, 3D Orbit Target
  • Documentation - Autobullets and numbering, Mtext match properties, Mtext superscript and sibscript tools, Caps lock detection
  • Connectivity - Design feed with local drawing storage, Autodesk translation framework
  • Customization - BIM 360 add-in, Autodesk Application Manager, Performance reporting

2016

  • User interaction - Move/copy performance boost
  • Design - Center of polygon object snap, High-fidelity lines and curves, Coordination model, Point cloud dynamics UCS, Point cloud geometry extraction
  • Documentation - Many text and PDF enchancements including but not limited to smart tools, alignment, searching, and properties
  • Customization - Selection effect customization, Sysvar monitor
Responder
6.202 Vistas
10 Respuestas
Respuestas (10)

wai1954
Advocate
Advocate

Ok, I've just parted with a huge amount of money (AUD 6,000 - approx USD 4,200) for a perpetual licence of AutoCAD 2016 and would like to know a couple of things. I currently have AutoCAD 2006.

 

First, can the two programs be installed on the same computer and work OK? I could not get an upgrade, so I still have the perpetual licence for AutoCAD 2006. They will both be needed initially while I get things changed over and try to earn some to pay off the AUD 6,000.

 

Second, I have a huge amount of software (VisualLISPs) and other customising I wrote for 2006. Are there going to be any issues moving them over to AutoCAD 2016?

 

Thanks.

wai1954 (Ian A. White)
0 Me gusta

martti.halminen
Collaborator
Collaborator

@wai1954 wrote:

Ok, I've just parted with a huge amount of money (AUD 6,000 - approx USD 4,200) for a perpetual licence of AutoCAD 2016 and would like to know a couple of things. I currently have AutoCAD 2006.

 

First, can the two programs be installed on the same computer and work OK? I could not get an upgrade, so I still have the perpetual licence for AutoCAD 2006. They will both be needed initially while I get things changed over and try to earn some to pay off the AUD 6,000.

 

Second, I have a huge amount of software (VisualLISPs) and other customising I wrote for 2006. Are there going to be any issues moving them over to AutoCAD 2016?

 

Thanks.


Generally, all AutoCAD versions after 2004 can happily co-exist on the same computer. There are some minor problems, like if you run two at the same time, the printer settings may get confused, and guessing which version starts if you double-click on a .dwg.

- A slightly larger problem is that the installer doesn't handle shared files correctly, so uninstalling one breaks the remaining ones. A repair installation can correct this, though.

 

On the Lisp side the language itself is practically unchanged, but using AutoCAD commands with (command ...), (vl-cmdf ...) etc. may cause problems.

 

A) The commands or their behaviour occasionally change between AutoCAD versions, so in a ten-version jump you'll probably hit several of these.

 

B) There was a change in AutoCAD internals, which caused changes in the (command ...) usage. Read the documentation on COMMAND-S.

 

 

-- 

 

 

0 Me gusta

wai1954
Advocate
Advocate

@Anonymous wrote:

@wai1954 wrote:

Ok, I've just parted with a huge amount of money (AUD 6,000 - approx USD 4,200) for a perpetual licence of AutoCAD 2016 and would like to know a couple of things. I currently have AutoCAD 2006.

 

First, can the two programs be installed on the same computer and work OK? I could not get an upgrade, so I still have the perpetual licence for AutoCAD 2006. They will both be needed initially while I get things changed over and try to earn some to pay off the AUD 6,000.

 

Second, I have a huge amount of software (VisualLISPs) and other customising I wrote for 2006. Are there going to be any issues moving them over to AutoCAD 2016?

 

Thanks.


Generally, all AutoCAD versions after 2004 can happily co-exist on the same computer. There are some minor problems, like if you run two at the same time, the printer settings may get confused, and guessing which version starts if you double-click on a .dwg.

- A slightly larger problem is that the installer doesn't handle shared files correctly, so uninstalling one breaks the remaining ones. A repair installation can correct this, though.

 

On the Lisp side the language itself is practically unchanged, but using AutoCAD commands with (command ...), (vl-cmdf ...) etc. may cause problems.

 

A) The commands or their behaviour occasionally change between AutoCAD versions, so in a ten-version jump you'll probably hit several of these.

 

B) There was a change in AutoCAD internals, which caused changes in the (command ...) usage. Read the documentation on COMMAND-S.

 

Thanks.

 

I don't think I will be running them at the same time, just that getting the lisps and configurations over will probably take sime time, and during that time I will still need to have a fully workable program.

 

It is a big jump, and I would have rather done it in stages over the years, only it was a case of our pricing here that made things difficult. We were always told we paid more because of the exchange rate, but there was no change in our price when the AUD was on parity with the USD or even worth more (and not for a short while either). Once the business of sunset on versions was implemented (and we were not really given enough notice), there was no leverage left to get us to buy again. Then, our dealer network saw 3 attempts over the years, to upgrade (with a concessional upgrade for those who were a number of versions older than the last able to be upgraded) rather than have to buy again went nowhere because dealers could not be bothered as there was only a concessional fee for them.

 

I had to bite the bullet given the licencing changes that happen on January 31 would have meant having to renew a subscription/rent/pay-as-you-go (all those descriptors have been used by dealers of the licencing model being used) had I had to do this later, just to extract information from a drawing of mine. It is not just the visible information that is the issue, but the additional information held in a CAD file.

 

Anyhow, I digress.

 

Thanks again. Looks like some long nights getting things working.

 

-- 

 

 


 

wai1954 (Ian A. White)
0 Me gusta

dgorsman
Consultant
Consultant

Something that Martti missed on the LISP side is the security features in the newer version.  This may restrict where you can load LISP files from.  And although its noted as recommended to use your own ACAD.LSP and ACADDOC.LSP files in lieu of changing the OOTB ACADNNNN.LSP file, that is now mandatory.  Ah, one more thing - there is no JET for x64 systems, so any database coding you are working with (e.g. ADOLisp) may need replacing if you are going from x32 to x64.

 

Another point to watch out for is operating system and hardware support.  You may not be able to get the older version to run and/or activate on a newer system.  Evaluate your plans for the next OS upgrade carefully - 2016 isn't fully/officially supported under Win 10, while the next release should be; 2010 will never be.  Both 2010 (2006?) and 2016 have problems with the newer 4k/UHD resolution monitors (watch out for new laptops, especially), hopefully the next release will do better.

----------------------------------
If you are going to fly by the seat of your pants, expect friction burns.
"I don't know" is the beginning of knowledge, not the end.


0 Me gusta

paullimapa
Mentor
Mentor

In addition to what others have posted, the 2016 graphics interface is completely different than 2006.  Even the menu file structure itself has totally changed.  So if you have any customized on screen menus, all that will have to be re-done to work with 2016.

 

 

Area Object Link | Attribute Modifier | Dwg Setup | Feet-Inch Calculator
Layer Apps | List on Steroids | VP Zoom Scales | Exchange App Store


Paul Li
IT Specialist
@The Office
Apps & Publications | Video Demos
0 Me gusta

Anonymous
No aplicable

WISP

 

You forgot to add to the 2015 list.

They changed the graphics display engine in 2015-2016

 

This is when I started having daily crashes in both 2015-2016 on multiple computers.

 

We have NEVER had 2014 crash !!!!   We go back to using 2014 when we need reliability and on a deadline !!!

 

But now with 2017 comoing out soon, if they don't get this corrected, I will not be able to keep my 2014 loaded(Due to License agrrement keeping 2 versions back)

 

Autodesk................Hope you've gone back to the old graphics display engine in 2017 !!!!!

 

Ron

0 Me gusta

paullimapa
Mentor
Mentor

Actually if you're on subscription, you can keep up to 3 versions back. And if you need even older versions, you can always submit a request to Autodesk through your dealer.

 

 

 

Area Object Link | Attribute Modifier | Dwg Setup | Feet-Inch Calculator
Layer Apps | List on Steroids | VP Zoom Scales | Exchange App Store


Paul Li
IT Specialist
@The Office
Apps & Publications | Video Demos
0 Me gusta

Anonymous
No aplicable

Paul

 

Thanks for that info ......... We will then keep 2014 loaded

 

Just hoping 2017 fixes these crashes.

 

I've sent dozens and dozens of incident reports...........

Some desktop computers have AMD Firepro V3900 Which is a Certified card.

I've tried all the versions of drivers for this card and currently running the one

Autodesk recomends...........Still random crashes

  Ran "With Hardware accelaration"   "Without hardware accelaration" Smooth lines off ....Smoth lines on....

Simple 2D drawings ........1 meg or less no AEC objects.

It will just stop during object moves ........copying.......saving........AutoCad can not continue !!!!

 

Argggggggg !!!!!

Ron

0 Me gusta

paullimapa
Mentor
Mentor

Have you tried turning off hardware acceleration in 2015?

 

 

Area Object Link | Attribute Modifier | Dwg Setup | Feet-Inch Calculator
Layer Apps | List on Steroids | VP Zoom Scales | Exchange App Store


Paul Li
IT Specialist
@The Office
Apps & Publications | Video Demos
0 Me gusta

wai1954
Advocate
Advocate

@dgorsman wrote:

Something that Martti missed on the LISP side is the security features in the newer version.  This may restrict where you can load LISP files from.  And although its noted as recommended to use your own ACAD.LSP and ACADDOC.LSP files in lieu of changing the OOTB ACADNNNN.LSP file, that is now mandatory.  Ah, one more thing - there is no JET for x64 systems, so any database coding you are working with (e.g. ADOLisp) may need replacing if you are going from x32 to x64.

 

Another point to watch out for is operating system and hardware support.  You may not be able to get the older version to run and/or activate on a newer system.  Evaluate your plans for the next OS upgrade carefully - 2016 isn't fully/officially supported under Win 10, while the next release should be; 2010 will never be.  Both 2010 (2006?) and 2016 have problems with the newer 4k/UHD resolution monitors (watch out for new laptops, especially), hopefully the next release will do better.


Thanks.

 

I have numerous utilities I have written over the past 25 years and more. They are AutoLISP/VisualLISP routines. Some do use reactors. Some use file access functions, but no database type routines.

 

On the operating system/computer, I have a HP ProBook 4740 with 8 GB RAM running Windows 7 Pro 64 bit and 750 GB HDD, so it should not be an issue.

wai1954 (Ian A. White)
0 Me gusta