KNOWN ISSUE: Server Instability & Errors After 'Secrets of the Machine God' Update

[FatsharkJulia]

Please be sure to include your logs with mods disabled. Thank you!

How To Provide a Crash Report, Console Log, or darktide_launcher.log

Crash Report After the crash has occurred, a pop-up window prompting you to enter the details of what you were doing prior to the crash will be displayed Submit the pop-up window Another pop-up window similar to the previous one will be displayed Click the ‘Copy to clipboard’ button Steam 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 sessi…

[Dirty_Hairy]

Thank you!
Confirming, that it has fixed the freezing for me, and game’s working fine with mods for longer periods. >4h session was stable.

Before it was freezing as if my graphics card overclock was unstable, but even after declocking it happened. In console logs, there were huge wait times. Now it’s gone.

Also, the logs say to use Lua viewer, but page with the given address is unavailable + the environment variables in paths aren’t replaced with values.

Below, part of the old pre-fix log - check out time stamps:

20:06:53.904 warning: [Lua] WARNING [WeaponTweakTemplates] Could not find modifier definition  for weapon thunderhammer_2h_p1_m1 when extracting buffs
20:06:55.872 warning: [Profiler] Stall 160 ms: 
    Application::update 160 ms
        MyGame::update 160 ms
20:06:55.872 warning: [Profiler] Stall 156 ms: 
    ThreadPool::do_work_while_waiting_for_event 156 ms
20:07:20.272 warning: [Profiler] Stall 24370 ms: 
    Application::update 24370 ms
        MyGame::update 24370 ms
            LuaEnvironment::dump_state 24370 ms
20:07:20.272 warning: [Lua] Running low on lua memory. Total allocated: 500MB.
Dumping lua state to '%APPDATA%\Fatshark\Darktide\lua_dumps\lua_dump-GLOBAL-%SESSION%-%UTCDATE%-%UTCTIME%-0.txt' and '%APPDATA%\Fatshark\Darktide\lua_dumps\lua_dump-REGISTRY-%SESSION%-%UTCDATE%-%UTCTIME%-0.txt'.
See https://fatshark.atlassian.net/wiki/spaces/CT/pages/4425318/Lua+State+Dump+Viewer for more information.

<Lua Stack></Lua Stack>
20:07:20.272 [Lua] <<crashify-exception>>
	<<system>>Memory<</system>>
	<<message>>Low on Lua memory. Allocated: '524288000', Used: '523371232'
		_G dump: %APPDATA%\Fatshark\Darktide\lua_dumps\lua_dump-GLOBAL-%SESSION%-%UTCDATE%-%UTCTIME%-0.txt
		Registry dump: %APPDATA%\Fatshark\Darktide\lua_dumps\lua_dump-REGISTRY-%SESSION%-%UTCDATE%-%UTCTIME%-0.txt
	<</message>>
	<<callstack>><Lua Script.Callstack>
  [0] =[C]: in function callstack
  [1] @scripts/foundation/utilities/crashify.lua:54: in function print_exception
  [2] @scripts/foundation/utilities/log.lua:187: in function exception
  [3] ./mod_loader:529:in function <[string "./mod_loader"]:528>
</Lua Script.Callstack>
<Lua Script.Locals>
  [1] system = "Memory"; message = "Low on Lua memory. Allocated: \'524288000\', Used: \'523371232\'\n\t\t_G dump: %APPDATA%\\Fatshark\\Darktide\\lua_dumps\\lua_dump-GLOBAL-%S..."; print_func = [function]
  [2] category = "Memory"; message = "Low on Lua memory. Allocated: \'%d\', Used: \'%d\'\n\t\t_G dump: %s\n\t\tRegistry dump: %s\n\t"
  [3] global_path = "%APPDATA%\\Fatshark\\Darktide\\lua_dumps\\lua_dump-GLOBAL-%SESSION%-%UTCDATE%-%UTCTIME%-0.txt"; registry_path = "%APPDATA%\\Fatshark\\Darktide\\lua_dumps\\lua_dump-REGISTRY-%SESSION%-%UTCDATE%-%UTCTIME%-0.txt"; total_allocated = 524288000; total_used = 523371232
