Misc Telemetry Tool for F1 24 (and many other games) 14.2

[Iko Rein]

hey mat its me again,
unfortunately this problem is still existing after load mid session save, program lost track and show like this ( redbul ring is driving but program show melbourne) and didnt save a data from lap View attachment 770141View attachment 770140

The issue is with the mid session load. It is like joining halfway the race with no history; All information and data prior the save-point is lost. And then some data, like the track information might come or might not, also the game state might not update correctly. I can check if something can be done to mitigate biggest issues.

The Tool has some checks to avoid saving bad data or wrong data, and starting halfway into lap is one of the reasons for not saving a lap.

Cheers

 

[jeri19]

also loading file in multi lap telemetry is not correct I loaded 4 lap from different stints and it merge in one, on screen show it like the same data , also in statistics table

 

[jeri19]

The issue is with the mid session load. It is like joining halfway the race with no history; All information and data prior the save-point is lost. And then some data, like the track information might come or might not, also the game state might not update correctly. I can check if something can be done to mitigate biggest issues.

The Tool has some checks to avoid saving bad data or wrong data, and starting halfway into lap is one of the reasons for not saving a lap.

Cheers

there is a chance that program can save this data ( in option to choose ) ?

 

[Iko Rein]

there is a chance that program can save this data ( in option to choose ) ?

Sadly no. There is the racehistory, which could maybe be used to reconstruct the general racehistory, but all the other details will be gone.
Cheers

 

[jeri19]

hey mate,
there is still a problem with the file when driver turning back to box when crossing a finish line. now saves data but also save out lap in the same lap. like on screen

Yeah,

In TT/Quali when you do restarts/lap restarts/flying back to pits/flying laps, the raceInfo/TTInfo data might not have the exact proper data. I will do bit more testing on the latest F1 24 to see, if I can mitigate the issues. I think still the actual lapdata files are saved even for some odd situations. I will also check that if something has changed on the latest F1 24 version.

Cheers.

 

[Arik Zillhardt]

Does someone here has experience with ACC and the relay? I want to get the telemetry from someone else, any Idea how I can do that? Just giving my IP and put it somewhere or what? Never used relay before so any help appreciated

 

[Arik Zillhardt]

Am I the only one experiencing that the Outlap in F1 Short Qualifyings are not getting deleted? The first one get's deleted but when doing the 2nd or 3rd Run, it shows that it's getting deleted but when opening the file it's still there and interfiering with the data

 

[Arik Zillhardt]

+ when importing a Lap into Multilap Telemetry it just imports multiple Laps at the same time so you can't use the Load Laps feature at all because it's just 100 Grpahs at the same time @Iko Rein

 

[Iko Rein]

also loading file in multi lap telemetry is not correct I loaded 4 lap from different stints and it merge in one, on screen show it like the same data , also in statistics table

View attachment 770299View attachment 770300View attachment 770301View attachment 770302View attachment 770303View attachment 770304

This will be fixed in the next version.

Current plan is to make it, when AMS2 1.6 version is released.

Cheers.

 

[Iko Rein]

Does someone here has experience with ACC and the relay? I want to get the telemetry from someone else, any Idea how I can do that? Just giving my IP and put it somewhere or what? Never used relay before so any help appreciated

With ACC the things depends bit what you want to do.

If you just want to collect data, then you can use just the UDP redirect.

If you have "flaky connection" or you might join later, below is the setup few of my users are using with ACC.

=====================
ACC Driver/Engineer setup for active engineering

In short, the driver uses the relay to send the SHMEM data to the engineer and the engineer uses ACC Broadcasting system to get the data for all drivers etc. from driver's ACC.

It is best to use some VPN tunneling software to make the connection between the driver and the engineer. Make sure the tunnel works. Here I assume the DRIVER_IP (driver's IP address in the vpn tunnel) and ENGINEER_IP (Engineer's IP address in the vpn tunnel) are known, i.e. the connection has been tested and it works.

