FS Golf app - ver. 7.0

[Mirek_62]

A new version of FS Golf has been released. It now includes a new Challenges section and Face Impact data is also available (for those who have paid the fee).
Does anyone know what the significance of the header colour for the data is? See photo.

[drawplayer87]

Cool...different header colours for different data types, e.g. Ball data, club data. etc.

[Mirek_62]

It's a bit confusing - e.g. Launch H and Spin Axis are Ball data and have different colour.

[bubbtubbs]

The challenges are fun. Nice to not have to switch to Skills to do any target practice.

[boungolf]

Cannot wait to try the new App.
we can get rid of the Skills App now and just use FS Golf.

[Dan13]

Go into table view and the headings are color coded by type. Categories are:
- distance / speed / spin /smash = dark green
- ball angles/ club angles / swing plane angles = light green
- flight / shot type / face impact = blue

Interesting way to group the data. Haven’t grasped the significance yet - if there is any. For a moment I thought FS had added something similar to the optimization data range feature in Trackman. Nope.

[bubbtubbs]

We should talk more about how awesome that is and how it'll never happen. That way, they'll add it later this year like impact location.

[Dan13]

I hope it works like that! Such a cool feature. It adds context to the data so you can compare to something optimum.

[Shankz]

I am going to preface this post with the fact that I did not have the app updated this morning when I went to the range but I did have the firmware updated. I am an improving golf who is just learning to hit in to out. I have had a lot of success lately hitting draws thanks in part to the pro package. This morning at the range I noticed when hitting driver I watched my ball draw and or hook to the left and the FS golf app dashboard read slice and the trajectory view showed a slice to the right. Prior to updating the firmware my swing path had been primarily right to left and now it’s just the opposite. I am also getting a lot of italicized spin numbers, not to mention reduced yardage as well. I have attached screen shots of the club path numbers as well as the shot types. The format is now in the new app because I updated the app when I got home and saw this post but the the range session was conducted prior to the update. I called FS support before I left the range and told them what was going on. I was told that the update was due out this week. Support told me to see what results I get after the update. Had I been told that the update was already available I would have downloaded it while at the range and tried but like I said support told me it was due to be released this week. Is anyone else experiencing this issue?

[Dan13]

No I hit some balls indoors with the new firmware but before the app update and didn’t have any issues.

[preludesam]

I’ve made a couple mistakes after new software or firmware most notably having the wrong radar type set i.e using outdoor in the garage or indoor at the range. I would check that first. It should be listed in your review session dashboard.

Can your remember which shot number gave you the wrong data?

Also I remember Henri answering the a couple questions in a webinar about range balls. He stated they are so inconsistent across the board and the hardest ball to measure. Is it possible you had a couple bad balls in the bucket? If they were all new range balls then probably not but man I’ve see some rough ones out there on the range.

[Shankz]

The mode is not listed in the new version but the temperature is 65 degrees so I am pretty sure I was in outdoor mode, plus I am very careful with the unit when I set it up with regards to alignment, distance to ball and height of mat.

I had multiple shots that were misread, both in shape and distance plus a large amount of italicized spin numbers.

The balls are in very good shape.

Prior to updating the firmware everything thing seemed great and I was feeling really good about the progress of my swing but now not so much because I don’t know what to trust.

[Justin JY Christensen]

just tested out the FS Golf 7.0 app but with Firmware 0.25/AVR 0.27...couple notes

- wedges are good...saw no issues
-irons are good...i do like the "autocorrect" ball shape after you hit...obviously its doing more calculating but it isnt perfect...it saw when i blocked a ball and when i drew a ball

-driver was good and getting better, until i started seeing the dreaded 45 degree spin axis monster come back...0.20 was a decent firmware and it wasnt that bad but it does seem like once they add features, something that was working no longer does

Next i turned on TGC 2019 and played a quick 18
typically i have ZERO no reads, this session i had 2...not a huge deal but it still happened....ball flight was normal, chipping was normal, numbers were normal

i will be testing out the 0 spin axis issue when chipping later tonight, then tomorrow ill update to the 0.26 firmware and do the same testing

[DrShaftE]

I have noticed also some odd numbers after updating latest firmware and FS app. There were a lot of misreadings which I got very rarely earlier. For example couple good drives show 81m and 85m carry and some 6 iron sky rocketed outside DTL range window. Also I noticed a little decreasing of distances (~5m) compared earlier with every club. Setup is identical compared earlier and I have used Mevo+ regularly 2-4 times per week the whole winter so I would say something has happened to accuracy.

Also I`m not a fan of new data order in listing view. Earlier user could arrange data parameters one by one but now data parameters have stacked under headlines like spin, distances, speed which include multiple data parameters and cannot be separated - really annoying.

[Stessier]

Also….I noticed 7.0 changed the mode settings. Used to be 3-options: short indoor, indoor, and outdoor. Now 2-options: Limited Flight (8ft-44yards) and Outdoor.

[Targuy]

Depending of the platforms (pc ipad iPhone) but there are regressions on the usage of the metric system or a mix between imperial and metric.

[Targuy]

Face impact settings have weird min and max limits par club type.
for example my 5 wood Callaway Mavrik which dimensions are 40 and 100 mm is too small to be configured. It is like the app has only driver dimensions for woods.
i have the same kind of issue for the height of my SM9 Titleist wedges that are to tall for FSGolf.

[preludesam]

It’s only to get an estimate of the club dimensions if yours is drastically different than the majority, hence a tiny blade versus a chunky game improvement club. If its reading the impact location correctly I’m not sure the complaint has merit?

[Bertikoks]

I went to the range today and hit about 120 shots. Only one of them was a missread. Sounds fine? Yes, for sure, but there was no „Face Impact“ located. Not even one single shot has had the wanted information. The field/sign/button (however you may call it) for FIL was there on the trajectory screen, but it was empty. I started different sessions of „Full Swing“ but the result was the same. I went to general settings and try to activate the add-on again, but got the answer, that FIL was already activated for my radar unit. What could be the issue? Any idea?

Targuy told us about FIL Settings. I didn‘t find them.
Thank you for your help.

EDIT: The new Video has an explanation. Will try it again tomorrow.

EDIT II: May be I‘m a bit goofy, but I would be happy if Flightscope decide to make a good manual. How to use the hardware and how to get the best out of the software. And how to install Add-ons (and calibrate it).

[VoodooZ]

You're right about manual! Only problem is they can't stop changing things so they can't document it properly..
It's nice to have new features but they need to seperate beta and stable software so that people who need to have stabibility can opt out of all this chaos.

[Bertikoks]

For your information: Seems to me, that it was a software bug. Got a firmware update today. I can see now the FIL sign in the session verification. Tomorrow I will try again to calibrate the tool.