Jump to content

Recommended Posts

Posted

Ever since the latest update, I have been having crashes during multiplayer fairly regularly. I run the mt client in VR on a 7900X3D / 64GB RAM / 3090. It seems to happen when I am descending through clouds, although perhaps that is just a coincidence. I have run the repair option and followed several suggestions from community members to no avail. All of the crashes have been on the Syria map on Enigma's Cold War server while flying a MiG19.

I have already reported this via a ticket and attached the crash logs, just curious if anyone else has been experiencing this also? FWIW, the only mods I have installed are for the A4.

  • Like 1
Posted (edited)

I've been having issues in SP with repeated CTD since the last update (don't do MP and i'm not on VR either) but also on the Syria map.  Not really clocked up enough time to definitively prove the theory properly yet but so far it has been more stable for me rolling back to the previous OB build (which I realise might not be practical if you're playing MP a lot).

Edited by bfr
Posted

I appreciate the response, but the reason I play DCS is for multiplayer. I have tried a few more things... I have removed the A4 mod, performed a clean install of graphics drivers, deleted the temp files for DCS.openbeta and NVIDIA shader cache, and increased my paging file to 107430 MB. I am still experiencing crashes very regularly as described in my original post. I am attaching the latest crash files... hoping someone can help me out here as the game is unplayable for me right now. Thanks!

 

dcs.log dcs.log-20230522-175347.zip

Posted (edited)

One other update... it's happening to me almost immediately even in 'instant action' missions, too. I loaded into the 2v2 MiG19 mission and it crashed almost immediately. I see the following in the event viewer:

Faulting application name: DCS.exe, version: 2.8.5.40170, time stamp: 0x6464e22d
Faulting module name: VCRUNTIME140.dll, version: 14.32.31332.0, time stamp: 0xefff39ad
Exception code: 0xc0000005
Fault offset: 0x0000000000001646
Faulting process id: 0x1330
Faulting application start time: 0x01d98cd82f629a1b
Faulting application path: F:\DCS World OpenBeta\bin-mt\DCS.exe
Faulting module path: C:\Windows\SYSTEM32\VCRUNTIME140.dll
Report Id: a0367dc0-8160-4db6-b4b3-91bc95a219af
Faulting package full name: 
Faulting package-relative application ID: 

 

Attaching the crash logs as well... these lines stood out to me:

2023-05-22 18:09:41.572 ERROR_ONCE DX11BACKEND (15196): texture 'VRTooltip' not found. Asked from ''

2023-05-22 18:10:08.841 INFO    EDCORE (Main): # C0000005 ACCESS_VIOLATION at 00007ff92e041646 00:00000000

dcs.log-20230522-181009.zip dcs.log

Edited by Creep
Posted
4 hours ago, Creep said:

One other update... it's happening to me almost immediately even in 'instant action' missions, too. I loaded into the 2v2 MiG19 mission and it crashed almost immediately. I see the following in the event viewer:

Faulting application name: DCS.exe, version: 2.8.5.40170, time stamp: 0x6464e22d
Faulting module name: VCRUNTIME140.dll, version: 14.32.31332.0, time stamp: 0xefff39ad
Exception code: 0xc0000005
Fault offset: 0x0000000000001646
Faulting process id: 0x1330
Faulting application start time: 0x01d98cd82f629a1b
Faulting application path: F:\DCS World OpenBeta\bin-mt\DCS.exe
Faulting module path: C:\Windows\SYSTEM32\VCRUNTIME140.dll
Report Id: a0367dc0-8160-4db6-b4b3-91bc95a219af
Faulting package full name: 
Faulting package-relative application ID: 

 

Attaching the crash logs as well... these lines stood out to me:

2023-05-22 18:09:41.572 ERROR_ONCE DX11BACKEND (15196): texture 'VRTooltip' not found. Asked from ''

2023-05-22 18:10:08.841 INFO    EDCORE (Main): # C0000005 ACCESS_VIOLATION at 00007ff92e041646 00:00000000

dcs.log-20230522-181009.zip 797.59 kB · 2 downloads dcs.log 105 kB · 3 downloads

 

i think you are having Visual C++ problem. run the two exe in the folder \Eagle Dynamics\DCS World OpenBeta\distr. this should repair the installations.

AKA_SilverDevil Join AKA Wardogs Email Address My YouTube

“The MIGS came up, the MIGS were aggressive, we tangled, they lost.”

- Robin Olds - An American fighter pilot. He was a triple ace.

The only man to ever record a confirmed kill while in glide mode.

Posted (edited)

thank you for the suggestion. i ran both of those, restarted my machine, and re-launched DCS. i crashed 2 minutes into an instant action mission. i tried disabling process lasso as well - i still crash very shortly after starting an instant action mission. i'm starting to think i should completely reinstall. if i do that, can i backup my keybindings by exporting Saved Games/DCS.openbeta/Config/Input and dropping it back in after a complete reinstall? is there anything else i should consider backing up?

 

 

Edited by Creep
Posted (edited)
4 hours ago, Creep said:

thank you for the suggestion. i ran both of those, restarted my machine, and re-launched DCS. i crashed 2 minutes into an instant action mission. i tried disabling process lasso as well - i still crash very shortly after starting an instant action mission. i'm starting to think i should completely reinstall. if i do that, can i backup my keybindings by exporting Saved Games/DCS.openbeta/Config/Input and dropping it back in after a complete reinstall? is there anything else i should consider backing up?

 

 

 

Before going to that level can you try this:

With DCS closed: Go into your saved games directory. Rename your DCS folder to DCS.old.  (This way you can revert it back to DCS if it doesn't resolve your issue because what you're basically doing is relocating ALL your settings/bindings/etc).

Relaunch DCS and see if this resolves the issue? DCS will automatically create a brand new config (like a new reinstall without going to the full nuke effort). 

If this fixes the issue, then you can go and move back just the things that you really need. (The most common would be the config/inputs directory for your keybinds) and just change only the settings you need to change again. If in changing those settings you get crashes again - you can repeat the procedure until you nail down which setting is causing the crash.

Sometimes some things just get corrupt in the config section. We don't know why or what - but doing this can be a quick easy way to resolving the issue.

If this doesn't resolve the issue, or there is another solution, simply deleting the new DCS directory and renaming the other DCS.OLD back to DCS completely undoes what you just did.

Edited by Dangerzone
  • Like 1
Posted

thanks for the response! i will try that this evening and share the results here so that it can hopefully help someone else out in the future.

  • Thanks 1
Posted
On 5/23/2023 at 1:23 AM, Dangerzone said:

With DCS closed: Go into your saved games directory. Rename your DCS folder to DCS.old.  (This way you can revert it back to DCS if it doesn't resolve your issue because what you're basically doing is relocating ALL your settings/bindings/etc).

Relaunch DCS and see if this resolves the issue? DCS will automatically create a brand new config (like a new reinstall without going to the full nuke effort). 

i think that fixed it! i only spent about 30 minutes playing instant action, but no crashes which is incredible because i was crashing within 2-3 minutes before. thank you so much!

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...