Could SkyTrak fix the shot delay by releasing ball flight first and populating club data while the ball is in the air?
Thinking through the ST+ / ST MAX shot delay and wondering if there’s a software fix that they could implement.
Camera measured ball data (speed, launch angles, spin) is captured almost instantly at impact. The slow part is the radar measured club data path, face, AoA which needs a settling window to extract clean velocity vectors from RF returns.
But why does the whole shot have to wait on the radar? Ball is in flight for 4-6 seconds on a full shot. Release the ball flight to the sim immediately once camera data is ready, then populate club data a second or two later while the ball is still flying. By the time it lands, you have everything. Perceived latency drops to near zero without sacrificing any data.
The obvious objection: the SDK to GSPro / E6 / TGC sends a single “shot complete” payload, so streaming partial data would mean updating every partner integration.
But that only applies to third-party sims. SkyTrak owns both ends of their native software (Course Play, the practice range). They could ship this in their own app first with no partner coordination needed. It would actually give native SkyTrak software a real reason to exist over GSPro for the first time, fastest shot-to-render in the ecosystem, on the same hardware. Then push it into the SDK later once partners catch up.
Square Omni is camera only (no radar) and feels near instant. ST MAX with a “faster processor” barely moved the needle vs ST+.
Anyone who knows the SkyTrak internals or has built sim integrations, is there a real engineering reason this wouldn’t work in native software at minimum?