Jump to content

2.9.7.59263 Crash Effects2.dll


Go to solution Solved by silverdevil,

Recommended Posts

Posted

With the A-10C II I've had my first crash when the AGM hit the target (TTI Sinai 2.5.0a, track disabled, TGP + MAV feed). The only change made to the system was NV drivers, from 551.86 to 552.44, in NVcp I've set max performance and Vsync on (60 FPS).

W10 error:
Faulting application name: DCS.exe, version: 2.9.7.59263, time stamp: 0x66c380d4
Faulting module name: Effects2.dll, version: 2.9.7.59263, time stamp: 0x66c37b2f
Exception code: 0xc0000005
Fault offset: 0x0000000000034927
Faulting process ID: 0xb64
Faulting application start time: 0x01daf95cabf3d02a
Faulting application path: E:\sim\DCS World\bin-mt\DCS.exe
Faulting module path: E:\sim\DCS World\bin-mt\Effects2.dll
Report ID: 2598bd3f-556e-4e45-9b9d-7f782951d69c
Faulting package full name:
Faulting package-relative application ID:

Recently I've noticed that smoke effects have a huge impact on FPS, really noticeable when firing rockets with choppers, could this be the cause of the crash or maybe shaders/fxo compilation took too much?

Crash.jpg

dcs.log-20240828-153913.zipFetching info...

I7-12700F, 64GB DDR4 3600 (XMP1), Asus Z670M, MSI RTX 3070, TIR 5, TM WH VPC base, Win10 Pro

  • Solution
Posted
  On 8/28/2024 at 4:13 PM, BJ55 said:

With the A-10C II I've had my first crash when the AGM hit the target (TTI Sinai 2.5.0a, track disabled, TGP + MAV feed). The only change made to the system was NV drivers, from 551.86 to 552.44, in NVcp I've set max performance and Vsync on (60 FPS).

W10 error:
Faulting application name: DCS.exe, version: 2.9.7.59263, time stamp: 0x66c380d4
Faulting module name: Effects2.dll, version: 2.9.7.59263, time stamp: 0x66c37b2f
Exception code: 0xc0000005
Fault offset: 0x0000000000034927
Faulting process ID: 0xb64
Faulting application start time: 0x01daf95cabf3d02a
Faulting application path: E:\sim\DCS World\bin-mt\DCS.exe
Faulting module path: E:\sim\DCS World\bin-mt\Effects2.dll
Report ID: 2598bd3f-556e-4e45-9b9d-7f782951d69c
Faulting package full name:
Faulting package-relative application ID:

Recently I've noticed that smoke effects have a huge impact on FPS, really noticeable when firing rockets with choppers, could this be the cause of the crash or maybe shaders/fxo compilation took too much?

Expand  

hello. the DCS.log shows just before the crash scripting errors. i am seeing MOOSE errors too. you could try to remove the scripts and see what happens. you could also try to lessen the smoke density.

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

Thanks for the input, I will try your suggestions.

  • Like 1

I7-12700F, 64GB DDR4 3600 (XMP1), Asus Z670M, MSI RTX 3070, TIR 5, TM WH VPC base, Win10 Pro

Posted (edited)

Next time attach also the ..\Saved Games\DCS\Logs\dcs.log , from your .crash I suppose a grafic driver issue, see https://forum.dcs.world/topic/356816-one-day-one-or-two-freeze-and-crashes/#comment-5509622 and https://forum.dcs.world/topic/218023-acces-violation-crash/#comment-218492 , first try to rool back drivers (if NVidia don't use versions after 552.44).

@silverdevil : the effects2.dll crash was due to exhausted resources, with the current DCS release I've also had occasional big memory leaks and performance drops previously unnoticed, since they're already investigating...

Edited by BJ55
  • Like 1

I7-12700F, 64GB DDR4 3600 (XMP1), Asus Z670M, MSI RTX 3070, TIR 5, TM WH VPC base, Win10 Pro

Posted

Much appreciated. I will check out the links and see what I can do. I do remember updating my Nvidia drivers also recently. I will see if rolling them back will help. Thanks for your suggestions.

  • Recently Browsing   0 members

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