Custom AC22 Door in AC28

[Lingwisyer]

Hi all,

I have a custom door that is based on the AC22 Pocket Door from the INT library. When I try to use it in AC28 it fails to generate and I get the following error:

Dictionary type value can be stored only in variables declared as dictionary
 at line 1331 in the 3D script of file gs_general_lt_door_macro_GKA.gsm. (D-09 | 5976EAC8-E37B-4AEA-9F2B-ED19B28AD641)
Library part was not converted properly (D-09 | 5976EAC8-E37B-4AEA-9F2B-ED19B28AD641)

Anyone know of some way to resolve this, other than remaking the door using the AC28 object...?

The GetDWSymbSettings macro also does not appear to exist in AC28 or it's migration libraries...

Ling.

[Barry Kelly]

What do you mean by custom door?

A version 22 object should work just fine.

I don't think they used dictionaries back then?

Or do you mean custom door leaf?

I believe they need to be opened and re-saved in 28 and possibly their subtype changed?

There was a post somewhere about that - I will see if I can find it.

Barry.

[Barry Kelly]

https://community.graphisoft.com/t5/Libraries-objects/Migrating-Custom-Components-for-Compatibility-...

The last section.

Barry.

[Lingwisyer]

I basically took the AC22 Pocket Door and rescripted it's functionality, so the macro's are mostly all the default ones with a few changes here and there.

Yeah, dictionaries were introduced in AC23. I can only assume that one of the core macros has been changed to use dictionaries meaning that the input into them has changed...

[Lingwisyer]

Hm... I would seem like all my doors and windows that were based on GS macros are broken in AC28... Zzz... Nice... Even one where the only thing I did was activate the transom function... They all have the same error...

[Barry Kelly]

---

@Lingwisyer wrote:

I can only assume that one of the core macros has been changed to use dictionaries meaning that the input into them has changed.

---

That must be it.

I still script all of my objects in 22 and they work just fine.

But if you have used default macros, maybe they have changed as you thought.

I know objects have new GUIDs in 28, which is why they don't migrate.

I am not sure if they did the same for macros.

It seems not maybe, as otherwise you would have missing macros.

Barry.

[Lingwisyer]

It would be a lot easier if all the macros were missing as then I could just extract them from AC22 and load them in seperately, but since they are not, it would cause a whole lot of other conflicts, or do nothing at all...

@Peter Baksa Any insight into what has changed?

[Lingwisyer]

Though one thing to note is that my objects did work in AC23. Have not used any versions between that and AC28, so not sure if they broke before the Global Library...