It's not shame - we're asking for the same chance we give everyone else. If you read through the forums, you'll see that it's been reported before, we've started looking into it, and have NEVER, not once, found a common factor/trigger for it. If you read through ANY other posts, you'll see we respond to issues personally and research them all. We have never hid behind blame deflection. That said, I have no interest in arguing with you.
Believe me, I am aware of what ignoring a major issue will do to our reputation - that's why we're not ignoring it. I've tried two or three different ideas to try to step around it these last two weeks (keeping in mind I have to wait for it to be tested, as it never happens to me). They all failed to correct it. I am now waiting on input from Lockheed Martin to see if they have any idea. If it ISN'T our fault, I'd like confirmation. If it is, I'm hoping they can point us toward what the problem is.
If you look at technically, it makes no sense. Our displays, that work almost all the time, randomly begin to show terrain textures instead of the image our code is creating. I managed to be on a TeamViewer session with a customer when it happened once, and I attached a debugger (he was nice enough to install Visual Studio to help me test), and I verified all of the code. The functions were getting called like they should, our code was still creating the image of the displays as it was the rest of the flight. It's also the same code that drives the right displays (it's just a single variable that tells it uses source 1 or source 2 to draw). So, we know it's not the logic causing the terrain. As well, our code does not do any massive memory copying or manipulation of internal resources in the sim like that, so there is no way it would be over-reaching and grabbing terrain textures or similar. So, hence us being at a bit of a loss here.
I refuse to admit we can't fix it, because that'd be giving up. There is ALWAYS a way, I just do not know what it is yet. We are all human, and unfortunately, the machine is thinking faster than I am about this one. All I ask is that we all have patience with each other (and yes, it goes both ways, us to you as well). I understand it's frustrating, just know it's not just frustrating to you.