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

Just noticed that TeamName does populate for me in Single Player, so it may just be a multiplayer configuration issue? Server?

 

Kunos, thanks for the updates today in the broadcast API in 1.3.12. I hope this can continue and we see some of the additions I have suggested above as well sometime soon!

 

I have started working on a strategy tool and noticed the game sometimes wouldn't connect. I tried the ksBroadcastingTestClient project and noticed it would only connect at certain times of the race as well, Is this a bug or is this intended, if it's intended is their documentation on when the broadcast api will accept need UDP clients and when it will not?

 

I have noticed when connecting from a remote machine it doesn't always connect the first time. I try again a second or two later and it always connects. Besides that I haven't had an issue connecting at any time or in any session.

 

In a single player session, it will only connect when the race is starting "before the green light" anytime after that it wont connect any more clients.

 

ah ok. most of my testing has been multiplayer, so that explains why I haven't noticed it.

 

@Zeraxx I do have the impression that since the 1.3.12 the broadcasting interface does take more time to connect, especially after the green light. But after increasing the timeout on the connection, I do manage to connect also after the green light (but it might take a few attempts and using a timeout of 5s.)

 

@Brado23 next to the added nationality for the car (team) and each driver, did you notice a change in the behaviour in one of the already existing fields?

 

It'd be nice to get some word from KUNOS, as far as I can see the C# example app doesn't have a timeout and its not always connecting.

 

No, but I gave up on TeamName and replaced it with an Enum of my own that lists out all of the Manufacturers. I use this in the teamName field now. The TimeOfDay still doesn't work. Haven't noticed any other changes to existing fields I was having issues with.

Did you?

 

In any network connection it is always good to handle timeouts. I'm not a C# buff, I've written my own SDK in Go, so I can't help you on the offcial SDK.

@Brado23 , no I did not find anything else different. I have also defined constants matching the different brands and also listing all circuits explicitly (see https://github.com/toonknapen/accbroadcastingsdk/blob/master/network/buffer.go#L69)

 

Yeah Im gonna create my own C# one as well, something must be busted in the official, because like I said even the example solution doesn't always connect.

 

Yeah, having problems with connections too, it seems to connect ok when you first join a session and before a race start, but during the race connecting / reconnections seem to simply not work, no matter how many attempts are made. That's using the example broadcast tool.

 

Just a thought I had.... I always connect as a spectator. Are you guys that are having trouble connecting, connecting as spectator or player? Not sure that it is the cause, but something to think about possibly.

 

So far I've always used tested my tool when doing single-player. So if I understand correctly, you are joining as player or spectator and then connecting to the broadcasting interface on your PC? This makes me wondering, is there any difference on the data available in the broadcasting interface when connecting to your own pc or when connecting to the UDP interface of the server ?

 

From the ACC game you can connect to a multiplayer server 2 ways... by specifying the server password (if one is set) to join as a racer, or you can join the multiplayer server as a spectator by specifying the spectator password. The latter is what you would do as a broadcaster/director of a race, as that way you don't appear on the server as a driver. All of my testing I have been connecting as a spectator on a multiplayer server as this is the way my league will be using the broadcasting client.

 

But I was wondering if the UDP interface of the server is the same as the UDP interface of the ACC client?

The server handbook specifies that each client establishes a TCP and a UDP connection and that the latter is for receiving the car positions etc, just like the UDP interface of the ACC client.

I tried running my own server and while I can connect with my own ACC client (and thus connect on the TCP and UDP port of the server with acc), I don't succeed in connecting my app on the UDP port of the acc server. If you know more, I'm all ears !

 

To my knowledge you can't connect directly to the server itself with the broadcasting client. I have never tried though tbh as you need the ACC game to display the video for the broadcast stream anyway.

 

Was using the client last night as a spectator, it was for some reason really laggy and unresponsive. Not very usable at all sadly and a massive pain to try and do for the 6h Silverstone race

 

I can confirm that after joining a session you can only request a UDP handshake with the client once, after you use that one request, it wont accept any more requests, the async client listener status just sits there waiting on a response. Additionally I noticed that "Track Position", "WorldPosX", "WorldPosY" are always 0. @Minolin Any information on the behavior of the SDK would greatly be appreciated!