deltalord

NineLine, I have done some additional testing. It looks like it has nothing to do with B17's as such, but possibly how close a formation is flying together. The original group of B17s I added in the test mission were in close WW2 bomber formation so I thought about testing this part out. I replaced the B17s with Su27s and was able to replicate it in the close WW2 bomber formation. Selecting other formation options with them being spread further apart seemed to allow the lock to break several seconds after pressing the undesignate button, with them being out of radar view. All of the WW2 formations and the modern bomber formations seemed to cause the problem, as did close other formation types.

I have a training / test map that has everything in it, including a formation of 4 B17s in a circle for gun practice for the WW2 stuff. While flying the Hornet yesterday, I encountered some strange behavior of the radar. I was messing around with TWS / RWS, randomly trying to lock/bug targets while heading to an area where I have some ships to destroy and found that afterwards, every press of the undesignate button would lock back onto the formation, no matter if they were 180 degrees behind me. I was able to recreate this in a simple test mission and the track also shows this strangeness. It seems to happen even after turning off the datalink, and also continues after landing while also messing with the NWS. I started off with a group of Su-27s on the test but could not replicate it until I set it to B17s afterwards. Not sure if any other aircraft can cause this. Also, I could not replicate this in further tests, but when I originally had this happen yesterday, it broke the radar completely after attempts to work out why it was tracking targets behind me. Pushing the Bars button would only increase the amount of bars being scanned, as in I had 100+ Bars and it was taking minutes to scan before it would reset back to the top again according to the arrow on the right side of the radar (each sweep pushed it down very slowly). Further, the radar azimuth in degrees was giving amounts of 22 degrees, 44 degrees etc, and then after wrapping around at something like over 200 degrees, would change the end unit to a different number, eg 24, 44 etc. Sadly I have not yet replicated this part of the oddness. RadarTestB17.trk test.miz

Just thought I'd also add to say I also have had this issue as described exactly above with the C++ runtime error, uh1h protect error and then straight after the zweiblau error (of it not zweiblau some other dcs dll is referenced which seems rather random). I was playing online on the AEF161 playground mission and it occurred every single time I tried to select any F15C in the Springfield grouping of them. The plane would start to load begin to zoom out for about a second then it crashed with the error. Upon restarting I would try again and it would crash again. I had to chose another F15 group from a different start location before I could fly it. Tried repeating this morning but unfortunately it's not doing it right now. I was flying the huey then the mi8 for a bit beforehand yesterday when I decided to switch to the F15 , and there were a couple of others on as well which may or may not have influenced the crashes.

Might just have to give it away for the time being and hope future versions correct whatever has happened. This did not happen in 1.1.2.1, and only started in 1.2.0. Older machine on amd/ati 12.3 drivers (5850) New machine on amd/ati 12.8 drivers (7970) Seems that some are also having this crash on nvidia also. Thanks for trying though with the suggestions , I'm just as stumped. No other problems with any other game or program.

Just did full reinstall with just DCSW 1.2.0. and the A10C Module. Nothing else. Went to settings and turned off the disable aero, and set a few other realism options to how I would have it normally setup. Copied test track to newly created DCS save folder after renaming old folder. First flight CTD again within half a minute after takeoff banking right, over the nearby town / city. Windows control panel says both x86 and x64 versions of the Visual C 2010 libraries are at version 10.0.30319. The test track was made on my new PC, which crashes with the same crash every time I have tried the random mission generator. I exited one random mission 30 seconds into it, and use that track as my test track, as luckily it crashes fairly easily with this d3d9.dll crash. I thought maybe the track itself is broken, but since it lasted 30 seconds and this crash occurs after taking control and beyond the end point of the track anyway, I can't see the test track being the issue. Also it wouldn't explain the original crashes before I saved that track to test this issue with.

