Different AC3D version ?

[Steve Jepson]

What is this error and how to I fix it?

I am working in 14 with a plan saved back from 15.

[David Maudlin]

Steve:

One way to get this message is to save a Shell from 15 as a binary library part, embed the object in the library, then save the .pln file back to 14. Placing the object and viewing it in 3D will bring up this error message. So you should look at your AC 15 file and see what elements were created using new tools/commands that are not part of AC 14. You can also do a progressive search of the AC 14 file by selecting parts of it in 2D and viewing it in 3D to discover the problematic element(s). If you click the "Continue" button, you might get another warning with additional information about the problematic element.

David

[Steve Jepson]

The problem is comming only from the .gsm's I am made in the 15 project.

We should be able to back-save objects we make in 15 shouldn't we ?

I wonder if the problem is that when 15 saves as a 14 file the version number is actually older than the most recent upgrade of 14.

The 14 version I make with 15 is 3276 but the 14 I am using is 4044.

Is this the reason I can not back save the objects I make with 15?

[Karl Ottenstein]

I don't believe we ever had the ability to save objects in the format and coding used by prior versions ... it would be a difficult task, as it is not obvious what a converter would do with stuff that does not exist in the earlier version. Not something I want GS spending resources on... That GS provides for back-saving PLN is more than other manufacturers do.

As Owen notes here:
http://archicad-talk.graphisoft.com/viewtopic.php?p=146948

you can use the XML converter to convert the binary representation from one version to another. But, if all commands do not exist in the prior version, the object won't work.

Karl

[Steve Jepson]

Karl wrote:
...That GS provides for back-saving PLN is more than other manufacturers do....Karl

Yes. I was very suprised to lean that we can back-save at all.

I made some simple parts with 15 in the original file. Back-saving ( after I worked out all the Renovation Filter problems !) worked on all parts in that file which included parts for 12, 13, 14 and some other custom parts that were make in who knows what version, but were not newer than 3276. All of the parts except the ones I made in 15 before the back save came through just fine.

The parts I made were very simple. Just a couple of simple slabs saved as .gsm.

Is it not possible to back-save objects you make in 15?

I will test to see when I have time but I would not be suprised to find out that back-saving does not work as well when you upgrade 14 to 4044.

This may be because ArchicAD 15 saves 14 files as 3276.
It would make sence to me that there should be a problem when you use 4044 to try and open the older 3276 file format that is generated by 15.

I don't have time to test that because to reinstall 3276 is complicated since I have newer version of JAVA and QuickTime which have to be deleted if you want to install the older version of 14.

Perhaps some one out there has 15 and 3276 and can confirm that you can back-save parts you make with 15.

Also can anyone with 15 back-save parts you make in 15 and get them to work with 14 (4044).

[David Maudlin]

Steve:

For library parts, the relevant version numbers are associated to the parts and relate to the ArchiCAD version they were made with. AC 15 parts are version 28, AC 14 are 27, etc. You can see the part's version number the same way you can see an ArchiCAD file's version: use Open Object... and the version number will show in the lower right corner of the Open Library Item dialog box when the part is selected. I don't think the build numbers matter.

I tried saving a simple object made of slabs from AC 15 to 14. When saving the slabs as an object, click the "Options" button in the Save Library Part dialog box and select the Editable GDL Script option, not the Non-editble binary 3D Data option. My guess is that this binary engine does change from version to version, so is not backwards compatible.

David

[Anonymous]

If they are simple objects, and don't use "new" commands you can open the object and copy the scripts. Then create a new object in the earlier version and just paste the script in. You'll have to recreate any parameters which can get REALLY tedious, but if they are just simple objects it is a little less painful that it sounds.