Pete Dowson

You have something assigned incorrectly, then. I cannot tell what you have done from here, with no information. Have you made sure that you haven't got things assigned both in FS and in FSUIPC? Multiple functions assigned in that way can be very confusing. Never have any button or axis assigned in both places. If you can't find it that way, enable Button and Event logging, also Axis logging, in the Logging tab in the FSUIPC options, and see what the Log file shows when this unwanted event is occurring. Show me the log if you don't understand it -- you can paste it, or parts of it, here. I can also check your assignments for you if you paste the [buttons] and [Axes] sections of the FSUIPC.INI filer here. Regards Pete

Source code for grabbing stuff inside FS wouldn't be any good for grabbing stuff from X-Plane or anything else! In fact the source code for FSUIPC3 isn't even any good for FSX or ESP either, as they are totally different -- FSUIPC4 is a SimConnect client and Simconnect didn't exist before FSX. The source code for the interface to FSUIPC is supplied in the FSUIPC SDK. That's all anyone needs to replicate the interface. Regards Pete

No, I've never heard of anything like that. It sounds like the router/switch is implementing its own firewall even though you think not. Either that or it is disguising your otherwise "fixed" IP addresses. The logs show nothing except that neither Server nor Client ever see each other. Have you tried providing explicit parameters in the WideClient.INI to tell it what the Server is? i.e. ServerName=BOZO1 Protocol=TCP Regards Pete

If you have purchased an FSUIPC4 key, and not, mistakenly, an FSUIPC3 key, then it will be valid providing all parts of what you are entering are correct. Every single time this has been reported it has ALWAYS turned out to be user error! I'm constantly amazed at how many ways folks have of spelling their own name differently, for instance. The name, email (or address) and key must ALL be exactly as stated. Use cut and paste to be sure. Regards Pete

MS aren't doing any more FSX development. There are some third-party instruction panels for FSX though. Regards Pete

