I have 2070, Ryzen 5, 16GB RAM and run the game fairly smoothly on High with nearly no crashes, and relatively few disconnects, so… It might be the game, it might be something with your PC, it might be both, it might be neither.
1 Like
-
Broken grammar, learn to spell.
-
It’s not even released yet, you wet napkin.
-
Sure buddy, your 1.7 million subribers are totally real, no doubt.
-
Yes, there are broken parts. It’s a beta.
3 Likes
-
Game isn’t released yet!
-
I have PC not as good as yours and dc/crush only few times every 2-3 games! NOT every game.
Wrong forum mate, wrong audience. These people can’t understand that beta doesn’t mean ‘pre-alpha’ (and this is actually the state of the current release), but come on. We are talking about the studio who can’t figure out how to fix the keybind crash. Keybind! I can’t leave the tutorial as I allowed myself to unbind special attack key & now the game crashes every time I enter options or get to the third part of the tutorial. These guys are a coding morons. Expect nothing from Fatshark, always 
Also, please make sure u inform your viewers to stay away from this release - at least until March, April next year. They can’t possibly hope to fix this joke of a game in 4 days.
Emperor’s not proud. Far from it.
“They’re not fixing X crash, they’re coding morons!”
Clearly you’ve never programmed before and don’t understand the literally impossible task of creating a bug-free program for tens of thousands of computers and consoles.
I’m sure you could do better yeah?
This is the worst state of a “beta” test I’ve ever seen. We are 4 days away from launch. How do you think November 30th is an acceptable day to release this game we’ve been testing on three occasions now?
I guess you weren’t here for the Vermintide 2 closed/open beta then?
Because that was MUCH worse. Entire hordes spawning on top of you, endless crashes, bosses teleporting everywhere, broken specials, graphical glitches, and so much more.
This game is in a much better state than Vermintide ever was during its initial launch.
Even for years after its release, there were lots of bugs and crashes that happened. It happens to a lot of games. Hell, you want a delayed release? Just don’t play until things are “fixed”.
Smh at the amount of people that get so whiny about a BETA TEST (Even IF it is a few days away, they’re saving their fixes for the actual launch instead of constantly releasing update after update).
Yeah, the launch will prolly have bugs and crashes in it too. Guess what, that’s the reality of most games. That’s what you need to expect when you preorder or beta test something.
First of all, i really enjoy DT. Second of all, you are not the first person who said that VT had the same or even worse beta/release. Ok. I get that. But why does history repeat itself ? Shouldn’t people learn from their mistakes so they won’t end up repeating them ? DT was delayed 3 or 4 times ? How did those delays help DT in becoming a proper functioning game ? Im just sayin’ … look, i really enjoy DT. Got over 90 hrs of gameplay. Medium settings with everything OFF, not great frames overall, a crash or two from time to time, but i still enjoy the game, as i did VT on my ps4 and VT2 on the pc.
Can people stop saying it’s beta ? 3 more days and what will people say then ? “Game still has issues, should have been delayed a couple of more times, game still feels like beta, game not ready, geting a refund…” stuff like that ?
Will everything be fixed on the 30th ?Of course not. Are we going to get all the features on release ? Not likely…
Look at Tarkov…game has been in beta for years…they also have that BETA watermark slapped across the screen…just so that they can wash their hands when gamebreaking issues occur, and say: “hey, look at your screen, it says beta. We are working on it.This is not our final product!”
But for DT, that beta watermark will be gone in 3 days and the issues will still be there.
I dont know code, im not a developer, but if you have an unpolished game and people have been raging on the forums, its probably best to delay. I also understand that they are being pressured by the higher ups to release the game, so i dont fully blame em…
long story short: really like the game, even buggy as it is and history repeats itself.
These are my 2 cents.
Seph, I’m talking about a possibility of changing something in options, not some in-game ‘out of the blue’ bug. Options. Something they clearly did right in VT2. Yes, they are absolutely freaking unbelievably bad. No excuses here. I have no intention in saying that it rains when someone is clearly trying to spit into my face. £30 for 15 minutes prologue gameplay. No thanks. Therefore instead of promoting this crap, and a monstrosity of a game, let’s make sure people don’t spend their money to fill Fatshark pocket, by commenting on youtube, giving out reviews & letting people know how the game really look like. I can’t see a massive sign on Steam saying “do not change your keybind as it will be like dropping your £30 into toilet & flushing water”, clearly they are trying to stay very silent about half of the stuff that’s going on. For this they should be severely punished, as it’s not far from thievery.
Never seen such a incompetent bunch of imbeciles. On top, they clearly don’t know how to fix their ‘option bug’, as they admitted it themselves in this thread Loading Keybind Screen Autocrashes Game - #5 by Borr
No knowledge, no skills. It’s so sad that another Warhammer 40K game is being held by studio with 0 experience. The galaxy suffers.
**Issue Description: The game constantly crashes during the cutscene to meet the inquisitor for the first time. This crash occurs 100% of the time and I can’t go past it.
I’m running a Windows 11 machine with a Ryzen 3900x, RTX 3080, and a WD m.2 SSD @ 7000mb/s r/w
**Crash Report (If Applicable):GUID: fd6af673-76e2-41c2-a950-c60ff51caab2
Log File:
Info Type:
**Error Displayed (If Applicable):GUID: fd6af673-76e2-41c2-a950-c60ff51caab2
Log File:
Info Type:
**Steps to Reproduce:
1.Running the game. The save point goes to a cutscene with the inquisitor and the game just keeps crashing constantly.
2. Crash
**Mission Name (If Applicable): Prologue
Platform:
[Steam/Microsoft Store]
Player ID:
[Swazza]
Approx. Time of Issue & Timezone:
[11/28/2022, 00:22AM] [+12 NZST]
**Reproduction Rate: Constant [100%]
Upload Supporting Evidence:
[Screenshots, recordings, links to Twitch VODs, etc.]
Upload Console Log:
- Press the Windows key + R
- Enter
console-2022-11-27-11.18.20-fd6af673-76e2-41c2-a950-c60ff51caab2.log (49.2 KB)
darktide_launcher.log (321.0 KB)
within the search input and select ‘OK’ - Navigate to AppData\Roaming\Fatshark\Darktide\console_logs
- Locate the console log that corresponds with the session in which the issue occurred, by looking at the timestamps in the log names
- Upload here
Upload darktide_launcher.log:
- Press the Windows key + R
- Enter %appdata% within the search input and select ‘OK’
- Navigate to AppData\Roaming\Fatshark\Darktide
- Locate the darktide_launcher.log in this directory
- Upload here
Issue Description:
Steps to Reproduce:
[Please add the steps that can help our QA department in reproducing the issue. For example:]
- Disruption as so far it is on both my Guardsman and Zealot
- Navigate to the midway point of the mission
- Just playing the mission
- Game crashes
Mission Name (Disruption):
Platform:
[Steam]
Player ID:
(Steam Community :: ArcherGoblin)]
Approx. Time of Issue & Timezone:
[11/26/2022, Don’t remember the time [CET]
Reproduction Rate:
Constant (99
Upload Supporting Evidence:
[Don’t have any do to the recording file is to big]
Upload Console Log:
console-2022-11-27-08.00.22-c0f044c4-721e-471a-8254-aedfae1ba56e.log (52.6 KB)
%)
Upload darktide_launcher.log:
darktide_launcher.log (28.0 KB)
I think i did everything right here.
2 Likes
same crash for me. the midway point event starts and seconds into it my game crashes.
Same issue for me. When I reconnect, if the other three players are still doing the objective I crash again.
If they have finished the objective and I can enter the giant fan to progress the mission I no longer crash and the rest of the mission is smooth.
1 Like
We kindly ask that you complete the questions below. With this information, we can add it to our database for investigation.
Issue Description:
Steps to Reproduce:
[Please add the steps that can help our QA department in reproducing the issue. For example:]
- Play Smelter as Ogryn (Skullbreaker)
- loading into the mission
- Crouch-slide into the dumpster next to the blue and white Tertium sign
- Get stuck
Mission Name (If Applicable): smelter
Platform:
[Steam/Microsoft Store] steam
Player ID:
[Steam ID/Steam Profile URL/GamerTag]
Approx. Time of Issue & Timezone:
[11/27/2022, 12:32AM/PM] [Eastern Timezone
console-2022-11-27-05.31.55-cf117607-a7e6-46be-b4b1-0a2fd2d0a4f0.log (17.5 KB)
]
Reproduction Rate:
Once - Rare (<10%) - Unusual (<25%) - Common (<50%) - Often (<75%) - Constant (100%)
Upload Supporting Evidence:
[Screenshots, recordings, links to Twitch VODs, etc.]
Upload Console Log:
- Press the Windows key + R
- Enter %appdata% within the search input and select ‘OK’
- Navigate to AppData\Roaming\Fatshark\Darktide\console_logs
- Locate the console log that corresponds with the session in which the issue occurred, by looking at the timestamps in the log names
- Upload here
Upload darktide_launcher.log:
- Press the Windows key + R
- Enter %appdata% within the search input and select ‘OK’
- Navigate to AppData\Roaming\Fatshark\Darktide
- Locate the darktide_launcher.log in this directory
- Upload here
PC fully blue screened while tryin to load into a mission
1 play as psyker.
2. Load into mission.
3. Play for a while
4.Crash to desktop.
Platform Steam
ID:76561198042279838
Reproduction 75%
console-2022-11-27-11.19.50-b8473a23-fec5-4141-931f-3b437bfb122c.log (662.4 KB)
console-2022-11-27-12.24.17-3395f479-2129-4be4-8cb5-2bd9ca0699d1.log (98.5 KB)
console-2022-11-27-10.32.22-65275798-fbd7-473d-8fba-f21229f015d5.log (99.1 KB)
console-2022-11-27-10.42.38-5f8f36c7-f361-4f26-855a-f6d2d1d74ad6.log (282.5 KB)
console-2022-11-27-12.45.04-28fa7ff4-78c8-44d5-9f47-792684db075a.log (242.6 KB)
console-2022-11-26-21.22.02-19621beb-0d9a-4b2a-87f6-625f2b58dbf6.log (582.9 KB)
console-2022-11-27-11.28.53-f1f315b9-4220-4aec-a933-21f719f7be30.log (431.1 KB)
console-2022-11-27-14.52.25-7dfd581d-4665-4155-8fc4-20c179452f39.log (135.1 KB)
console-2022-11-27-13.37.44-ab211bb8-0ef8-4b8f-b95a-5add9f1e3d14.log (422.9 KB)
console-2022-11-27-14.35.48-c47adeee-9ec8-4b09-987f-e4a8df8e4735.log (67.1 KB)
crash_dump-2022-11-27-11.28.53-f1f315b9-4220-4aec-a933-21f719f7be30.dmp (876.7 KB)
crash_dump-2022-11-27-13.37.44-ab211bb8-0ef8-4b8f-b95a-5add9f1e3d14.dmp (1.3 MB)
We kindly ask that you complete the questions below. With this information, we can investigate your issue properly.
Crashed at the end of Relay Station just after turning off heretic transmissions (also crashed earlier on same level in the room with the statue that leads out into the town, but I don’t have info for that)
Crash Report (If Applicable):
GUID: b2a634c3-8253-4e92-bd77-d4e9025e2c7b
Log File:
Info Type:
Error Displayed (If Applicable):
Steps to Reproduce:
[Please add the steps that can help our QA department in reproducing the issue. For example:]
-
Play Chasm Logistratum as Ogryn (Skullbreaker)
-
Attempt to pick up the second Grimoire
-
Crash
-
Played Relay Station TRS-150 as Ogryn (Skullbreaker)
-
Get through the map normally with no issues
-
Get to final corruptor area
-
Turn off heretic transmission then a few seconds later Crash
(I have no idea how I crashed)
Mission Name (If Applicable):
Relay Station TRS-150
Platform:
Steam
Player ID:
Approx. Time of Issue & Timezone:
[11/27/2022, 14:20PM] [GMT]
Reproduction Rate:
Once - Rare (<10%) - Unusual (<25%) - Common (<50%) - Often (<75%) - Constant (100%)
<50% (Played it yesterday as Ogryn with no crashes)
Upload Supporting Evidence:
[Screenshots, recordings, links to Twitch VODs, etc.]
Upload Console Log:
console-2022-11-27-12.35.29-b2a634c3-8253-4e92-bd77-d4e9025e2c7b.log (476.6 KB)
Upload darktide_launcher.log:
- Press the Windows key + R
- Enter %appdata% within the search input and select ‘OK’
- Navigate to AppData\Roaming\Fatshark\Darktide
- Locate the darktide_launcher.log in this directory
- Upload here
darktide_launcher.log (1.4 KB)
Issue Description:
Game keeps crashing whenever it gets intense and have to use the flamthrower as the Zealot more actively, or sometimes not at all. it costs me my last match to not receive my rewards simply because it crashed minutes before extraction. I can not say if the flamethrower usage is behind this or just randomly crashing, but its been happening all day
Steps to Reproduce:
1. Play any normal match until it intensifies or randomly just happens
2. It tends to happen when im using the flamethrower or holding it
3.randomly or during build up of hordes when using flamethrower
4. Freezes and crashes
Mission Name (If Applicable):
Platform:
Steam
Player ID:
[Steam ID/DaEmperorDude!]
Approx. Time of Issue & Timezone:
[11/25/2022, 4:25PM] [TIMEZONE]
Reproduction Rate:
Often (<75%)
Upload Supporting Evidence:
[Screenshots, recordings, links to Twitch VODs, etc.]
Upload Console Log:
console-2022-11-25-23.49.29-2252e5a9-a319-408e-b8ff-c7a86cd8349a.log (186.5 KB)
Upload darktide_launcher.log:
darktide_launcher.log (826.2 KB)
Just gonna add the crash dump as well if this helps
crash_dump-2022-11-25-23.49.29-2252e5a9-a319-408e-b8ff-c7a86cd8349a.dmp (1004.8 KB)
Every mission i play, the game crashes to desktop. About 5 or 6 times every match. i have done every “fix” and nothing has worked at all. I really love this game but the crashing is making it impossible to enjoy
GUID: 094905bb-0b94-43ce-8db2-90ac7ecc7d86
Log File:
Info Type:
console-2022-11-18-11.05.17-ff42bb18-9144-47f4-94d6-febe3337fdda.log (154.6 KB)