A-10C II Crash to desktop round three...

[Ramses823]

After the recent update I have had three CTDs flying the A-10C II. It only seems to happen after flying for about two hours on the NTTR map,(note: I have not flown on other maps since the update),  I had a mission where I was doing air to refueling and BFM after I would say 1 hour and 45 minutes without warning I mean no stutters or anything then out of nowhere CTD, then after that I built an air to ground training mission on the NTTR map once again everything was going smooth as butter then bam CTD no warning or anything... I even rolled back my Nvidia driver then tried to replay the same mission once again CTD after two hours and like I said no stutter or anything nor did it happen as I was releasing weapons every time it has happened, I have been in the midst of simply flying... The only other time I have had a CTD was after the previous update with the F-16C on the Persian Gulf map at that time it started stuttering then I got a CTD but it only happened once and I never had the issue again, so up until this recent update I have had no problems running DCS at all and nothing about my system has changed except, the recent update....

I did send a crash report here are the logs I hope i am sending the right thing as I have never sent any logs before

dcs.log-20230316-193617.zip dcs.log

[Ramses823]

Here are my computer details.

Device name    DESKTOP-VE3PPC6
Processor    Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz   2.59 GHz
Installed RAM    16.0 GB (15.9 GB usable)
Device ID    50947FF0-C356-4E40-8BDB-155E33F2B47A
Product ID    00325-81338-25768-AAOEM
System type    64-bit operating system, x64-based processor
Pen and touch    No pen or touch input is available for this display
 

[Flappie]

Hi. You crash happens right after a "wcTanker:onEvent5" condition. This is tied to air-refueling and it looks like a DCS bug (I see no sign of lack of memory, nor PC unstability).

Were you the one refueling when you crashed?

2023-03-16 19:36:16.525 WARNING LOG (2992): 13 duplicate message(s) skipped.
2023-03-16 19:36:16.525 INFO    EDCORE (Main): (wcTanker::Channel)enterToState_:6
2023-03-16 19:36:16.525 INFO    EDCORE (Main): (wcTanker)enterToState_:3
2023-03-16 19:36:16.525 INFO    APP (Main): wcTanker::onEvent:1
2023-03-16 19:36:16.540 INFO    APP (Main): wcTanker::onEvent:5
2023-03-16 19:36:16.553 INFO    EDCORE (Main): try to write dump information
2023-03-16 19:36:17.058 INFO    EDCORE (Main): # -------------- 20230316-193617 --------------
2023-03-16 19:36:17.058 INFO    EDCORE (Main): DCS/2.8.3.37556 (x86_64; Windows NT 10.0.19045)
2023-03-16 19:36:17.059 INFO    EDCORE (Main): C:\Program Files (x86)\Steam\steamapps\common\DCSWorld\bin\DCS.exe
2023-03-16 19:36:17.059 INFO    EDCORE (Main): # C0000005 ACCESS_VIOLATION at 00007ff712926804 00:00000000
2023-03-16 19:36:17.062 INFO    EDCORE (Main): SymInit: Symbol-SearchPath: 'C:\Program Files (x86)\Steam\steamapps\common\DCSWorld\bin;', symOptions: 532, UserName: '17022'
2023-03-16 19:36:17.063 INFO    EDCORE (Main): OS-Version: 10.0.19045 () 0x300-0x1
2023-03-16 19:36:17.064 INFO    EDCORE (Main): 0x0000000000526804 (DCS): SW + 0x907B4
2023-03-16 19:36:17.065 INFO    EDCORE (Main): 0x00000000005714b4 (DCS): SW + 0xDB464
2023-03-16 19:36:17.065 INFO    EDCORE (Main): 0x000000000057607c (DCS): SW + 0xE002C
2023-03-16 19:36:17.066 INFO    EDCORE (Main): 0x00000000005a8310 (DCS): SW + 0x1122C0
2023-03-16 19:36:17.067 INFO    EDCORE (Main): 0x0000000000577a70 (DCS): SW + 0xE1A20
2023-03-16 19:36:17.067 INFO    EDCORE (Main): 0x0000000000003b63 (World): wSimTrace::CommandsTraceDiscreteIsOn + 0x4C3
2023-03-16 19:36:17.068 INFO    EDCORE (Main): 0x0000000000004074 (World): wSimCalendar::DoActionsUntil + 0x204
2023-03-16 19:36:17.068 INFO    EDCORE (Main): 0x0000000000873158 (DCS): SW + 0x3DD108
2023-03-16 19:36:17.068 INFO    EDCORE (Main): 0x0000000000872e21 (DCS): SW + 0x3DCDD1
2023-03-16 19:36:17.068 INFO    EDCORE (Main): 0x00000000008943c9 (DCS): SW + 0x3FE379
2023-03-16 19:36:17.068 INFO    EDCORE (Main): 0x0000000000852674 (DCS): SW + 0x3BC624
2023-03-16 19:36:17.068 INFO    EDCORE (Main): 0x0000000000853554 (DCS): SW + 0x3BD504
2023-03-16 19:36:17.069 INFO    EDCORE (Main): 0x000000000235ee4f (DCS): AmdPowerXpressRequestHighPerformance + 0xFB9E4B
2023-03-16 19:36:17.069 INFO    EDCORE (Main): 0x0000000000c512c2 (DCS): SW + 0x7BB272
2023-03-16 19:36:17.069 INFO    EDCORE (Main): 0x0000000000017614 (KERNEL32): BaseThreadInitThunk + 0x14
2023-03-16 19:36:17.870 INFO    EDCORE (Main): Minidump created.
2023-03-16 19:36:17.870 INFO    Lua::Config (Main): stack traceback:

 