No, not me. Sorry, I've too much to do as it is, and I'm really trying to do less these days, not more! (I'm over 66 now). The interface is well defined, however, and there has been success in making an FSUIPC interface for X-Plane, a module called "XPUIPC" -- google for it. There's even a WideServer and Client for it too. I've no objections to folks copying the interface for other sims, but I don't want to be involved, thanks. Regards Pete

Are you sure your program is getting enough processor time to actually run frequently enough? FSX is very processor intensive -- it will use 100% of one core, easily. If you are using a 2 or 4 core PC you might want to make sure FSX is using a different one to you. Try using the Affinitymask parameter in FSX.CFG to stop it using core 0, i.e. {JOBSCHEDULER] Affinitymask=14 for a 4-core processor, but use =2 for a 2 core one. Regards Pete

Sounds like you had the same axes assigned to different functions in different places. If you assign axes in FSUIPC, make sure they are not assigned in FS. It is really best to use only one or the other -- if using FSUIPC, turn off joysticks in FS altogether. Otherwise, if you disconnect and reconnect, or even for no apparent reason, FS will decide to do its auto-assignment based on its "rules" in its Joystick look-up files. Regards Pete

I've no idea what FSUIPC client DLL does, so I'm afraid you'll need to await an answer separately for that, but FSUIPC's data is updated when it changes. It receives changes (only) from SimConnect. It is asynchronous, though, because of the way SimConnect works (unlike how FSUIPC got data in FS9 and before, where FSUIPC grabbed it specifically on each frame, i.e. synchronously). The main determining factor on update rates will be FSX performance -- its frame rates. Really you should be reading the data at the FS frame rate, so limit the frame rate in FSX (eg to 25 fps) and read the data at matching intervals (e.g. 40 mSecs in this case). Note that FSX SP2/Acceleration is much more efficient in keeping to frame rates than the unpatched FSX or FSX+SP1 because of the way SimConnect changed its mechanisms for in-process clients -- before SP2 it still used TCP/IP protocols for this. The way your program, and this DLL you are using, is written will also determine what results you get. Each time data is requested (the "FSUIPC_Process" call to FSUIPC) there's a message placed on FSX's queue, and your own process is held up till that is processed and a response is made. if your program is resulting in many process calls per cycle, that will make it extremely inefficient. All of the data you need, per cycle, should be requested in one call, once per cycle. I suspect you are not doing this -- this bad programming practice is the usual reason for poorly performing programs. Finally, note that even at relatively good frame rates, larger (than the FS panel ones) and more realistic gauges can often still be observed to "step" unless you apply some smoothing in your own program. In other words interpolate or extrapolate between steps and keep the needles or whatever moving when they should be. Regards Pete

Okay -- if you come up with any specific questions whilst you work it out, do come back and ask them. Just because I don't give comprehensive tutorials here doesn't mean I won't answer specifics. Regards Pete

What sort of software would induce glitches to zero? That doesn't make sense. Unless you mean a specific add-on. I remember I had to add special spike elimination facilities in FSUIPC for a buggy FS aircraft panel for FS2002 -- but that wasn't on throttle, but rudder I think. The facilities are still available on the "miscellaneous" tab in FSUIPC3. Doesn't seem likely. However, if so then the USB adapter should be okay because the AtoD part must surely be dealt with in the adapter. I prefer made-for-FS scenery myself. Maybe that idea will be okay one day. Presently there's not enough high res satellite stuff on Google -- my house is there but whole swathes of England not far from me are only fuzzy low res still. Regards Pete

Well, overshoot isn't the proper term. The delay between you moving the lever and the Sim seeing the change could be anything from 20 to 100 mSecs (i.e. a 50th to a 10th of a second). If it was always a 50th or not far off you wouldn't have a problem, but, although 100 mSecs doesn't seem long, it is long enough for your real-time flying to make things difficult. YOU then overcontrol, because the response you expect to see comes a tenth of a second later than you expected. Not "overshoot", but "overcontrol". Pretty much most joysticks are stil "analog" in any case. Not sure what you mean by throttle jumping -- unless you mean it has gaps in its wiring or dirt on its carbon surface making breaks in the circuit? I'd use a good switch cleaner on it -- something like Servisol is good. Well, the filtering option might help if the spikes were really short-lived. There 's aslso a specific spike elimination facility. But neither of these things would have been any different on a WideFS client computer, even assuming such a facility was implemented. You've still not said why you cannot use your current one on the FS PC. If it is merely the lack of a Game Port you can get USB Game Port connectors quite cheaply, and they do a good job. Look here, for example: http://www.amazon.co.uk/s/?ie=UTF8&keyw95einlsg_e I really don't think there are any specific FSUIPC4 problems with any yokes you can get. The earlier Saitek ones had a problem with spurious button presses being generated (for which I put a facility in to eliminate) but I'm sure that's been fixed by now. I don't know any CH units by number. The link on the download site, the link in the documentation, and the links up in the Announcements above, all go to the right place in SimMarket. Or just go to SimMarket and select or search for FSUIPC4. And, no, there's only SimMarket, world-wide exclusive apart from a Japanese language site in Japan. Regards Pete

Can you tell me which steps, exactly, in the step-by-step procedures provided, that you don't understand? It seems a little pointless merely reprinting them here. Why do you want to change the Delta? The default value set for you is normally fine. Do you have lots of horrible jitter on your axes? If so you should really first try getting the hardware fixed, or using a better USB connection. You can experiment with things like Delta if you like, but I don't see any point in doing so BEFORE you've calibrated correctly because you really cannot yet see whether you need to nor if you are making things better or worse. The Delta is nothing to do with specific positions on the axis, is is merely the sensitivity to change, wherever. You are calibrating for a conditioning lever, then, not a normal fuel mixture which has no detente, no centre? If there's no "detente" in the Sim, don't calibrate in FSUIPC with a "centre" detente -- use the no centre option. If there is a detente in the Sim, then calibrate to it using the centre calibration facility in FSUIPC. You need to match your axis to what FS expects. That is why FS calibration is so versatile and why it can be as specific as you need to your particular choices of aircraft. Regards Pete

WideFS would allow the buttons to be used, but not the axes. It really isn't a good idea to have axes on a separate PC -- the response is too slow and would result in over-controlling the aircraft. Just plug your yoke and pedals into the FS PC. Why would you need to purchase new ones? Where do you "gather" that from? Yes, you can buy the two as a bundle, saving some money, but they are separate purchases otherwise. The only difference between FSUIPC3 + WideServer and FSUIPC4 is that the Server code is bolted onto the FSUIPC4 code, to make it operate more efficiently when otherwise SimConnect would need to load them both separately. It is due to the different module mechanisms in FSX compared to previous versions of FS. WideClient, the part that runs on the Networked PC, will NOT run on a computer which is also running FS. So, no, you do not run FSX on both PCs if you are using WideFS. That would be WidevieW you are thinking of. And WideClient is not a "controller". it is simply a networked FSUIPC interface for FSUIPC applications. You can link you computers in any way you like provided Windows will make them into a usable Network. You must have an operational network before you try WideFS. WideFS does not make a network for you. Regards Pete

The ATC responses are assigned in FS to the keyboard number keys, not the NUMpad number keys. However, they are still FS controls, so you can assign them to any keys or joystick buttons you like. In FSUIPC, use the key press assignments to assign keys to the FS controls "Atc menu 0" to "Atc menu 9" keys. To bring up and dismiss the menu use the "Atc" control. Pete

1. Update to 3.93 as 3.90 is no longer supported. 2. Sorry, no idea what CM is. 3. If you have problems calibrating in Windows, try doing FSUIPC calibration. If you properly follow the instructions in the User Guide you'll be fine. Pete

When it says "as ..." it means that is how it is stored there -- in other words in units of 1/65536ths of a metre per second. If you want whole numbers of metres per second, rounded down, just divide it by 65536, or shift right 16 bits which amounts to the same thing. If you want more accuracy, copy it to a floating point variable and then divide by 65536 so you get the fraction too. Please try using the FSInterrogate program provided in the SDK to help you understand things better. That is what it is for. You can see all the representations, side by side, in real time as they are changing. Pete

Thanks, except for calling me Pete Dobson :roll: Anyway, glad you are all sorted now. Regards Pete DOWSON :) :D :o

