Multiplayer Crash

[mike4t5]

hi there, 

I've been having multiplayer issue  where the game keeps crashing at random points, is there any way to fix this issue as it makes it unplayable. i have attached the crash log and dump file if it helps. 

 

Thanks,

Mike

dcs.20221225-190118.crash dcs.20221225-190118.dmp

[Flappie]

0x000000000003B9E3 (edCore): CoreUtils::TempFilesManager::TempFilesManager + 0x3A13

Hi. Please try this:

1. Go to "C:\Users\your_login\AppData\Local\Temp"
2. Delete all "DCS..." folders you can find in there (these are DCS temporary files).

If crashes keep happening, please attach the latest ZIP file from our Logs folder.

Edited December 25, 2022 by Flappie

[RedAero]

I have the same sort of crash quite regularly. It correlates with graphical settings, and version: on 2.7, I basically ran at max settings (I have 3 1080p screen, two of which only show the DDIs), while on 2.8 the same settings cause a crash like the above in no more than 15 minutes. With much lower settings, it's a toss-up, I might be able to go 4 hours no problem, or it could crash in 45 minutes. It also varies by map: Caucasus (GAW server) is pretty stable, Gulf (PGAW) less so, and Syria is unplayable, with the game crashing in less than 30 minutes.

Clearing the temp folder as described above helps, in that the game is less likely to crash than if it's left full of stuff, but it's no guarantee.

For reference I'm on Win10, 16GB of RAM, 3070, 5800X.

Attached are 3 different instances of the crash, as you can see it's invariably edcore.dll.

crashlog_2023-01-12_2010.zip crashlog_2023-01-12_1824.zip crashlog_2023-01-17_0201.zip

Edited January 17, 2023 by RedAero
spelling

[Flappie]

@RedAero You log file end resembles the OP's indeed, but you also have a few "(function-name not available)", and it looks like the sim cashes while failing to load a big F-14 texture. Seeing you only have 16GB of RAM and a 4GB pagefile, I think you may solve your problem by maxing your pagefile.

1. Ensure you have sufficient free space in your drives (more than 50 GB is good).
2. Use this guide: https://mcci.com/support/guides/how-to-change-the-windows-pagefile-size/
3. Set :
   • init size = 16384 (16GB)
   • max size = 32768 (32GB)

[RedAero]

The initial size is indeed 4GB but the max is already 32, set manually. Even if the issue is memory, I hardly think 16GB + 32GB of PF should be so little to cause a crash, especially when running at quite modest settings (1080p with a 3070!).

[Flappie]

OK, then I have no more ideas sorry.

[Maverick87Shaka]

On 1/18/2023 at 9:01 AM, RedAero said:

The initial size is indeed 4GB but the max is already 32, set manually. Even if the issue is memory, I hardly think 16GB + 32GB of PF should be so little to cause a crash, especially when running at quite modest settings (1080p with a 3070!).

Unfortunately when comes to multiplayer most of the performance issues are related to how many players are in the server itself and how large it's the mission that server is running, with current active and inactive ground units, static objects etc, and not so much to your GPU only.

In most of the log you have explicit memory exception or unable to load new texture:
 

2023-01-17 01:01:42.807 ERROR   DX11BACKEND (15356): Failed to create shader resource view for /textures/AH-64D_inside_D_Normal.dds. Reason: Not enough memory resources are available to complete this operation.


2023-01-12 17:24:19.501 ERROR   EDCORE (Main): Can't open file: /textures/liveries/f-14a-135-gr/vf-142 ghostriders/description.lua.
2023-01-12 17:24:25.832 ERROR   DX11BACKEND (8916): Can't load image '/textures/liveries/f-14a-135-gr/vf-14 tophatters ab100 (1976)/HB_F14_EXT_PILOT.dds'. Reason: The request is not supported.



2023-01-12 19:06:50.663 ERROR   DX11BACKEND (11828): Can't load image '/textures/liveries/f-16c_50/18th agrs arctic splinter/f16_bl50_kil_roughmet.dds'. Reason: The request is not supported.
2023-01-12 19:06:50.695 ERROR   DX11BACKEND (11828): Can't load image '/textures/liveries/f-16c_50/18th agrs splinter/F16_bl50_wing_L.dds'. Reason: The request is not supported.

So basically I suppose you're out of memory every time it crash.
Even if page file can help a bit, can't solve the problem since its magnitude slower than RAM speed, if you want play in large server or high populated mission, you must upgrade your ram to 32GB at least.