Pete Dowson

That shows FSUIPC4 installed okay. Where's the FSUIPC4.LOG? This would show if FSUIPC4 is loaded but experienced a SimConnect problem. No. Is there a "Tools" menu for your SDK add-ons? Deactivation may not be enough. But see if there's an FSUIPC4.LOG. Also see the FSX Help announcement above. You may need to get a SimConnect log. Pete

No, ASX is a SimConnect client, and there never have been any AI traffic add-ons which needed FSUIPC. Regards Pete

You'll never find any "new" offsets via FSUIPC these days as the representation of the data as being laid out in memory inside FS which contains all of its stuff is merely an illusion. The offset values are now simply ID codes -- the data is obtained from all over the place, sometimes by direct access through layers of C++ style class pointers, sometimes procedurally via C++ style virtual function calls. I don't know any way to get into the FS ATC subsystem at all. Sorry. Regards Pete

I do hope you are not doing a separate FSUIPC_Process call for every variable! Each one requires a process change. Collect all of your FSUIPC_Reads and Writes together for one Process call. What do you mean by "slow"? It simply returns the current value, just like anything else. No difference. How are you measuring the response? Pete

You should not assign anything in FSUIPC if you also assign it in FS itself. If you do this then every time you move the axis there twill be two copies of exactly the same things being sent through to the Sim engine. Very inefficient. Only assign in FS or in FSUIPC, never both. The only problem with aircraft like the LevelD is that it assumes the axes are coming from FS controls. If you assign in FSUIPC to go "direct" it bypasses the code in the LevelD aircraft. You can of course make assignments in FSUIPC aircraft-specific, so that LevelD can be treated differently from others quite easily. Regards Pete

I do document these things. I know nobody reads documentation, but surely after having a problem, didn't you try reading even just the Installation section of the FSUIPC4 user documentation, where it (hopefully) clearly explains how to make registration work on Vista? If so, could you tell me what wasn't clear about it so I can improve it? Regards Pete

When you press ALT in normal flight mode, do you see any menu at all? the "Add-Ons" entry is only the last (right-most) one -- it is added by SimConnect when any add-on is loaded and run. Is there an FSUIPC4.LOG file in the Modules folder. If not then FSUIPC4 isn't even being loaded. If so, look at it, see if it reports a SimConnect problem. For SimConnect problems see the FSX Help announcement above. Regards Pete

Thanks, but actually it was the Bravo Zulu "Special Achievement" Award. HiFi's ASX won Best Utility in the Bravo Zulu section, and Radar Contact 4.3 won best utility in the Reader's Poll. Regards Pete

Just run the supplied Globalsign Root fix (see inside the FSUIPC.ZIP). You have a faulty install of Windows, or an old version without the GlobalSign root included. Pete

The Latitude value at 0560 is NOT floating point, but fixed point. Where a floating point value is documented, you simply read it directly into a floating point variable. Do not convert it into floating point, it is already floating point! Pete

Please always test with current supported releases of FSUIPC first. The main current release is 4.20 and there are updates in this forum. Are any of the axes assigned in FS? If not, and you haven't assigned them in FSUIPC's axis assignments either, they won't be seen in the FSUIPC calibration section. If you can make it work with FSX then it will work with FSUIPC4. Check that first. Regards Pete

Is that possible? it would need either NMEA or Aviation format input capabilities. Maybe, but GPSout was never ever intended for interfacing to any GPS. The whole purpose is to make FS+GPSout look like a GPS to mapping programs, so you can connect a moving map or similar, as you might to a real GPS. There are some GPS units which allow positional input via NMEA or Aviation (AV400?) format input, but not many. I have three GPS units and none have such capabilities. Regards Pete

There's no FSX.CFG file, which means you have not yet run FSX after installing it. Please run FSX first. FSUIPC4 install needs to find the FSX.CFG file so that it knows where to place the DLL.XML file. Regards Pete

Assuming your controls aren't faulty, it sounds like you have more than one assignment active for the same FS controls -- have you actually disabled all joysticks in FSX, or merely de-assigned the axes? It sounds like they are still active and therefore interfering. Er, can you explain that? The Axis Assignment facilities in FSUIPC are really aimed at specialist use, for those who wish to do things like have different controls automatically connected when changing aircraft, or who need to convert axis inputs into other actions entirely. The main use of FSUIPC for axes is in the Joystick Calibrations section, which can, as always, be used no matter how you assign them. The Axis Assignments facility was a recent addition for specialist uses -- the calibration facilities are the most used, so why are they not of use to you? Regards Pete

But none of the default aircraft? If so, then you really do have to get th add-on makers to help. Sudden wind changes, especially reversals, yes, but they would affect all aircraft, defaults included, which seems not to be the case. If it were, just enabling Wind Smoothing in FSUIPC should fix it. FS9 is known for wind reversals, but these are occasional not all the time, and related to the numbers of weather stations in the locality, so are not universal all over the globe. Well, this is unique to yourself, so it is very difficult to understand. I can only suggest you stick to the default aircraft, or purchase good quality add-on aircraft. Regards Pete

FSUIPC or FSUIPC4? There's no way it will do that. But did you run the Installer? Please check the FSUIPC logs in the FSX Modules folder -- are there both Install logs and a normal Log? It is more likely that you have another add-on installed which is doing this, but I cannot tell from the zero information you supply. Sorry. I am away now until December 4th. Regards Pete