### ON THE DRIVER SIDE ###
1) The driver should install the Telemetry tool and make sure, it works with ACC, i.e. there is e.g the driver names in the MAP.
2) Driver makes separate 'ACC relay' copy, e.g. by copying the acc_relay directory to acc_relay_to_engineer
3) Driver then copies the relay_settings.ini from %appdata%\ACC_SharedMemory_relay to the directory created in 2).
4) Driver edits the copied relay_settings.ini and sets the IP to be ENGINEER_IP in the VPN tunnel.
5) Driver creates a shortcut to the new acc_relay_to_engineer\ACC_SharedMemory_Relay_x64

### ON THE ENGINEER SIDE ###
1) Setup Telemetry Tool and make sure it works.
2) Get the ACC Broadcast settings (Port + Passwords) from the Driver Edit the 'ACC Settings' and set the values there + set as "Remote IP" the DRIVER_IP.
3) IF you do engineering for many drivers, you could create directories e.g. like C:\tt\joe, C:\tt\ben and then make a shortcut of the Telemetry Tool, which sets one of these directories as the 'working director'.

### PROCESS TO GET THE DATA GOING ###
1) Start the tunneling on both ends
2) The drivers starts the acc_relay_to_engineer
3) Driver start ACC
4) The Engineer starts the Telemetry Tool (You can press CTRL-M to see messages, which IP the Tool is using to request Broadcast connection).
==> If tunnel is up and correctly setup, the Engineer should see the data.
##############

This way the driver will no collect their own data, but they could run Telemetry Tool on the side, as it would not interfere with the "driver-to-engineer" setup.

Cheers.

 

[jeri19]

i see the issue that file for every quali (except first) is broken, even if driver go proper in lap. there is a chance to repair it ?

 

[Iko Rein]

i see the issue that file for every quali (except first) is broken, even if driver go proper in lap. there is a chance to repair it ?

Fixed for the upcoming 14.3 version.

I am waiting for the AMS2 1.6 to come out for the release of the new version.

Cheers.

 

[Chrismpy]

With ACC the things depends bit what you want to do.

If you just want to collect data, then you can use just the UDP redirect.

If you have "flaky connection" or you might join later, below is the setup few of my users are using with ACC.

=====================
ACC Driver/Engineer setup for active engineering

In short, the driver uses the relay to send the SHMEM data to the engineer and the engineer uses ACC Broadcasting system to get the data for all drivers etc. from driver's ACC.

It is best to use some VPN tunneling software to make the connection between the driver and the engineer. Make sure the tunnel works. Here I assume the DRIVER_IP (driver's IP address in the vpn tunnel) and ENGINEER_IP (Engineer's IP address in the vpn tunnel) are known, i.e. the connection has been tested and it works.

### ON THE DRIVER SIDE ###
1) The driver should install the Telemetry tool and make sure, it works with ACC, i.e. there is e.g the driver names in the MAP.
2) Driver makes separate 'ACC relay' copy, e.g. by copying the acc_relay directory to acc_relay_to_engineer
3) Driver then copies the relay_settings.ini from %appdata%\ACC_SharedMemory_relay to the directory created in 2).
4) Driver edits the copied relay_settings.ini and sets the IP to be ENGINEER_IP in the VPN tunnel.
5) Driver creates a shortcut to the new acc_relay_to_engineer\ACC_SharedMemory_Relay_x64

### ON THE ENGINEER SIDE ###
1) Setup Telemetry Tool and make sure it works.
2) Get the ACC Broadcast settings (Port + Passwords) from the Driver Edit the 'ACC Settings' and set the values there + set as "Remote IP" the DRIVER_IP.
3) IF you do engineering for many drivers, you could create directories e.g. like C:\tt\joe, C:\tt\ben and then make a shortcut of the Telemetry Tool, which sets one of these directories as the 'working director'.

### PROCESS TO GET THE DATA GOING ###
1) Start the tunneling on both ends
2) The drivers starts the acc_relay_to_engineer
3) Driver start ACC
4) The Engineer starts the Telemetry Tool (You can press CTRL-M to see messages, which IP the Tool is using to request Broadcast connection).
==> If tunnel is up and correctly setup, the Engineer should see the data.
##############

This way the driver will no collect their own data, but they could run Telemetry Tool on the side, as it would not interfere with the "driver-to-engineer" setup.

