Walt Posted October 14, 2009 Report Share Posted October 14, 2009 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. Link to comment Share on other sites More sharing options...
Pete Dowson Posted October 14, 2009 Report Share Posted October 14, 2009 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. That is not a "problem with Event Logging", that is a problem with something sending all those presumably unwanted events. There's no problem with event logging -- you just turn it off if you don't want it!! I know something is triggering this constant Open - Close. Of course something is doing it --- you need to find out what it is which is doing it and get rid of it, as it will potentially be interfering with other things and certainly not doing the performance of your FS installation any good! Exactly what is Panel_ID Open and Close. The Open one opens (i.e. displays) the panel which has that ID, if there is one, and the Close closes it. The ID is provided in the "parameter" part of the event. There are a number of pre-defined IDs and any number of others added by folks who make FS aircraft panels. They are defined in the PANEL.CFG file. Regards Pete Link to comment Share on other sites More sharing options...
Walt Posted October 14, 2009 Author Report Share Posted October 14, 2009 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. Link to comment Share on other sites More sharing options...
Walt Posted October 14, 2009 Author Report Share Posted October 14, 2009 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 Link to comment Share on other sites More sharing options...
Pete Dowson Posted October 14, 2009 Report Share Posted October 14, 2009 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. Sounds like something on of their Gauges is doing, then. 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? Only if that key or button or whatever is stuck and continually signalling -- and then, if it only occurs with that one aircraft, you must have done is as "aircraft specific" or "profile specific" so it isn't programmed with anything else. Just look at the assorted [Keys] and [buttons] sections in your FSUIPC INI file -- or temporarily remove that file from the Modules folder before running FS, as a simple way of eliminating such a possibility If not, I read you that there is something within the Mustang panel code that is causing this. That seems a lot more likely, yes. On your log it looks even less likely to be anything you've assigned: 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 There's a repeating sequence of 4 different events there -- on 4 different Panels! Isn't there a Support forum for the aircraft. Maybe they can explain what they are trying to do with these events? Incidentally, there's a list of FS pre-defined PANEL ID names against numbers in this thread: viewtopic.php?f=54&t=74623&p=458356&hilit=GPS_PANEL#p458356 Regards Pete Link to comment Share on other sites More sharing options...
Walt Posted October 14, 2009 Author Report Share Posted October 14, 2009 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. 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