TGC Shot delay

[arwin]

Not sure if this is the right section of the forum but....

In all simulators that I've been to, once the ball is struck, the simulator instantly shows the ball in motion.
I noticed in all the videos that I've watched with ST & TGC, there is a delay from when you strike the ball and when you actually see it on the simulator.

From what I read, it's because TGC needs to interpret the data and process the shot and I don't think it's related to ST because I think I also saw it in a GC2 video with TGC.

Is this something that is going to be fixed later on or is this something that we have to live with?

I'm very close to getting a sim setup with the ST and will get TGC once it is released from ST

[neboruchi]

I'm guessing it's something we have to live with. I get a delay with ST and the E6 demo, and I believe there's a delay using the basic ST iOS app and WGT.

[Ryan5508]

E6 delay can be dramatically reduced based of the pc you use. My laptop can take around 30 seconds. My media pc is more like 5-6 seconds.

[mthunt]

I have a GC2. The shot is pretty instant. I think it's under a second. It's not noticeable and seems as fast as anything I've played on. I will say this, a weak Bluetooth or Bluetooth to far from the unit increases that time. My GC2 was a foot from the pc and it was fine. I moved the pc 6 feet away and it was like 3 seconds. When I tested Skytrak with an iPad, it was 6 seconds.

[TorchRedRob]

I'm hoping they can eventually set it up so that it starts to render based on ball speed and launch angles alone, and then adds the spin in while the ball is in flight. I think that is how the GC2 does it (or something like this). I think the algorithm to determine spin is what takes the most time.

You could estimate a spin based on the quickly-calculated launch parameters, and show a flight path based on these numbers. Once you get the spin calculated, you could then interpolate between the current flight path and the spin-based flight path until you are looking at the actual flight path.

I think this would work in theory, since the spin effects don't really start to happen until a little farther downrange anyway. Sure, it wouldn't be a completely accurate flight path, but I bet it would be close.

You could also set this as an option, so you wouldn't have to use it if you didn't want to.

[MrHogan]

I like the delay. It allows me to complete my swing fully without rushing to look up and also gives me a chance to retrieve the sometimes bouncing golf ball pinging around the garage ready for my next shot.
It allows time for me to analyse the shot in my mind first & then process the numbers of the projected shot. I think this encourages more thought into the shots rather than allowing the tendancy to scrape and hit.
I don't know what the delay is in TGC but WGT is a couple of secs and that to me is perfect, I agree 5 or 6 secs might be a drag.

[Jel]

Sorry if I'm out of the loop but does TGC now officially support SkyTrak ?

[goatbarn]

No not yet.

[voodoo_ca]

I dont have a unit - just been watching the videos and reading the threads.
I think the best person to answer the original question is someone (like Skytrak) who understands why the delay happens in the first place.
If the unit is doing calculations, that is less likely to change without a hardware revision/change, if it is the iPad or Computer doing the work and causing a delay... you would think that could be changed by using more "power".

[ks-man]

What I was told when thinking about these was that the GC2 does it's own processing where the Skytrak needed to send the information to the computer to do the calculations. So essentially there was an initial delay which couldn't be overcome of sending the information to the computer and then however long it took for the computer to process and output the information to the software.

[Vincent_Vega]

I dont have a unit - just been watching the videos and reading the threads.
I think the best person to answer the original question is someone (like Skytrak) who understands why the delay happens in the first place.
If the unit is doing calculations, that is less likely to change without a hardware revision/change, if it is the iPad or Computer doing the work and causing a delay... you would think that could be changed by using more "power".

I believe it has more to do with what you're feeding the data to. I have an iPhone 6s plus and the delay is right around 2 seconds. Much quicker than some of the reported times from older iPhones and iPads. Not sure what makes the GC2 display quicker, but it obviously does the calculations on the unit itself.

[aja]

Somehow the agreed to culprit is being left out of this conversation. Other threads have identified the delay as being inherent in how SkyTrak works. The delay is due to Skytrak processing its data before passing it on to the sim software.
TGC is virtually instantaneous when fed by the ProTee sensors.

[keither5150]

I have a GSA simulator and the delay is a second or less. I like having a slight delay. It gives you time to take a look at the screen. 3 seconds or more would seem too long.

[arwin]

I guess my concern would be that if I hit a shot and then it doesn't register and then I go and bang off another shot and then all of a sudden my 1st shot registers.
I guess I'll just have to live with it when I get it!

[Joko]

You can visually look at the SkyTrak and see the top light turn red (off basically) after it's read the shot, then it will turn green after indicating it's ready for another shot.

[neboruchi]

Just to add to my earlier post. The delay I'm getting feels around 3-5 seconds. It doesn't bother me at all. In my setup, I hit into a net and my TV is actually behind me, so it's actually nice to have a few seconds to hold my finish then turn around and see the shot shape. I could see the delay being annoying if I was playing into an impact screen with the simulator displayed on it. In that situation, having to wait 3-5 seconds after every shot might detract from the realism you'd otherwise achieve with the impact screen setup.