Matchmaking is taking forever - or empty_ticket error

Issue Description:
When trying to join a quick match the search for a strike team is going on forever. I’m also not able to leave the queue with “F10” forcing me to reload the game. Sometimes also the search ends with “Failed joining server: empty_ticket” and i need to start searching again.

Crash Report (If Applicable):
[Please see instructions on how to provide a crash report in the pinned Topic]

Error Displayed (If Applicable):
Error - no ticket

Steps to Reproduce:
[Please add the steps that can help our QA department in reproducing the issue. For example:]

  1. Search for a quick match
  2. Idle forever or get the “Failed joining server: empty_ticket” error

Mission Name (If Applicable):

Platform:
Steam

Player ID:
Steam ID :76561197960388652

Approx. Time of Issue & Timezone:
[11/19/2022, 20:15 PM] [GMT +1]

Reproduction Rate:
Often (<75%)

Upload Supporting Evidence:
[Screenshots, recordings, links to Twitch VODs, etc.]

Upload Console Log:

  1. Press the Windows key + R
  2. Enter %appdata% within the search input and select ‘OK’
  3. Navigate to AppData\Roaming\Fatshark\Darktide\console_logs
  4. Locate the console log that corresponds with the session in which the issue occurred, by looking at the timestamps in the log names
  5. Upload here
    console-2022-11-19-18.41.00-b00dac10-6373-4ddb-8ca7-f373189c5886.log (274.5 KB)

Upload darktide_launcher.log:

  1. Press the Windows key + R
  2. Enter %appdata% within the search input and select ‘OK’
  3. Navigate to AppData\Roaming\Fatshark\Darktide
  4. Locate the darktide_launcher.log in this directory
  5. Upload here
    darktide_launcher.log (131.2 KB)
2 Likes

I’ve also been having this issue all afternoon - can’t join any strike teams, selected or quick match, also can’t cancel via F10…does nothing. 100% failure rate.

console-2022-11-19-17.57.41-1185d5cd-1fb0-4f65-ae8f-85510954dc69.log (169.1 KB)
console-2022-11-19-19.38.18-7c674075-239e-4ba4-a57d-fbd0a0c69cbe.log (94.1 KB)

darktide_launcher.log (365.8 KB)

3 Likes

so its gone from almost unplayable to literally unplayable

1 Like

Same issue. I was stuck behind the internal_error bug. Then this morning I got into a game, and got a bunch of internal_errors but was always able to reconnect before getting totally dropped right before finishing the mission. Now after selecting a mission (quick match) I get nothing until eventually empty_ticket.

Ye, same here, it was fine yesterday tho, levelled my Sharpshooter to 9 without any issue.

Same for me from Europe started before 30 min, 20:50 every single one matchmaking isnt working…

Here to report that I am also experiencing this issue, exactly the same as OP

Edit: Also this is in Midwest America, roughly 2 hours ago. I do find it kind of humorous to see this influx of this issue at exactly the same time.

Same issue for me. Was fine until about 2000 in Norway now I can’t join a single game. Just after I convinced my friend to buy :smiling_face_with_tear:

1 Like

Same here, EU Germany started 40 min ago since than not able to join a game

Also been having this issue as of about 2:00 CST Nov 19. Previous to that it worked fine. If I restart my entire PC I can play 1 match, then I have to restart the PC again (game restart does not fix problem).

I am experiencing the same issue. Stuck in matchmaking and F10 is unresponsive…

1 Like

On mine it has now given up even trying to form a strike team: click on’play’ on any mission and you get the audio prompt and goes back out to the 3rd person view and nothing is happening. Can just repeat this over and over.

1 Like

Problem looks resolved for me, i made two mission

I’ve been having this issue for the past hour or two now, have restarted the game 4 times and validated my cache, still cannot join any games, always the same error.

Our developers have been working on it, but in the mean time you should be able to play in premades of 4.

4 Likes

Now I am back to Internal_Error…