1. There is no version 6.77 of WideFS. 2. My ZIPS contain no such program as "fsclient.exe", so it seems very likely that you are actually downloading the wrong package entirely, one by someone else. 3. All my products are now signed with a GlobalSign certificate and are guaranteed against interference and virus infection provided the signature is correct. Just right click on any of them, select properties then see if the signature tab says it is all okay. If it isn't, do not use it. 4. Most of my products are also encrypted and compressed, producing in them random looking bit patterns which some anti-virus programs may occasionally identify as a virus. This is always a false indication, and the virus updating authority for the package should be informed of this mis-indication so they can make their checking more accurate. Regards Pete

I've no idea where you are looking, but I've not seen any such confusion at all. But the answer is easy. No FSUIPC applications need registering provided you are using current versions of FSUIPC. How on Earth do you read anywhere at all that WideFS has any capability whatsoever to fake GPS output? You most certainly won't get that at all from WideFS. Please read the WideFS documentation -- it clearly and absolutely says that WideFS provides support for the FSUIPC interface -- i.e. for applications using FSUIPC -- across a NETWORK! Your com link is not a Network and your "Delorme Atlas" or Streets and whatnot are most certainly not FSUIPC client applications! How do you come up with such an idea? GPS output, oddly enough, is provided by GPSout, which for FSX is built into the User Facilities in FSUIPC4. To use them you need to pay for and register FSUIPC4. There is an advanced facility in wideFS for receiving the output from GPSout and sending it to a serial COM port on the Networked PC, but this is most certainly not something your are needing as (a) you are not using a Network, and (b) you are linking the PCs with a serial cable, exactly as documented for use with GPSout. Do you realise that neither of your actual questions seem to relate at all to your first statement about registration confusion! Regards Pete

Either COM1 (value 0x80 in 3122) or COM2 (value 0x40) are always set. They read okay and write okay here, and the change is visible on the radio stack switch LEDs. I've just checked with FSUIPC 3.766 and the default FS9 Cessna. Maybe the aircraft you are using doesn't have a COM2? Pete

No confusion, and not a problem. Please do come back if you find anything else. As I said, logging in FSUIPC might help. But I think some process of elimination will be most enlightening. I'm not here again till the 14th in any case, so there's no need to rush anything for my benefit! ;-) Regards Pete

Your Client log shows the client is simply waiting to receive a broadcast from the Server so that it knows who it is and what protocol to use. Are all PCs running WinXP? If the clients aren't running WinXP you'll need to provide the ServerName and Protocol parameters in the WideClient.INI files. This is documented. The automatic connection makes use of Broadcasting from the Server, and I don't think older versions of Windows handle that. The other thing to check is that all the PCs are in the same workgroup. Broadcasts don't work between different workgroups. Regards Pete

Assuming you are using Windows XP or Vista, if the whole system freezes it is a driver issuemost likely video driver, but possibly, less likely, a game controller driver. Or even a sound driver (check that by turning sound off). The fact that it occurs only in specific circumstances only means that the timing coincidences critical for the hang to occur are altered by what is running, memory arrangements, and so on. In fact, considering the latter it could even be a memory chip problem. I don't support any FSUIPC earlier than 3.75 in any case. There's also a later one available above (3.766) - see the "Other downloads" announcement. Try also without sound, with earlier or later video drivers, with different graphics settings in FS. And see if you can get the memory chips tested. With current versions of Windows it is impossible for user level applications like FS and FSUIPC to cause the whole system to hang. Such things have to be low-level drivers or harware. Regards Pete

Yes, but those are all either for built-in FS facilities, or ones added by FSUIPC. The one you asked for is specific to that add-on panel, and is probably implemented internally as some sort of throttle adjustment. Maybe you could emulate it easily with an Axis throttle set control with the parameter giving the required value. Like the "0" key on the keyboard to set the throttle to idle. But I don't know. I don't have that aircraft and I've never heard of the function before. If you are wanting to use it you probably know what it does and can therefore select the best way to do it. Where are you looking? If FS's assignments, or the FSUIPC drop-down? The FSUIPC assignment drop-downs merely list the internal name for functions directly from FS's own "CONTROLS" table. Even I don't know what many of them do, and some don't work in any case. It's a matter of experiment. You can't do any harm. I did try, in FS98/FS2000 days, to annotate some of them -- the document doing that is still available on http://www.schiratti.com/dowson . But I gave up when I found how many were added / deleted/ not working in subsequent releases. The FSUIPC-added specials are documented clearly enough, I hope, in the FSUIPC Advanced User's Guide. Button flags and all of the Offset controls are detailed there. The NT361 thing is a relic of some old yoke which FS98 used to support directly. That control may or may not still be hooked up inside FS, I don't know. If you had an NT361 you could try it, but I've never even seen one. Regards Pete

Yes, in the documentation in FSUIPC where it explains about registration. The name and email address has to be the same for both FSUIPC and WideFS. They are your identity as far as the Registration component is concerned. If you ZIP up your FSUIPC.KEY file (from the FS Modules folder) and send it to me along with your WideFS registration receipt and details from SimMarket, to petedowson@btconnect.com, I will replace one of your two keys with a matching one for the other. Decide which email you want to use and let me know. I'm afraid that if this doesn't arrive soon (i.e. before 1800 GMT today, Monday) , I won't be able to deal with it until I return on the 13th. If you miss me and want to sort it out before then you'll need to raise a problem ticket with SimMarket and see if they can handle it. Regards Pete

Hmm. I don't think I'll have enough time, at least in the daylight hours. As I say, it'll be hectic. Work work work. (Well hobby-turned work, but still ...) And I'll have no transport in any case (I am not allowed to drive because of my partial sight problems). I've always found the U.S. pretty difficult for non-drivers. The holiday is in Argentina and Chile -- another steam railway tour! ;-) Regards Pete