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

[Iko Rein]

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

Hmm,

I do development on Win10, but I do testing on Win11 laptop and if I recall correctly, I had to do something in the Windows security settings allow the Tool to run. Check your logs on the Windows security, if there is some hints on what is going on.

Is this a new install btw?

If the feedtester works, are you starting it from the Terminal?

You might try the following in Terminal
cd <to the directory where you installed the Tool>
then run in that directory
.\bin\win\bin\java -jar .\Telemetry.jar
This should start the Telemetry Tool (or launcher). When I do this on "new install", I get the Window Security question about allowing public and private networks connections to Java. Might be that you missed that.
And you can try also
.\bin\win\bin\java -cp .\Telemetry.jar apps.Launcher
or
.\bin\win\bin\java -cp .\Telemetry.jar apps.SystemProperties
just to see, if you get any errors to the commandline.

If this does not help, send me PM and we can try some other things.

Cheers.

 

[CRMS]

Hi Iko,
Great work continues. I'm trying to use a controller button to change the tab on a Fanatec Clubsport

V2 steering wheel. It has many buttons and switches but it is difficult to find one that isn't already in use.
In your list there is a Special - but I have no idea what that equates to?? Ad then below that the UPD buttons. I have an up/down rocker that could scroll through the tabs in either direction - wheel button 12/13 and PC 32/34.
Is there anyway to map the Special to a Fanatec/PC wheel button?? Or indeed other buttons??
I found an entry in settings.xml for the tab button.

 

[Iko Rein]

Hi Iko,
Great work continues. I'm trying to use a controller button to change the tab on a Fanatec Clubsport View attachment 796663View attachment 796664V2 steering wheel. It has many buttons and switches but it is difficult to find one that isn't already in use.
In your list there is a Special - but I have no idea what that equates to?? Ad then below that the UPD buttons. I have an up/down rocker that could scroll through the tabs in either direction - wheel button 12/13 and PC 32/34.
Is there anyway to map the Special to a Fanatec/PC wheel button?? Or indeed other buttons??
I found an entry in settings.xml for the tab button.

What I do is that (in F1 games) I map in the game the UDP 12 button to a button in the wheel. You could test the actual button by opening the "raw data" view and at the top there is the corresponding value of the pressed buttons. So you could map the up (or down) rocker to the UDP 12 and then set the UDP 12 in the Tool to be the "tab change button".

In other games, like AC/R3E/rF2/LMU, which don't report the buttons, I use often the 'Brake bias down' option, so when you change brake bias down, the view changes and you can then move brake bias back as it was before. That is a nice workaround. In ACC I have mapped the Racelogic button to also change the view in the Tool.

I could add the brakebias up/down or TC up/down option too to F1 games, but haven't really gotten into that, as the game allows you to map any button in the wheel into the UDP buttons.

Cheers.

 

[okn1]

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.

We have a plugin to translate the lfs data stream into the dirt data stream. But for some reason your program cannot perceive it... Maybe we need to fix something in the data format?.. We will be very grateful for your help. Thanks

 

[Iko Rein]

We have a plugin to translate the lfs data stream into the dirt data stream. But for some reason your program cannot perceive it... Maybe we need to fix something in the data format?.. We will be very grateful for your help. Thanks

Interesting, so the game sends out the data in DR1 format too? There is something already in the tool, which we could test. I will send you PM so we can check, how to get going.

Cheers.

 

[CRMS]

What I do is that (in F1 games) I map in the game the UDP 12 button to a button in the wheel.

Thanks Iko and works a treat. Otherwise, do you know what all those UDP buttons are for? There isn't any info in the F1@23 game or at EA Answers.

 

[Iko Rein]

Thanks Iko and works a treat. Otherwise, do you know what all those UDP buttons are for? There isn't any info in the F1@23 game or at EA Answers.

So the F1 games (since F1 2018) have been able to report the buttons pressed in game. The buttons are reported as a 4-byte Integer, i.e. it can show 4x8=32 different buttons (pressed at the same time) via a bit mask.

The buttons from 1-20 are listed as the normal PS/X-box controller buttons, like CROSS or A etc, but that does not limit, what you can do with them. They are just "names" on the mapping. Then there are buttons 21 - 32, i.e. 12 buttons with no preset "name", the UDP 1 - 12 buttons are used for these.

If you want to e.g. use a custom button box, or your wheel has more than 20 buttons, you can assign an in-game action to these buttons. E.g. if you connect a button in the wheel to 'UDP 1', then when you press the button in the game, the game reports then the associated value. This allows bit more control e.g. Tool developers to make things happen in their tools, or you can in-game bind the 'UDP 1 button' e.g. to 'PIT limiter'.

Cheers.