GDL
About building parametric objects with GDL.

3D object disappeared after migration

Yvonne
Advocate

I created an object using slabs/walls etc. The project was migrated and now the object doesn't appear in 3D. I can see still see it in plan. 

 

The project was started in AC25 and is now in AC26. 

 

There was an archive file that I opened in AC26 and the object is showing fine there. I tried to copy it across but no luck.  I have no idea what's gone wrong...

AC26 | Win11 | 64 bit | 32Gb RAM | Intel i9-9900K @ 3.60GHz
13 REPLIES 13
Lingwisyer
Guru

Does the Session Report say anything?

File => Info => Session Report

AC22-23 AUS 7000Help Those Help You - Add a Signature
Self-taught, bend it till it breaksCreating a Thread
Win11 | i9 10850K | 64GB | RX6600 Win10 | R5 2600 | 16GB | GTX1660

The object is called No.14.  It appears macro is missing? What does that mean and how do I fix it? 

Yvonne_0-1679983990207.png

 

AC26 | Win11 | 64 bit | 32Gb RAM | Intel i9-9900K @ 3.60GHz
Lingwisyer
Guru

Ah. You have made a custom object which CALLS an object from the AC25 library.

 

A quick but temporary solution that might work would be to add the AC25 Migration Library to your file. Not quite sure if this will actaully work as the names of objects in the migration library do not actually match the original...

 

Better, would be to update your custom object itself but changing the call to "Window 26". Updating it to work with AC26 in this way will prevent it from working with previous versions if it is still being used there.

 

CALL "Window 25"

CALL "Window 26"

 

If you need it to work in multiple versions, open the object in your oldest AC, and create a new Text Parameter with the value "Window 26", if that will be your primary AC version and replace the call with your parameter name. Once done, when you open the object in alternate AC versions, you can just edit the parameter to match the current AC version. So if you open it in AC25, you would type "Window 25" into that parameter.

 

CALL "Window 25"

CALL newtextparameter

 

If you are really confident, you could possibly automate this by querying the AC version then constructing a string from that to insert into the CALL.

 

 

Ling.

AC22-23 AUS 7000Help Those Help You - Add a Signature
Self-taught, bend it till it breaksCreating a Thread
Win11 | i9 10850K | 64GB | RX6600 Win10 | R5 2600 | 16GB | GTX1660

Adding the migration library didn't work. 
I changed the call to "Window 26"  but got an error message...

Yvonne_0-1679986302917.png

Yvonne_1-1679986321272.png

 

AC26 | Win11 | 64 bit | 32Gb RAM | Intel i9-9900K @ 3.60GHz
Lingwisyer
Guru

Are the Fills different between your AC25 and AC26 template?

AC22-23 AUS 7000Help Those Help You - Add a Signature
Self-taught, bend it till it breaksCreating a Thread
Win11 | i9 10850K | 64GB | RX6600 Win10 | R5 2600 | 16GB | GTX1660

Nothing has changed. The file was created using our AC25 template then migrated to AC26. Everything else in the file looks fine except this object...

AC26 | Win11 | 64 bit | 32Gb RAM | Intel i9-9900K @ 3.60GHz

What does it say at the line mentioned? You can press "ctrl + L" to line jump.

AC22-23 AUS 7000Help Those Help You - Add a Signature
Self-taught, bend it till it breaksCreating a Thread
Win11 | i9 10850K | 64GB | RX6600 Win10 | R5 2600 | 16GB | GTX1660

Yvonne_0-1679988034448.png

 

AC26 | Win11 | 64 bit | 32Gb RAM | Intel i9-9900K @ 3.60GHz
Lingwisyer
Guru

Ensure that that parameter exists in the parameter list. Does the object generate? If it does, try modifying that parameter in a placed instance.

AC22-23 AUS 7000Help Those Help You - Add a Signature
Self-taught, bend it till it breaksCreating a Thread
Win11 | i9 10850K | 64GB | RX6600 Win10 | R5 2600 | 16GB | GTX1660