GC2 real world accuracy and general questions?

[davray666]

Hi there all you GC2 owners! I am seriously considering becoming one as well.
I still have some questions that are difficult to get answers to by reading the official documents or marketing material.
So if any of you could shed some light on the topics I would be grateful.
We can assume that everything is setup correctly and that I am using new balls in an indoor environment.

1. Flop shots, what is the highest vertical launch angle that the unit can pick up reliably. The spec claims 70 degrees. Would you agree that this works reliably at the specified +/- 0.2 degrees accuracy?
2. The Horizontal launch angle is specified to +/- 1 degree. While this might be accurate for some low launching irons and drives. Would you say it's also valid for wedge shots that launch higher?
In some cases people tend to measure the accuracy based on feel. Have you done or seen any accuracy tests where something more scientific has been done?
3. If I buy a used unit, is it still possible to register it and get support from Foresight without paying transfer fees?
4. I have seen some discussions on TGC + GC2 compatibility but can't conclude if it is indeed compatible with the latest firmware, Is it?
5. If a simulator software supplier wants to read the data the unit produces via Bluetooth to use it for game play or other things. Do they have to pay Foresight or is this protocol provided for free?

Am I barking up the wrong tree, should I post the questions somewhere else like Foresight official support or something?

[davray666]

Very interesting test and results. Thanks for sharing. The fact that the unit and Foresight range show different trajectory and carry is a bit unexpected since I assumed they use the exact same algorithm to calculate. Even if they use Red Chain SW now you would think they looked at the different algorithm's and settled for 1 being more accurate than the other.
Did you test any high launching chip shots or short 10 - 50y wedge shots?

[SFR]

I was not too worried about the height of the shots and more just the carry being accurate and the off line being accurate. For the short 50 to 100 yd shots I was chipping an 8 iron. In the past my wedges on the sim in the shop gave me the same carry as I would get out doors so that has never been a concern.

Js1010 brought up the point about the updated FSS software which I think he was right. I forgot that I had never updated the laptop since I don't use it on the sim anymore. That would account for the yardage being different on the GC2 readout compared to the range software and what it used. Just not sure that it changed the side spin effect.

[TaS]

I have always felt that the gc2 showed more bend than would actually happen when I hit trouble shots and tried to put a big curve on the ball (out if trees for example). I'm pretty good at curving it either way irl, but can never get a slice to bend like it does on the sim. I always chalked it up to the camera having to see the ball from the side and the errors inherent in trying to measure side spin.

On normal shots, it has always felt right though. I feel like it doesn't ever mistake a mild draw for a fade and vise versa. That is the main thing I'm looking for when I hit thousands of balls through a winter.

[Js1010]

SFR, what version of the FSS Range Software are you using. They updated it last year to 1.291.1011.18.. I believe they updated the carry algorithim in this version to coincide with firmware changes they made which included some carry algorithm updates. I have not tested extensively but the shots I have looked at the carry on the GC2 matches the Range software.

[SFR]

I will need to check that. Come to think of it I had updated my sim computer but I used the laptop and that may still have been the old version. Now that you reminded me of that update, I remember that the old software did boost the carry on it's own but its funny that for carry distance here, the boost is closer to real carry. Crap, now I might have to update and try again. I wonder if the hook and slice was updated so that it was not as extreme as it was in the old software. I still use an older firmware so I have a flash count but they had said nothing in the firmware had changed for ball flight...... at least that was up to 3.7 version. Wonder about the newest one now.

The big thing I got out of the test was that the GC2 readout was short on the driver and by about 5%.

[SFR]

SFR, what version of the FSS Range Software are you using. They updated it last year to 1.291.1011.18.. I believe they updated the carry algorithim in this version to coincide with firmware changes they made which included some carry algorithm updates. I have not tested extensively but the shots I have looked at the carry on the GC2 matches the Range software.

Just wondering if you updated the firmware yet the the newest now to compare and if so any thoughts?

[Js1010]

I have not tried the new firmware yet.

I dont find gc2 short at all. If anything i find the carry to be long with low spin driver shots. I tend to hit up on my driver so i get a lot of 2000 back spin and some under that. I find gc2 carry is more than it should be in thes cases. I plug those numbers into optimal flight and flightscope optimizer and i get what i would expect for carry number. I will post a few of my driver numbers later tonight to show.

I am curious what your driver numbers are that are carrying short on gc2 - backspin very high or really low?

[SFR]

I did not have a lot of time and was mainly just wanting to compare carry with the GC2 readout. If I get another chance I will need to record some of the numbers with spin and compare when the yardage is off most compared to real life carry. It's not often I can have someone stand out on the range and watch the balls landing spots to compare with.

I was on the 1.147.1133.060511 with the laptop. Going to update it.

Just did the update I had on file and it was only 1.271.1020.090713 so it looks older than yours.

Do you still have the newer update?

[Js1010]

Just sent you a PM with link to this update.

[Js1010]

Here are two driver swings where I am pretty sure the carry stated by GC2 is too long. Nothing scientific here but I don't think I can carry a ball 284 yards with my ballspeed. I added in a column for Optimal Flight and also Flightscope and the numbers those gave seem much more likely. Again my issue is only with fairly low spin shots on GC2 - as the spin numbers get up in to the 2200-2700 the numbers GC2 gives vs Optimal Flight and Flight Scope are a lot closer.
.

Ball Speed	Launch Angle	Azimuth	Side Spin	Back Spin	GC2 Carry	Optimal Flight	FlightScope
155.8	14.3	-1.6	468	1712	277.22	257.3	257
162.1	12.5	1.4	449	2153	283.58	270.4	271.6

[Nobblescrunch]

Hi JS1010. Intriguing reading with regard to the possible algorithm change in the new software. I'm running an older version and have noticed a few times numbers that just don't seem right. Have you got an up to date version of the software to hand?