Telemetry SecondMonitor (Timing & status App)

Ams and rrre use shared memory to share data, and multiple apps can read from it at once.

But only one app can listen at an port and receive the udp data F1 games share.

Simhub has a handy feature where it can receive the data and resend them to other ports. I use that, so I can have simhub, fanalabs and my app having access to the data.

 

Thank you, I'll try that Simhub feature and see if it solves this.

 

I'm having trouble understanding this and getting it to work - so do I set the F1 2024 UDP port to 20778 in Second Monitor and then in Simhub, forward UDP data to 20778 ?
Thanks

 

Never mind I've finally done it! It was made very difficult by the nut behind the steering wheel (me).
After trying multiple combinations, there was no need to change anything other than the port in my Asetek Racehub software, and it now works fine.
Thanks for your help.

 

Glad you got it sorted, and it works

 

Hello
A crash on LMU

Nom de l'application défaillante : SecondMonitor.exe, version : 9.30.1.2757, horodatage : 0x67110000
Nom du module défaillant : KERNELBASE.dll, version : 10.0.26100.3470, horodatage : 0xcdfc8fa1
Exception code: 0xe0434352
Fault offset: 0x00000000000cab6a
Identifiant du processus défaillant : 0x4558
Heure de début de l'application défaillante : 0x1DB9CB924A464EE
Chemin de l'application défaillante : C:\Program Files (x86)\SecondMonitor\SecondMonitor.exe
Chemin du module défaillant : C:\WINDOWS\System32\KERNELBASE.dll
ID du rapport : a743ec98-9949-49f7-8dcb-701a6fad4188
Nom complet du package défaillant :
Package défaillant – ID d'application relatif :

 

Hi
Thanks for the report, hopefuly todays update will improve the situation

 

Is there a setting available so that SecondMonitor remembers a laprecord when it's set on the first lap? Noiw it starts saving after the first hotlap, not the first one driven.

 

There isn't a setting, sounds more like a bug. I need to check why it doesn't remember first hot lap. This is in raceroom right?

 

Yep, it's in Raceroom.

 

Hi,I'm getting an issue with the latest version,
When opening the settings and I try to drag and drop a new column for the race tab the app just freeze and crashes,any chance this could be looked at please?

 

Ok so last update fixed my crashing issue .
Just wanted to ask if it would be possible to implement a function where I'll be able to see the current AI fuel for the session I'm in for assetto corsa or Is that function already in the app?
Thanks

 

As always, thank you for your continued work on this app!

On LMU, would it be possible for the data for the average Virtual Energy per lap to be added to the race results exported spreadsheet (like fuel per lap / per min does currently)?

 

Hey, just found this project and I like it a lot, keep it up!
Just asking: Is F1 25 support planned? I dont know how active it is

 

Planned in todo list.
Also the plan is to have virtual energy available on the timing grid of all cars (as it is available on the ingame ui).

Depends... I can only implement support for games I own... so it depends how the general opinion will be on F1 25 after a week or two. If people still think it is good, I will buy it ( as I planned with F1 24, but that didn't turned out that good ). How fast the support will come depends on how busy IRL is.

 

Are there possibilities to lower the rate at secondmonitor is polling :6397 for LMU? What rate is it now?
Im aware of issues.

The rest api of LMU has been refactored, from Java to native C.

 

Currently it is each 16ms, from user point of view it is not possible to change the pooling rate...

But honestly, now that I think about it, I will lower it next update, as there really isn't any good reason to pool it as often as i.e. telemetry data... as the info retrieved from there is fairly static (fuel states + tyre names).

 

Since the update to LMU on Tuesday, I experience frame rate issues when running 2nd monitor.

Edit: See that crew chief have made an update and referenced LMU Rest API changes.

 

I've pushed a new update. I have identified a REST API Call that was causing the stutter (atleast for me). This was required to query some data to check if the sim is in a session and other data can be queried. The API now seems more stable, so it is hopefuly no longer requiried.

The stutter looks to be gone now on my PC, but I haven't had time to test it extensively.

 

Confirmed. Stuttering is gone for me! Working great as usual, can't race without my SM!

Thank you.