We need to make sure your crashes are caused by the "wcTanker:onEvent5" condition. Please keep attaching your dcs.log here if you keep having crashes.

One thing to try: remove all tankers from your training mission and see if DCS keeps crashing.

[Ramses823]

 when I refuel my wingman gets stuck on the tanker so I refuel first then I push on with my mission and maby about 20 min later he makes the call he is done refueling, to be honest the A-10C ii wingmen Always gets stuck on the tanker I figured that's just a bug that DCS has to get worked out in due time but it's not a deal breaker to me so I don't usually pay it any mind however normallly he is stuck on the tanker on for a while then he rejoins but I did notice on my last session he said going RTB instead of saying he is going to rejoin after he was done refueling but I was already in the midst of finishing my bombing run and was about to go RTB myself so I didn't think much of it.... 

I'm going to try the same mission again but this time, after I refuel I will bring my wingman with me instead of telling him to hit the tanker and I will see if it crashes again.  If it does I will send that log then I will try one with no tankers..  

[Flappie]

That matches an internal report I've read about a very similar crash. It was supposed to be fixed in late 2022, but I guess it was not .

What we need now is a Caucasus track showing the AI refueling issue. Can you please try to make one? I tried but the AI A-10C II doesn't get stuck.

AI A-10CII refueling OK.trk

[Ramses823]

OK what I will do is 1st refly the Nellis mission without telling my wingman to hit the tanker to see if I still get the CTD and I'll see what the results of that are, then  I will build a A-10C ii mission on the caucus map to see if the AI wingman will refuel and I'll post the logs for that.....

[Ramses823]

Ok so I replayed, the NTTR Mission but this time I hit the tanker and didn't tell my wingman to go to refuel, when I was done refueling, as I left the tanker track he rejoined on me, and I continued with the rest of the mission and I was up by the 76 ranges and made it back to maybe 15 miles from Gass Peak at this point I told the AI wingman to anchor here. from that point right as I made it to Gass Peak it crashed on me.. I thought I was going to make it all the way back to Nellis without a CTD  because this is the furthest I have made it as far as this mission goes. I do have some other AI assets set to orbit here points just so I have other assets flying around the map so I don't know if maybe one of them hit the tanker and caused it to crash or maybe the A-10C ii wingmen not refueling is it's own issue and some other bug maybe causing the CTD, however this is the furthest that I have made it in the mission because normally the CTD comes when I'm still in the 76 ranges but I don't think the 76 ranges is the issue because on the BFM mission I did a few days ago I was over the 60 ranges.... Tomorrow I'll build the Caucasus mission and see what happens as well as trying the NTTR mission without tankers...

dcs.log-20230317-010333.zip

[Flappie]

Very interesting. It seems the crash happens whenever events 1 and 5 are executed one after the other:

