Official v3.2 SkyTrak App Release

[jdgould]

SkyTrak_Seth I'm not sure if this has already been addressed, but last night I was using the latest version of skills assessment under game improvement and when I click on the 8th club it adjust the yardage for the 9th club instead of the yardage for the 8th club? There doesn't seem to be a way to adjust the 8th club.

[aushizz]

SkyTrak_Seth

You guys rock! Keep it up.

[SkyTrak_Seth]

SkyTrak_Seth I'm not sure if this has already been addressed, but last night I was using the latest version of skills assessment under game improvement and when I click on the 8th club it adjust the yardage for the 9th club instead of the yardage for the 8th club? There doesn't seem to be a way to adjust the 8th club.

Yeah, I'm trying to get a quick patch out today for that. Sorry about that

[SkyTrak_Seth]

With the adjustable feet on a metal jacket, you end up with your best guess at being level with the hitting surface. Just how critical is this? What numbers would this throw off if you're not perfectly level?

It's not terribly important that you are spot-on to the millimeter, but there are 2 things that can happen if a unit is wildly off-level from the hitting surface:

1) You'll end up with no-reads because the ball is getting cropped off the top or bottom of the images
2) The laser dot won't be at the correct distance away from the unit. Again, there's wiggle room here but still can be an issue.

[trumb1mj]

What are the consequences of the laser dot not being the correct distance away from the unit?

[whitlecj]

My hitting surface is not completely level due to the the slope of my garage to a drain. It is not drastically sloped but there is a slope there. Should the skytrak unit be level to the hitting surface or truly level?

[mikestuewe]

I really like the wedge matrix concept, but man is it just a constant reminder that the skytrak can’t read wedge shots. Great software though Seth, I am really impressed how far it’s come.

[trumb1mj]

What issues do you see with wedge shots? For me, as my ball speed gets greater, the inaccuracies creep in.

[mikestuewe]

trumb1mj, nothing that hasn't been reported before. skytrak just can't read high launch wedge shots. trying to pitch a 60 degree wedge leads to 50% misreads, thats with the ball in front of the laser dot.

[SkyTrak_Seth]

The only time I've ever had to move the ball is on the pitch shots, so I typically move the ball about 1 inch in front (toward the net) of the laser dot. Haven't missed one since.

[Mandragora]

I used the wedge matrix for the first time and it worked well. I have been doing this manually so now I can just get the printout and make the changes to the card I carry. Is there any way you could create a way to save a session so that you don't have to do it all at once. Same for Bag mapping and dynamic handicap. For the matrix, if each position requires 5 shots, that is 80 shots to complete the matrix.

[SkyTrak_Seth]

Yeah, I'm working on that.

[Mirek_62]

The bug with trajectory rendering was not fixed 😥

[SkyTrak_Seth]

Mirek_62, Crazy...let me see if I can reproduce this here.

[doublebogey]

SkyTrak unstable after upgrading to v3.2 - see video (https://streamable.com/easm1) where although the app shows SkyTrak is connected via wifi, the top light keeps changing from green to red and back to green causing the laser to disappear and reappear, etc.

[SkyTrak_Seth]

doublebogey, This may be a hardware issue...I'm checking now. But does it do the same thing if it is outside of the metal case?

[SkyTrak_Rahim]

doublebogey,
This looks like the symptoms of a looping state achieved when the IR beams are reflected back into the SkyTrak unit. I suspect that IR from your unit is being reflected from a surface in the room back into the ST or from the aftermarket case you have it in now, the latter is the most likely the case here. A simple re positioning of the unit in the case or removing from case completely should solve this. Please keep me posted on this issue
Thanks

[doublebogey]

SkyTrak_Seth and SkyTrak_Seth,

FYI took FMJ case off and reinstalled case, and looks like this looping state created by IR beam reflection might be gone now. Thanks.

But still get quite a bit of no reads and/or dropped wifi connections - more than before v3.1 - like others have mentioned? Basically usually after 2-4 shots into session, I either get RGG and it stays there or middle light turns yellow and I have to exit session, connect and restart a new session (then 2-4 more shots and problem repeats itself).

Also one more interesting thing to note: Before v3.1, I believe when one exits a session back to main menu the ST stays connected (i.e., bar at bottom of app stays green and shows "CONNECTED"); but after v3.1, every time I exit a session the bottom bar of app turns yellow showing "CONNECTING" and tries to reconnect each time one exits a session. Do you think maybe this is the problem introduced since v3.1? Thanks.

[Ykaar]

Hello doublebogey,

I just sent my unit back because of this issue (but I have not upgraded the 3.2 ...). Let me know if you find a fix on this, the skytrak support could be interested.

[doublebogey]

Thanks Ykaar. Would be interested to hear what SkyTrak support tells you what was wrong w the unit you've sent back (connection issue, laser issue, etc.)? Of course will post back if I ever figure out what the problem is and if able to find a fix for this. Would also love SkyTrak_Seth to be able to chime in on this w his thoughts on what the problem might be. Thanks.

[Ykaar]

I will let you know what they figure out for my unit. They made me a lot of test before sending it back to them. But I am confident that is not related to the update because I stayed in 3.1.

I show the same prob than you here but they asked me to test in lefty mode (which is working good ...)

Right mode KO

https://www.youtube.com/watch?time_continue=7&v=zJuoGjlnEY0

Left mode OK

https://www.youtube.com/watch?v=yyUmBv6PdH8

[doublebogey]

Interesting it works left-handed but not right-handed... I will give that a test too.

[JB3]

A few things:

1) Thank you all for the helpful feedback!!

