Seems to be an ID stability bug of some sort: if I create a scopesession containing two scopes and save it, then open the filter graph editor after reopening the session, sometimes the trigger nodes in the graph will have traded places.
The connectivity is still correct, the scopes will trigger as expected, but the nodes are drawn in the wrong place leading to annoying criscrossing lines.
Seems to be an ID stability bug of some sort: if I create a scopesession containing two scopes and save it, then open the filter graph editor after reopening the session, sometimes the trigger nodes in the graph will have traded places.
The connectivity is still correct, the scopes will trigger as expected, but the nodes are drawn in the wrong place leading to annoying criscrossing lines.