Masterius

I've used "List Local Panel Vars" quite a bit, but didn't think to try Event Logging. It looks as if it might be [VOR1_OBI]. Going to experiment with that now. Update: VOR1_OBI worked!

That is the instrument in question, and the knob that adjusts the heading. Tried them ; didn't work. Or, at least, didn't work how I tried using them (as macros). I really do try and make use of the 14 or so documents that you've provided. It's rather rude and disrespectful to you if I don't take advantage of the large amount of documentation and instructions you've provided. Thanks again for such a rapid, and insightful, reply. I'll keep on working at this. ~Al

I have registered FSUIPC, using FSX-SE, and the add-on aircraft Accu-Sim B-17G Flying Fortress. This seems so simple, yet I'm pulling my hair out at this point. I want to adjust the flux compass (AP) heading using two buttons (one INC, one DEC). I've found numerous references to [HEADING BUG INC 65879] and [HEADING BUG DEC 65880], which do work to change the C-1 autopilot heading, but do not adjust the compass itself. I've also found references to "AP Heading, 07CC 2 Autopilot heading value, as degrees*65536/360", but I haven't been able to get that to work with two buttons. I'm probably stumbling right past the answer, but, for now, any help will be appreciated. ~Al

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!

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