cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 
GDL
About building parametric objects with GDL.
SOLVED!

Issue with Parameter Display in GDL Editor (Archicad 27 INT 6060)

NMK195
Participant

Hello everyone,

I’m currently using Archicad 27 build 6060 INT and have encountered an issue related to the GDL editor.
When I update the code in the Parameters scripts, the values of the variables no longer display correctly. However, after saving, everything still works fine in the floor plan — the issue only appears within the GDL editor.

NMK195_0-1752035578787.pngNMK195_1-1752035593177.png

 

I’ve attached the file below and would appreciate any help or solution to fix this. Thank you very much.

1 ACCEPTED SOLUTION

Accepted Solutions
Solution
Jochen Suehlo
Moderator

Why do you set the Parameters A, B, zzyzx, although you do not use them in the scripts?
If I change the Value A from 0.001 to 0.002, everything works fine for me.
If you use A, B, zzyzx in one of the Scripts you should change your Master -Script like this:
A = 0.001 : B = 0.001 : ZZYZX = 0

parameters A = A, B = B, ZZYZX = ZZYZX
so that the values of the variables will be changed, when the Parameter-Script was not running, as well.
Jochen Suehlo . AC12-28 . MAC OSX 14.4 . WIN11
GDL object creation: b-prisma.de

View solution in original post

2 REPLIES 2
Solution
Jochen Suehlo
Moderator

Why do you set the Parameters A, B, zzyzx, although you do not use them in the scripts?
If I change the Value A from 0.001 to 0.002, everything works fine for me.
If you use A, B, zzyzx in one of the Scripts you should change your Master -Script like this:
A = 0.001 : B = 0.001 : ZZYZX = 0

parameters A = A, B = B, ZZYZX = ZZYZX
so that the values of the variables will be changed, when the Parameter-Script was not running, as well.
Jochen Suehlo . AC12-28 . MAC OSX 14.4 . WIN11
GDL object creation: b-prisma.de

Setting the parameters A, B, and ZZYZX is a standard practice in our company, which has been in use since Archicad 21. We're not sure why this issue has suddenly occurred in Archicad 27.

After applying your suggested modification, everything is now working properly again. Thank you very much for your helpful solution.