As seen below, I am getting booted from TT sessions. I have never had this issue in the past. I was having disconnect issue from multiplayer back in April 2024, but after the April update, that was resolved. If I drive against ghosts, I am lucky to make it .5 Laps before being kicked from the session. This is my 4th time From Log: [12:15:56:178][0x000026f8] [Info ] [ProgressPointManager::Init] [ProgressPoint] ProgressPointManager Initialised [12:16:27:771][0x000026f8] [Info ] [Authentication::NotifyApp] [Accounts] Logged in! [12:16:41:357][0x000026f8] [Info ] [TimeTrialView::OnPageActivating] [ProgressPoint] num_defined_tt_events 13982 [12:18:23:800][0x00002830] [Info ] [GameBrowser:: Disconnected] [GameManager] Lost connection to online service - cleaning up game browser [12:18:42:094][0x00002830] [Warn ] [Authentication::ValidateTicketCallback] [Accounts] ValidateTicketCallback responded with error 6, assuming we have been VAC banned [12:19:02:143][0x000026f8] [Info ] [TimeTrialView::OnPageActivating] [ProgressPoint] num_defined_tt_events 13982 [12:26:20:047][0x00002830] [Info ] [GameBrowser:: Disconnected] [GameManager] Lost connection to online service - cleaning up game browser [12:27:08:108][0x000026f8] [Info ] [TimeTrialView::OnPageActivating] [ProgressPoint] num_defined_tt_events 13982 [12:28:12:219][0x00002830] [Info ] [GameBrowser:: Disconnected] [GameManager] Lost connection to online service - cleaning up game browser
The last person that posted a log that had the vac banned thing in it fixed it by reinstalling steam (i.e remove everything in steam folder except SteamApps and steam.exe and then re-run steam.exe - you shouldn't lose any installed games but if your login is saved you'll need to know what it is)
Got this message from another failed connect: [13:45:57:639][0x00001b7c] [Warn ] [ServerBrowser::ServerResponded] [GameManager] Received dedicated server response from Steam for server 210 (DMSK AMS2 Server 1 - StockCar 2023 at Cascavel) with invalid server protocol version 10073, expected 10074
The failed connect looks like they are running the wrong version of something. I'd guess it's a red herring from the other connection issues you're having. I'm testing now to see if TT is working for me (It was the other day) edit: Yeah it's fine here...