LISt and IF not working as expected

1

Hi,

could you please tell me, what is wrong with this IF statement?

if
if.png1177Ă—746 95.5 KB

2

H @adnandj ,

Yes it is very interesting but I think it solves the problem “List Create”.

List
List.gif3770Ă—1630 1.1 MB

3

Wonderful, thanks @Durmus_Cesur. Is that is mistake in Dynamo? It is really big problem.

4

Hi,

There is surely a solution. Did you have a chance to test in older versions? (1.3,0.9 …)
(@Kulkul, I am wondering what is your idea.)

1 Like
5

Hello

The reason of this behavior is :
The IF node replicates on all nodes AS THOUGH SET TO SHORTEST.

Greetings Nico

6

Hello ngochungwru and Adnan @adnandj

Here are some examples off the behavior off the ootb IF node.

If%20statement%20problems%20and%20solutions
If statement problems and solutions.png2908Ă—1462 416 KB

I think the Python solution or ScopeIf+ from clockwork package is what you are looking for.
I didn’t test the ootb node ScopeIf but that one in the past causes most off the time dynamo to crash

Nico Stegeman

3 Likes
7

Not a bug, it’s just returning shortest lacing.
See these issues for background & solutions:
DynamoDS/Dynamo#7467
DynamoDS/Dynamo#6258
DynamoDS/Dynamo#6491

So use OOTB node ScopeIF:

if
if1416Ă—657 140 KB

4 Likes
8

Hi Kulkul
I stopped using the ootb node ScopeIf in the past. Because it causes dynamo to crash sometimes. I use python or the clockwork ScopeIf.
Is the ootb node recently changed and more stable?

9

It has nothing to do with being stable but the intent of the node… It is meant for another use than this, namely not executing up stream nodes… Failing to have completely separate tracks will cause dynamo to crash…

2 Likes
10

Hello Jonathan.
You’re right.
Thanks

1 Like
11

Hi all,

thank you for the feedback. I used Scopeif+ from Clockwork package.

Best Regards,
Adnan

2 Likes