This is a copy of a statment from FS2Crew forum:Hi, I have the following problem. Everytime when I try to fly with FS2Crew in a multiplayer session on my favorite server (Happy Hippie Germany) i get kicked shortly after takeoff when the flaps are going up because of intense network traffic generation from my aircraft. This problem was existent in the past until SP1b for the NGX and everything seems to work fine with SP1c too, but when I start using FS2Crew the bot detects massiv network traffic from my aircraft and kick´s me. Hopefully this can be fixed, because I love Fs2Crew and it´s too bad i can´t use it on my favorite MP-Server.The answer form one of the FS2Crew guys was:Just to give you all an update on this...We identified the cause of the event flooding.The source is having the FO's VSD display turned on.It's something PMDG will have to fix on their end since the VSD is their code.As you all know, FS2Crew turns on the FO's VSD during the runway entry and descent flows.So what I did is this...In SP1, you have the ability to remove the VSD setting from the FO's flows.(Or, if you don't want to do that, you can just manually turn off the VSD after the FS2Crew FO turns it on.)What does PMDG answer to that statment?Christian

Just as an alternative until PMDG gives a statement: You can turn off the VSD in the PMDG Options in the NGX. Then the FO can't turn it on. That should solve the problem until a proper solution is available.

I'm not saying it's not a problem, but I'm kind of confused as to why the VSD would be generating network traffic.

I'm not saying it's not a problem, but I'm kind of confused as to why the VSD would be generating network traffic.

I am neither a software programmer nor a network administrator, so i'm not able to answer your question, Kyle. But I believe that the guy from FS2Crew knows what he is talking about. The point is that I have the same problem as mentioned in the quotation above and I'm just looking for a solution.

Just as an alternative until PMDG gives a statement: You can turn off the VSD in the PMDG Options in the NGX. Then the FO can't turn it on. That should solve the problem until a proper solution is available.

Thank you Emanuel for the hint. I gonna try that.Btw I actually wanted to know if PMDG is trying to find a solution for that problem.

I am neither a software programmer nor a network administrator, so i'm not able to answer your question, Kyle. But I believe that the guy from FS2Crew knows what he is talking about. The point is that I have the same problem as mentioned in the quotation above and I'm just looking for a solution.

I'm not saying it's not a problem, or that anyone doesn't know what they are talking about. I'm just finding it hard to understand that connection. If I'm finding it hard to steer my car, I'm not going to start blaming the radio. By all means, though, if my steering demands energy from the electrics and my radio does too, there could be a correlation, but it's not my first thought. That's all I'm trying to say.If he found that the VSD is generating net traffic, then I'll believe him. I'm just trying to understand why something that seems to be isolated from, or has no use for (at least in my brain) network communication, is generating network traffic.

Hey Kyle, I see what you are talking about, btw I didn't want to offend you. I don't have any idea why the VSD causes such a problem. The interestingthings is that according to FS2Crew post it is only the FO's VSD that is responsible for network flooding.I just hope that PMDG will take of that problem.Christian

The explanation is quite simple.If "YOU" turn the FO's VSD display on, it FLOODS ( both Free Flight & Multiplayer -- its just more obvious in Multiplayer)Maybe most that fly the 737NGX don't turn it on, as they should when strickly following the checklist.FS2CREW does correctly follow the checklist, so it does turn it on... and hence the Flooding.FS2CREW itself, is not the cause of the flooding -- it is just operating the 737 , and has highlighted an issue with the FO's VSD.----------Actually, FS2CREW makes a very nice, "Repeatable & CONSISTENT" TEST program . It it can run through all the checklists, and everything works in the 737 as expected, then all is well probably well. :)FS2MAINTENANCE ??

The explanation is quite simple.

It's really not. What need does the VSD have for network communication?Your explanation of what's actually going on is simple and makes sense, but again it really isn't a logical jump from VSD to net communication.

It is related to SimConnect. SimConnect is flooding the network by sending data that is totally useless. MS do some extremely weird and inexplicable things, and the strangeness is not limited to FSX! Maybe it is how they debug (then again "Microsoft" and "debug" is an oxymoron so that can't be it). PMDG however could avoid the problem by not using SimConnect. SimConnect has its own problems on top of everything else.Best regards,Robin.

It's really not. What need does the VSD have for network communication?Your explanation of what's actually going on is simple and makes sense, but again it really isn't a logical jump from VSD to net communication.

Turn FO's VSD "ON", and there is Flooding.Turn FO's VSD "OFF", and ther Flooding stops.That seems like a "logical" jump to me.The only remaining question to be answered, is what Key_Event is Flooding when the FO's VSD is turned on -- then exactly why, when you examine that event's code.

The only remaining question to be answered, is what Key_Event is Flooding when the FO's VSD is turned on -- then exactly why, when you examine that event's code.

I'm not sure if you're trying to get a rise out of me, or are being intentionally combattive, or you simply are not understanding my issue, so here it goes:I have no issue at at - as I have stated (twice) - understanding that a problem exists, and that the problem exists and can be traced and isolated to the VSD. My issue of logic is not that I cannot understand VSD OFF, NO ISSUE; VSD ON, ISSUE.My issue of logic, as I have stated (twice), is that there is no logical link between the VSD and network communications. I am a "why" person. You can't simply state facts to me without explaining why and have me idly accept them. So, yes, as you mentioned, this may only be answered by looking at the code, but I've been at that conclusion since I typed my first post.My hope, though, was that someone who either knew the code issue, or had some hypothesis as to what the code issue was, would answer it.In any case, simply restating "the problem exists" in different forms isn't going to help me understand why. There is no logical connection (functionally) between the VSD and network communications, as it doesn't need the network. All of its necessary information is right there in the sim.If you need another metaphor:I show up the scene of an accident and someone tells me "hey, we isolated the reason the engines quit to the fact that the pilot unfastened his seat belt."That could be the reason, but I'm going to need an explanation as to why before I can fully understand it. In this case with the VSD, I'm not owed an explanation, I'm just curious, and publicly stating my curiosity. Again, this is not fixed by restating how one can use isolation techniques to see that the two are somehow related. It's the 'somehow' that's my issue.

My issue of logic, as I have stated (twice), is that there is no logical link between the VSD and network communications. I am a "why" person. You can't simply state facts to me without explaining why and have me idly accept them. So, yes, as you mentioned, this may only be answered by looking at the code, but I've been at that conclusion since I typed my first post.

The CONNECTION is that the FO's VSD must be sending excessive KEY-EVENTS, that will affect network Communications.If you really want to educate yorself, try a google search onFSX "KEY EVENTS" FLOODING MULTIPLAYER(and only PMDG can "look at the code" and fix it )

The CONNECTION is that the FO's VSD must be sending excessive KEY-EVENTS, that will affect network Communications.If you really want to educate yorself, try a google search onFSX "KEY EVENTS" FLOODING MULTIPLAYER(and only PMDG can "look at the code" and fix it )

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.

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).

My problem is that something that has no business with network communications at all is generating network traffic

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. Since that has not happened. I can only guess that it's 1 of 2 things.1) They do not have enough information about your situation to explain it.or2) It has something to do with FS2crew and therefore it's not their problem to deal with.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.