</Lua Script.Locals>
<Lua Script.Self>
</Lua Script.Self>
<</callstack>>
<</crashify-exception>>
20:07:20.272 [Lua] Lua state dump took 24.4 s to generate
20:07:20.275 warning: [Profiler] Stall 24366 ms: 
    ThreadPool::do_work_while_waiting_for_event 24366 ms
20:07:20.307 [Window] Window => inactive
20:07:20.307 [Lua] LUA window => DEACTIVATED
20:07:20.327 [Lua] INFO [UIWeaponSpawner] [cb_on_unit_3p_streaming_complete] unit: [Unit '#ID[2ffa87c8f45832e2]']

In the post-fix log, there were no stalls logged with 4+ digit time, except for the game launch.

[Tamren]

Still getting 2014 errors after the hotfix that was supposed to resolve this. I use mods but talking to other players during missions where people disconnect tells me that people without mods still get the same 2014 issue.

Should I try the ini file fix?

[Spokez]

Issue Type (Required):

Freezing and crashing

Issue Description (Required):

Since the latest hotfix, the game has become unplayable for me. I can stay all day on the Morningstar, however as soon as I enter a mission, after 2-3 seconds, the game freezes and then crashes. Happens every single time, doesn’t matter which mission is selected. I verified the game files, no changes to the behavior since, still crashes.

Steps to Reproduce (Required):

1. Enter mission.
2. Game freezes and crashes

[PC] Do You Use Mods? (Optional):

No.

###LOGS:
console-2024-07-05-11.16.45-e1c2201c-5432-4d1c-b153-4877c94acfbf.log (158.5 KB)

crash_dump-2024-07-05-11.16.45-e1c2201c-5432-4d1c-b153-4877c94acfbf.dmp (1.1 MB)

Reproduction Rate (Required):

Constant (100%)

Platform (Required):

PC - Steam

[fnowign]

Every fcking game I get this god damned error. Before patch, after patch. I played over 700 hours with no problems. Starting 4 weeks ago now. Every game, after 5-10 minutes, is lag then error 2001. Sometimes 2x in the same game. I tried no mods, a reinstall, lowering graphical settings, the memory work around that was given out. Nothing works. Someone please enlighten me. Any information on how to solve this problem would be greatly appreciated. This is bullsh*t.

[kalindichan]

what logs? the game isnt crashing its 2014 me right back to character select. its not producing a crash dump.

[FatsharkJulia]

Any remaining issues are predominantly mod-related, though we acknowledge some users continue to experience these issues without mods. We are continuing to monitor our error rate for those without mods.

For those using mods, per advice from our developer Lopus, please:

1. Navigate to: Steam\steamapps\common\Warhammer 40,000 DARKTIDE\bundle\application_settings
2. Open win32_settings.ini in Notepad or similar
3. Locate the line memory_dump_state_enabled = true
4. Change true to false
5. Save your changes
6. Launch Darktide as normal

An added note from Lopus:

Dont change anything else in there or you might end up breaking your install and having to use the steam reset but that should disable the lua state dumping and get rid of the stall.

[Index]

while i´ll of course try the .ini setting because as of late certain issues have grown worse, it´s not so much an error or crash but unresponsiveness of servers in general.

up to the point of enemies floating or attack patterns “hickup” both in sound and animation until they get fired up eventually.

last 2 extraordinary cases were affecting every team member ( do mods of one person have an effect on the server as a whole ? ) where one time the whole group crashed simultaneously, or rather the server opted out after not registering anything for couple seconds and send poxwalkers into orbit.

the second one was unique in a way that both the beast of nurgle and a horde of hounds couldn´t find an agreement of how to kill me, hence boxing me in at 1% health, immortal but immovable as well, while chat and spectating of the other dead players went on “fine”.

they did however experience the same issues that led to my ultimate demise earlier.

couldn´t ask everyone about mods but how could this be a mod-thing if the others could spectate the “show” and still see the same issues ?

dont have any logs either since it didnt crash per se, just “funny” stuff that lead to an unplayable match.

i can upload the last part of the match in question to my channel and link here if that might help

[kalindichan]

yeah but what are you doing with it? this is every update or change. you repeat the same fixes every time i think the entire community has them memorized and does each one before posting here. i know i do.
GUID: c3988a57-36f9-4bb9-b3ae-6db2c12f7be7
Log File:
Info Type:

---

