Xref compatibility when saving from 2019LT

Xref compatibility when saving from 2019LT

aj_email_2010
Contributor Contributor
675 Views
11 Replies
Message 1 of 12

Xref compatibility when saving from 2019LT

aj_email_2010
Contributor
Contributor

Strange occurrence with compatibility of drawings.......

 

We have 4 users on a project, 3 of them are using CADv2016 and one is using CADLTv2019 - all have their file save format set to v2013-v2017 within the options.

 

User with CADLTv2019 was asked to do some minor amendments to a few drawings. Only a few paperspace items were changed and then a couple of items such as north arrow symbol size and re-setting the zoom level of model-space was done.

 

The drawings were saved by the CADLTv2019 user ..... but now the users with CADv2016 get xref errors, showing the notice "incompatible version" in the xref manager list.

 

1st question...

Why are the xrefs being amended in CADLTv2019 when the drawing is saved?

2nd question...

Why isn't CADLTv2019 saving in the v2013-v2017 format when asked to do so? 

 

Thanks for any answers given.

0 Likes
676 Views
11 Replies
Replies (11)
Message 2 of 12

S.Faris
Advisor
Advisor

Read this to know more on Backward compatibility of 2018 format : Error: "This drawing contains custom objects that are not supported in previous versions" when savin...

SALMANUL FARIS

0 Likes
Message 3 of 12

aj_email_2010
Contributor
Contributor

Thanks for the reply.

I was previously aware that the file format had recently changed and that v2018 and v2019 would now be creating their own objects that would not be backward compatible with earlier years.

 

However, the problem I seem to have is that when no objects have been created in CADLT2019, just by saving the DWG as v2013-v2017, it seems to have created incompatible entities - namely it seems to have done something to the xref files within the drawing.

 

Should the software be doing this?

 

0 Likes
Message 4 of 12

RobDraw
Mentor
Mentor

@aj_email_2010 wrote:

Should the software be doing this?

 


 

That is what happens. Objects will be saved as the newer format. AutoCAD warns the user of this. "Save As" to previous versions does not convert these objects. The file needs to be exported to a previous format.


Rob

Drafting is a breeze and Revit doesn't always work the way you think it should.
0 Likes
Message 5 of 12

S.Faris
Advisor
Advisor

using command EXPORTTOAUTOCAD or DXF conversion are the best possible solutions.

SALMANUL FARIS

0 Likes
Message 6 of 12

RobDraw
Mentor
Mentor

@S.Faris wrote:

using command EXPORTTOAUTOCAD or DXF conversion are the best possible solutions.


 

Disagree. Best practice says to make sure everyone working on a project uses the same version.


Rob

Drafting is a breeze and Revit doesn't always work the way you think it should.
0 Likes
Message 7 of 12

S.Faris
Advisor
Advisor

In this case they have already messed up the file, So that is not going to do any good I believe. I was just providing a solution for the problem they are in. The one you mentioned is the best practice and not the solution if am not wrong.

 

Sorry I'm not a native English speaker,so kindly pardon my English.

SALMANUL FARIS

0 Likes
Message 8 of 12

aj_email_2010
Contributor
Contributor

Cheers.

Seems I did have a misunderstanding with the "save as" function. 

From the replies given I now understand it to be that even if v2013-v2017 file format is selected, a 2019 version of AutoCAD will still save in a non-compatible format with v2013-v2017. Which begs the question as to why they have this 'back-dated format' in the list of file types under "save as" ?

 

I think the solution to this will be to instruct our I.T. to remove all versions of CADv2018 and v2019 from our software list to avoid the problem happening again.

 

I think this is a huge failing from AutoDesk, what they seem to have created is AutoCAD v1 and AutoCAD v2, whereby one is not compatible with the other. As our projects are on v1, we will have no need for v2.

0 Likes
Message 9 of 12

pendean
Community Legend
Community Legend
"Best practice says to make sure everyone working on a project uses the same version."

0 Likes
Message 10 of 12

RobDraw
Mentor
Mentor

@aj_email_2010 wrote:

From the replies given I now understand it to be that even if v2013-v2017 file format is selected, a 2019 version of AutoCAD will still save in a non-compatible format with v2013-v2017. Which begs the question as to why they have this 'back-dated format' in the list of file types under "save as" ?

 

I think this is a huge failing from AutoDesk, what they seem to have created is AutoCAD v1 and AutoCAD v2, whereby one is not compatible with the other. 


 

A while back, .dwg format changes happened every three years and it was common knowledge that the "save as" to a previous format would not work and files needed to be exported or converted using Drawing TrueView. That common knowledge has been lost in recent years because of the long gap in format changes.


Rob

Drafting is a breeze and Revit doesn't always work the way you think it should.
0 Likes
Message 11 of 12

aj_email_2010
Contributor
Contributor

Thanks for the replies everyone. Much appreciated.

Just a final question from me.... what is the purpose of CAD v2018/v2019 having the "save as" function and including the v2013-v2017 file format as an option when the software is unable to properly 'save as' to that file format?

 

 

 

 

0 Likes
Message 12 of 12

RobDraw
Mentor
Mentor

@aj_email_2010 wrote:

Thanks for the replies everyone. Much appreciated.

Just a final question from me.... what is the purpose of CAD v2018/v2019 having the "save as" function and including the v2013-v2017 file format as an option when the software is unable to properly 'save as' to that file format?


 

Out of the dozens of times I've had this conversation, no one else has ever seen the uselessness of that function.


Rob

Drafting is a breeze and Revit doesn't always work the way you think it should.
0 Likes