Differentiating between track configs

[rickwest]

Hey Brad! Hope you are well?!

Great work on this library, it's been really useful as I've been trying to build something similar myself. There doesn't seem to be much information or documentation around the AC UDP telemetry at all, but I stumbled across this after reading some of your old forum posts whilst doing a bit of research and it's been much more helpful that the 'official' documentation!

Anyway, I'm wondering if you know what should be returned for trackConfig from a HandshakerResponse as I'm getting the same value returned for trackName and trackConfig.

To cut a long story short, when consuming the data, I can't differentiate between, for example Brands Hatch GP and Brands Hatch Indy, I just get ks_brands_hatch returned for trackName and trackConfig for both tracks. Am I missing something?

[bradland]

Hi Rick, I’m glad to hear you’re finding it useful! The documentation and support for the UDP API is, indeed, very sparse.

As best I can tell, trackConfig isn’t properly implemented. Just like you, I see only duplication of the trackName value.

After several inquiries, I was left to conclude that Kunos just never got around to addressing it with the third-party they used for the PS4 port. I get the impression that it turned out to be a bit more work than they expected.

I was originally going to build a lap time logger, but the lack of track layout identifier makes that a fruitless effort. Users would have to manually select a layout. I considered using lap time as a heuristic to guess the layout, but some tracks Silverstone) have layouts that will have similar lap times. The other option would be to use coordinate data from the actual telemetry, but... Ooof. No thank you :)

Sorry I can’t be more help, but please let me know if you discover anything in your search for more info.