Reducing Protee Shot Delay as much as possible.

[Joshua1745]

In order to get the best sim experience, believe reducing shot delay as much as possible is neccessary. Ideally I'd like to get it closer to optishot or the Korean Golfzon arcade simulators.

I have core i7 4ghz and 1070 gtx. Before I had an older motherboard and corei7 processor with only 1 USB 2.0 controller. When I upgraded the motherboard and processor to usb 3 the shot delay significantly decreased. This makes me believe the USB interface is the bottle neck if you have a decent processor and GPU. I'm currently running the 2 cameras on separate USB 2 and 3 controllers and that seems to be better then putting everything on the 1 USB 3.0 controller. Unfortunately, all the protee hardware is USB 2 or worse serial to USB. I'm wondering if adding another USB 3 PCIe card might help get the Shot delay as close to 0 as possible.

[FaultyClubs]

What's your delay now?

Is the residual delay from the hardware to the protee interface , or from the protee interface to tgc launch?

[Joshua1745]

How can this be differentiated? I’ve seen a video where
someone had entered the command line of TGC and entered shot data to illustrate minimal shot delay on TGC’s end.

[ProTee United]

TGC accepts shots data without delay. Delay on ProTee is caused by the cameras (analysis of the data). Delay is about 1 second.

[Joshua1745]

I'm well under a second. Just trying to get it as close to 0 as I can. This makes sense, I know reducing the resolution to 320x240 instead of 640x480 did decrease this. So perhaps overclocking my CPU will make a difference.

[aja]

In an alternate universe you may be able to tweak it enough that your shot shows up before you hit it!

[Joshua1745]

I'm now happy with my shot delay. I think the USB was the bottle neck. USB 2.0 might be fine for 1 camera but not for putting multiple cameras on the system. I've placed both cameras on different USB controllers and kept them at 320x240. Overclocking didn't have any obvious affect as I think any recent processor will handle the job fine especially if its above 3 GHz (if you increase the camera resolution then it might). You can experiment where the source of delay is by turning off your cameras in the interface, which would result in the lowest possible shot delay.

[gene438]

I too run the cameras on separate usb controllers and at 320 x 240. I also am running the latest interface version which cleared up a data analysis error I would get occassionally from the "H" camera. I think I am as close to 0 shot delay as possible....I am very happy with this.....this adds so much to the sim experience and really impresses most visitors when they see my simulator. It's the most common remark I hear....