(possible bug) Connections between network nodes on planes are not refreshing/updating after moving plane. They can be refreshed after changing location of the node.
This has long been the case - the network nodes need to be moved for it to redraw. I'll send a note for the developers to consider.
Thanks,
That was my workaround (changing location of the network node OnReset).
This is a problem/bug that bothers me a lot and caused my analysis results to be wrong. The worst is that you may be unaware of it. Especially when you use the experimenter to change the position of the plane as a parameter.
See the example I have attached. During the simulation, the operator moves 2 items between the planes (result: time ~ 127, distance: ~ 238)
I change the position of the plane - the paths are broken and even a reset does not refresh them. Despite the longer distances, you will get the same (false) results (result: time ~ 127, distance: ~ 238).
Using flexscript I'm changing (+1, ..., - 1 z) node position, you can see that the network is refreshing (as proposed by @Dawid Dabal). It looks good. But you are wrong! Reset, run ... (result: time ~ 127, distance: ~ 238) (!)
Only "manual" movement of the node (+ -) also refreshes the network data (not only visually). Reser, run ... (result: time ~ 164, distance: ~ 311). Now correct!
So as you can see, it can lead to a lot of problems and errors. Now, I "touch" all the nodes by hand to make sure I get the correct results. But it is not elegant and very time-consuming.
@jason.lightfoot I think that this should be treated as a priority.
Maybe there is some "hidden" function to refresh the path network?
You should call optimizenetwork() after you've adjusted the nodes. The developer note links to this page, so your view on priotity will also be seen.
Note: For anyone trying this model in 21 - Importing this model to 21.0.3 forces the model into an experiment scenario for which you have two y locations defined and they're constrained to -30 to -60 which is why you can't replicate the actions shown in the gif and why you can't set the y value in the experimenter to 0 until you've altered the model parameter constraint.
@jason.lightfoot thank you,
changing (+-) the location of the node and optimizenetwork() after changing the position of the plane finally refreshes the network.
8 People are following this question.