B560 is not correct for Latitude! It is 0560. You need to look in the document provided in the FSUIPC SDK, the one called "FSUIPC for Programmers". They don't need "converting". The offsets are provided in hexadecimal, used in C/C++ as "0x..." and in VB as "&H ...". there's just different conventions for telling the compiler they are hexadecimal numbers instead of decimal, that's all! Pete

Ah, glad it is sorted! Your earlier post confirming that must have come through as I was composing my last reply and searching for the fixing program! Regards Pete

So you could not unzip 3.90, which was available for months and downloaded and unzipped by many thousands of users with no problems, and now you have the same problem with 3.93, which is most certainly a completely different file and which has also been downloaded, unzipped, and run by many users already. ALL my files, here and on the Schiratti "Dowson" page are Zipped up the same way. And they are all perfectly good. I'm sorry, but you most certainly have a problem on your system or with your ISP/Router. I really cannot help further. You will need to find out what is wrong at your end and get it fixed. Regards Pete

The registry entry for Flight simulator is incorrect, then. It sounds like you moved your FS folder after installing FS. Sorry, but, for FS2004, that is nonsense. Copying the files is what you always did with FSUIPC before 3.93. There's no difference now except the Installer has tried its best to install for you. [FSX is different because there are other files, used by SimConnect, which point to the files so they get loaded okay]. Neither FSUIPC now its installer uses or has anything to do with the Internet. The file is an ordinary text file and is short enough to paste in a message here. By all means edit out your address in it if you wish. I expect the DASH8 is also trying to find your FS installation by referring to the Registry. Unless you get that sorted out correctly you will have problems with many add-ons. This is nothing to do with FSUIPC, but your faulty FS install. Once registered FSUIPC has nothing to do with the registry, but I'm not sure how you managed to mess up the registry entries for FS itself. I'm pretty sure there's a freeware program for repairing FS's registry entries some place. Otherwise you could try editing the Registry yourself. Let me google a while ... ... Yes! Go here: http://www.flight1.com/view.asp?page=library and get the "FSX/FS9 Registry Repair Tool (36KB)". Regards Pete

Assuming you are talking about user aircraft, not AI, you only get any indication of those if the user has files a flight plan. And then I think you have to locate and read the flight plan. Those are the states of AI traffic, not of the user aircraft. There's no indication anywhere in the system of what the user is doing, except by reading all of its data, like altitude, speed, etc. Regards Pete

Not sure about that. I think you uninstall SP2 which exposes SP1, then that, then FSX itself. But I'm only going by reports. I've never uninstalled FSX myself, and judging by all the problems that follow I am not inclined to ever do so. I know one thing for certain -- the uninstall does NOT uninstall SimConnect, which gets lodged into Windows' "side-by-side" (SxS) library system -- all the uninstall seems to do is break the links to it. When you then attempt to reinstall FSX, the installer thinks that SimConnect is installed (as it sees the WinSxS files) and doesn't re-install them, so the links stay broken. Those are the version numbers of the DLLs inside which correspond to the FSX.EXE version in the respective release. You are missing 61355 which is the SP1 version. The folder names contain the SimConnect revision levels which are 10.0.60905.0 for Base, 10.0.61242.0 for SP1 and 10.0.61259.0 for SP2/Acceleration. Not much use at all. I've complained about this right since the Beta days of FSX and it was never fixed -- it sort of fell between the FSX team and the Windows development teams in responsibilities and was never resolved. That is almost impossible. The SxS thing is insidious. You are more likely to make things worse. Just delete the two folders (not just the contents, you must delete the folders), then re-install FSX, then SP1, then SP2. There's probably no need to uninstall again first. Regards Pete