Hi,

Example 1: Try setting smaller QuickRouter.UBendMaxLen value if you'd like the U-bend segments to be shorter in this example.

Example 2: Generally this happens because QuickRouter ignores link lengths but only counts the number of tiles (each tile possibly having different dimensions) generated by some kind of spatial trees. Our developer is looking into ways to implement evaluation of true link lengths without slowing down the algorithm. In this particular case you might get better results if you set larger QuickRouter.TurnCost value.

Example 3: Larger QuickRouter.TurnCost value should help here.

GridRouter: Path finding fails if some nodes are too close to each other (distance <= twice the router's grid size). In that case the empty area between such nodes might still be marked as an obstacle if the nodes intersect the grid tiles. You could either decrease the grid size, which will lead to slower path finding, or otherwise pull such nodes away from each before routing the links.

I hope that helps,
Stoyan

Could you attach the diagram xml file here or email it to support@mindfusion.eu?

The problem in this case is that the attached transparent nodes you are using as labels are very big but are marked as obstacles. If you do this after loading the file, you will see that the "delay" and "annunciate" labels overlap and the link cannot pass between them:

foreach (ShapeNode node in diagram.Nodes)
    node.Transparent = false;

You could either set Obstacle = false for label nodes, or set their Bounds.Width to be no bigger than the master node's Width.

I hope that helps,
Stoyan

It seems TurnCost is considered only if Granularity is set to Normal:

QuickRouter router = (QuickRouter)diagram.LinkRouter;
router.TurnCost = 100;
router.Granularity = Granularity.Normal;

Increasing TurnCost from 50 to 100 leads to much fewer bends, but it's still not quite perfect. And then when I tried larger costs, it started showing the longer path again, which is very strange. Our developer will debug this next week to see what exactly happens.

Stoyan

It works much better(not perfect).  Do you have any time estimate when these changes will be released?