2023-03-17 01:03:32.736 INFO    APP (Main): wcTanker::onEvent:1
2023-03-17 01:03:32.752 INFO    APP (Main): wcTanker::onEvent:5
2023-03-17 01:03:32.764 INFO    EDCORE (Main): try to write dump information
2023-03-17 01:03:33.258 INFO    EDCORE (Main): # -------------- 20230317-010333 --------------
2023-03-17 01:03:33.258 INFO    EDCORE (Main): DCS/2.8.3.37556 (x86_64; Windows NT 10.0.19045)
2023-03-17 01:03:33.259 INFO    EDCORE (Main): C:\Program Files (x86)\Steam\steamapps\common\DCSWorld\bin\DCS.exe
2023-03-17 01:03:33.260 INFO    EDCORE (Main): # C0000005 ACCESS_VIOLATION at 00007ff712926804 00:00000000
2023-03-17 01:03:33.263 INFO    EDCORE (Main): SymInit: Symbol-SearchPath: 'C:\Program Files (x86)\Steam\steamapps\common\DCSWorld\bin;', symOptions: 532, UserName: '17022'
2023-03-17 01:03:33.264 INFO    EDCORE (Main): OS-Version: 10.0.19045 () 0x300-0x1
2023-03-17 01:03:33.265 INFO    EDCORE (Main): 0x0000000000526804 (DCS): SW + 0x907B4
2023-03-17 01:03:33.266 INFO    EDCORE (Main): 0x00000000005714b4 (DCS): SW + 0xDB464
2023-03-17 01:03:33.267 INFO    EDCORE (Main): 0x000000000057607c (DCS): SW + 0xE002C
2023-03-17 01:03:33.268 INFO    EDCORE (Main): 0x00000000005a8310 (DCS): SW + 0x1122C0
2023-03-17 01:03:33.269 INFO    EDCORE (Main): 0x0000000000577a70 (DCS): SW + 0xE1A20
2023-03-17 01:03:33.269 INFO    EDCORE (Main): 0x0000000000003b63 (World): wSimTrace::CommandsTraceDiscreteIsOn + 0x4C3
2023-03-17 01:03:33.270 INFO    EDCORE (Main): 0x0000000000004074 (World): wSimCalendar::DoActionsUntil + 0x204
2023-03-17 01:03:33.270 INFO    EDCORE (Main): 0x0000000000873158 (DCS): SW + 0x3DD108
2023-03-17 01:03:33.270 INFO    EDCORE (Main): 0x0000000000872e21 (DCS): SW + 0x3DCDD1
2023-03-17 01:03:33.270 INFO    EDCORE (Main): 0x00000000008943c9 (DCS): SW + 0x3FE379
2023-03-17 01:03:33.270 INFO    EDCORE (Main): 0x0000000000852674 (DCS): SW + 0x3BC624
2023-03-17 01:03:33.271 INFO    EDCORE (Main): 0x0000000000853554 (DCS): SW + 0x3BD504
2023-03-17 01:03:33.271 INFO    EDCORE (Main): 0x000000000235ee4f (DCS): AmdPowerXpressRequestHighPerformance + 0xFB9E4B
2023-03-17 01:03:33.271 INFO    EDCORE (Main): 0x0000000000c512c2 (DCS): SW + 0x7BB272
2023-03-17 01:03:33.271 INFO    EDCORE (Main): 0x0000000000017614 (KERNEL32): BaseThreadInitThunk + 0x14
2023-03-17 01:03:34.078 INFO    EDCORE (Main): Minidump created.

I don't know what these events are exactly.

It is weird that this crash does not produce a track. Can you please ensure your don't have this line in your "Saved Games/DCS.../Config/autoexec.cfg" file ?

disable_write_track = true

Edited March 17, 2023 by Flappie

[Ramses823]

OK I will do that and I'm going to completely rebuild the NTTR mission from scratch basically I have a baseline template that I use with assets already placed that I use whenever I build a mission so I don't have to rebuild everything from scratch so I'm just going to start everything fresh I did notice with the F-16 on the persion gulf map when DCS first implemented the new lighting effects any old missions would not render a air to ground map image but if I started a fresh mission from scratch the problem went away so I basically had to start over and build a new a persion gulf template frustrating to say the least but I understand that it has got to be incredibly difficult to weed out every single bug that may come with a update and quite frankly the whole purpose of DCS beta is to have the community test updates out so the DCS team can identify and fix any bugs for the stable version, so I'll try what you said and I'm going to start the NTTR mission from scratch and I'll get back to you with the results..

[Ramses823]

dcs.log-20230316-193617.zipdcs.log.old

I checked for the auto excel file and there isn't one so I guess that's why it's not creating a track file but I am not familiar with track files as I  have never sent one I don't know if you can send me a copy of the the file so I can place it in the folder and get a track file.... I completely rebuilt the mission and from scratch this time and I had a flight of AI F-117s orbiting by Tonopah test range, I also set a tanker just outside of the 70's ranges by the time I got the A-10 started at Nellis 45 min ( I go so far as naming weapons profiles so it's a lengthy start up) and flew up to the tanker track I set up, the F-117s were on the tanker refueling which surprised me so I flew off tankers wing for a while to see if they would get there fuel and depart the tanker track but they didn't so I pushed into the 70's ranges at which point I once again got the CTD but it happened quicker than it did yesterday... Now with the mission I flew the other day I had a flight of F-117s orbiting as well but I had them placed further from the tanker which is why I think the CTD happened a little later in the mission the other day so right now my best guess is the AI F-117s are causing this CTD however I can't confirm right now if the F-1117 flight went to the tanker yesterday and caused the CTD or if another AI flight went to the tanker and caused the CTD... so now I'm going to replay the mission whith no AI assets airborne except for a tanker for me to refuel on, and if I don't get a CTD then the issue is clearly some kind of conflict with AI assets refueling on the NTTR map, now I'm not sure if this extends to any maps beyond NTTR as I have not tried them since the update...

