[Вопрос] Visual Scripting: Allplan crashes with Visual Scripting - Infinite loop?


Hello all,

I have noticed in my script that when some nodes connect, the connection is interrupted or takes an exceptionally long time. The script normally works fluently without any problems. The errors shown in pictures 1 and 2 occur, when I connect two specific nodes with each other - regardless of whether I have already started the script or not. I only know this error from other programming languages when an infinite loop is created. Can this be related to this and what do I have to pay attention to in my script so that this error no longer occurs?

Update: This error only occurs in the Allplan version 2021, but not in version 2020! I tested both versions with the same file.

Best regards and a happy & successful new year

Marco

Вложения (2)

img
2021-01-01_Allplan VS crash_1.JPG
Type: image/jpeg
Загружено 29 раз
Size: 39,71 KiB
img
2021-01-01_Allplan VS crash_2.JPG
Type: image/jpeg
Загружено 12 раз
Size: 28,80 KiB
1 - 3 (3)
  • 1

It might be related to the different list handling setting in some nodes in two Allplan versions. But without further information, it is really hard to locate the problem...

Another Allplan user replied in the German forum ( https://campus.allplan.com/de/forum/themen/topic/topics/cad-visual-scripting-1/allplan-2021-0-3-reagiert-bei-vs-nicht-mehr.html ) and suspected that I have a circular reference in my script, where the output of a node is connected to the input of a node further to the left and thus a kind of feedback occurs.

I had several circular references in my script, which I eliminated by rearranging the nodes (see picture 1). This actually fixed the problem for some nodes(although sometimes it takes a bit longer than usual), but not for all: In picture 2 and 3 you see some simple lines. In the first case, I could easily connect them with eachother, but in picture 3 I tried to connect them with the existing line on the right and it didn`t work again. Allplan 2021 stopped working.

But what I am still wondering is why this problem already occurs when arranging the nodes on the VS surface and not after running the script? The Allplan user suspects that the arrangement is checked when the connection is established and is just not recognised due to identical UUID's, which is why such an endless loop triggers this checking routine.

It is also strange why this only occurs in Allplan 2021-0-3 and not in Allplan 2020. Do you know if there`s been a change in the checking routine in version 2021?

Regards,

Marco

Вложения (3)

img
2021-01-06_VS Node-Anordnung.JPG
Type: image/jpeg
Загружено 13 раз
Size: 71,30 KiB
img
2021-01-06_VS Allplan crash.JPG
Type: image/jpeg
Загружено 10 раз
Size: 55,68 KiB
img
2021-01-06_VS Allplan crash 2.JPG
Type: image/jpeg
Загружено 16 раз
Size: 45,77 KiB
1 - 3 (3)
  • 1

https://campus.allplan.com/ uses cookies  -  More information

Accept