How many different ways do I need to phrase this issue for you to understand it?I do not have an issue that there is a problem. I'm not debating that, yet every post of yours essentially says there's a problem and what the problem is, but not specifically why. That conclusion is something we've all been at since post number one. Bryan's (FS2Crew's) answer provides everything you've simply been reiterating this whole time.Clearly, if the VSD is what's causing the network flooding, then a whole bunch of network packets have their origin there. That's not my issue (as I've stated several times now).My problem is that something that has no business with network communications at all is generating network traffic. I don't need knowledge of what network flooding is (I hate touting credentials, but I'm a Security+ guy, so I know quite well what network flooding is in all of its implementations), because that's not really my root issue. My root issue is that something that has no obvious need to go talking to other computers (generate net traffic) is attempting to talk to other computers. I couldn't care less that the net traffic exists. To be honest, not once in here have I asked you specifically to answer any of my questions about the issue, so I'm not sure why you feel obligated to keep attempting to answer my question that I've clearly stated nobody one the outside would have knowledge of. A hypothesis of why the VSD would be generating net traffic would be nice, but I'm not looking to have my questions answered specifically. Even in my first post, my curiosity was mostly posed in rhetoric.

Kyle, of couse you are 100% correct."YOUR problem is that YOUR BELIEVE that something that has no business with network communications at all is generating network traffic"If you read and understood some of the information you should have read, with a google search, you might be more informed.If you cannot read between the lines, and deduce what is happening, I'm not going to be the one to spell it out to you in PMDG's forum.I do not use FS2CREW, so I really have little interest in discussing this futher with you. Let's let it drop.I have already been contacted by Bryan, and we have talked at length about this issue.I am confident that Bryan & PMMDG get get the matter resolved.

Multi-Crew (Shared Cockpit)? I'm betting it's there, we just can't see it. As I recall, the gauges have to be designed to send the data from the start. Maybe a loopback wasn't implemented when not connected to another IP?Just guessing here, and breaking my rule of not posting in the PMDG forums (we'll see how that goes).

Dave, despite your rule, thank you for actually providing something useful regarding my question. I'd forgotten about the multi-crew aspect which would need to send status and so on.

Kyle, of couse you are 100% correct."YOUR problem is that YOUR BELIEVE that something that has no business with network communications at all is generating network traffic"If you read and understood some of the information you should have read, with a google search, you might be more informed.If you cannot read between the lines, and deduce what is happening, I'm not going to be the one to spell it out to you in PMDG's forum.I do not use FS2CREW, so I really have little interest in discussing this futher with you. Let's let it drop.I have already been contacted by Bryan, and we have talked at length about this issue.I am confident that Bryan & PMMDG get get the matter resolved.

I'm very glad you're talking to a developer about it, and I'm very confident the both of them will work it out. I honestly don't care. It's not affecting me. My question is more academic than practical. I'm not sitting here trying to point fingers or throw people under the bus. I'm simply here trying to understand why a gauge that seemingly has no need to communicate is communicating.Another thing I don't understand is why you're being so combative. Again, I didn't directly ask you to answer a question, so there's no need to keep responding and getting frustrated when you're not providing anything helpful to me. Despite your reference to key events, it remains unanswered. Your post about Key Events in the other forum simply states that they exist and there's a tool to check if there are excessive amounts, not the cause of the events.

I am quite suprised nobody from PMDG has chimed in yet to set the record straight. It would only take a couple sentences to explain what is happening and why.In any case it looks like your more likely to get an answer from PMDG by doing a support ticket and asking your questions there.

It's not a problem for me. Beyond that, my questions are only curiosity and nothing more. I'm simply wondering why a gauge that has no reason to reach out onto the network, is reaching out onto the network.

*******, Kyle, how do you manage to stay so calm?I am sitting here wanting to slap some sense into that guy and it is not even me he is talking to.

*******, Kyle, how do you manage to stay so calm?

 

I'll admit, I do come unhinged from time to time, but most of the patience comes from my primary job. I teach computer classes and half the time I have people who aren't paying attention to what I said, the other half of the time, I have people in an Excel VBA class but they still haven't figured out what a column is.

 

There's a certain amount that comes from hanging around these fora so much, too.

Issue now fully understood .. :Party: Thanks Bryan.

Thanks also to those who helped with the testing over the past few days.