Unsolved CTD in AAR TE
-
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()
-
@Boxer Thank you for confirming I am not crazy, haha. It happens sometimes is what I have seen as well.
I will try out the eastern flight as you described. Is there any other debug setting that would be useful to invoke to get details pertaining to the wingman - right now I use the 512 flag as suggested ?
-
Would anyone from this thread be willing to test a fix for this issue? If so, please message me.