PC specs should be in the DXDiag.txt file for my test machine. Its an older machine now but can run DCS at medium settings for testing things out fairly well with a little stutter. I'll try a full reinstall and see what happens, but I don't have anymore time today. Hopefully by weekend I'll report back with results. As for tacview, I only installed it to find a possible cause for this CTD, so it is certainly not tacview. When I viewed the exports, I could not see anything that stood out.

I ended up doing the full package install, removing the old 2010 VC libraries and letting the full SDK package install. Did 2 quick test flights a few nights ago and it didn't crash (5 mins each). Though as I've said my test track doesn't necessarily crash each time, just most (75%). I shut down the machine and it did an update of the 2010 VC, some security update I believe it said at the time. Tonight I have had some time and given it another test, and first flight ended up CTD within 30 seconds after takeoff. :(

I will try it and see what happens over the next few days on my test machine. I doubt the SDK is the fix on its own as more people would have this issue surely. I'm guessing the VC reinstall to the older version is more likely the fix, so i'm going to go that way first as I can't see why an end user would ever need the SDK anyway. I also would be concerned about this older VC version being updated again through either windows update or another game installation and DCS not working if the newer version doesn't work well with DCS.

I had feared you might not be able to replicate it if you haven't had this CTD before, considering I have got it every random mission flight I have tried to fly in 1.2.0 excepting one where it CTD with weapons.dll. I did as requested and installed the specific DX9 and Visual C libraries. DX9 installed as expected OK. The x86 version of the C libraries could not install because it detected a newer version, and I clicked "repair" on the x64 version to "install it to its original state". I cleaned out the DCS Save folder and let it recreate it, then started the sim. First 2 flights were with the disable aero nonsense on by default, and it did not crash. Sometimes my test track doesn't crash, but 75% chance it does and fast (within 1 min of takeoff). Then I disabled the "disable aero" option and selected HDR (closer to normal settings rather than the defaults from the clean out) and flew (not sure how much options are overridden using the saved track file). It lasted longer than 1 minute which is good, but died after another minute. I am about to upload the logs directory and a fresh DXDiag dump. I will test this again when I have alot more time to spend on it with aero disabled and see what happens. Maybe something to it, maybe not. But I would assume most would turn this thing off anyway? No idea at all on this one, as said previously a simple multiplayer map with simple target areas has so far given me no grief. I have even gone into mission editor and "created chaos" by adding a huge number of units in an all out battle over a tiny zone hoping it would trigger something. No crash. But every random mission generator flight CTD as I head to battle. On my test track sometimes NOT taking off would not trigger a CTD after an hour, but in some tests it did (I'd say ~4 out of 15 tests of not taking off). :huh: Edit: Logs added. Includes entire DCS Save Directory and DXDiag.txt. DCS.rar

Thanks for looking at it. I cant play any random mission generator flight without a d3d9.dll crash. In post 2 of this thread http://forums.eagle.ru/showthread.php?t=93013 I have included some info and my crash logs, and my dxdiag txt file. I had another thread also which died fast where I saved the track from a random mission at the start and can usually cause a quick crash shortly after takeoff. I will test the track again tonight and see if I can easily cause it to crash again. Seems to happen when looking down upon the town / city below from a few hundred feet above in a right bank after takeoff. Also it doesn't usually crash just by not taking off. But it can and has done in my testing, just not often. Weird. Some notes: I did try reinstalling DirectX9 June 2010 but it made no difference, and the machine is fully up to date. Happens on 2 machines I own, both ATI cards, different driver versions, though I've seen in other threads that some have this crash on nvidia as well. EDIT: Got track to crash again first try, about 1 min after takeoff looking towards ground over city near runway, after turning to the right a fair way (maybe 180 deg from RW heading). If there is anything else needed info wise I'll try to give it. I've stopped playing DCS for now until its fixed, as sadly I can't finish a single flight and I normally use the Quick / Random mission generator to fly. The track I used is here http://forums.eagle.ru/showthread.php?t=92371, second post called crash test.rar. To crash it on my end I simply let camera zoom out at start, take control, turn the bank hold AP on, takeoff and immediately bank right with gear / flaps up at maybe 200 ft and look towards ground.

Yeah, I get this with nearly every single mission I have played single player with 1.2.0. I used the random mission generator alot previously and have not completed a single mission in 1.2.0. due to 90% this d3d9.dll crash. It happens normally for me 10 minutes into a mission as I am heading to battle. Had it happen in A-10C and BS2 modules. Haven't tried P-51. I also have had the odd weapons.dll crash further into the mission if I don't get the first crash happen. I exited one mission right at start, saved track and then took control to see if it would crash. When it did I copied it to another machine and could get it to crash on that as well, so it's to me not a PC issue on my end but something else. I am out of ideas with this, and although there are a few posts, including one I started which pretty much died, there is not a huge amount of people posting about this particular crash which is worrying in that I don't know if its known / fixed for next version etc. In the crash dumps I get 2 kinds of this crash. One leaves the 1 line of Direct3DCreate9Ex() and the other leaves 4 lines at the top part of the crash dump. Playing my saved track generates both randomly. Finally I can join an online server and play a simple mission with non moving targets in practice zones just fine. I have been enjoying one simple mission where I have not had a single crash yet. I can unload a fully armed A-10 on many targets in simple maps like this and have not had an issue as yet after several hours. It's like once a map becomes complex with AI doing its thing, it crashes on me. But as I said I just don't know whats causing it, only started in 1.2.0. In 1.1.2.1 I was affected often by weapons.dll crashes, but I could finish 50% of missions generated by the mission generator. Now I can't seem to finish one after about 6 - 8 attempts. EDIT: Ok, I crashed my test track in 45 seconds after takeoff. Attached is full logs directory after a clean out, and previous crash dumps with both the 1 line and 4 line crashes included. Also a DXDiag file is inside the rar as well. Crash Dumps.rar

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.

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

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

Same crash but different mission and after 45 minutes of playtime. SP-US Battalion Day Advance - Maykop.miz Not sure if this mission has also been known to crash but I thought I'd post this anyway for info / beta testing feedback. Better mention also I am using the updated version of the missions. Faulting application name: dcs.exe, version: 1.2.0.3205, time stamp: 0x4ff3450d Faulting module name: Weapons.dll, version: 1.2.0.3205, time stamp: 0x4ff3450e Exception code: 0xc0000005 Fault offset: 0x000000000003c999 Faulting process id: 0xd20 Faulting application start time: 0x01cd625f5a55e5ee Faulting application path: F:\DCSWorld\bin\dcs.exe Faulting module path: F:\DCSWorld\bin\Weapons.dll Report Id: 598221f5-ce59-11e1-aef1-005056c00008 # -------------- 20120715-084452 -------------- # C0000005 ACCESS_VIOLATION at E669C999 00:00000000 00000000 00000000 0000:00000000 E669C999 001CF040 0000:00000000 E66A42BD 001CF0E0 0000:00000000 E66A4096 001CF110 0000:00000000 E668CA86 001CF140 0000:00000000 E668E341 001CF2D0 0000:00000000 E6797351 001CF300 0000:00000000 ?deactivate@woShip@@UEAAXXZ()+1F1 EE938361 001CF390 0000:00000000 EE93882A 001CF3E0 0000:00000000 3FB44199 001CF470 0000:00000000 3FB4624D 001CF4D0 0000:00000000 3FB5C964 001CF500 0000:00000000 3FB5C848 001CF530 0000:00000000 3FBE08E8 001CF5A0 0000:00000000 3FBE1853 001CFA70 0000:00000000 3FBE4107 001CFB20 0000:00000000 76B6652D 001CFB50 0001:0001552D C:\Windows\system32\kernel32.dll BaseThreadInitThunk()+D 7700C521 001CFBA0 0001:0002B521 C:\Windows\SYSTEM32\ntdll.dll RtlUserThreadStart()+21