Unsolved CTD in AAR TE
-
I just experienced a CTD in the AAR training TE.
Version: BMS 4.37.3 (x64) Build 1329
Situation:
I was lead in the heavy training flight, refueled on the west coast, then flew across and refueled at the KC-10 on the East coast. I asked AWACS for a divert field and it sent me to Pohang. After having landed at Pohang the CTD happened while was taxiing back. Just before that, my jet was sluggish, I had to use afterburner to even get it to move on the taxiway.I will upload the dmp. This is the crash log (2023-11-16_154724_crash.txt):
================================== CRASHLOG ===================================== Falcon BMS.exe caused an EXCEPTION_ACCESS_VIOLATION in: 00000000047EC44E Falcon BMS.exe, DigitalBrain::TerminateRefuelEvolution()+78 byte(s), E:\BMS\bms-code\SIM\DIGI\Refuel.cpp, line 1552+7 byte(s) Exception handler called in UnhandledExceptionHandler. Read from location 0000000000000038 caused an access violation. Bytes at CS:RIP: 0F B6 42 38 84 C0 75 04 0F B6 42 39 3C 04 75 07 Registers: RAX=0x00000000e37e6100 RBX=0x00000000ffffffff RCX=0x000000003b0d50d0 RDX=0x0000000000000000 RSI=0x0000000471197450 RDI=0x0000000000000002 RBP=0x000000002f93ed60 RSP=0x000000002f93ec58 RIP=0x00000000047ec44e FLG=0x0000001a00010246 R8=0x00000000050cc0d0 R9=0x00000000ffffffff R10=0x0000000000008000 R11=0x000000002f93eb90 R12=0xffffffffffffffff R13=0x0000000000000001 R14=0x0000000000000002 R15=0x00000000e37e6100 CS=0x0033 DS=0x002B SS=0x002B ES=0x002B FS=0x0053 GS=0x002B Call Stack: 0033:00000000047EC44E Falcon BMS.exe, DigitalBrain::TerminateRefuelEvolution()+78 byte(s), E:\BMS\bms-code\SIM\DIGI\Refuel.cpp, line 1552+7 byte(s), Parameters(0x00000000E37E6100 0x000000002F93ED60 0x00000000050CC0D0 0x00000000FFFFFFFF) 0033:0000000004E07379 Falcon BMS.exe, FalconTankerMessage::Process()+6441 byte(s), E:\BMS\bms-code\FALCLIB\Messages\TankerMsg.cpp, line 636, Parameters(0x00000000A00B8F90 0x0000000000000000 0x00000000A00B8F90 0x0000000000000000) 0033:0000000004C74F9C Falcon BMS.exe, VuMessageQueue::DispatchVuMessage_FromDrain()+236 byte(s), E:\BMS\bms-code\vu2\src\vuevent.cpp, line 379+72 byte(s), Parameters(0x0000000000000004 0x000000001DA4E060 0x0000000000000000 0x000000001DA4E060) 0033:0000000004C7515E Falcon BMS.exe, VuMessageQueue::DispatchAllMessages()+270 byte(s), E:\BMS\bms-code\vu2\src\vuevent.cpp, line 429+7 byte(s), Parameters(0x00000000158CBC10 0x000000002F93F040 0x000000002F93F050 0x00000000097BDD30) 0033:0000000004C6908E Falcon BMS.exe, VuMainThread::Update()+1822 byte(s), E:\BMS\bms-code\vu2\src\vu.cpp, line 561, Parameters(0x0000000018149E30 0x0000000000000000 0x000000000153AB7C 0x00000000050B8590) 0033:0000000004AED253 Falcon BMS.exe, SimulationLoopControl::Loop()+2083 byte(s), E:\BMS\bms-code\SIM\SimLoop\Simloop.cpp, line 554+118 byte(s), Parameters(0x0000000000000000 0x000000000108001F 0x0000000000000000 0x0000000004AEC72A) 0033:0000000004529A9D Falcon BMS.exe, ThreadUnhandledExceptionWrapper()+109 byte(s), E:\BMS\bms-code\FALCLIB\ehandler.cpp, line 1588+5 byte(s), Parameters(0x000000002F0238B0 0x0000000000000000 0x0000000000000000 0x0000000000000000) 0033:0000000004F4E4AE Falcon BMS.exe, thread_start<unsigned int (__cdecl*)(void *),1>()+90 byte(s), minkernel\crts\ucrt\src\appcrt\startup\thread.cpp, line 97+23 byte(s), Parameters(0x0000000000000000 0x0000000000000000 0x0000000000000000 0x0000000000000000) 0033:0000000040017344 KERNEL32.DLL, BaseThreadInitThunk()+20 byte(s), Parameters(0x0000000000000000 0x0000000000000000 0x0000000000000000 0x0000000000000000) 0033:00000000414426B1 ntdll.dll, RtlUserThreadStart()+33 byte(s), Parameters(0x0000000000000000 0x0000000000000000 0x0000000000000000 0x0000000000000000) Top of Stack: 0x000000002F93EC58: 0000000004E07379 00000000E37E6100 000000002F93ED60 00000000050CC0D0 ys.......a~.....`../............ 0x000000002F93EC78: 00000000FFFFFFFF 00000000E37E6100 000000000506FF38 00000003B02F2E00 .........a~.....8........./..... 0x000000002F93EC98: 000000000269B3EA 000000050000000D 0000000019533842 6137303030307830 ..i.............B8S.....0x00007a 0x000000002F93ECB8: 30303030303A6339 0000000000303030 00000003B02F2E00 0000000000000000 9c:00000000......./............. 0x000000002F93ECD8: 0000000000000013 000000000000001F 00000003B02F3100 0000000000000000 .................1/............. 0x000000002F93ECF8: 0000000000000000 000000000000000F 000000044899E162 0000000000000001 ................b..H............ 0x000000002F93ED18: 0000000000000000 30303A31313A3630 000000003430362E 0000000471197450 ........06:11:00.604....Pt.q.... 0x000000002F93ED38: 0000000000000000 000000000000000D 00000004B0813310 000000002F93EE60 .................3......`../.... 0x000000002F93ED58: 0000000004579D8F 00000000180A4000 00007FFC41415BA1 0000000000008CCD ..W......@.......[AA............ 0x000000002F93ED78: 000000002F93EE00 000000000153BF04 0000000000047F45 0000000300000000 .../......S.....E............... 0x000000002F93ED98: 0000000000008CCD 000000047EB22630 000000000000005D 0000000000004E35 ........0&.~....].......5N...... 0x000000002F93EDB8: 00000004A00B74F0 000000041325B000 000000000F26B690 0000000000180000 .t........%.......&............. 0x000000002F93EDD8: 000000000000000A 0000000000000000 0000000470FC2C50 0000000000000000 ................P,.p............ 0x000000002F93EDF8: 0000000000000001 0000000000000001 0000000000000000 0000000018149E30 ........................0....... 0x000000002F93EE18: 0000000000000000 00000004A00B9830 00007FFC414147B1 0000000000000001 ........0........GAA............ 0x000000002F93EE38: 0000000000530000 0000000000000000 0000000000000000 0000000000000000 ..S............................. 0x000000002F93EE58: 000000001DA4E060 0000000000000000 0000000000000000 3FA99999A0000000 `..............................? 0x000000002F93EE78: 0000000000000000 0000000471197450 0000000000000001 0000000000000000 ........Pt.q.................... 0x000000002F93EE98: 0000000018149E30 0000000000000000 000000001DA4E060 0000000000000000 0...............`............... 0x000000002F93EEB8: 00000004A00B8F90 0000000000000000 0000000004C74F9C 00000004A00B8F90 .................O.............. 0x000000002F93EED8: 0000000000000000 00000004A00B8F90 0000000000000000 00000000050B7510 .........................u...... 0x000000002F93EEF8: 0000000004C7515E 0000000000000004 000000001DA4E060 0000000000000000 ^Q..............`............... 0x000000002F93EF18: 000000001DA4E060 00000000050B8590 0000000000000008 00000000050B7510 `........................u...... 0x000000002F93EF38: 0000000004C6908E 00000000158CBC10 000000002F93F040 000000002F93F050 ................@../....P../.... 0x000000002F93EF58: 00000000097BDD30 0000000470FC2C60 00007FFC00008014 0000000000008014 0.{.....`,.p.................... 0x000000002F93EF78: 000000000A090201 00007FFC3A2D98C8 0000000000000000 0000000470FC2C60 ..........-:............`,.p.... 0x000000002F93EF98: 00007FFC414147B1 0000000000008014 0000000000530000 00007FFC3A2D9748 .GAA..............S.....H.-:.... 0x000000002F93EFB8: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ................................ 0x000000002F93EFD8: 00000004A070F070 00000004A070F080 0000000000000000 0000000000000000 p.p.......p..................... 0x000000002F93EFF8: 00007FFC41415BA1 0000000000530000 0000000000530000 0000000000000000 .[AA......S.......S............. 0x000000002F93F018: 0000000000530000 0000000000000000 0000000000000000 00000000E3774B00 ..S......................Kw..... 0x000000002F93F038: 000000000000005A 0000000470FC2C60 00000000E3BB2090 0001000000000028 Z.......`,.p..... ......(....... 0x000000002F93F058: 4100C13BEC87F1E3 0000000000180000 0000000000000000 0000001400000000 ....;..A........................ 0x000000002F93F078: 00000B0A12AB5CE1 0000000000000001 0000000000000000 0000000000000000 .\.............................. 0x000000002F93F098: 0000000000000000 00000004A070F080 00007FFC414407C0 00000000E3BB5930 ..........p.......DA....0Y...... 0x000000002F93F0B8: 00007FFC414147B1 0000000000000001 00007FFC3F081DE0 00007FFC3A2D9748 .GAA...............?....H.-:.... 0x000000002F93F0D8: 0000000000000000 0000C19E568FF185 00007FFC3F081DE0 0000000000000000 ...........V.......?............ 0x000000002F93F0F8: 00007FFC3E8650A9 0000000000000000 0000000000225000 0000000000000000 .P.>.............P"............. 0x000000002F93F118: 0000000000000001 0000000000000000 0000000000225000 0000000000000002 .................P"............. 0x000000002F93F138: 0000000000000001 0000000000000000 0000000000000000 0000000000000048 ........................H....... 0x000000002F93F158: 0000000000000001 0000000000000000 0000000000000000 0000000000000000 ................................ 0x000000002F93F178: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ................................ 0x000000002F93F198: 0000000000000001 0000000000000000 0000020000000000 459774DF00000000 .............................t.E 0x000000002F93F1B8: 0000000000000000 0000000000000000 0000000000000002 00000004A070F080 ..........................p..... 0x000000002F93F1D8: 459774DFC4FB84C5 00000012C652AF4B 00007FFC4141B86B 0000000000000000 .....t.EK.R.....k.AA............ 0x000000002F93F1F8: 0000000000000000 000000002F93F2A0 FFFFFFFFFFFFFFFF 0000000000000000 .........../.................... 0x000000002F93F218: 00000000E3BB5930 00000000E3BB4AD0 0000000000180D20 00000000E3BB5930 0Y.......J...... .......0Y...... 0x000000002F93F238: 0000000000000000 0000000000000000 0000000000001810 003800630065007B ........................{.e.c.8. 0x000000002F93F258: 00007FFC4142E26F 00310063002D0033 0034002D00620033 002D003000300031 o.BA....3.-.c.1.3.b.-.4.1.0.0.-. 0x000000002F93F278: 0037006600350062 003800620038002D 0034003500640034 0063000000360000 b.5.f.7.-.8.b.8.4.d.5.4...6...c. 0x000000002F93F298: 00000000007D0062 0000000000000000 0000000000000000 0000000200180000 b.}............................. 0x000000002F93F2B8: 0000000000000002 0000000000000090 0000000000000000 0000000000000000 ................................ 0x000000002F93F2D8: 00007FFC414407C0 0000000200000000 00007FFC414407C0 FFFFFFF0FFFFFFA0 ..DA..............DA............ 0x000000002F93F2F8: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ................................ 0x000000002F93F318: 0000000000000000 0000000000000000 00007FFC41415BA1 0000000000000000 .................[AA............ 0x000000002F93F338: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ................................ 0x000000002F93F358: 0000000000000000 00000000E3774B00 0000000000000043 0000000000000000 .........Kw.....C............... 0x000000002F93F378: 00000000E3BB2090 0000000000000000 0000000000000000 0000000000180000 . .............................. 0x000000002F93F398: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ................................ 0x000000002F93F3B8: 0000000000000000 0000000000000000 0000000000000000 0000000000000001 ................................ 0x000000002F93F3D8: 00007FFC414407C0 00000000E3BB4AD0 00007FFC414147B1 0000000000000FDC ..DA.....J.......GAA............ 0x000000002F93F3F8: 0000000000530000 00007FFC3A2D9748 0000000000000000 0000C19E568FF2D5 ..S.....H.-:...............V.... 0x000000002F93F418: 0000000000000000 00000000E3BB4AD0 00007FFC3E864478 0000000000000000 .........J......xD.>............ 0x000000002F93F438: 00007FFC3E88D010 00000000E3BB4AD0 0000000000000000 0000000000000000 ...>.....J...................... ================================================================================ TLS frame allocator: 20695 allocations with 93469256 bytes [0] 0 allocations with 0 bytes [1] Renderer command count: 1948 Object at RCX(000000003B0D50D0) ================================================================================ Compiler Options: _MSC_VER=1937 WINVER=0x601 _WIN32_WINNT=0x601 _WIN32_WINDOWS=0x601 NTDDI_VERSION=0x6010000 _WIN32_IE=0x800 ANSI _M_AMD64 _AMD64_ _WIN64 Release* System Information: 'F:\Falcon BMS 4.37\Bin\x64\Falcon BMS.exe', run by Jorgen. Error occurred at 16:59:52 on 2023-11-16. Version: Falcon BMS 4.37.3 (x64) 1329 Game is Tactical Engagement type Local Theater terrain path: 'F:\Falcon BMS 4.37\Data\Terrdata\korea' Operating System: Windows 10 (10.0.19045) Platform 2 . Computer Name: JORGENPC Domain: WORKGROUP. 8 logical processor(s), type 8664. CPU: Intel(R) Core(TM) i7-9700K CPU @ 3.60GHz. GenuineIntel. Stepping: C Model: E Family: 6. 33% memory in use: 32675 MB physical memory 21838 MB physical memory free 65443 MB paging file 45978 MB paging file free 134217728 MB user address space 134193515 MB user address space free Module List: C:\WINDOWS\System32\MSCTF.dll, loaded at 0x0000000003710000 - 1127120 bytes - TimeDateStamp 0x ff3fa85a - File date is 09:28:44 on 2023-11-15 C:\WINDOWS\System32\coml2.dll, loaded at 0x0000000003b80000 - 489296 bytes - TimeDateStamp 0x a94b367 - File date is 09:28:28 on 2023-11-15 F:\Falcon BMS 4.37\Bin\x64\Falcon BMS.exe, loaded at 0x0000000004470000 - 88841216 bytes - TimeDateStamp 0x 653965e0 - File date is 20:00:50 on 2023-10-25 C:\WINDOWS\System32\NSI.dll, loaded at 0x000000001c280000 - 25976 bytes - TimeDateStamp 0x 6fe3e240 - File date is 09:28:42 on 2023-11-15 F:\Opentrack\modules\NPClient64.dll, loaded at 0x000000006a940000 - 19968 bytes - TimeDateStamp 0x 526cd113 - File date is 22:38:12 on 2023-02-28 Environment Variables: 3: <ALLUSERSPROFILE=C:\ProgramData> 4: <AMDAPPSDKROOT=C:\Program Files (x86)\AMD APP\> 5: <ANDROID_SDK_HOME=C:\Program Files (x86)\Android\android-sdk> 6: <APPDATA=C:\Users\Jorgen\AppData\Roaming> 7: <CommonProgramFiles=C:\Program Files\Common Files> 8: <CommonProgramFiles(x86)=C:\Program Files (x86)\Common Files> 9: <CommonProgramW6432=C:\Program Files\Common Files> 10: <COMPUTERNAME=JORGENPC> 11: <ComSpec=C:\WINDOWS\system32\cmd.exe> 12: <DriverData=C:\Windows\System32\Drivers\DriverData> 13: <FPS_BROWSER_APP_PROFILE_STRING=Internet Explorer> 14: <FPS_BROWSER_USER_PROFILE_STRING=Default> 15: <FP_NO_HOST_CHECK=NO> 16: <HOMEDRIVE=C:> 17: <HOMEPATH=\Users\Jorgen> 18: <JAVA_HOME=C:\Program Files (x86)\Java\jdk1.8.0_112> 19: <LOCALAPPDATA=C:\Users\Jorgen\AppData\Local> 20: <LOGONSERVER=\\JORGENPC> 21: <NUMBER_OF_PROCESSORS=8> 22: <OneDrive=C:\Users\Jorgen\OneDrive> 23: <OneDriveConsumer=C:\Users\Jorgen\OneDrive> 24: <OS=Windows_NT> 25: <Path=C:\Program Files\Microsoft\jdk-21.0.1.12-hotspot\bin;C:\Program Files\Microsoft\jdk-11.0.16.101-hotspot\bin;C:\Program Files\Eclipse Foundation\jdk-8.0.302.8-hotspot\bin;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\iCLS\;C:\Program Files\Intel\Intel(R) Management Engine Components\iCLS\;C:\ProgramData\Oracle\Java\javapath;C:\Program Files\Common Files\Microsoft Shared\Windows Live;C:\Program Files (x86)\Common Files\Microsoft Shared\Windows Live;C:\Program Files (x86)\AMD APP\bin\x86_64;C:\Program Files (x86)\AMD APP\bin\x86;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static;C:\Program Files\Microsoft\Web Platform Installer\;C:\Program Files (x86)\MKVToolNix;C:\Program Files\Microsoft Windows Performance Toolkit\;C:\Program Files (x86)\Windows Live\Shared;C:\PHP;C:\Program Files\Microsoft SQL Server\120\Tools\Binn\;C:\Program Files (x86)\AMD\ATI.ACE\Core-Static;C:\Pr 26: <PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC> 27: <PROCESSOR_ARCHITECTURE=AMD64> 28: <PROCESSOR_IDENTIFIER=Intel64 Family 6 Model 158 Stepping 12, GenuineIntel> 29: <PROCESSOR_LEVEL=6> 30: <PROCESSOR_REVISION=9e0c> 31: <ProgramData=C:\ProgramData> 32: <ProgramFiles=C:\Program Files> 33: <ProgramFiles(x86)=C:\Program Files (x86)> 34: <ProgramW6432=C:\Program Files> 35: <PSModulePath=C:\WINDOWS\system32\WindowsPowerShell\v1.0\Modules\;C:\Program Files\VisualSVN Server\PowerShellModules> 36: <PUBLIC=C:\Users\Public> 37: <SESSIONNAME=Console> 38: <SystemDrive=C:> 39: <SystemRoot=C:\WINDOWS> 40: <TACVIEW_DCS2ACMI_PATH=C:\PROGRA~2\Tacview\DCS\> 41: <TEMP=C:\Users\Jorgen\AppData\Local\Temp> 42: <TMP=C:\Users\Jorgen\AppData\Local\Temp> 43: <USERDOMAIN=JORGENPC> 44: <USERDOMAIN_ROAMINGPROFILE=JORGENPC> 45: <USERNAME=Jorgen> 46: <USERPROFILE=C:\Users\Jorgen> 47: <VISUALSVN_SERVER=C:\Program Files\VisualSVN Server\> 48: <VS100COMNTOOLS=C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\Tools\> 49: <VS110COMNTOOLS=C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\Tools\> 50: <VS120COMNTOOLS=C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\Tools\> 51: <VS140COMNTOOLS=C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\Tools\> 52: <windir=C:\WINDOWS> 53: <__COMPAT_LAYER=ElevateCreateProcess> ================================================================================
Dump file: https://drive.google.com/file/d/1aRSm2MC-MvA9c0cIwvcD0PUj4QOgrdR7/view?usp=drive_link
-
@jayb i don’t know if I’m good enough at AAR to repro this… but I will try thanks for the quality bug report – very weird, the part about being sluggish after landing.
did your wingman refuel too? once or twice? or did you just RTB him
-
@airtex2019 Thank you for picking this up so quickly!
We were in package 2075, Goblin3 flight. As for my wingman, he refueled fine at the first tanker (the one on the briefing for the flight), but when we got to the 2nd tanker (KC-10) he did not.
It went like this: I asked the KC-10 for us to refuel inside 10nm (think it was 7 or 8 nm out) and was told I was “number one to refuel”. After having refueled and stating Done Refueling, there was no comms from the KC-10 towards my wingman, but the radio text started listing messages, quickly 10 identical radio texts came onto the screen. Paraphrasing it said “Goblin 3-2, Camel 1-1, you are outside my airspace, contact me at 10 miles” or something to the effect of him being too far away. I had to manually enter the KC-10 frequency for UHF since it was not one of the presets, dunno if that can mean anything. It shouldn’t, since the AI mimics our UHF choice so he should have entered the same tanker freq as me.
As for the sluggishness once landed, I might have dinged up the gear since I went a bit off the runway.
-
@airtex2019 I got a dump file from Windows Error Reporting too. It’s quite big (500 Mb zipped) so let me know if I should make that available
-
@jayb said in CTD in AAR TE:
Dump file: https://drive.google.com/file/d/1aRSm2MC-MvA9c0cIwvcD0PUj4QOgrdR7/view?usp=drive_link
please share google drive access…it is still protected
-
I hope that did it, copied new link :
https://drive.google.com/file/d/1aRSm2MC-MvA9c0cIwvcD0PUj4QOgrdR7/view?usp=sharing
-
A guess… Is it possible that after taking fuel you might have not told the tanker “done”?? That might explain the reason the wingie didn’t take fuel at the second tanker and it would be a big clue for us in debug direction…
-
Past the guess question – just want to rule that out quickly - what the crash signature says is that your jet was still in the AAR Qs after you landed. Probably the waiting for the rest of the flight to finish Q. If you did issue the “done” call and it went to the right tanker, then somehow that message likely didn’t work to free the boomer up to work the wingman onto the boom.
Is there a chance that the messages to Goblin 3-2, your wingman presumably, were not coming from the tanker you took gas from?? Can we also assume that at the time you said “done” (again, presuming that you did), that your wingman was well inside 10nm radius of the tanker you got fuel from??
And again, just to rule out the obvious – Camel 1-1 is the second tanker that you took gas from - that’s the one that cleared you for the second fueling??
That it crashed on you so far in time after the AAR evolution makes this harder to pinpoint…so just looking for as many clues as possible on how to reproduce. This is not an area of the code we see a lot of problems with. However!! The path through the code for a second refueling in a mission from a tanker that your flight wasn’t necessarily fragged to visit is a path that has had less flight time and testing so something could easily be lurking…we just need some clues to help find it
-
For reference, this is the scheduled flight plan for the Goblin3 flight and the detour to the KC-10 tanker track on the East coast :
I will run the scenario again and make a recording. If the messages reappear we can check. If they don’t, it might have been a fluke. As for your questions:
I am 99% sure that I did issue the Done (Y-3) command after the KC10 disconnected me because I had been topped off. I was sliding to the right and looked back at my wingman who was close to me and that is when the messages appeared. Did I close my fuel door too, hm I will check in the remake.
It makes some sense that he would get “strange” messages if the tanker did not kick me from its queue. Well, atleast that could be some kind of explanation.
An additional thing that came to mind. Since the KC-10 tanker visit was not on our flightplan, there was no refueling steerpoint. Just something the code might be confused about ?
-
That’s good extra context. Thanks.
If you are running this again to try a repro, would you consider turning on logging??
If you wanted to do that, setting g_fXMonoprintFilter in the config file to 512 and running with the -mono command line flag. That should generate a monolog file with specific tanker/AAR state info and having that in addition to any crash txt and dmp files would be potentially very helpful.
You could paste this into your user config file and that should work:
set g_fXMonoprintFilter 512 // tanker
To your questions, the fuel door in your jet should not matter for the case you are describing.
Equally, not having a refuel waypoint active for the tanker that you were at should not matter.
-
@Boxer Just an update: Still working on reproducing the CTD / tanker problem. Last night I had the comms issue for my wingman already at the first tanker (the one on the flight plan). Unfortunately I had not seen your -mono and did not take any video of that. Since then I have flown the mission a couple of times with debugging and video but now the problem will not reappear. Figures. I will keep trying, it happens too often for it not to happen eventually, and I will have video and debug output then.
-
@Boxer said in CTD in AAR TE:
Past the guess question – just want to rule that out quickly - what the crash signature says is that your jet was still in the AAR Qs after you landed. Probably the waiting for the rest of the flight to finish Q. If you did issue the “done” call and it went to the right tanker, then somehow that message likely didn’t work to free the boomer up to work the wingman onto the boom.
Is there a chance that the messages to Goblin 3-2, your wingman presumably, were not coming from the tanker you took gas from?? Can we also assume that at the time you said “done” (again, presuming that you did), that your wingman was well inside 10nm radius of the tanker you got fuel from??
And again, just to rule out the obvious – Camel 1-1 is the second tanker that you took gas from - that’s the one that cleared you for the second fueling??
That it crashed on you so far in time after the AAR evolution makes this harder to pinpoint…so just looking for as many clues as possible on how to reproduce. This is not an area of the code we see a lot of problems with. However!! The path through the code for a second refueling in a mission from a tanker that your flight wasn’t necessarily fragged to visit is a path that has had less flight time and testing so something could easily be lurking…we just need some clues to help find it
AFAIR there is queue protection : when you fly away , you are automatically removed from the queue
how this code could have failed is the question
EDIT : i can’t find this code again, so maybe i missed this case, will investigate
-
@Mav-jp I have been trying - and is still trying - to replicate this issue. This time with debug info.
The situation is that my wingman (Goblin 3-2) is right next to me, but gets the “outside my airspace” messages from the tanker. It is as if he has been entered into the tanker queue properly but when I am done refueling and the time comes for him to refuel, the tanker has wrong information on where he is. My theory is that the pointer for him on rare occasions at that moment points to another object/jet or the position property gets reset or just points into unallocated memory.
The above happened to me in SP. The other day someone complained about a MP situation where his human wingman could refuel but he could not. Perhaps this is also because the tanker perceives him to be far away, even though he is right next to the tanker. Again, the stray pointer theory could explain that.
The theory could be total garbage. But if not, then the tanker queue management code might be just fine and the problem lies elsewhere.
-
@jayb said in CTD in AAR TE:
@Mav-jp I have been trying - and is still trying - to replicate this issue. This time with debug info.
The situation is that my wingman (Goblin 3-2) is right next to me, but gets the “outside my airspace” messages from the tanker. It is as if he has been entered into the tanker queue properly but when I am done refueling and the time comes for him to refuel, the tanker has wrong information on where he is. My theory is that the pointer for him on rare occasions at that moment points to another object/jet or the position property gets reset or just points into unallocated memory.
The above happened to me in SP. The other day someone complained about a MP situation where his human wingman could refuel but he could not. Perhaps this is also because the tanker perceives him to be far away, even though he is right next to the tanker. Again, the stray pointer theory could explain that.
The theory could be total garbage. But if not, then the tanker queue management code might be just fine and the problem lies elsewhere.
Can you reliably replicate the problem with your wingman beeing told “outside my airspace” ?
-
I have run the mission a couple of times since, but I have not yet been able to replicate it. After I turned on debugging (and started taking video of the mission) the problem has not (yet?) appeared.
-
@Mav-jp – I have reliably reproduced that in the AAR TE training TE. Not in the way described in the OP’s report. It happens because the wingman is not going into RefuelMode it seems. Now why that happens is still a puzzle.
-
@Boxer Can I ask how you recreate the problem (which flight)? I flew it two more times yesterday as Goblin3-1 and did not come across the issue
-
@Boxer said in CTD in AAR TE:
@Mav-jp – I have reliably reproduced that in the AAR TE training TE. Not in the way described in the OP’s report. It happens because the wingman is not going into RefuelMode it seems. Now why that happens is still a puzzle.
can you provide a repro case or do you want to handle it ?
-
@Mav-jp – I already mentioned this in RC so this is more for @jayb here.
Take eastern TRAINING flight, refuel as normal. Clear the tanker by a full 10 miles once wingie has completed refuel and rejoined of his own accord. Call for fuel y-1 again to the same tanker (i.e. don’t change UHF freq)…confirm that he tells you to call again from inside 10nm. Close to ~4nm (enough so you and wingie are both well and truly inside 10nm) and call y-1 again. Refuel yourself and y-3 at the end of that and then see what happens with the wingie. For me at that point the radio goes bonkers.
I think you can tell something is up before that though – I suspect but I forgot to confirm – I would guess from the code that as you are on the boom for the second time, the wingie is NOT in the on-deck position or even close on the tanker wing – more like he’s in “normal” en route formation keyed off your ownship position rather than being in the refuel pattern.
Now having written all of that, I just tried it again and I managed 3 complete cycles with the AI in tow and it didn’t fail Must be something else to it…but I did see it fail in two separate flights in recent days…
-
@Boxer said in CTD in AAR TE:
@Mav-jp – I already mentioned this in RC so this is more for @jayb here.
Take eastern TRAINING flight, refuel as normal. Clear the tanker by a full 10 miles once wingie has completed refuel and rejoined of his own accord. Call for fuel y-1 again to the same tanker (i.e. don’t change UHF freq)…confirm that he tells you to call again from inside 10nm. Close to ~4nm (enough so you and wingie are both well and truly inside 10nm) and call y-1 again. Refuel yourself and y-3 at the end of that and then see what happens with the wingie. For me at that point the radio goes bonkers.
I think you can tell something is up before that though – I suspect but I forgot to confirm – I would guess from the code that as you are on the boom for the second time, the wingie is NOT in the on-deck position or even close on the tanker wing – more like he’s in “normal” en route formation keyed off your ownship position rather than being in the refuel pattern.
Now having written all of that, I just tried it again and I managed 3 complete cycles with the AI in tow and it didn’t fail Must be something else to it…but I did see it fail in two separate flights in recent days…
I don’t have much time today, if you have time I suggest you put a break in RemoveFromQ()