Not sure what's going on here, but maybe someone can help. I have 1.30 and 1.31 installed into my FSX. I'm running the most recent version of FSUIPC and it's registered. For some reason, I have no activity on the airspeed indicator. It remains at 45kts and never moves. Anyone else experiencing that? Also, I've noticed that the DME reading on the DME gauges is always 80.3nm or something in that range and never changes no matter how far away I am from the VOR. Thanx for making TM2 avail for FSX! I appreciate it very much.-Rick Schaefer

Not sure what's going on here, but maybe someone can help. I have 1.30 and 1.31 installed into my FSX. I'm running the most recent version of FSUIPC and it's registered. For some reason, I have no activity on the airspeed indicator. It remains at 45kts and never moves. Anyone else experiencing that? Also, I've noticed that the DME reading on the DME gauges is always 80.3nm or something in that range and never changes no matter how far away I am from the VOR. Thanx for making TM2 avail for FSX! I appreciate it very much.-Rick Schaefer

Make sure you are not starting the sim in the VC. If you are, switch to a 2D cockpit, shut down FSX, then restart. If that doesn't solve it, start FSX with the default C172, then switch to the 'mouse, and see if that helps. I've had two others that were having the weird ASI issue report that works for them.RegardsBob ScottColonel, USAF (ret)ATP IMEL Gulfstream II-III-IV-VColorado Springs, CO

Make sure you are not starting the sim in the VC. If you are, switch to a 2D cockpit, shut down FSX, then restart. If that doesn't solve it, start FSX with the default C172, then switch to the 'mouse, and see if that helps. I've had two others that were having the weird ASI issue report that works for them.RegardsBob ScottColonel, USAF (ret)ATP IMEL Gulfstream II-III-IV-VColorado Springs, CO

Whelp, no luck there. Did as you suggested (loading the C172 1st) and no go. Exited, loaded it again, made sure that the engine was running on it, then loaded the mouse. No go. Tried it without the engine running, no go. Not sure what's going on.-Rick

Whelp, no luck there. Did as you suggested (loading the C172 1st) and no go. Exited, loaded it again, made sure that the engine was running on it, then loaded the mouse. No go. Tried it without the engine running, no go. Not sure what's going on.-Rick

OK, this sounds like an FSUIPC problem. The DME and the airspeed data are both obtained from FSUIPC.In the FSUIPC drop-down menu, select the logging tab, and type 02BC into one of the four offset boxes, select type U32 from the data type drop down next to it, and check the Display to AdvDisplay box. When you return to the sim you will see a value that's the indicated airspeed x 128 in the green stripe across the FS window. If that number isn't changing to reflect the airspeed, then FSUIPC is not communicating with FS, or possibly SimConnect is not communicating with FSUIPC. Let me know the results of this test, please.As for the DME issue, also make sure you do not have the DME hold switch(es) in "hold" on the radio panel.Also please confirm that neither the digital speed drum nor the needle are moving.RegardsBob ScottColonel, USAF (ret)ATP IMEL Gulfstream II-III-IV-VColorado Springs, CO

In FSX I have to load the plane twice to get it working correctly, there is a command you can assign, CTRL+SHIFT+R. Hopefully that works for you.

I have been having the same problem with the airspeed indicator needle and speed drum. I have discovered that the airspeed indicator failure for me is tied to the windowed mode and then going to full screen. I always start in windowed mode. If I load the Tinmouse directly (or load the default Cessna first, then load the Tinmouse), as long as I stay in windowed mode, airspeed indicator works fine. Once I go to Full Screen it stops working and I have to reload the aircraft (in full screen) and then the airspeed needle, drum start working again. Brad

Ok. Info for FSUIPC is being sent correctly. So, it's not that. For some reason, it started to work this time. Also, I noticed and forgot to mention that the autothrottle and the speed/epr hold on the 177 were not working either. THIS time they did tho. I'm at a complete loss now.-Rick

I have been having the same problem with the airspeed indicator needle and speed drum. I have discovered that the airspeed indicator failure for me is tied to the windowed mode and then going to full screen. I always start in windowed mode. If I load the Tinmouse directly (or load the default Cessna first, then load the Tinmouse), as long as I stay in windowed mode, airspeed indicator works fine. Once I go to Full Screen it stops working and I have to reload the aircraft (in full screen) and then the airspeed needle, drum start working again. Brad

I am assuming this is in FSX...this might explain what's happening--in FSX when the main window is resized (including a switch between windowed/full-screen mode) it triggers the panel system's disconnect state. There's a command to close FSUIPC in that part of the code.I've moved it to a different section of the DLL code that executes only when the gauge DLL unloads. I have a patch file for those experiencing this problem to try...send an e-mail to the support address listed in the readme, and I'll send it to the first couple of people who respond to try out.Also, as we troubleshoot this and other problems, please tell me which version of FS and service pack level you are using, your operating system (and whether it's 32 or 64-bit), and your CPU type. When I'm troubleshooting a problem that I can't reproduce on my computers, I can't do much good if I'm left guessing what environment the problem you are having is occurring in.RegardsBob ScottColonel, USAF (ret)ATP IMEL Gulfstream II-III-IV-VColorado Springs, CO

I am assuming this is in FSX...this might explain what's happening--in FSX when the main window is resized (including a switch between windowed/full-screen mode) it triggers the panel system's disconnect state. There's a command to close FSUIPC in that part of the code.I've moved it to a different section of the DLL code that executes only when the gauge DLL unloads. I have a patch file for those experiencing this problem to try...send an e-mail to the support address listed in the readme, and I'll send it to the first couple of people who respond to try out.Also, as we troubleshoot this and other problems, please tell me which version of FS and service pack level you are using, your operating system (and whether it's 32 or 64-bit), and your CPU type. When I'm troubleshooting a problem that I can't reproduce on my computers, I can't do much good if I'm left guessing what environment the problem you are having is occurring in.RegardsBob ScottColonel, USAF (ret)ATP IMEL Gulfstream II-III-IV-VColorado Springs, CO

Bob, I sent an email to your GMail account. Thanks, Brad

Bob, I sent an email to your GMail account. Thanks, Brad

Hi Bob, I've just sent you one too :( Rick Canham

OK, this is a confirmed problem in FSX-only, and occurs when resizing the screen or switching between full-screen and windowed modes, at which time FSUIPC gets closed and the panel stops getting the data it needs from FSUIPC (this is a panel/FSX issue and not an FSUIPC problem). I have a fix, and will be releasing either a patch or perhaps a new gauge file shortly.RegardsBob ScottColonel, USAF (ret)ATP IMEL Gulfstream II-III-IV-VColorado Springs, CO