Missing 3D geometry

[anderson51]

Hello,

I am running 2018 Vanilla

Client is running 2014 Vanilla

When they open the .dwg  3D geometry is missing and the following message appears in the command line for each missing item:

Modeling Operation Error:
     Save file is from a later version of ASM.

All geometry was created with 2018 Vanilla.

Any ideas?

[DarrenP]

2018 is a different file format from 2014

you will need to save down to the 2013 file format

[anderson51]

The file is saved as 2013

[cadffm]

It is the internal Modeling core, that changed and your message looks like.. it isn't compatible in every case.

Search for this paper in english
https://knowledge.autodesk.com/de/support/autocad/learn-explore/caas/CloudHelp/cloudhelp/2018/DEU/Au...

Google for? New features 2018.1 autocad 2018

or ask in the .net / arx Forum here to get more informations(without a solution?)

I would only try one thing: From the newer Version, -exporttoautocad

Perhaps @john.vellek have more informations about sharering between versions and the ASM

A (simple) sample file could be helpful.

[cadffm]

One test please, only for me.
Open your file in 2018 and type-in
(Sslength(ssget "_x"))

Open the SAME file in 2014, do the same.

Is the result in 2014 a lower number?

[john.vellek]

Hi @anderson51,

This is an interesting issue. I have not seen this error but I guess it does not take me by surprise.  I imagine certain types of geometry from the current ASM might not be backwards compatible.  This would especially be true if you were using Viewbase which relies on the Inventor engine.

I created some simple geometry in 2019 product, saved down to 2013 format and had no issue so I suspect this is geometry-type specific. Can you share one of your files so I can explore this issue?

Please select the Accept as Solution button if my post solves your issue or answers your question.

[dmfrazier]

I have some drawings that are exhibiting the OP's "Modeling Operation Error".

I ran your little LISP snippet with one of these files in 2018 and 2014 and the number returned was the same.

[dmfrazier]

Have there been any further developments regarding this issue?