[v150] constructing Roads via "Route to"-Option

[Sanguinus]

Hey,

constructing Roads via the "Route to"-Option often ends in strange behaviour.

Say I want to construct a road with 3 tiles from one city to another. After finishing the first tile, the Worker "warps" through the air, landing near/in the target city and continues his work on the last road tile, leaving the middle one blank.

Or: the Worker aborts his missions and flees the field right into a nearby city.

 

[lukeloh]

Yeah this bug has been around since forever, even in vanilla. Don't think this is something Thal can fix.

 

[Seek]

I haven't seen this issue, but I've noticed sometimes the worker takes twice as long to build a road when "route to" was ordered - the road will be done but the worker will just stay on that tile digging for an extra turn or two. Perhaps these problems are related.

 

[Thalassicus]

This is a vanilla bug we can't fix with mods.

 

[Sanguinus]

Question is then, wouldn't it be better to remove the option due to it's faulty behaviour?
On the other hand, I think a route distance of 2 tiles does not end in errors and can be used for sure.

 

[Thalassicus]

I rarely "route to" for long distances because Firaxis coded the routing algorithm wrong. It follows the shortest before-roads distance, instead of the shortest after-roads distance. This sends the worker on the wrong path when there's a "red herring" road pointing in a different direction.

... if that made any sense. It's hard to describe in words.

 

[Zaldron]

I always wondered why my workers go crazy like that with existing roads. I never route to more than 2-3 tiles at a time for that reason.

 

[Thalassicus]

To put it another way... it moves the worker from point A to point B, and just happens to stop to place a road on each tile. That means it follows the shortest distance currently visible on the map. This is sometimes the ideal route, but not always.