I'm looking for some help in trying to isolate an issue with FSX.
I've been trying to track down a "loss of flight controls" issue that I
have plagued with for some time now and, with the help of Peter Dowson, I've
zeroed in on SimConnect as being the most liklely culprit.
The symptoms...loss of throttle, rudder and joystick axis inputs to FSX.
I'm still able to control throttle, etc, with keyboard inputs and the buttons
and switches on my stick/throttle still work fine ( Saitek X-45, CH analog pedals )
I noticed the problem on flights of about an hour or more and usually noticed
a several second "freeze" of FSX. On some occasions, after I noticed the loss
of controls, I also saw multiple "FSUIPC" entries in the drop-down addon menu.
Peter made some changes to FSUIPC to eliminate the multiple entries. I have
determined that those were a result, and not the cause, of the problem.
The problem has occured without having multiple FSUIPC menu items.
After checking my FSUIPC4 logs lately I have noticed something rather troubling.
Every hour, something goes amiss with SimConnect! If this interruption lasts
more than a few seconds, I experience the loss of flight controls. I've appended
the applicable sections of one of my 2 hour+ flights that shows interrupts at
one hour after starting FSX and again at two hours after starting FSX.
I'd like to see if anyone else is having these "interruptions" occur. If there
is no loss of flight controls you may not even notice them, but the FSUIPC log
will show their existance. The next flight you take that is 1 hour or longer,
look at your FSUIPC log and see if you have activity similar to that shown
in my log excerpt below.
Something is definately amiss and it's related to the time FSX has been running!
I don't have any anti-virus stuff running. Memory is only 50% used ( of 2.5 GB )
and display memory is usually around 350MB of 512MB on the ATI X1300 Pro.
These "events" happen regardless of where I'm flying of what aircraft I'm in.
Paul
============ Excerpts from my FSUIPC4 log =====================
---> 109 System time = 20:58:53 <---- this is the time FSX was started
2437 SimConnect_Open succeeded: proceeding to initialise interface!
23250 Running in "Microsoft Flight Simulator X", Version: 10.0.60905.0 (SimConnect: 2.0.60905.0)
323750 SimStart Event: Initialising SimConnect data requests
323750 FSUIPC Menu entry added
416187 System time = 21:05:49, FSX time = 05:15:13 (04:15Z) <--- Started the flight
437093 Advanced Weather Interface Enabled
3589156 **** No SimConnect events or states being received! Re-connecting now ... ****
3589156 SimConnect_Open succeeded: proceeding to initialise interface!
3589156 Initialising SimConnect data requests now
3589156 FSUIPC Menu entry added
3589297 **** No SimConnect events or states being received! Re-connecting now ... ****
3589297 SimConnect_Open succeeded: proceeding to initialise interface!
3589297 Initialising SimConnect data requests now
3589297 FSUIPC Menu entry added
3591406 Running in "Microsoft Flight Simulator X", Version: 10.0.60905.0 (SimConnect: 2.0.60905.0)
-->3591672 System time = 21:58:45, FSX time = 06:07:22 (05:07Z) <---- Time of recovery from the "1 hour" glitch
7188797 **** No SimConnect events or states being received! Re-connecting now ... ****
7188797 SimConnect_Open succeeded: proceeding to initialise interface!
7188797 Initialising SimConnect data requests now
7188797 FSUIPC Menu entry added
7188922 **** No SimConnect events or states being received! Re-connecting now ... ****
7188922 SimConnect_Open succeeded: proceeding to initialise interface!
7188922 Initialising SimConnect data requests now
7188922 FSUIPC Menu entry added
7189047 **** No SimConnect events or states being received! Re-connecting now ... ****
7189047 SimConnect_Open succeeded: proceeding to initialise interface!
7189047 Initialising SimConnect data requests now
7189047 FSUIPC Menu entry added
7191156 Running in "Microsoft Flight Simulator X", Version: 10.0.60905.0 (SimConnect: 2.0.60905.0)
-->7192328 System time = 22:58:46, FSX time = 07:04:27 (06:04Z) <---- recovery from the "2 hour" glitch