no live intervals or any information on other cars on track is in the data coming from the game.Does telemetry give live intervals ? Annoyed it still not implemented in VR. So would it be technically possible to use text to speech every lap or every minute for intervals to leader / front and behind ?
There are several car data lists online, like this and this.Hi,
as in gt7dashboard is a carID used (and a car csv with the name of each car), I would like to have the weight of the car (for each carID).
Is a list of all car weights somewhere available ?
Does someone know ?
Wow, this is intriguing.CoachDave released telemetry for gt7 with subscription plan $4.99 / month or $49.00 / year
Delta for Gran Turismo 7 - Coach Dave Academy
The first ever tool that gives you the ability to analyse your GT7 data in extreme detail, giving you the opportunity to gain lap time like never before.coachdaveacademy.com
I watched his demo video, the app looks pretty good. Nothing revolutionary, just very well made and integrated.CoachDave released telemetry for gt7 with subscription plan $4.99 / month or $49.00 / year
Delta for Gran Turismo 7 - Coach Dave Academy
The first ever tool that gives you the ability to analyse your GT7 data in extreme detail, giving you the opportunity to gain lap time like never before.coachdaveacademy.com
Agree with the "first-ever", but there is for sure a lot of work done presentation-wise. But indeed there has been tools like this available for GT7 for a while now – in various levels of complexity and data analysis.I'm pretty confident that Delta simply takes the output of https://github.com/vthinsel/GT7Proxy and displays it in a pretty page.
Being labeled as a "first-ever-tool" is pretty misleading if not disregarding any of the existing prior work. I don't have access to the files but hopefully someone can confirm this.
There is no tyre pressure in gt7 from what Kaz said in some interview ;d Maybe its some kind of interpolation based on tyre temps if that even make sense.Agree with the "first-ever", but there is for sure a lot of work done presentation-wise. But indeed there has been tools like this available for GT7 for a while now – in various levels of complexity and data analysis.
One thing I was wondering about though; it says "Tyre pressures", but AFAIK we never found anything related to that in the telemetry data, right? It's possible of course that it hides somewhere in the undocumented data fields, but I would think we'd have found that by now if it did.
With regard to my own work (EzioDash included), I've been doing most of the "unique features" in various tests, like track detection, track maps, sector times, stint tracking and so on – as have others. But hey, if it helps anyone and you want to part with $49/year, I'd say go for it! 😄
Kinda sounds more like they forgot to remove that line, and it's a remainder from some other game like ACC or something. If they try to interpolate, I would seriously not trust the data too much 😂There is no tyre pressure in gt7 from what Kaz said in some interview ;d Maybe its some kind of interpolation based on tyre temps if that even make sense.
Our tech is completely custom built, we don't use any open source tools or listeners. We've done this so that we can 1) control the entire flow and 2) it gives us flexibility on features.I'm pretty confident that Delta simply takes the output of https://github.com/vthinsel/GT7Proxy and displays it in a pretty page.
Being labeled as a "first-ever-tool" is pretty misleading if not disregarding any of the existing prior work. I don't have access to the files but hopefully someone can confirm this.
Does that mean that you are not using the telemetry from the game by talking to ports 33739 and 33740?Our tech is completely custom built, we don't use any open source tools or listeners. We've done this so that we can 1) control the entire flow and 2) it gives us flexibility on features.
Coach Dave has a team of full time developers working on Delta across multiple sim racing titles. All of it custom built from the ground up.
We use those ports but interpret the data with our own custom code.Does that mean that you are not using the telemetry from the game by talking to ports 33739 and 33740?
That unfortunately doesn't appear to be quite correct:Our tech is completely custom built, we don't use any open source tools or listeners.
You're under no obligation to choose a license. However, without a license, the default copyright laws apply, meaning that you retain all rights to your source code and no one may reproduce, distribute, or create derivative works from your work.
Hey, lead dev on Delta here to address your concern.That unfortunately doesn't appear to be quite correct:
View attachment 1387024
gt7-dash/server at d77c32d323a09dcedb762525e61f60029c3320ab · santiDotIO/gt7-dash
Contribute to santiDotIO/gt7-dash development by creating an account on GitHub.github.com
This repository appears to not have any license at all, and as per github:
binary-parser
over the binary data to handle reading the packets into a workable format (JSON) - I'd rather use that than do it manually like we do in iRacing for example. It's quite common to use. We do the exact same thing for our rf2/LMU support if you wish to take a look as you're diving into our code as we speak.I think there is one thing that is not well understood and should be well separated - understanding a mechanism/algorithm (whether it is Salsa20, or the simulator interface as a whole, or really, anything else) from a reference implementation which in this case is gt7-dash.Hey, lead dev on Delta here to address your concern.
Salsa20 is a cipher, and a well documented one, it's is the only way to read the data from the game and not patented (just like the one you have in your PDTools repository actually! https://github.com/Nenkai/PDTools/b...7322e185679f38f/PDTools.Crypto/Salsa20.cs#L26).
Also, the parser is just a tiny file usingbinary-parser
over the binary data to handle reading the packets into a workable format (JSON) - I'd rather use that than do it manually like we do in iRacing for example. It's quite common to use. We do the exact same thing for our rf2/LMU support if you wish to take a look as you're diving into our code as we speak.
Happy to answer any other questions or concerns you have. To clarify, outside of literally just grabbing the data from the UDP socket, which can only be done one way, we've written everything from scratch. How we handle connections, how we track the game state, that's all proprietary and our IP. During research phase we investigated what other things were on the market, and none were doing what we needed, hence a complete from-the-bottom build.
Absolutely - if it wasn't for what's available right now, it would be a lot more difficult to figure out how to get data from the game - but that's not even 10% of the difficulty. Trust me we know! It was excruciating and time consuming to create what we have in Delta. For example how do you detect pit stops in all of the game modes in Gran Turismo 7, how do you get sector times, how do you tell what track you're on, how do you tell if you're in time trial vs a series of championship races, and how do you get all this without having to ask the user for an IP address? I couldn't find anything on those topics at all.I think there is one thing that is not well understood and should be well separated - understanding a mechanism/algorithm (whether it is Salsa20, or the simulator interface as a whole, or really, anything else) from a reference implementation which in this case is gt7-dash.
It is fair game to learn how it all works from existing projects, I mean, I wouldn't expect anyone to "just" figure out the decryption process, but copying implementations and source files (i've checked) from existing projects essentially turns this into a derivative.
Technically you don't have any rights to use any sort of code from gt7-dash, only viewing. Seeing as the repository is not licensed at all, I suggest reaching out to the author as for the licensing status, or alternatively, just implement it your own way.
More information here.
Literally 3 pages back: https://www.gtplanet.net/forum/threads/overview-of-gt7-telemetry-software.418011/post-14044980And how do you get all this without having to ask the user for an IP address? I couldn't find anything on those topics at all.
No, it’s unfortunately not possible. At least it’s not info that is in the telemetry.Quick question for you guys. Is it possible to see the data from other drivers in online races/lobbies? Seeing that gtws shows data for tyres, tyre usage and fuel consumption, I was wondering if this is accessible via telemetry. Thanks
Thanks for the clarification.No, it’s unfortunately not possible. At least it’s not info that is in the telemetry.
There are ways to achieve similar things, but not publicly available on normal PSN accounts. There are some things only PD can access. At least in a usable manner.
I think I can answer this pretty simply with: don’t trust the replays for minute details. I don’t know exactly why it’s not a one to one replay, but it could be that they average out values and interpolate them when replaying. I do know, as you mention, that they differ.@snimat: I just run accros you gt7dashboard and it looks very cool. Great stuff putting it togheter from both the backend and frontend side.
May I ask a question about how to use it in a specific usercase?
I have manually created a Json copy/pasting my best lap recorded live against Tidge lap recorded via replay.
The resultant Json file is well bigested by your app.
Now, taking Turn1 as example:
I see he is braking later
View attachment 1393348
and this is also confirmed by the brake graph
View attachment 1393349
but I also read somewhere that replay runs show some sort of delayed/filtered patterns for the braking.
Is this the case for your app?
Does this json created by me make sense, or should I create one with Tigd and mine lap both recorded as replay?
Thanks