dcs.log

Edited March 17, 2023 by Ramses823

[Ramses823]

Well my Job is done for the First time in days I got the A-10C ii to fly a complete mission on the NTTR map... It looks like the Issue has to do with AI assets trying to refuel for some reason it causes a crash to Desktop so basically on this mission the only aircraft I had flying were me my AI wingman and the tanker. On this one when I was done  refueling I didn't send him to the tanker I had him rejoin on me so it looks like one of the crashes came from a mission where I refueled then sent him to refuel then when he got stuck on the tanker, I pushed on with my mission I heard him call RTB then shortly after came the CTD. Now for the mission before this one I just did I went to the tanker seen a flight of F-117s stuck on the tanker so I pushed on then shortly after CTD and with this successful mission I just did no AI assets were in the air except for the tanker and my wingman who I did not allow to refuel and what do you know no CTD... so I'll be flying solo till the DCS team can get a fix for it....

Edited March 18, 2023 by Ramses823

[Flappie]

Many thanks for your tests. I still need a Caucasus track to show this bug to devs. I'll try to make one but I suck hard a refueling. It might take some time...

[Flappie]

I cannot replicate your issue with A-10C II wingman refueling. Please attach your NTTR mission and I'll go from there.

A-10CII_refuel with AI.trk

[Ramses823]

I can run the A-10 refueling test on the Caucasus map the only thing I is know you said there was no tracks with the crash logs I sent you so you would have to explain to me what I need to do to create a track.... by the way the only maps I can confirm the A-10 refueling problem is on the Syria map,Persion Gulf map, and the Nellis map, if you can tell me how to create a track I can run it across the board including the Caucasus map.. it might take me a week to complete though as I owe my girl for some lost time... she doesn't appreciate DCS like I do ...

[Ramses823]

OK give me a second I'll get my computer fired up and I'll send you the original NTTR mission..

[Flappie]

Ah, girls... they're almost all the same when it comes to DCS!

Usually, when DCS crashes, it embeds the track in the zip file. Since it does not in our case, you need to reproduce the conditions for the crash to happen, then exit the mission when your know for sure the failure will happen, then click the "Save Track" button (in the  Debriefing page).

[Ramses823]

it keeps telling me the mission file is too large I even tried to compress it..  Maby if I delete some of the static aircraft on the ramp I can get the file size down...

[Ramses823]

I just created a new mission on the NTTR map with the A-10C ii and got my wingman to refuel I'm going to run it a few more times and I'll see what happens

[Ramses823]

I just ran the refueling test again and I'm not having a problem getting my wingman to refuel any more...

As far as the CTD issue I think that's being triggered by one of the AI assets because when I removed all the AI assets I didn't get a CTD... 

[Ramses823]

I just ran a very interesting test I sped time up and went to external view on a flight of F-117s to see what they would do and at 14:10 they went to the tanker and at 14:39 they were still on the tanker then the screen froze and I got the CTD... I'm about to send you the log on that one if you create a mission on the NTTR map and set a flight of F-117s to orbit and speed up time you should be able to recreat the circumstances.. I'm going to run it again when the F-117s go to the tanker I will go to the debrief and save the track file and send it to you...

Edited March 18, 2023 by Ramses823

[Ramses823]

dcs.log-20230318-150142.zip

[Ramses823]

I have the track file but it's 104 MB and the max file size is 50MB is there some other way I can send it to you?   by the way when I ran this test I watched a AI flight of f-16's hit the tanker with no problem so the issue is defiantly with the AI f-117s refueling... I also ran the the A-10 wingman refueling test again and there is no problem with the A-10C ii wingman refueling  I think I got the false impression there was a problem with my wingman being stuck on the tanker but I realize I simply wasn't being patient enough as it took a little while before he refueled because of the distane so that was completely on me.

[Flappie]

Sure, you can use a tool such as WeTransfer then send me the link.

[Flappie]

On my end, F-117 are refueling just fine.

I'll see what your track shows.

F-117 refueling OK.trk

[Ramses823]

https://we.tl/t-TYlhlIGGNd

this is about maybe 15 min before the CTD