Masterius Posted July 21, 2019 Report Share Posted July 21, 2019 (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 July 21, 2019 by Masterius Link to comment Share on other sites More sharing options...
John Dowson Posted July 22, 2019 Report Share Posted July 22, 2019 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 Link to comment Share on other sites More sharing options...
Masterius Posted July 22, 2019 Author Report Share Posted July 22, 2019 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! Link to comment Share on other sites More sharing options...
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now