CTD in VirtualDisplay::TextCenter() .. when launching HARM
-
Hey airtex, if you can compress and upload I’d love to take a look. The full dmp should shrink down a lot, but I’ll take either one of them :).
-
Same. Please share!
-
Download links send via DM. Thanks!
-
Download links send via DM. Thanks!
Thanks – do you recall what you had been doing recently when the CTD occurred? Were you selecting a threat type in the HARM POS mode? If so, do you recall if it was with the HOTAS shortcuts or with the MFD keypress?
-
There was a lot going on – but at the exact moment of the crash, I pickled off a HARM in POS (PB) mode toward a SA-2 threat steerpoint. (Literally heard the “whoosh” sound effect but never saw the missile – the screen froze with what you see in the screenshot.
AWACS was talking at the time … you can see the caption. Our CAP flight was heavily engaged.
I had 1 AI wingman also carrying 2x HARM … I had recently given weapons-free command and I think she fired 1 HARM toward the nearer SA-2 target steerpoint.
But to answer your question, I would have selected the PB submode and the SA-2 target type, using the MFD buttons.
-
Thanks for the context. Yes, the RWR picture was pretty busy there :). The crash has to do with displaying the emitter type targeted by the HARM in flight. For some reason that didn’t get set correctly.
-
I remember I had been playing around with the HAD … locked up the SA-2 there, but I was PGM5 and it switched off. So I switched over to WPN page, POS mode, PB, selected SA-2… at some point there I did a DMS-down to move SOI to HSD, and used cursors there and TMS-up to select steer 57.
I notice the HSD is still SOI in the screenshot. Also notice the HUD says “HTS” … is that expected? not sure.
-
The HTS part could be a major clue!
Do you recall if you had used MSL STEP or for some other reason had selected station 7 (like firing off a previous HARM)? The state from your crash dump seems to indicate you were working with that station.
-
No, unless by accident. Which is entirely possible … I couldn’t testify in court but the sequence probably went something like this…
1. I wanted to change from EOM to PB … but couldn’t remember which hotas button to hit …
2. probably intended to hit cursor-enable … which is not correct (it’s pinky switch!) but still can’t remember that
3. give up and click left-MFD button #3 with mouse to cycle submode to PB
4. but my cursor-enable button is right next to msl-step on my stick … so entirely possible I switched from station 3 to 7 before firingsadly I had fov zoomed in at the moment of crash, the screenshot doesn’t show the WPN page fully
-
That’s it! I was able to repro the same crash by locking up something on the HTS, then switching to the WPN page in POS mode. Still not sure precisely what conditions are necessary, but it should be straightforward to narrow down now, thanks!
-
Awesome! Like most of my bug reports, root cause is me fumbling with hotas bindings and pressing buttons randomly…
-
This one bit me pretty bad…seems like there are multiple ways to induce a CTD in the HTS, but I found a good repro case and posted here:
https://bmsbugs.blu3wolf.com/view.php?id=203Hopefully they are all related and one fix will solve most of them.
-
I think JP and Abelian already fixed this.