Shot delay 4-5 seconss

[philipgabriel@gmx.com]

Hello,
I ve got a shot delay of 4-5 seconds.
I read much about it.
I ve got a new i7 2.6 ghz notebook.
After the shot the cpu goes uo for about 4 seconds.
My question:
If i buy a bug server cpu with 4 ghz.
Could i reduce the shot time?

Which mode is the best? Usb or wifi direct/network mode. I can see any differences.

Best regards
Philip

Sent from my SM-G930F using Tapatalk

[Shardak]

You may reduce it a little bit, but not much.

USB/Wifi makes no difference in shot delay based on my testing. (Vid here of testing usb vs wifi: https://www.youtube.com/watch?v=_ppTlCMT5TE)

[philipgabriel@gmx.com]

In two days i get a new pc with an intel i7 4x4ghz with turbo 4x4.4ghz.
I will report if the delay is getting shorter

Sent from my SM-G930F using Tapatalk

[philipgabriel@gmx.com]

Nearly the same delay :-/
No noticable difference

[Shardak]

Sorry to hear that. Thanks for confirming it though.

[Lawyer]

Seems the key is the usb 3.0 connection and not the pc speed. I am asking if the unit comes already with a 3.0 usb port or must be placed an adaptor (if possible)

[Shardak]

Seems the key is the usb 3.0 connection and not the pc speed. I am asking if the unit comes already with a 3.0 usb port or must be placed an adaptor (if possible)

Its a USB 2 device, so plugging it into a USB 3 port will make no difference.

Maybe Seth can confirm, but I think I have seen him confirm this in the past.

[Lawyer]

Its a USB 2 device, so plugging it into a USB 3 port will make no difference.

Maybe Seth can confirm, but I think I have seen him confirm this in the past.

Very bad it's a usb 2 device. At this point I ask how many have connected it to a usb 3.0 and have a delay of just 1 second. If I remember well it was YonexMan and one other folk

[philipgabriel@gmx.com]

USB is not the problem.
If you are connected via USB or WIFI (doesnt really matter) and make a hit, the skytrak unit needs about 0,5 second to send the pictures made to the PC.
After delivery the PC calculates all the parameters (Skytrak Interface do this job) and the duration for this job is about 3-5 seconds, depending on your CPU power.
If the job is done, TGC needs no additional time to show the ball flying in the game.
The apple ipad is really faster. i guess the code for apple is better than for windows, because my windows PC is much faster than my apple device.

[Lawyer]

I really don't understand, many are using very fast computers without success. They say the delay looks is always the same also with last generation pc

[aeroburner]

Skytrak is skytrak there is a 3 to 4 second delay no matter what method you try to improve it will still be a 3 to 4 second delay, i have owned one for over a year now and can run it through every different method and it will be the same delay.

[SkyTrak_Seth]

Just to clear this up, it's not the transfer of data that takes the time - it's the image processing on the computer/iPad before we can fly the ball. So USB 3.0 wouldn't really make any difference. There are checks and rechecks in place for accuracy, hence why we can't just be instantaneous.

[TorchRedRob]

I think it would be really neat (if even possible) to start a ball earlier while the other checks are still going on, based on the "highly-probable" data (such as launch angles and ball speed, for example), and then adjust mid flight based on verified spin data. For example, guess a spin based on other parameters and launch the ball at maybe 1-1.5 seconds, then 1.5-2 seconds later, interpolate the difference between the first calculated path and the verified path and gradually adjust the flight path to actual during flight. This could be an option that you could turn on or off. If you then performed a replay, it would use only the verified (second set of data) flight path only.

Not sure if that's possible given the way the software is currently set up, but that would be something that I would like to see. I may be wrong on what the "highly-probable" parameters are, but I think something like this would be neat. The delay is the only thing I don't like about SkyTrak at this point. (I know, I know... beggars, choosers, etc.)

[Shardak]

I think it would be really neat (if even possible) to start a ball earlier while the other checks are still going on, based on the "highly-probable" data (such as launch angles and ball speed, for example), and then adjust mid flight based on verified spin data. For example, guess a spin based on other parameters and launch the ball at maybe 1-1.5 seconds, then 1.5-2 seconds later, interpolate the difference between the first calculated path and the verified path and gradually adjust the flight path to actual during flight. This could be an option that you could turn on or off. If you then performed a replay, it would use only the verified (second set of data) flight path only.

Not sure if that's possible given the way the software is currently set up, but that would be something that I would like to see. I may be wrong on what the "highly-probable" parameters are, but I think something like this would be neat. The delay is the only thing I don't like about SkyTrak at this point. (I know, I know... beggars, choosers, etc.)

I think that solution would be more complex than the best option..which is to just make it faster to begin with!


Hopefully Skytrak 2 comes out, with the processing all inside the unit, based on some relatively inexpensive chipset specialized for image (and hopefully radar!) processing. I can hope anyway...

[FaultyClubs]

It's a great idea Torch. The Foresight fsx software has this feature. It's called "wait for spin" or something like that.