Cheers.

How would this be done for Assetto Corsa?

Edit

I figured it out!

 

[****AssettoCorsa****]

https://imgur.com/izpJhXJ

Is there any way to fix this error for WRC? the directory does exist.

 

[Iko Rein]

https://imgur.com/izpJhXJ

Is there any way to fix this error for WRC? the directory does exist.

Hello,

So you have to have the directory
<userhome>\Documents\My Games\WRC\telemetry
in your system. This gets created automatically by the EA WRC game, when you start that game.

If the directory exists, then the Tool will copy from <telemetry tool install directory>\bin\wrc the tt_feed.json to that directory.

The error you see, comes when the <userhome>\Documents\My Games\WRC\telemetry\ directory does not exist.

If for some reason the WRC game does not create the directories, you can do the following via File Explorer
0) Stop EA WRC + Telemetry Tool
1) Create the <userHome>\Documents\My Games\WRC\telemetry\udp
directory
2) Copy from the file tt_feed.json from the Telemetry Tool's install's directory bin\wrc to the directory created at 1)
3) Now start the Tool in WRC mode and it should start ok.
4) if 3) was success, start the EA WRC

Cheers.

 

[****AssettoCorsa****]

Hello,

So you have to have the directory
<userhome>\Documents\My Games\WRC\telemetry
in your system. This gets created automatically by the EA WRC game, when you start that game.

If the directory exists, then the Tool will copy from <telemetry tool install directory>\bin\wrc the tt_feed.json to that directory.

The error you see, comes when the <userhome>\Documents\My Games\WRC\telemetry\ directory does not exist.

If for some reason the WRC game does not create the directories, you can do the following via File Explorer
0) Stop EA WRC + Telemetry Tool
1) Create the <userHome>\Documents\My Games\WRC\telemetry\udp
directory
2) Copy from the file tt_feed.json from the Telemetry Tool's install's directory bin\wrc to the directory created at 1)
3) Now start the Tool in WRC mode and it should start ok.
4) if 3) was success, start the EA WRC

Cheers.

I figured it out with your help, I keep the Documents folder on my D drive so this doesn't exist "<userhome>\Documents\My Games\WRC\telemetry" so I just created a new Documents folder there and copied the WRC folder there, thanks.

 

[Iko Rein]

I figured it out with your help, I keep the Documents folder on my D drive so this doesn't exist "<userhome>\Documents\My Games\WRC\telemetry" so I just created a new Documents folder there and copied the WRC folder there, thanks.

Good to hear. I rely on the '<user home>' data to find out, if there is the telemetry/udp directory. I will check, if I can add some extra checks, if the Documents is not at C-drive.

There are some new extra EA WRC trackmaps at

Telemetry Tool - Addons

I will do the base maps for Latvia/Poland bit later.

The tool will automatically create trackmaps for those tracks, which you drive. Those maps are based on the fastest lap's trace.

Cheers.

 

[okn1]

Hello!
Great tool, thanks! I would really like to use it for LFS. Is it difficult? Maybe there is some way?

 

[xanderale54]

Hi there,

I've used the tool and been super impressed in the past, and recently moved to a new PC on Windows 11 and have found that the program doesn't work when I try to run it - I suspected it was to do with the firewall as you mentioned further up the thread but I've allowed all the Java executables through the Windows control panel to no success. The launcher launches, and the feed tester also works, but the telemetry tool itself does not open - could I have some help with getting it going again? Not sure if I'm missing something obvious

(using for F1 24, AC, and ACC)

Thanks

 

[Iko Rein]

Hello!
Great tool, thanks! I would really like to use it for LFS. Is it difficult? Maybe there is some way?

I think LFS is bit out of scope as it is pretty old game.

I used to provide data in F1Perfview format, but that was quite a lot of versions ago. I could still quite easily add back the option to read F1Perfview files, but that would still be offline usage, and not real-time usage.

I saw that LFS provides some server solution. If someone would write a "plugin" to e.g. send data out in F1 2016 or even F1 2017 format, then I could work bit to make the tool use that format with LFS.

Cheers.