BWright

Thanks for the info. I was beginning to think it was just me or my computer.

Thanks for the information. That has been annoying me for a long time. I finally decided to ask about it to see if anyone else has experienced the same problem. It is a shame that we have that annoyance. FS9 runs so great on my new computer, too. I have maximum realism set. My New System: Gateway FX4710 PC - 6 GByte DDR2 RAM Windows Vista Home Premium 64-bit Intel Core 2 Quad 2.5 GHz Q9300 Processor Nvidia GeForce 9800 GT OC 512 MB RAM Thanks, BWright

I am still running FS9 with Windows Vista and most everything is fine. I only have one problem: When I turn on AntiAliasing, which is all the time, I cannot acess the FSUIPC interface. I see the menu item for it but when I select it I get nothing but a black screen. If I then press ESC, I return to the cockpit. I thought that was fixed once but I cannot remember which version of FSUIPC did it. I am currently running 3.71 and have tried 3.82 but to no avail. Does anyone remember which version addressed that problem? And how would I find older versions of FSUIPC if I wanted to try myself? Thanks.

Could you use 4.02, (or, better 4.023 available here) please, and let me know? I cannot really investigate problems with old versions. The TAS is read directly from SimConnect and is always okay here --- can you tell me what is wrong with it when to see it "not working"? Is it non-zero and static, or zero, or changing but a wrong value? Note that you cannot necessarily go by the default FSX gauges. I notice that the "TAS" in the ND of the default 738 is actually the IAS -- it is identical to the speed indication on the PFD! If you do get an incorrect indication, please enable IPC Read logging (in FSUIPC4's Logging page) and repeat the test so I can see just what that gauge is reading. If the log is large please ZIP it up and send it to petedowson@btconnect.com. Thanks, Pete Hi Pete, Actually a strange thing happened. The problem just went away. And I was unable to reproduce any crashing of FSX, too. I thought the crashing might have been related to default scenery as in FS9 before the patch. But whatever is going on with FSX, it seems to be sporadic. Thanks for your reply, however. Respectfully, Tim

Not to worry, Tim! I certainly saw the intention behind your post as merely being one of reporting a possible problem with the latest version of FSUIPC reading and reporting the TAS variable. The second paragraph being then only a tongue-in-cheek comment regarding alledged support response... ;) I'm glad all is well, guys. I hate those kinds of misunderstandings and, believe it or not, I really do worry about them. There is enough tension in our present world without us guys at FS sites quarrelling among ourselves. I have the deepest respect for all FSers and developers. I am often amazed at the enormous amount of knowledge at these sites. And Mr. Pete Dowson ranks right at the top of the list, for me. What would FS be like without him? Peace to all. Tim

Ooops! Sorry, Bill. I do get confused sometimes about where I am when posting. I don't see how anyone could read my post and think I was being sarcastic or disrespectful to MS or Pete Dowson! Did you notice the emoticon following that last sentence? I was just kidding about MS getting a solution so quickly. Actually, I was unable to reproduce the problem, anyway. I have noticed that many problems with FSX appear very sporadically. It is also just possible that someone at this forum might have experienced a similar problem. I am truly sorry for any misunderstanding about my post. I am not angry with anyone, MS or, certainly not, Pete Dowson. I just thought he should know about the gauge failure. As you no doubt have already experienced, the printed page is not always the best medium for communication. That is one good reason for using the emoticons. :) Respectfully, Tim

I use the RKG Airspeed Gauge from FS9. That gauge and the RKG FuelStatus gauge still work fine---with FSUIPC 4.0.1.0. As soon as I installed FSUIPC 4.0.1.5, the TAS readout for the RKG Airspeed gauge stopped working. I deleted FSUIPC 4.0.1.5 and reinstalled FSUIPC 4.0.1.0 and the RKG Airspeed gauge worked again! I experienced several crashes in FSX while flying a D> flight from KJFK to KBGR in the A321 Airbus. I was somewhere just past KPSM (Portsmouth, NH) when the crash occurred each time. I was using FSUIPC 4.0.1.0 at the time of the crash. A report was sent to MS and they called in the entire crew on Saturday to resolve the problem. We should have an answer by lunch. :lol: Tim

Actually, there are all kinds of issues with the FSX A321. The Airspeed Hold does not work correctly; it will not hold MACH speed during climb. It is necessary to keep reducing the set MACH number to avoid over-speed. In level flight, it seems to do okay. The Relative Wind arrow on the display is actually reversed! It will show a tail wind when the digital readout for wind direction (both on the gauge and when you type Shift+Z) shows a head wind. Regards, Tim

Yeah, I saw the link in Joshua's post just seconds after I posted. Got it. Thanks, John.

Hi Joshua, So you're the guy... :D Glad to meet you. Great program. How does it look for upgrading the program for FSX? Too soon to tell? Tim

Thanks for all the help, Pete. 3.605 seems to have done the trick. The Time Zone crossing display works every time, now. To test it, I just place the aircraft on a runway in a certain time zone, and then, use the World Airport Interface to plop the plane on an airport I know to be in a different time zone. Every time the green bar shows up with the red scrolling message that tells me I am in a different time zone. The clock change is always correct using FSUIPC 3.60, just the message that I have crossed into another time zone is missing. I realize real pilots don't have such a message to inform them of the exact moment they crossed a time zone, but that is not my real purpose for wanting that message, anyway. I want to know which time zone I am in, now. That is important to me. Thanks again, Pete. And I am sorry for all the extra work I caused you. Tim

Thanks, John. I'm glad it is not just me. I experimented by putting fsuipc 3.53 back and RealTime worked just fine, again. Maybe when Pete gets back he can fix it. Tim

I just installed FSUIPC version 3.60 and FS RealTime 1.76 will no longer tell me when I cross a time zone and what time zone I am in. I liked that feature and it seems that the new version of FSUIPC has stopped that. Is there a way I can get that program functionality back? Thanks, Tim