Tacks showing as failed gybes and wrong failed gybes

Support
1

Hello there,

A number of tacks show as failed gybes in the turns stats.

The tacking track quite clearly shows an upwind turn, you can tell by the “triangle shape” and cross of directional lines and the lack of a round shaped track with no lines crossing that would indicate gybe.

Also, withun the turns actually marked as gybes, the number of failed ones is not right.

Is this something that could be revised?

Thanks

2

Hi,

which version of the analyzer was used? You can check this by opening the session and scrolling down to the info section.

Tack/gybe classification also depends on the wind direction setting — even a degree or two can flip borderline maneuvers, so it’s worth adjusting that first.

If the issue persists, please send the original file (anchor icon in the info section) to support@sunbits.de so I can take a closer look.

3

Hi, coming back to this issue.

I use v12 of the app and the quality shows as 1.4 - very good.

The app keeps counting tacks as missed jibes.

I’ve adjusted the wind direction but still a significant tacks wrongly qualified as missed jibes.

Over 2h sessio, port stance I only jibes twice and the rest were all tacks. On starboard I only tacked once and the rest were all gybes. The s-jibes count seems quite accurate at 32, but port turns show as 12 p-tacks and 20 p-jibes. It’s the 20 p-jibes where the issue seems to mainly lay on. Those should be additional 20–tacks. In the track it’s clearly a tack move, not even close to a jibe curve.

Normally I don’t mind this metric but yesterday I deliberately only tacked on port and jibed on starboard.

Would you mind having a look at this please?

Thanks

1000093438
10000934381080×2340 164 KB

1000093444
10000934441080×2340 267 KB

1000093442
10000934421080×2340 252 KB

4

Hi,

thanks for the detailed breakdown — that’s really helpful for reproducing the issue.

Could you send the session file to support@sunbits.de? I’d like to take a look at the actual track data to investigate further.

5

Hi,

version 2.0.20 is out — it includes an improved maneuver detection algorithm based on the file you sent, so your case directly contributed to this fix. Thanks for that.

The update also brings automatic wind and weather data loading, which should eliminate the manual wind direction guessing. Wind shifts are now tracked throughout the session, so rotating winds are handled correctly too. If the default hourly resolution isn’t precise enough, you can manually edit the weather data at 10-minute intervals directly in the session.
Would be great to hear if this resolves the issue for you.