[kalindichan]

Issue Type (Required):

Error - 2014

Issue Description (Required):

since machine god, i cant take 3 steps into the morningstar and then back to the character select screen. occasinally a 3013 also. all without a crash report because the game dosent actually crash it just boots me back to the char select scree. well today i got it to crash. so heres you report. side note, every time you add anything to this game its unplayable for months.

[PC] Do You Use Mods? (Optional):

No, I don’t use mods

Reproduction Rate (Required):

Constant (100%)

Platform (Required):

Steam (PC)

Player ID (Optional):

Steam Community :: kalindiprana

[PC] Crash Report (Optional):

GUID: ad905f46-ad4e-49e0-b1e4-88a836b97418
Log File:
Info Type:

---

[kalindichan]

and another one
GUID: c3988a57-36f9-4bb9-b3ae-6db2c12f7be7
Log File:
Info Type:

---

[FatsharkJulia]

Hi @kalindichan! We acknowledge that some issues remain for those not using mods, and we are monitoring the situation. I apologise I don’t have any news to share at this time.

[kalindichan]

unsatisfactory, why does not modding the game make it not work? this is not an answer or a solution.

[FatsharkJulia]

I think there’s a misunderstanding. Modding will not make it work, if it is already broken. There is a specific solution for those using mods above, which I recognise is not an option for all, as the errors persist for some even with mods disabled - which is something we’re continuing to look in to.

[kalindichan]

and another one. why would there be a fix for a modded game and not the standard game you sold? i think you misunderstand.

GUID: 9f994ef3-f788-4978-86de-332251b15cec
Log File:
Info Type:

---

[FatsharkJulia]

All I can do is reassure you that we’re looking in to it.

[nuggets]

Issue Description:
At some point during missions enemies start running and floating in the air and allies just fly around and then I get disconnected. It still gives me the option to reconnect to my previous match. The error codes I get are 2001 or 2014.

Your Region & Name of ISP:
Region:EU
ISP: British Telecommunications PLC

Platform:
Steam

Player ID:

Steam Community :: nuggets

[PC] Upload Console Log:
console-2024-07-13-01.05.31-8f88ce30-26d6-4b5a-8966-2734c07ced6b.log (329.2 KB)

[Mirsoress]

Issue type:

Error: 2004

Issue Description (Required):

Almost every time (when I starting a game or after mission) when I am on choose character window - after choose a character and press start - after a while I’m back on the characters window and getting message: disconnected form the server. Error code: 2004.

Platform: Windows 10

[PC] Do You Use Mods? (Optional):

Yes, and I’ve tried disabling them

Reproduction Rate (Required):

Almost constant (95%)

Platform (Required):

Steam (PC)

I did everything described in this post: https://support.fatshark.se/hc/en-us/articles/15604389552157-Error-Code-2014 (about error 2014), I play two games without any issues, and after that get the same error 2004.

console-2024-07-22-20.12.21-68b202a2-79fc-414a-aa4d-74731e36dd70.log (574.6 KB)
darktide_launcher.log (31.6 KB)
user_settings.config (4.9 KB)

I hope that You can help me solve this, I really love this game, and want to play it.

[Mirsoress]

I updated the bios to latest one, and playing without any error yesterday (2 matches)
console-2024-07-24-20.01.17-5bc26d84-612e-4a84-93ed-235c90e3ad3d.log (325.8 KB) ,
today windows wants to change form 10 to 11, and i did it. I played without any errors (just one match, but problem always was to start one). I have a problem with starting computer (bios starting about 4 minutes!) but its not related to game.
I sent files, maybe it will help somehow…
console-2024-07-25-17.21.40-a91ba2b1-cae3-46d9-8ea4-cf51098cfe97.log (185.3 KB)
darktide_launcher.log (181.5 KB)
user_settings.config (4.9 KB)
(user settings is the same i think, but I upload it anyway).

[Mirsoress]

sorry, that’s not it… Today I got error 3013 and then error 2004 twice (or more didn’t count it). Can’t play, getting on character select screen and when I push button to start got errors (every time).

darktide_launcher.log (219.0 KB)
console-2024-07-26-15.37.11-3cbe6dad-94ca-4d09-a369-ad57bae33a45.log (124.3 KB)
user_settings.config (4.9 KB)