BS2 Random Mission Crash

[deltalord]

Just had a crash with the BS2 module using the SP random mission generator. Was not more than 10 minutes into it, when it CTD before I even got to the frontline.

 

First random mission I have done since 1.1.2.1, and its quite frustrating not having a clue what may have caused it.

In 1.1.2.1, I also suffered alot of CTDs during the random missions, and would

guess nearly half of them CTD at some point into them (usually after 40 minutes or more). Was flying just A10C then.

 

From using the F2 and F6 view I was watching a lot of missiles being fired among the AI.

No idea where to start to think about what may have caused it or how to reproduce.

 

Here is the Windows Event Log and I have attached the crash file.

 

Faulting application name: dcs.exe, version: 1.2.0.3205, time stamp: 0x4ff3450d

Faulting module name: d3d9.dll, version: 6.1.7601.17514, time stamp: 0x4ce7c5a4

Exception code: 0xc0000005

Fault offset: 0x0000000000011631

Faulting process id: 0x1c60

Faulting application start time: 0x01cd6d4a4454890b

Faulting application path: F:\DCSWorld\bin\dcs.exe

Faulting module path: C:\Windows\system32\d3d9.dll

Report Id: 7a7dc2df-d93f-11e1-9d5b-005056c00008

DCS-20120729-053725.rar

[deltalord]

I have had a horror night of CTDs in both Ka50, and A10C using the random mission generator.

Windows crash dialog references d3d9.dll as being the crashing module, and I seem to be getting these regularly using the mission generator. I have attached the crash dumps.

 

Unlike some others have mentioned, I do not crash online at all so far, I have spent quite a few hours on one server, using a training map and having fun with the A10, P51 and Ka50 without any such issues. Though the map is basic training so not a lot going on.

 

I'm not sure if this is a known issue that is going to be fixed or not but I decided to try to find some cause or at least a mission that would crash each time so it might be able to be fixed.

 

I decided to save each random mission track and then take control at start to try and get something that would crash both my machines. I managed to get one that crashes within a few minutes.

 

On my old PC, I originally set graphics to low and turned off everything except civilian traffic (thought it could be that), but during my first run I couldn't get it to crash. I then hit the High preset leaving it as follows:

 

Textures, Scenes, Water and Visi Range, Shadows at High

Civi Traffic OFF

Heat Blur ON

Cockpit Disp. Res 256

MSAA and HDR OFF

Default Sliders for High Preset

Only the Cockpit Shadows Ticked.

 

I simply took control of attached track at start, full throttle, gear/flaps up and turned to the left slightly to fly over some ground forces, put on autopilot and about 3 or so minutes later it CTD just as it did on my main PC at full graphics.

 

Haven't got any patience left tonight to see if any particular option does or doesn't cause it, hopefully a tester can reproduce this and find out whats going on. Should note also that I did put Combined Arms on both machines to try to match them DCS software wise. If I get time later in the week, I might run my copied directory before I installed it and see if it makes any difference without it.

 

Seem to be similar crash logs here

http://forums.eagle.ru/showthread.php?t=92200 and

http://forums.eagle.ru/showthread.php?t=92191 and

http://forums.eagle.ru/showthread.php?t=91722

and there are a few others I have seen.

Logs.rar

Crash Test.rar

[deltalord]

Just wanted to check something and found that the options used by the machine that makes the track overrides at least some of the running machines options.

 

I had said above my civi traffic was off on my old pc when it crashed but it was indeed actually on even though it is off in options. I assume the track records and uses options which means I cant narrow down specific options which may contribute to the crashes.

 

 

Edit:

 

Did some final testing. Flying slightly left and then straight doesn't seem to always work to reproduce. Circling the airfield immediately after takeoff with ~500 ft alt and alt hold on in a constant right banking circle over the area seems to crash the sim more consistently. Sometimes after 8 minutes, though on my last run a few mins ago, 1 min.

I also found that simply not taking off or touching anything doesn't seem to crash the sim at all. At least not in the several tries I put it through. After 10 to 15 mins or more no crash. Strange.

I would assume by now that this bug may be known but no ones confirmed it yet so I'd thought I'd figure out how to reproduce it in case it was required for testing. Hopefully the track does the same

on others machines as its done on both of mine.

Edited July 31, 2012 by deltalord
Test Update

[Speacy]

Same crash log here

 

Nom de l’application défaillante DCS.exe, version : 1.2.0.3205, horodatage : 0x4ff3450d
Nom du module défaillant : d3d9.dll, version : 6.1.7601.17514, horodatage : 0x4ce7c5a4
Code d’exception : 0xc0000005
Décalage d’erreur : 0x0000000000011631
ID du processus défaillant : 0xf6c
Heure de début de l’application défaillante : 0x01cd6e8d66dedcdd
Chemin d’accès de l’application défaillante : C:\Program Files\Eagle Dynamics\DCS World\bin\DCS.exe
Chemin d’accès du module défaillant: C:\Windows\system32\d3d9.dll
ID de rapport : 7f6e2554-da8e-11e1-a6ce-485b39760191

Nom de l’application défaillante DCS.exe, version : 1.2.0.3205, horodatage : 0x4ff3450d
Nom du module défaillant : d3d9.dll, version : 6.1.7601.17514, horodatage : 0x4ce7c5a4
Code d’exception : 0xc0000005
Décalage d’erreur : 0x0000000000010fa8
ID du processus défaillant : 0xdbc
Heure de début de l’application défaillante : 0x01cd6e87774a495c
Chemin d’accès de l’application défaillante : C:\Program Files\Eagle Dynamics\DCS World\bin\DCS.exe
Chemin d’accès du module défaillant: C:\Windows\system32\d3d9.dll
ID de rapport : 4f031288-da80-11e1-a6ce-485b39760191