2) I hear you on the tracers, I will have them thickened up a bit for the next release.

3) The reason 64-bit will not work on some of your computers is because it is missing Visual C++ Redistributable for Visual Studio 2012. I will include that in the installer and have them update the website. But for now, you can download it here: https://www.microsoft.com/en-us/down....aspx?id=30679

4) Assuming the bottom of the unit is level with the hitting surface, the ball should go directly on the laser dot for 90% of users. High ball speed players can move it to the right a tad, shorter/pitch shots can move to the left a tad. But you should never change back and forth in distance away from the unit.

I agree to for the ability to have your custom tracer thickness. I love the thin lines but i have a impact screen and projector, I am sure I would feel the other way is I was looking on my iPad or phone. Maybe they could just keep it simple and have a toggle from thick or thin.

[wjf67]

SkyTrak_Seth Great thread - very helpful. It is great that you continue to develop the product. I am just about to update my hitting area and move from using a monitor only to adding the impact screen. Is it possible to have a dual screen functiin, with the impact screen showing the shot and the monitor showing the data screen?

[SkyTrak_Seth]

Yep, will be looking at that!

[Greasegun]

Another update, another 6 hours trying to get skytrak working again. And to top it off the new addition isnt even available in practice mode. Like im going to spend another $200 per year on a device that only works sometimes after I already paid 2k for the thing to begin with. Skygolf business model = we have thier money so who cares. I have spent more time trying to get my skytrak connected to my pc than I have spent using it. If something is still in Beta testing they shouldnt sell it for 2k.

[HappyGilmore102]

Greasegun

Skytrak may not be for you, sell it, and get a used GC2.

My SKytrak works perfectly, all the time, everytime.

Good luck!

[Greasegun]

Maybe you got lucky or I got unlucky. Either way its the first and last skygolf product ill purchase.

[LWGoffa1]

Hi Seth,
Finally found time to install 32-bit v3.2 on my Win10 laptop without issues related to OS errors, etc. Due to time constraints with my job and a baby on the way SkyTrak is my only option for golf. It goes without saying I really want it to work flawlessly like most of other members' SkyTraks. Below is a summary of my observation and feedback:

1. Win10 laptop
- Direct mode
- Battery was at 85% (full charge after 2 days still only show that much btw).
- Hit 19 shots with 9i without issues.
- 20th shot was a misread, then the unit went into RRG state for a full minute before I cycled off/on.
- Second session I was able to hit 3 shots and then device went into RRG state again. Waited for 2+ minutes but it wouldn't connect to laptop.
- Disconnected laptop and proceeded to use iPhone 7.

2. iPhone 7
- Direct mode.
- Battery was at 65%.
- Used same club to hit 170+ shots with just 2 misreads.
- Unit went into RRG state after about 1.5 hours since switching to iPhone 7. Total uptime ~2.5hrs.
- Cycled off/on and managed to hit another 15 shots before battery depleted to 5%.

Positives:
Graphic improvements over v3.0.2 and other features are A+. Keep up the good work and continual support
I particularly like the swing speed estimates and shot height. The former appears to be more inline with my real world swing speed. At some point I will try it with my SSR to see the variations. I'm cognizant of the SSR's limitations but I know it's consistent with my measured SS.

Negatives:
Instabilities with the noreads and RRG state continues to persist from v3.1.
This is a problematic issue because my Win7 laptop (v3.0.2) and iPhone (v3.1) do not exhibit similar issues at all from misread and RRG state average. Note that I purposely did not upgrade iPhone to version 3.2 so I can have a stable baseline of v3.1+ train to compare.

If it warrants I may uninstall v3.2 from Win10 laptop and install v3.0.2 that I still keep a copy of. I do not want to install v3.1/v3.2 on my 6yr old Win7 laptop because it lags significantly.

Thanks,
LWG