Walt

Hi, Thank you for sharing. Why does the developer change numbers with each update? Is this deliberate to make it difficult for you to control the gauges?

No reason to get upset. It was just an honest statement. I do see that the site had an Avsim headlines on 6 Oct. Curious why nothing at SimFlight? I'm guessing here but I would suspect Pete reads the SimFlight headlines. And yes I do have Pete's email address. No, he didn't give it to me. I've seen it here in many past posts.

Maybe I have no business writing this since this is not my forum but ....... If you only wanted to give Pete a heads-up, why not email him vs posting in this public forum.

From what I read, appears to be ex-staff members that bailed-out of MyCockpit.org and now looking for members by posting here.

Thanks for the help Pete! Yes, F1 does have a support forum. I just wanted to be armed with the best information when I present the issue to them.

Here is part of the log file. Appears to be the same entries over and over. FSUIPC4 Key is provided WideFS7 Key is provided [Continuation log requested by user] Running inside FSX on Windows Vista (using SimConnect Acc/SP2 Oct07) Module base=61000000 Wind smoothing fix is fully installed 632880 System time = 14/10/2009 12:16:23, Simulator time = 14:14:45 (19:14Z) 632927 LogOptions changed, now 60000000 00000001 632989 *** EVENT: Cntrl= 66507 (0x000103cb), Param= 231 (0x000000e7) PANEL_ID_OPEN 632989 *** EVENT: Cntrl= 66508 (0x000103cc), Param= 240 (0x000000f0) PANEL_ID_CLOSE 632989 *** EVENT: Cntrl= 66508 (0x000103cc), Param= 250 (0x000000fa) PANEL_ID_CLOSE 632989 *** EVENT: Cntrl= 66508 (0x000103cc), Param= 260 (0x00000104) PANEL_ID_CLOSE 633067 *** EVENT: Cntrl= 66507 (0x000103cb), Param= 231 (0x000000e7) PANEL_ID_OPEN 633067 *** EVENT: Cntrl= 66508 (0x000103cc), Param= 240 (0x000000f0) PANEL_ID_CLOSE 633067 *** EVENT: Cntrl= 66508 (0x000103cc), Param= 250 (0x000000fa) PANEL_ID_CLOSE 633067 *** EVENT: Cntrl= 66508 (0x000103cc), Param= 260 (0x00000104) PANEL_ID_CLOSE 633114 *** EVENT: Cntrl= 66507 (0x000103cb), Param= 231 (0x000000e7) PANEL_ID_OPEN 633114 *** EVENT: Cntrl= 66508 (0x000103cc), Param= 240 (0x000000f0) PANEL_ID_CLOSE 633114 *** EVENT: Cntrl= 66508 (0x000103cc), Param= 250 (0x000000fa) PANEL_ID_CLOSE 633114 *** EVENT: Cntrl= 66508 (0x000103cc), Param= 260 (0x00000104) PANEL_ID_CLOSE 633176 *** EVENT: Cntrl= 66507 (0x000103cb), Param= 231 (0x000000e7) PANEL_ID_OPEN 633176 *** EVENT: Cntrl= 66508 (0x000103cc), Param= 240 (0x000000f0) PANEL_ID_CLOSE 633176 *** EVENT: Cntrl= 66508 (0x000103cc), Param= 250 (0x000000fa) PANEL_ID_CLOSE 633176 *** EVENT: Cntrl= 66508 (0x000103cc), Param= 260 (0x00000104) PANEL_ID_CLOSE 633208 *** EVENT: Cntrl= 66507 (0x000103cb), Param= 231 (0x000000e7) PANEL_ID_OPEN 633208 *** EVENT: Cntrl= 66508 (0x000103cc), Param= 240 (0x000000f0) PANEL_ID_CLOSE 633208 *** EVENT: Cntrl= 66508 (0x000103cc), Param= 250 (0x000000fa) PANEL_ID_CLOSE 633208 *** EVENT: Cntrl= 66508 (0x000103cc), Param= 260 (0x00000104) PANEL_ID_CLOSE 633270 *** EVENT: Cntrl= 66507 (0x000103cb), Param= 231 (0x000000e7) PANEL_ID_OPEN 633270 *** EVENT: Cntrl= 66508 (0x000103cc), Param= 240 (0x000000f0) PANEL_ID_CLOSE 633270 *** EVENT: Cntrl= 66508 (0x000103cc), Param= 250 (0x000000fa) PANEL_ID_CLOSE 633270 *** EVENT: Cntrl= 66508 (0x000103cc), Param= 260 (0x00000104) PANEL_ID_CLOSE 633332 *** EVENT: Cntrl= 66507 (0x000103cb), Param= 231 (0x000000e7) PANEL_ID_OPEN 633332 *** EVENT: Cntrl= 66508 (0x000103cc), Param= 240 (0x000000f0) PANEL_ID_CLOSE 633332 *** EVENT: Cntrl= 66508 (0x000103cc), Param= 250 (0x000000fa) PANEL_ID_CLOSE 633332 *** EVENT: Cntrl= 66508 (0x000103cc), Param= 260 (0x00000104) PANEL_ID_CLOSE 633379 *** EVENT: Cntrl= 66507 (0x000103cb), Param= 231 (0x000000e7) PANEL_ID_OPEN 633379 *** EVENT: Cntrl= 66508 (0x000103cc), Param= 240 (0x000000f0) PANEL_ID_CLOSE

Ok. It appears to be an issue with the F1 Cessna Mustang. If I load a default FSX aircraft such as the C172, I the Event log file does not show the stream of Open and Closes. As soon as I load the Mustang, the Open-Close stream begins. Is it possible to assign a key, button, or axis to this event? In other words, can I be causing it with a keyboard or joystick assignment? If not, I read you that there is something within the Mustang panel code that is causing this.

Hello Pete, I have a problem with Event Logging. Button/Key, Events and Console are in view. Events show a constant stream of 66507 - Panel_ID_Open and 66508 - Panel_ID_Close. I know something is triggering this constant Open - Close. Exactly what is Panel_ID Open and Close. Thanks.

Yes, Key2 Mouse is easier to use but from what I remember the panel you want Key2Mouse to control must be in focus. That is why Mouse Macro was such a benefit to have. It works even if the panel you want to control is not in focus. I do not know for a fact, but I believe the no required focus is also a AutoHotKey feature. I just wish I could get MouseMacro to work with all the F1 Mustang panels. Not sure how F1 programmed the Mustang panels but its a no go for me.

This program might work where Mouse Macro doesn't. http://www.autohotkey.com/