Laser "on" for next shot - bigger delay in V2.2

[awisnia]

SkyTrak has said the delay for next shot is the same as before, except the laser light has now been synchronized to come on at the moment the app is ready for the next set of data from the ST..

Maybe technically "the same", BUT....before the user was able to place a ball on the dot, address, waggle, etc during the "ball roll-out" delay..then hit.

I was really used to hitting, waiting, glancing at my shot shape and then placing a next ball long before the ball had finished rolling out in the sim screen. ( I user the range a bunch)

I suppose that sometimes in an angry rush I'd get a missed-read, but not typically.

Now it seems like forever to wait for the laser to come back on, just to place my ball. (I was actually thinking of putting a sharpie spot on my mat to get things moving again.)

I guess from an engineering standpoint, it might seem clean to leave laser off until the app is ready again, but you've already got a long enough delay to process the images before the sim display.

If the discussion ever comes up again - and it doesn't break anything else - I would vote for the following in order:

1. SOLID laser indicates ready to hit, BLINKING laser indicates shot accepted--processing. (but go ahead and place/address the ball for the next shot)

2. Like it was before V2.2


Obviously too many engineers on the forum!

[ForeLeft]

I totally agree with this. I would like the laser to come as early as possible, else I am waiting to put the ball down. That way we can get the ball there and then wait 30 seconds over the ball to hit he next shot Joking aside, it would be very useful and speed up play if we can get the dot there, as it does take few seconds after you place the ball and hit it.

[N54TT]

I agree with this as well. It even takes a couple seconds after the ball stops rolling before the laser comes back on. I used to place the ball as I'm watching the ball flight and looking at the numbers...then I just set up to the ball and go. Helps to minimize the delay between shots.

I like the way it was before and understand why they might have changed it..to prevent miss reads for those that are hitting before the ball even stops rolling.

Seth: can we get the laser to come back on like before and just add an indicator on the screen that signals when it's ready to read the next shot?

[SkyTrak_Seth]

I completely get where you guys are coming from. Actually, the reason for the change was to make sure there was no cross-over/confusion between the app and the hardware. Each have a different point in time where you are able to hit your next shot. This is part 1 of 2 of the "why isn't my skytrak triggering?" To put it very simply, now we just use the top light/laser to tell you when the coast is clear...unfortunately with a bit of a delay as to when the laser comes on (although not a delay as to when you can actually hit your next shot - make sense?)

So I'll look into it for a future update. Right now, stability and capture consistency trumped the delay on the laser.

[awisnia]

Thanks..my assumption was always that the ST was faster than the app - taking its photos, passing them off, and then returning to a ready state. I assumed that the misreads were the result of the app not being ready for the next set of photos in most cases.

in V2.2, is the ST waiting for the app to completely finish and get the *listening* state before relighting the laser?

If so, I'll repeat my suggestion for a blinking laser when the app or ST is not ready to accept a shot - and a solid beam when everything is a go. The top light could do the same.

cheers

[Jimsol]

I am having issues with the laser being ready even when it shows on the mat. I can hit, laser goes off comes back on I hit again and it doesn't register. I hit again it does register second attempt. Seem like every other registered. Today I'm going to start skylark and try it agin in direct mode to see if I get the same issue. Not sure yet if it's the device or the software, but getting frustrated.

[Jimsol]

I havent noticed a to big of a delay as much as I notice that even when the laser is shown as ready I can hit and it doesnt register, I need to wait and hit again then it registers. not sure why. I didnt notice this as being as big of a issue in the 2.1 release.