Carry numbers discrepancy between FSS and GC2a

[Smurfsky101]

Running the latest firmware 4.0.0.15


Which ones are right ?

I plugged some of the ball numbers into flightscopes optimizer, showing something closer to what the gc2 is indicating .

Tgc is showing numbers consistent with the unit. My gut is that something is wrong with the foresight desktop software .

Ive got the latest drivers on the desktop too. Connected via Bluetooth , not USB. I'm gonna try connecting to the iPad Bluetooth app later

Also, hmt data is not coming into the desktop app.

Any ideas ?

[Snaphook]

It is known that the gc 2 shows inflated carry numbers when spin drops below 2000. (i wish foresight would fix this) But there is something wrong with the FS software numbers. It's almost like it's showing meters (i know it says yards)
It must be something in the settings. Is everything properly aligned?

[Mozza]

You haven't got wind or slope activated by mistake

[Js1010]

FSS desktop software carry seems very low for those numbers. Very strange.

Are you getting the Foresight Desktop Software numbers from the foresight range? I believe if you are hitting in the foresight software on a course then the elevation of the hole is taken into account on the carry number. Also, as Mozza said - make sure the wind is off.

[Smurfsky101]

OK so I used the ipad software, matches whats on the GC2, which ... I assume.. is accurate? Any math wizards or rocket scientists on here that can fact check the general spread on these numbers here? They're wildly inconsistent, I was playing around with a bunch of different driver swings and trying to stop doing my out to in thing.



I've got a pretty ugly slice that's popping up, i'm hoping that with all this data I can find a swing that produces a straight shot without intentionally pulling it / doing nasty stuff with my hands

[Snaphook]

The numbers look correct. That path looks to be a severe out to in (also explaines lots of toe strikes) This is going to take some work to correct. But once you do, you will be happy you did!
Good luck

[Smurfsky101]

The numbers look correct. That path looks to be a severe out to in (also explaines lots of toe strikes) This is going to take some work to correct. But once you do, you will be happy you did!
Good luck

Truth ! I've been able to make it work with some pull cuts on the course , but the strikes are glancing at best and my smash factor suffers.

Have been able to get an in to out swing working for my wedge through six iron, hoping to find a way to make it translate to my driver. If I can maintain the high clubhead speed I should be able to milk some distance out of it

[Shankygolf]

Face to path numbers aren't actually too bad. I'd say play the ball position an inch or so further back in your stance, that way you'll be hitting less up on the ball and the path will be going less out to in. You'll need to work on release after this to match face and path again but easier to change ball position than swing!! Also smash factor isn't too far off, we'll never see the dizzy heights of 1.5 smash on gc2 hmt as measurements are taken at slightly different points to TM

[mthunt]

Face to path numbers aren't actually too bad. I'd say play the ball position an inch or so further back in your stance, that way you'll be hitting less up on the ball and the path will be going less out to in. You'll need to work on release after this to match face and path again but easier to change ball position than swing!! Also smash factor isn't too far off, we'll never see the dizzy heights of 1.5 smash on gc2 hmt as measurements are taken at slightly different points to TM

Shanky, are you using one dot on the HMT? What data points do you get?

[Shankygolf]

Shanky, are you using one dot on the HMT? What data points do you get?

It depends on what I'm looking for with a student, with one dot you get club speed, angle of attack and club path.

[Smurfsky101]

Help me out here, how would moving the ball to the right in my stance reduce the out to in path? (am trying to visualize but am not seeing it)