Jump to content
The simFlight Network Forums

Recommended Posts

Posted (edited)

I was trying to determine codes for selecting radio channels (ex. toggling between NAV1 and NAV2) so I decided to use event logging. Here is just an example of what is being logged:

76921269 *** EVENT: Cntrl= 66508 (0x000103cc), Param= 102 (0x00000066) PANEL_ID_CLOSE
 76921269 *** EVENT: Cntrl= 66507 (0x000103cb), Param= 100 (0x00000064) PANEL_ID_OPEN
 76921332 *** EVENT: Cntrl= 66508 (0x000103cc), Param= 102 (0x00000066) PANEL_ID_CLOSE
 76921332 *** EVENT: Cntrl= 66507 (0x000103cb), Param= 100 (0x00000064) PANEL_ID_OPEN
 76921394 *** EVENT: Cntrl= 66508 (0x000103cc), Param= 102 (0x00000066) PANEL_ID_CLOSE
 76921394 *** EVENT: Cntrl= 66507 (0x000103cb), Param= 100 (0x00000064) PANEL_ID_OPEN
 76921457 *** EVENT: Cntrl= 66508 (0x000103cc), Param= 102 (0x00000066) PANEL_ID_CLOSE
 76921457 *** EVENT: Cntrl= 66507 (0x000103cb), Param= 100 (0x00000064) PANEL_ID_OPEN
 76921457 *** EVENT: Cntrl= 66508 (0x000103cc), Param= 102 (0x00000066) PANEL_ID_CLOSE
 76921457 *** EVENT: Cntrl= 66507 (0x000103cb), Param= 100 (0x00000064) PANEL_ID_OPEN
 76921519 *** EVENT: Cntrl= 66508 (0x000103cc), Param= 102 (0x00000066) PANEL_ID_CLOSE
 76921519 *** EVENT: Cntrl= 66507 (0x000103cb), Param= 100 (0x00000064) PANEL_ID_OPEN
 76921566 *** EVENT: Cntrl= 66508 (0x000103cc), Param= 102 (0x00000066) PANEL_ID_CLOSE
 76921566 *** EVENT: Cntrl= 66507 (0x000103cb), Param= 100 (0x00000064) PANEL_ID_OPEN

This goes on non-stop, and I've no idea what's driving it. I have registered FSUIPC, using FSX-SE, and the add-on aircraft Accu-Sim B-17G Flying Fortress, with quite a few macros and several LUAs, but I can't see anything out of the ordinary, or looking suspicious. I've tried several other, standard aircraft, and it doesn't seem to happen with them.

~Masterius

Edited by Masterius
Posted

Hi Masterius,

they will be used (ie re-purposed for internal use) by your add-on aircraft or Accu-Sim - I also get them  with A2A's Cherokee (with Accu-Sim).  Just ignore them.

You can add the following to the '[General]' section your FSUIPC4.ini file so that these are ignored:

DontLogThese=66507,66508

John

 

 

Posted

Thank you for responding so quickly! I was worried more about that being a potential resource hog than I was it "flooding" the event log. (Hey! That rhymed! 😁) Even so, it's nice to be shown a method to block that from being logged.

Thanks again! 

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.