Jump to content

LonelyRacer

Members
  • Content Count

    59
  • Joined

  • Last visited

Community Reputation

8 New Car Smell

Gaming Setup

  • Platforms
    Steam
  • Peripherals
    Steering Wheel
  • Steering Wheel
    TS PC-Racer

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. LonelyRacer

    F1 2020 UDP Specification

    ACC has this through the Broadcast API. In ACC there can be many drivers per car. There is EntryListCar, which has car data (racenumber etc) and that has BroadcastDriverInfo[], which has first name, last name, short name, category and nationality. In Project Cars 2/AMS2 there is PacketParticipantsData, which has 3 arrays name[], nationality[], participantMPId[], name is String, 2 others are int16. There is also another struct ParticipantStatsInfo, which has array ParticipantStatsInfo[], which contains the players OnlineRep (has 2 elements, safety & "racecraft") + timing info. The PC2 stucture is bit messy, the ACC model is quite nice. With ACC there are some other issues with their broadcast API, which has some lag/latency issues, i.e. data is not always super up-to-date. Cheers.
  2. LonelyRacer

    Pitcoins Missing | COME HERE

    lonelyf12012racer - steam
  3. LonelyRacer

    F1 2020 UDP Specification

    Hi, I see those names too, i.e. player and "giocatore" (player in Italian), haven't seen yet 'joueur'. My wild guess is that these are PS4 or XBox players. I don't use the lobby packet for anything, as the player order in that packet is different than in any other packets. I was just checking it during the last days to see, if I could use it for something, but to no avail. Cheers.
  4. LonelyRacer

    F1 2020 UDP Specification

    @Hoo Found two issues during testing today 1) The tyreInnerTemperature in CarTelemetry is different, that what is being shown in the MFD. I suspect, that the value is the real inner air temperature, not "carcass" temp, which is shown in MFD. I think with F1 2019 and maybe even with the beta (cannot be sure on that), the tyresInnerTemperature was same as in MFD. Any change for a fix? 2) During Time Trial in F1 2019 the lap data info was sent, which contained e.g. the lap distance and some other info of the ghost. Now in F1 2020 only players data is available, all other data (even the personal best ghost) is just 0's. I hope this is bug and not intentional. It would be great, if at least for the active Ghost there would be the laptime + sector times and the lapdistance per each packet. I used the lapdistance with F1 2019 to show laptime trace for the ghost, so my users could see where they were gaining on the ghost and where they lost time to the ghost. So any change, we could get the ghost's LapData filled with data as it was in F1 2019? Extra: And one request for F1 2021. Any change you could change Sainz driverId to be something else than 0. Would make life easier, if/when we have to do data massage to fix/notice problems in the feed. Edit: The tyreInnerTemperature is ok. Just a note to self, if you change from using direct index number to using special method, it is a good idea to update all locations, where the direct index number was used. ;-.) Fix request: The lapdata for Ghost in Time Trial is still just 0's. Checked and in F1 2018 and f1 2019 the data was there. Would be great, if in addition to the players car, also Personal Best ghost + Active Ghost data would be filled in the PacketLapData in Time Trial. Cheers.
  5. LonelyRacer

    F1 2020 UDP Specification

    Just tested this as I had not noticed anything odd. This is the data I am also getting, the ERS was fixed as per earlier comments. And the DRS distance too is working for me.
  6. LonelyRacer

    F1 2020 UDP Specification

    Did a rerun and actually found out, it was in Sochi on T6, where I had a super crash, i.e. went straight into the wall (was changing the telemetry pages, pressing overtake and changing fuel mix all at the same time ;-)). I guess the RoadSurface id 12 is under the barriers. See the image for the spot. So nothing critical. Cheers.
  7. LonelyRacer

    F1 2020 UDP Specification

    It was on certain section. I can run the data recording to try see, where it was/is. Cheers.
  8. LonelyRacer

    F1 2020 UDP Specification

    It seems to show real driver names, but based on the lobby packet, you cannot tell who is who. Cheers.
  9. LonelyRacer

    F1 2020 UDP Specification

    Hi, I managed to get into some nice 10+ player lobbies. Here are my findings on the Lobby Packet With the lobby packet the "m_frameId" in the PacketHeader doesn't increase, as I was expecting to happen. My tool uses the frame change as trigger to update screen, so I had to make a workaround, i.e. lobby packet also trigger a "frame change" regardless of the header. FIX NEEDED: Would be great, if the frameId would increase with the lobby packet. The lobby packet data order is just "random". The packetHeader in other packets has different playerindex, than with the lobby packet. Still the playerIndex in the LobbyPacket's header isn't correct. So the lobby data is totally useless for anything than showing who are ready or not, but you will see that anyway when you are in the lobby. E.g. FinalClassification comes in the right order, so I am still assuming this is a bug in the lobby packet, i.e. the data order is faulty. Or if in the LobbyInfoData there were driverId, then one could use that to assign the data to the right driver. FIX NEEDED: The order of data in lobbyPacket should be the same as in other packets. Or add DriverId to the LobbyInfoData, Cheers.
  10. LonelyRacer

    F1 2020 UDP Specification

    Great additions. Thanks. One note: I just drove in Sochi and from my tool's log I noticed, there was road surface with id 12. Could you check, if that was a correct detection and if there are other road surfaces added to the data. Cheers
  11. LonelyRacer

    F1 2020 UDP Specification

    @Hoo I have been doing more driving on the weekend, when I noticed the beta was available. While driving and testing two requests came to my mind. In the MFD you see the warning sign, when temps are too low or high or there is some other issue with the car. 1) Any change, you guys could add data for the MFD warning sing, i.e. a uint8 into the Car Telemetry Packet, which would have values 0 (no warning), 1 (tires too cold), 2 (tires too hot), 3 (brakes too cold), 4 (brakes too hot) etc. It could even be a bitmask, if you have too hot brakes + engine problems at the same time. 2) Now there is EngineDamage in the CarStatus packet. Would it be possible to get the individual component's damage level there instead, i.e. MGUH, MGUK etc. Cheers.
  12. LonelyRacer

    F1 2020 UDP Specification

    Ok. No worries on the DRS. I actually made a solution in my tool, where the DRS status is "undefined" at the start of each session. Then if any of the drivers gets the 'canUseDRS', I turn the DRS status to Enabled. After that if there is DRSD, then it goes to Disabled status or if there is DRSE, it goes to enabled. Works quite well. The speed trap would be great. Fingers crossed. Cheers.
  13. LonelyRacer

    F1 2020 UDP Specification

    @Hoo, I think the ERS mode is different than what is mentioned in the first page. (Tested with 2nd week beta). The modes seems to be 0 = none, 1 = medium, 2 = overtake, 3 = hotlap Could you check if that is the case and maybe update the data on the first page. I haven't noticed issues on other enums, but will keep checking them as I test. Cheers.
  14. LonelyRacer

    F1 2020 UDP Specification

    Is there supposed to be data coming into the lobby packets? When I am in an online lobby, I just get empty data for all drivers, i.e. the teamId is 255, everything else is 0 and name is empty string. This with lobby with other players. The number of drivers in lobby gets updated and is correct. I would expect at least my own driver name to be visible. Cheers
  15. LonelyRacer

    F1 2020 UDP Specification

    It seems to work as earlier. Waiting to see, how the lobby participant stuff works. A note about events. DRSE/DRSD. Would it be possible to send one of these after SSTA to provide info, if DRS is available or not. If you don't want to add another message, the SSTA could contain a byte of 0 or 1 indicating, if DRS is available or not at the start of the session. Speed trap event? Would it be possible to add a speed trap event, i.e. when the player gets notified of new top speed on speed trap, the game would also send an event like the FTPL but for top speed with driverId and the top speed gained. Cheers.
×