did I hit the pixel o' deth, wtf?

[ratatosk]

Decided to fly stuka some during intermission, had a few reasonable missions, then came Sortie 260732, pfft.

Approaching Longwy along road from east, ~1.8km, got almost over town and chopped throttle, deployed dive brake, BOOM! There were certainly EA in the area within audible range, but I never heard anyone fire, so I figured lucky hit by AA even tho I never saw any tracers from the ground.

But deth cam just showed wingless hulk hanging in the air and Killed By was "-" when I thought that "-" had been replaced by "Enemy Forces" if AI did you in? Last time I encountered something like that was a few years ago when a Heinkel I was flying back from England just exploded in mid-air in the middle of nowhere and my conclusion after discussing with others was that I had encountered the pixel o' deth (meaning a graphical flaw sort of like the sarlacc phenomenon that people on the ground used to (?) know and love).

I haven't flown in several campaigns, but am I seeing a mystery where there isn't one? What does the hive think the answer is? Thanks.

[GOPHUR]

I think the physics loop has a gremlin in it that killed you dead. And if I could replicate it Id squeeze the life right out of him.

[ratatosk]

Resurrecting an old thread because the same thing just happened to me in 110 at 4k over Hastiere- began dive, BOOM, wingless plane left hanging in air, killed by "-". 2+ years of broken, if and when CRS ever gets the 3-4 additional people it will take to actually make any progress, please chase this one down.

[OLDZEKE]

It's not replicable Rata. It's a very random thing......

My past experience with POD, if it happens to you it'll (usualy) occur in the same spot until you relog into the game. Sometimes it does, sometimes it's a one off deal. Very random thing.

But it may not happen again for weeks or years or in might happen again tomorrow.

I used to get them pretty often around 5 or 6 years back then none until this year. A map or so back I hit a POD, my 1st in many years.

They can't track down something they can't make happen. Gotta see it to fix it.

Maybe post specs including any OC and get some data going but it's just a wild arsed guess as to if it's hardware or over clock related.