As a lot of you know, GC2/GCQ exaggerates longer carry distance on a low spin driver shot that is less than around 1900rpm. I have sent out my findings to engineers at Foresight a while back and they have recently acknowledged that there indeed was a flaw at the carry distance GC2 and GCQ output.
They told me through my sales rep that the new firmware is coming soon within this week with a fix on this issue.
This will be a very important milestone and a next step for Foresight to gain more competitiveness in the industry against Trackman and more accurate algorithm such as OptimalFlight.
I also noticed an oxymoron on Flightscope's Flight Optimizer; They also use OptimalFlight algorithm but they also had issues showing the correct distance on low spin driver shot like Foresight.
I think the main issue was because they fluctuated the Height/Apex to be higher than real life, causing the distance to go farther. I am aggregating my findings to send out to Flightscope as well on this.
They told me through my sales rep that the new firmware is coming soon within this week with a fix on this issue.
This will be a very important milestone and a next step for Foresight to gain more competitiveness in the industry against Trackman and more accurate algorithm such as OptimalFlight.
I also noticed an oxymoron on Flightscope's Flight Optimizer; They also use OptimalFlight algorithm but they also had issues showing the correct distance on low spin driver shot like Foresight.
I think the main issue was because they fluctuated the Height/Apex to be higher than real life, causing the distance to go farther. I am aggregating my findings to send out to Flightscope as well on this.
Comment