Let's talk about broadcasting (programmer's thread)

Any news if the incorrect mapping of GlobalX, GlobalY and Yaw in the UDP interface will be fixed at some point?

 

Hello everyone !

I'm using the test client available with the dedicated server tool from steam (as they removed it from the game client) and i'm developping my app with C#.

I already did the connection between my app and the game, but i can't find how to send data from the app to the game (i would like to, for example, be able to make a driver change request from the app)

Also, i tried to get the car gear, but it always returns 0. Is the client still updated ? Or, if someone know, was there an update for that client with the recent 1.9 update ?

Thanks !

 

The requests you can send are quite limited

public enum OutboundMessageTypes : byte
{
REGISTER_COMMAND_APPLICATION = 1,
UNREGISTER_COMMAND_APPLICATION = 9,

REQUEST_ENTRY_LIST = 10,
REQUEST_TRACK_DATA = 11,

CHANGE_HUD_PAGE = 49,
CHANGE_FOCUS = 50,
INSTANT_REPLAY_REQUEST = 51,

PLAY_MANUAL_REPLAY_HIGHLIGHT = 52, // TODO, but planned
SAVE_MANUAL_REPLAY_HIGHLIGHT = 60 // TODO, but planned: saving manual replays gives distributed clients the possibility to see the play the same replay
}

I think @TheBigO managed to do want you are trying but only via screen scraping or some other magic IIRC (https://www.assettocorsa.net/forum/...incl-voice-control-for-acc-pitstop-mfd.68024/). To get the gear, I'd personally use the information in shared memory (for the player car only)

 

Thanks mate !

I see, i guess it would be better (as the request are limited) to probably just do something like a macro that can send to the game window multiple inputs (i mean, if your MFD is binded on B, then my app could send a "fake" input B until he get it open), i think i've seen something about the MFD in shared memory, which i could use to check if he's open right ?

Also, there is someone else who managed to do that but i don't really know how, through his soft "ACC Drive"

So i guess this is something possible, but since he's selling his soft (and i agree that every work should be paid), he doesn't want to share his knowledge

 

Hi, ACC Drive as well as my suite is sending keyboard commands to ACC. There is no official API to control the pitstop settings like rF2 provides, for example. But it is very complex to "understand" what is currently selected in the pitstop dialog, so that you can send meaningful cursor up/down, left/right messages to change the desired setting.

My suite provide two different methods, each with their pros and cons. The first uses some kind of image recognition to "detect" the currently chosen settings. It is very fast, but you must provide your own pictures for your screen resolution and color settings. The second method uses a heuristic option walk, which looks quite funny and takes some time. But at the end, it fully understands the available options (refueling yes/no, driver change, which options like tyre change, break pad change, and so on, are currently chosen) and then applies the desired changes. Very reliable, but as I said, looks funny. The algorithm behind this heuristic walk is quite complex, though.

 

Ah, and by the way, my suite is open source, so you can borrow the algorithm as far this is a practical approach for you.

 

Hello there !

I see, thank you ! I will definitely take a look at your work

 

Good Day to all,
I seen in Broadcast these fields:
world_x , world_y ,yaw and spline
So with this information i think i can understand the positions of the cars into the map ...is it true or not?

 

It's me again. world_x, ... are the same coordinates as in the shared memory interface, for which I gave you a code example. spline position is the distance the car has travelled on the track starting from start(finish). I think, the value ranges from 0.0 to 1.0, so you must multiply it with the track length.

 

Sorry but i not see the same coordinate i seen in shared memory. For example i tried Donigton i was stopped into PIT and with shared memory i had this value:
x= -394,2784

into broadcasting i had:
x= 2,52231

 

Most probably only a scaling / transformation thing...

 

As far as I know, world_x, world_y and yaw are falsely documented. It's roll, pitch and yaw in radian instead (not sure about the order). But yes, the values are exactly the same as in shared memory. Only the sampling rate differs, depending on how often you query the UDP interface. Or did they fix it in the meantime?

 

@Minolin I appears that the 24H Nürb track does not publish the 0x05 track data event after it has been requested.

This is a bit of a big problem since the track data event contains cameras, hud pages and the track length.
Without this information a whole slew of features does not work for my app.
Can this please be fixed.

 

Hi,

Based on my pretty quick test, the data is coming in and for my uses it works. The ones using cameras etc. might still want to check their tools.

Cheers.

 

Hi at all, i have a trouble with is_invalid data from lap from field from broadcast...it seems like sometimes send info about invalid lap but is not... someone have this problem?
Thanks

 

For completness sake of this thread the most recent update fixed the track data issue for me.

 

Good morning everyone, after some investigations and tests, I arrived at this acc problem, in the broadcast data.
Most likely it is caused by the ESC key when returning to the pits i tested all in qualify... and you can see it if you observe someone in track... I noticed that the lap after leaving the pits doesn't count if we use the Escape key in the laps.. Then tell me if I'm wrong or not, if you have the opportunity to try... I noticed it on Donington, but I think it's the same on other tracks too. Therefore, to see the problem, you should follow someone from the cockpit, that someone should in track, for example 2 laps, and then return to the pits with the ESC button on the track, it seems that, when you exit the pits and then cross the finish line, acc not reset the timer and therefore the lap does not count and broadcasting continues to send the data linked to the old lap, such as an invalidated lap and the timing of the lap obviously incorrect because it continues until the lap ends. So practically the user physically completes 2 laps but broadcasting counts one added as well as returning the invalidated lap of the first lap always until the second lap ends.
Do you happen to have any feedback on this issue?

 

(In spectator mode)

 

for complete the information i can put a lap about a driver. Focus into spline and location,we can see at time (field tempo_giro_attuale_driver) 0:00:40.711 the driver return into PitLane after return out of the pitlane, and at 0:03:05.139 the spline is 1 and so broadcast shoud be do a reset of is_invalid (field giro_invalidato) ,the time of the driver and add a lap (filed giri_completati)...but not happend and it still continue the timer, so after an another lap(not counted) broadcast add the lap and reset all fine..i think is a bug.
I can't add xls files, but i put here the share of the lap into excel file:
https://docs.google.com/spreadsheet...ouid=102755023487466089395&rtpof=true&sd=true