Strange Trace behaviour with V4

With V3.9.X trace works as expected. :slight_smile: Not so with V4.X. Do you know a workaround for that Problem?

Trace.kmz (486.3 KB)

just back from a road trip. will review today.

1 Like

Don’t hurry, I have a plan B :wink:

disable ease down … I merged a recent PR to make that more flexible and it’s causing that segment to be passed over. need to debug further. thanks

1 Like

fixed. will push around GMT+3 tonight

1 Like