New update not measuring accurately

[Schlob27]

Is anyone else getting bad yardage since the update?

I noticed I lost 10+ yards on all shots and more with wedges.

when I plug my data into flightscope optimizer, flight scope says I should be getting 10 more yards with the data given.

I have my altitude sat at 5000 feet for my ISS but when I zero it out its still 10 yards off.

every other shot I get 10k backspin but I see so is everyone else.

Thoughts??

[Morini]

To my knowledge, no change in firmware, image engine or ball flight model, so coincidental. I don't know if altitude is the best way to compensate for ISS. It does affect the impact of spin etc. I am guessing that if you ran the same comparison at sea level, it would be closer. But ball flight models are all slightly different. For example, Trackman and Flightscope don't have identical carry for identical ball data. Also, it is possible that the impact of lack of spin decay on Skytrak increases at altitutde.

[Schlob27]

As I stated when I zero out the altitude, its still 10 yards.

Are you compensated by Skytrak? Everyone one your comments deflects any fault with any skytrak.

It's amazing that when I got my skytrak and complained about numbers off, you stated the flightscope optimizer was the holy grail of accuracy.

Now that it's conflicting, it's nominal.

[Morini]

I misread that part, though your image was a 5000 feet comparison. Still no need to be rude. I don't recall ever telling you to use Optimizer. But it does takes spin decay into account so a good second opinion regardless. That aside, I did not see the words "holy grail" or "nominal" any where in my posts. And I think you missed my many posts pointing out the Skytrak spin issue for high ball speed 7 irons.

[RAH5]

I haven’t noticed anything. My carry and spin numbers generally seem the same as they were.

[thorin33]

With all the beta and now official release spin and carry numbers are the same

[Morini]

The release notes indicate no changes to ball flight. Every update, people post about lost distance, but it always turns out to be co-incidence.

[SkyTrak_Seth]

Someone else started a similar thread, and I'll post the same in here...It's hard to say what could cause that, but I can guarantee that nothing was changed regarding image processing, analysis, measurements, algorithms, etc.