Pete Dowson

Well there's nothing designed in it to do that. I think the only way you might be able to do that is to program the first keystroke to send the FSUIPC-added control 'Key Press and Release'. You should be able to find it in the drop down list. The parameter for that gives the Keycode + 256 x the shift code. You'll need to look up the key and shift codes in the Advanced User's guide (the list in the Buttons section). For Shift+5 it would be 101 + (256 x 1) = 356, if you mean the NumPad 5, else 53 + (256 x 1) = 309 for the main keyboard 5. Regards Pete

That was just two days ago. Is that when you installed FSUIPC4 or FSX? If not, what have you changed in the last two days? Is the INI file, or the folder, read-only? Check their properties. If you used the FSUIPC4 installer (for any recent version -- 4.16 is the current one), then the Modules folder should be marked for read and write access. Otherwise, if you let FSX install in the Program Files folder, as it will by default, all of its folders are "read only". Try re-running the FSUIPC 4.16 installer. Pete

Sounds like you deleted the FSUIPC4.INI file. All those settings are contained in there. It will be in the FSX Modules folder. Take a back-up next time. FSUIPC4 itself never deletes it, but it will write a new one if you do. It simply re-reads the Button settings from the INI file. It allows you to make changes by directly editing the INI file (for the more advanced stuff like conditional actions or sequences) then load them in without having to close and restart FS. The FSX.CFG file is in your Documents and Settings\\Application Data\Microsoft\FSX folder -- unless you are using Vista, when it is somewhere similar. Regards Pete

Did you use "Run As Administrator" to load FSX, as instructed in the Installation section of the User Guide? Pete

Try version 3.761, from here: http://fsuipc.simflight.com/beta/FSUIPC3761.zip Let me know. It can't get those values any faster. Regards Pete

No. If you are talking about FS2004 or before, there are priorities, to avoid affecting FS performance. No, I think they are mostly the same. But even FS's own gauges are a little jerky. If you enlarge them you can see this. They get away with it because they are normally too small to notice. Programs like Project Magenta, and well-programmed add-on aircraft, tend to use their own smoothing (interpolation) to make the displayed gauge values change nice and smoothly. Well, I can check to see if it is one of the lower priority items. I have just had a look. The Manifold Pressure values are part of a large group updated at a second (not top) priority, which rates it at a little over 4 updates per second -- a quarter of the normal update rate (18.2 per second). FSUIPC has had this rate built in for these values for its whole life, 8 years now. Odd that itr should only now be seen as a problem? Anyway, seeing as PCs are several times more powerful now than they were 8 years ago, I guess I could relax some of those timings. Are there any others whilst I'm at it? Regards Pete

That's worrying. Not sure how they could arise .... FSUIPC certainly doesn't invent winds, and the incremental values to those which exist should be reasonably small. Where are you seeing these reported? If through WeatherSet or Radar Contact or other programs reading weather via the NWI, that may just be incorrect reporting due to me breaking the NWI, not 'real' winds. Okay. If you still see "freaky winds", please close FSX, add these lines to the [General] section in the FSUIPC4.INI file, and test again. Try to keep the test short as the log will get huge: Debug=Please LogExtras=256 Zip up the log and post to petedowson@btconnect.com. Thanks, Pete

This indicates that the TCP/IP connection used by SimConnect is being blocked by a security program you have running, probably a firewall. There's a note about this on the Microsoft FS web-site, and quite a few in my FSUIPC read-me which was installed with FSUIPC4. Regards Pete

The PFC yoke is not driven by my PFC driver unless it is wired for and connected through a PFC digital control system -- which in turns connects to a serial or USB port. The direct connected yoke is a normal joystick and is driven by normal joystick drivers. You do not use my PFC driver. Doesn't the yoke come with any documentation at all? I should need to tell you these things. As far as versions of my software are concerned, the answer is always "the current ones". I only support current versions in any case. Please check the Announcements above. Regards Pete

For you, the person? Yes. That's what it is for! It also adds facilities to write them where relevant. If you mean "you, as a programmer, via a program", then, no, but then neither was it possible with FSLook. The subset of values common to FSX, FS2004, FS2002 and FS2000 can also be read with FSLook2. Only FSLook itself, the original one, is not compatible with FSX. Regards Pete

Sorry, it evidently has to be something to do with the add-on aircraft. Since you did actually purchase it from someplace I think you ought to seek help from the suppliers/makers. Though I must say, a 1.9% increase doesn't sound like much of a "surge" to me -- more like a blip? And maybe the default idle under autothrottle control is higher than 54%? What do the specs for the aircraft say? Regards Pete

Sounds like you have some corrupted cloud graphics, or something similar. I've been using ASX from a Networked PC ever since it came out with no problems. You probably had a SimConnect.xml file with no local connection capabilities listed. Re-running the FSUIPC4 installer would have fixed that. There's no such thing as FSX without SimConnect, it's an integral part, and needed for lots of things as well as ASX and FSUIPC4. It means what it says. You have somehow corrupted or lost the original Simconnect version, the one which would be installed from the FSX DVD. Please refer to the FSX Help Announcement for details of how to repair/re-install that. That's right, and that's exactly why that FSX Help Announcement has been there so long and is still important! ;-) Regards Pete

