"Noise" in logs

[Hipp0]

Noticed that with some planes, there is constant activity going on when I turn on logging. For example on the Realair Duke, these events are constantly and continually being sent:

2127433 *** EVENT: Cntrl= 66466 (0x000103a2), Param= 0 (0x00000000) COM_RECEIVE_ALL_SET

2127480 *** EVENT: Cntrl= 66463 (0x0001039f), Param= 0 (0x00000000) COM1_TRANSMIT_SELECT

2127480 *** EVENT: Cntrl= 66466 (0x000103a2), Param= 0 (0x00000000) COM_RECEIVE_ALL_SET

2127511 *** EVENT: Cntrl= 66463 (0x0001039f), Param= 0 (0x00000000) COM1_TRANSMIT_SELECT

2127511 *** EVENT: Cntrl= 66466 (0x000103a2), Param= 0 (0x00000000) COM_RECEIVE_ALL_SET

2127542 *** EVENT: Cntrl= 66463 (0x0001039f), Param= 0 (0x00000000) COM1_TRANSMIT_SELECT

2127542 *** EVENT: Cntrl= 66466 (0x000103a2), Param= 0 (0x00000000) COM_RECEIVE_ALL_SET

2127573 *** EVENT: Cntrl= 66463 (0x0001039f), Param= 0 (0x00000000) COM1_TRANSMIT_SELECT

just wondering whether this is normal?

[Gypsy Baron]

That sort of activity is often due to the way some gauges are improperly programmed.

By "improperly" here I mean that even though the gauge functions as intended, the code

used is not efficient or optimized to reduce or eliminate unnecessary "events".

I have encountered this in many aircraft from many different developers. I often

will go into the code, if it is an XML gauge, and 'correct' the implementation if possible.

The one drawback of this sort of inefficiency is that often multi-keystroke commands

will not be recognized by FS because a gauge "Key event" interrupts the keyboard

input sequence. This is often the case if one cannot reliably select engines use the

"E + 1 + 2 +3...etc" keyboard inputs.

If everything is working OK for you then I wouldn't worry about it.

As a former assembly language programmer from the days when every line of code

was scrutinized to minimize CPU and memory usage, these sort of things make me crazy! :)

Paul

[jgar]

Paul "Gypsy Baron"...Thank you for your service!