Too many packets from 3rd party aircraft??

[petejg5]

I was wondering if anyone knows of any fix to third party aircraft in multi-player sessions to reduce the amount of packets that get sent out from these aircraft?

It would greatly help if anyone had some answers to improve multi-player sessions. :jump:

[Sieggie]

The only way to fix it is to go into the XML code and remove (rewrite) the code that is sending key commands each time through the control loop. Many developers do not test to verify a key command needs to be sent, before sending a key command to FSX in the gauges. It is more expedient to just send the command without a test since it has no undesirable effects on single player mode. This causes the command to be propagated to the MP server multiple times a second. If the code that send the multiple key commands is in a gau file or in the model, you cannot do anything except ask the developer to correct the code as it is not modifiable by anyone but him.

Dave

[fsafranek]

If you know that a particular gauge is causing the problem you can always disable it by commenting it out in the panels.cfg file. Hopefully it's not an important one.
:ernae:

[mjrhealth]

Ye its not so simple, Aerosoft took quiet some time to get the Bronco in Multiplayer because of that issue.

[hschuit]

Doug Dawson has created a gauge that traces key events flooding in FS9 and FSX ( fsx_event_logger.gau ). It can be found here:

http://www.douglassdawson.ca/ (http://www.douglassdawson.ca/)

event_logger, v2.1.2 (http://www.douglassdawson.ca/files/event_logger_fsx_v212.zip). This is version 2 of a diagnostic gauge, targeted primarily at gauge and panel authors. It writes all Key_Events issued in FSX or FS9 to a log file, thus allowing the detection of repeating Key_Events which interfere with normal panel operation. It will not identify the gauge issuing the repeating Key_Events, but by identifying the Key_Events themselves, it should make the gauge issuing them somewhat easier to locate. If you have a panel which does not allow the selection of a second engine or exit, or which exhibits improper autopilot operation, this gauge may help you discover why. Updates include a displayed count of the number of Key_Events issued by the sim, along with a tooltip display of the most recently issued Key_Event. Code signed for use in FSX.

[petejg5]

Cheers guys I'll look into those suggestions you have given me. :jump:

[rcbarend]

As an addition:
These excessive XML events (i.e.: unnecessarily giving the same event 18 time per second) can ALSO come from aircraft mdl code;
For example:
An older version of a very popular freeware jet has this problem, continuously giving SpoilerUp event from the .mdl code when the aircraft flies faster than 500 knots (to force the spoilers up). Instead, it should continuously check for the current state, so it only needs to issue the event once (when the pilot lowers them when flying fast).

In short: beware that the problem isn't always caused by gauge code, although it usually is :)

Rob