D2M causing game crash

[microvax]

This bug still exists, its reproducable, I really dont get why this isnt fixed yet.

 

 

Slowly but surely loosing my trust here. I am not all up on the fence asking for features.

But fixing CTDs imho kinda should be a priority. :)

 

my 2 cents.

[Esac_mirmidon]

Could you please elaborate?

[microvax]

Could you please elaborate?

 

You can reproduce conditions, where too many IR detections CTD the game.

This can be either achieved by few launches and high rollrate or just a high number of launch events.

 

This is in for more then 8 months at this point. Its rare that it happens but its reproducible and its the second or third time I report it. :)

 

Thats why I am a little annoyed by it still beeing here and didnt elaborate too hard. :)

[Esac_mirmidon]

Interesting.

 

How many detections on average for CTD?

[microvax]

Interesting.

 

How many detections on average for CTD?

 

Last time I build a mission to reliably trigger it non maneuvering was like 24 launches fron aspect distributed.

 

In MP the issue usually happens when you have launches and roll fast with the sensor FOV on the launch. I think something crashes because its too many single events.

Thats why its kinda rare in MP.

 

I will build a reproduction mission tomorrow again if that gets it fixed. :)

[Esac_mirmidon]

Uhm.

 

24 ¡¡¡

 

Thats a lot of launch events. Is not a surprise to be so hard to detect. Good test from your side.

[microvax]

Here, load the mission punch the afterburner and watch. Crashes each time.

 

I think its not total launches, I am pretty sure its angular density of launches, which would also explain why it does crash with fast rolls against few launches.

 

With any other aircraft the crash doesnt happen, so its not a DCS issue.

do_not_tell_me_the_odds-make-crash.miz

Edited February 9, 2018 by microvax

[microvax]

here a crash log from a case where just 2 f15s aim120s and maneuvering is enough.

dcs.log-20180209-220731.zip

[Azrayen]

Here, load the mission punch the afterburner and watch. Crashes each time.

I'm trying this now :)

[edit] Reproduced! + info sent to Razbam.

 

I think its not total launches, I am pretty sure its angular density of launches

Hum, more simply, number of threats detected as seen by the D2M? You rolling = Detection/End Detection/Detection/End Detection... and so on, for the same threat.

Edited February 9, 2018 by Azrayen

[microvax]

Any update?

[unknown]

Uhm.

 

24 ¡¡¡

 

Thats a lot of launch events. Is not a surprise to be so hard to detect. Good test from your side.

It was alot worse, only one launcher! Fast forward to 2:20, this was posted here in the bug section almost one year ago https://forums.eagle.ru/showthread.php?t=187056

 

 

@microvax

I did not test it recently, but the last time in DCS 2.2.X i had less CTD with my first "problem child" the OSA(in the video above, DCS 1.5.x) but more with the TOR - SA-15 SAM. Placing 6 or 8 of them on the map and flying in their direction my DCS was crashing ~1-2 seconds after they launched their missiles(2.2.x on normandy), even with the D2M turned off if i remember correct. I will give it another try tomorrow. With what SAM systems do you test this problem?

[unknown]

I did a little test today in DCS 2.5 open beta latest patch. I placed a couple of OSA SAM systems but had no crash. After that i switched the OSA to SA-15 Tor and didn't get a crash. The interesting part is if i place the SA-15 TOR as a group (first pic, 1 of 13 units) i had several tries and no crash, but only one of the 13 units fired at me. As soon as i placed the SA-15 as single units(second pic) all of them fired at me at the same time and i got a CTD(LOG attached). It shows the same error that Zeus found in my log months ago in an ED dll.

2018-04-07 08:00:03.966 INFO    EDCORE: D:\DCS World OpenBeta\bin\edCore.dll
2018-04-07 08:00:03.968 INFO    EDCORE: # C0000005 ACCESS_VIOLATION at 8B600BE2 00:00000000

But after i restarted DCS and tried the same mission again(which first crashed) i didn't get a CTD this time, i got obliterated by them. :D

 

I will continue testing if i get some more time to :joystick: