Hi,

You've helped me in the past to make some good progress in making our diagrams look better.
I need some additional help.
Please examine the attached screenshots which demonstrate some of the challenges we are having.
As you might recall, I am using the "angle" approach that you provided for determining which anchor points to use on the task shapes (the blue rounded rectangles).  And although this is working, we'd still like to avoid the overlaps.

Any suggestions?  Would adjusting the various avoidance values be an option?  Here's how I currently have them set:

diagram.RoutingOptions.CrossingCost = 50;  // Original = 50
		diagram.RoutingOptions.LengthCost = 10; // Original = 10
		diagram.RoutingOptions.NodeVicinityCost = 5; // Original = 5
		diagram.RoutingOptions.TurnCost = 1; // Original = 10 

Thanks for any advice.

Jim

Hi,

RoutingOptions values are considered only by GridRouter, are you using its instance as diagram's LinkRouter? In addition, at this time CrossingCost is only calculated for links whose Shape is set to Cascading.

If using GridRouter and Cascading links, try also setting smaller RoutingOptions.GridSize, because two links passing through the same grid square would add the CrossingCost penalty even if they don't actually intersect. Thus a coarser grid might lead to choosing a path where links do intersect visually if evaluating alternative routes but the penalty values remain the same (when the non-intersecting alternative still shares a grid square with another link).

I hope that helps,
Stoyan

Please attach a saved diagram file showing these links. I've tried to reproduce from one of the screenshots but am getting nice results with all default RoutingOptions settings, both with QuickRouter and GridRouter.

I can see the strange bends after loading the files, but setting your options and calling RouteAllLinks without doing anything else removes them:

diagram.LinkRouter = new GridRouter();
diagram.RoutingOptions.GridSize = 2.3f;
diagram.RoutingOptions.CrossingCost = 50;
diagram.RoutingOptions.LengthCost = 10;
diagram.RoutingOptions.NodeVicinityCost = 35;
diagram.RoutingOptions.TurnCost = 5;

diagram.RouteAllLinks(); 

Are you sure you aren't running some additional post-processing code that modifies ControlPoints? The chosen paths might depend on the initial positions of links, so I might be seeing different results when calling RouteAll on the already-routed links. Does it look better if you call diagram.RouteAllLinks() for a second time?

Stoyan