There is no difference in access between one file and another in this Server folder. they are all files in one folder. I don't understand how you find that you cannot get one particular file, but all the others are okay!? Which file is it you cannot get in any case? What "beta" are you talking about? I don't have access to that server at all, it isn't mine. The current one is fine for all interim and beta releases as I can change the contents quickly and easily, and all but one or two folks have access to all of them 100% of the time. To get files uploaded elsewhere is much more complicated and I only do it for final releases. It takes a few days at best each time. Please clarify, exactly what are you saying does and does not work. Your message makes no sense at all I'm afraid. Regards Pete

The latest interim version, 4.169, now available, is more efficient in performing the visibilty graduation and other filters, only writing back the weather when it has changed sufficiently. If you are still testing 4.168 or before please change to 4.169. Regards Pete

The latest interim version, 4.169, now available, is more efficient in performing the wind smoothing and other filters, only writing back the weather when it has changed sufficiently. If you are still testing 4.168 or before please change to 4.169. Regards Pete

Good. Really? It seems clear to me: this is directly from the FSUIPC4 page: 1. DOWNLOAD LATEST PRODUCT FILES AT http://www.schiratti.com/dowson 2. PURCHASE KEY FROM THIS PAGE 3 . Personal Registration Key will be generated upon purchase, an email is sent ONLY ONCE to your email address used to order. You can find your key on record in your order listing in your user account online anytime. Your Key is valid for ALL Version 4 updates! (My emboldening) Other than using a huge font for the word "Download", what would you suggest would make it any clearer? It has stood the test of time without any problems -- one year for FSUIPC3 but over 4 years for FSUIPC3 and WideFS6. Regards Pete

FSLook was written to test Gauge variable access in FS2000. It did work through to FS2004 because the Gauge system was broadly compatible. However it won't work in FSX. And the message you should have got, if you used it on the same PC as FSX, was "Error: IPC message failure: not correct FSUIPC installation?". However, its close cousin "FSLook2" will work perfectly well, as that was written using the standardised FSUIPC interface, not the Gauge interface. However, its list of Gauge-type variables has not been updated for some time, so it will not reflect any new provisions in FSX. The best way to see FS variables, and indeed to manipulate them in real time, is via FSInterrogate. The latest version, including an FSI variable definition file which is up-to-date for FSX, is provided in an update to the FSUIPC SDK on my Support Forum. Well, actually you'd get answers quicker if you asked in the right place -- Pete Dowson's Support Forum, as publicised in all my programs and documentation. ;-) Regards Pete

Erwhen you "ordered the program via SimMarket", all you did was pay for a 12-character access Key. The program itself is downloadable from http://www.schiratti.com/dowson whether you make an order or not. SimMarket do not supply the package itself, and you don't get anything delivered at all -- in fact I think you have to go and collect your Key from your Account page at SimMarket.. It does actually tell you this on the SimMarket order page. You could have installed it, read the manual etc etc before you paid for a Key to access the additional user features. Regards Pete

Sorry, I cannot support such old versions! (3.4 dates back to October 2004, three years ago!). The current supported version for FS2004 is 3.75. Pete

What is an "attempt to install FSUIPC", please? There are no "attempts" needed, you simply put the DLL into the Modules folder. That's it. It's either done or not done, not attempted and failed or anything else. What EXACTLY is the message? What makes you think it is anything to do with FSUIPC? If you are not using the currently supported version, 3.75 or later, please do so. Regards Pete

And, if you have run FS9 and registered, there must be three other FSUIPC files there too: FSUIPC.LOG FSUIPC.INI FSUIPC.KEY These three files are generated for you. The INI and LOG files are re-written every time you run FS with FSUIPC installed. I do not know this "RealATIS" program, and I cannot imagine what it is doing looking for the FSUIPC.KEY file. Are you using Vista by any chance? If so it is likely you are not looking at the real FS Modules folder, but at an alias. Vista plays some funny tricks with programs like FS2004 which are marked as "legacy" programs (non-Vista compatible, effectively). These aliases deal with the problems of programs, written to run perfectly under Windows XP or before, which actually have the cheek to try to write to their own folders! Under Vista ALL folders in "Program Files" are read-only except for Installers unless you are an Administrator with elevated privileges. It sounds like this RealAir program is also not truly Vista-aware and is looking in the aliased Modules folder not the real one, though how you do get to the real one I've no idea. Maybe someone who knows Vista will help. Personally, what I would do if I were you, to avoid this problem and probably many more in the future, is un-install FS2004 and re-install it someplace else, like C:\FS9, or even on another drive. Avoid the default "C:\Program Files\Microsoft Games\Flight Simulator" folder install like the plague. If you aren't using Vista I'd need more information to help. In either case please make sure you are using the latest supported version of FSUIPC (3.75 or later). Regards Pete

Yes, annoying, isn't it? Apparently the "administrator" cannot actually administrate properly without gaining extra status through an assortment of extra measures. I think MS have gone a little too far in trying to protect the user against himself! Regards Pete

You need to run FSX in elevated Administrator mode. The need to "run as Administrator" is actually clearly documented in the User Guide. Please refer to the section on Registration which deals with this very point. (Or at least it does unless you are referring to a very out of date manual, in which case please go get and install the current version). Pete

Okay. If it proves difficult at all, and now I know this field is supposed to be the filepath, not the filename, I can do one of two things in the next version of FSUIPC4 (which is fairly imminent, awaiting only the release of the Acceleration Pack from MS): 1. convert any relative filepath to a complete filepath automatically, OR 2. Convert any filepath at all to a full UNC path -- i.e. one which can be used from any PC on a local Network. Does IYP work through WideFS at all? If so it would need the latter form.