Why doesn't Foresight fix the low spin carry?

[Alex Ma]

I know I'm potentially beating a dead horse here. I've done some research online but couldn't find a good answer so I'm posting the question here. I think it's widely known that foresight rewards low spin shots too much by giving high carry numbers to low spin shots, especially with drivers. That issue has been existing for a while and was never fixed and here is few things that just baffle me all the time.

1. It should be a relatively easy fix. When you hit a driver with sub 2000 spins or even below 1500 rpm, they won't have enough airborne time and thus wouldn't carry that long. why don't they just change the algorithm to fix it?
2. Lots of the famous YouTubers use GCQ numbers for instructions and equipment testing. I bet that they know that 170mph shot with 1600 spin doesn't carry 320 yards yet they never say a thing. Don't they know that they can't hit their drivers 350+ yards on a regular basis on the course?
3. Lots of tour pros use GCQ and shouldn't they be bothered by those numbers? Don't they provide feedback to foresight so they can update the algorithm?

For such an expensive equipment to have such a big error for years without fixing it is crazy in my opinion. Especially given that the fix is not as big as the graphics change. It's just a simple algorithm change.

Anyone has any insights?

[Baller]

It's not al algo issue...I think. I'm pretty sure the Quad reads this correctly, but the issue is with how FSX 2020 takes that info and shows it. In the low spin high carry issues I've seen, my Quad always gets it right and the issue is ONLY shown in FSX 2020.

Are you seeing otherwise?

As far as fixing it, that's a good question though, but perhaps they've tried to duplicate it and have been unable. Just a thought. It doesn't happen every time.

[Alex Ma]

It's not al algo issue...I think. I'm pretty sure the Quad reads this correctly, but the issue is with how FSX 2020 takes that info and shows it. In the low spin high carry issues I've seen, my Quad always gets it right and the issue is ONLY shown in FSX 2020.

Are you seeing otherwise?

As far as fixing it, that's a good question though, but perhaps they've tried to duplicate it and have been unable. Just a thought. It doesn't happen every time.

FSX2020 just takes the calculated carry distance from the GCQ right? The problem is the underlying algorithm from GCQ is wrong and has 10-15 extra yards of carry.

[Baller]

Post if you see that happen and post what the quad shows that you think might be extra carry. I've not seen this at all. I have never seen the quad miscalculate one single shot on the quad (in my opinion) and I have probably 100k shots on my quad (just a guess, but I use it at least 4 days per week in the more than 5 years I've had it. There used to be a shot counter on there but looks like it isn't there anymore and I looked years ago and I was at 30k+, so whatever the number is, it's now much much higher. I have seen miscalculations of that data in 2020 though and it is sometimes different because of course conditions and 2020 calculating what that shot will do under course conditions.

[Ronsc1985]

FSX2020 just takes the calculated carry distance from the GCQ right? The problem is the underlying algorithm from GCQ is wrong and has 10-15 extra yards of carry.

FSX 2000 and every other sim program does not take the distance from the launch monitor. They all take the launch conditions i.e. ball speed, launch angle, azimuth,spin rate and axis, and put this date into their ball ballistics algorithms. These algorithms are not closed form solutions but rather iterative computations.

[Alex Ma]

So GCQ has a carry distance shown on its screen. Are you guys saying that FSX will have a different carry distance than that number? I’ve never seen it happening.

[Baller]

Yes, exactly. The quad determines what happens from your shot assuming there is ZERO landscape and nothing to affect your shot. FSX takes that info and plugs it into the course conditions and then estimates what would happen on the course you're playing (or range, or whatever...). Even if the number happens to be the same or similar, it isn't.

[Ronsc1985]

So GCQ has a carry distance shown on its screen. Are you guys saying that FSX will have a different carry distance than that number? I’ve never seen it happening.

Of course it will. The LM assumes flat terrain and some ambient weather conditions. If you play a sim course with undulations the carry distance will be different as it is in real golf on different courses with different ambient atmospheric conditions.

[delaloi]

Yes, the carry distance numbers on GCQ and in FSX2020 are not always the same. I have not noticed them differing wildly, no more than a few yards. I thought it was probably due to how they measure atmospheric conditions or something. But I do not hit my driver at 170mph with 1600 spin.

[Alex Ma]

Oh, I guess I never adjust the environment and I'm only talking about the driving range so there is no slope change. Terrain shouldn't impact carry at all. And forget about FSX. Just the carry distance on the machine itself favors low spin shots. My ball speed is usually around 145-150mph and it says I carry it 250+ yards with 1300-1500 spin. No way that is happening in real life.

[preludesam]

With the right launch angle that would be correct. Three basic metrics to determine carry distance. Ball speed, vertical launch angle, and spin.

[Baller]

And even in Driving Range, everything is being interpreted by FSX and you can get those low spin extra carry ones, but it won't do that in the Quad itself. It's an FSX issue only.