Pete Dowson

Sorry, in FSX such text can only be handled by FSUIPC if it is sent to FSX through FSUIPC. In FS9 all programs sent text there through FSUIPC, and also FSUIPC could intercept FS9's own texts. Not in FSX though. :-( It is something i tried hard to achieve -- also, and even more importantly for me, the ATC menu screens and other menus like that. But i failed miserably! Regards Pete

The amount of thrust available for reverse varies from aircraft to aircraft, and is never mre than 25%. The value is defined in the Aircraft.CFG file. Actually airbus thrust control is very different in any case, if implemented correctly by the programmers. AFAIK there really is no continuous thrust "axis" as such, the different inputs just select the thrutst gates or modes (sorry, I am not well up on airbus terminology). You probably need a button to select reverse mode before you can control that. Regards Pete

FSUIPC options are found in the Add-Ons menu (in the menu bar at the top of the screen during flight - press ALT if it isn't visible), and the calibration tab is actually called "Joystick Calibration" so it should really not be difficult to find -- surely not very mysterious? The first calibration page has a section marked "Throttle". Surely you can find that? Again it isn't very difficult, and certainly not hidden! Then see where it says "Map to 4 throttles" just as I already told you? Click that, then use the little right-pointing button near the top to move to page "3 of 11". Now just "Set" and calibrate Throttle 1 there. When done, just use the Map buttons to cover the other engine throttles on the same page. There is nothing difficult to find, and it has proven to be quite easy and intuitive to use even without documentation, so I am realIy at a complete loss to know why or how you haven't managed to go even one step!? What is missing in the documentation and my earlier reply to casuse this problem? I have explained everything in the User Guide. If I were to explain it all again here it would be like an extract from the User Guide. Seems pointless writing one in the first place if it has to be repeated on-line as well, don't you think? It isn't as if you have to read all of the manual. I pointed you to the section to read, and it does actually show pictures of the correct part of the options, and gives you numbered steps to success! Pete

The client Log shows that it is simply waiting to find out where the Server is -- i.e. its IP address and the protocol to be used. This is, by default, broadcast every second by the Server. But it only gets to computers in the same WorkGroup (a Windows' restriction). Please check that both your PCs are in the same workgroup -- with Windows 7 you can find the Workgroup name in Start -- Computer -- Properties. You can also change it there, to be the same. An alternative, and one which was the only way to link Client to Server in the earlier days of Windows (WideFS has been around since 1995), is to add the Server IP address (ServerIPAddr) or Name (ServerName) and the Protocol ("Protocol=UDP" or "Protocol=IPC") to the WideClient INI file. This is all described in a short section of the WideFS User Guide, the part headed by a Red banner urging you to read that little bit at least. Once the Client knows how to contact the server you should have no problem. It would be the same for any networking program. I don't understand this part. (If you want to run ActiveSky on the client PC, you should really install it there. It will be very inefficient otherwise). Regards Pete

No, that's realy not true. Installation merely consists of placing WideServer in the FS9 Modules folder, and WideClient anywhere you like on the other PC, then runnng FS on the one and WideClient on the other. There's normally absolutely nothing else to do if you have a properly working network with no impediments like fiewalls -- and why put a firewall between two of your own PCs in any case? Except in rare circumstances WideFS doesn't even need any configuring at all, it is all automatic. There's no sharing options for WideFs as it doesn't read/write files across the network. There are no "error logs", only logs telling you what is going on, and in general if there's anything odd in them you are better off just showing them to me. I see that you have pasted in 2 partial and 2 complete Server logs which show that the server is indeed running correctly. Unfortunately, as you must surely realise, a Network link has two ends -- one on the FS PC and the other on the other PC, the 'client', where you run WideClient. You need to show me the Wideclient log. The Server is fine but that's only half the story. I also need to know what versions of Windows you are running on the two PCs concerned. Also you really do need to actually describe why you think it isn't working. What programs were you trying to run on the Client? Are they FSUIPC applications? Regards Pete

Reverse thrust on the joystick lever is available if you either map the throttle to the 4 throttles, then calibrate there, or assign to an individual engine throttle and calibrate in the same 4-throttles page. You can map the throttle for the other endines there too. All this is covered quite clearly in the FSUIPC User Guide. Check out the calibration chapter. Pete

Yes ... I don't think the version of SimConnectP3D.DLL FSUIPC installs will support such an old version of P3D. I should really change the Installer and warn you to update to 1.4, the current version of P3D, as it is difficult to support anything earlier. It might work if you remove the SimConnectP3D.DLL from the Modules folder, but you would really be far better off updating to the current Prepar3D, which has been out some time now. There are rather a lot of things not working in 1.2. Regards Pete

The autoscan option only affects whether it looks for new devices when entering the options. This just repeats exactly the same device scan which is always performed when FSUIPC first loads. Pete

Please never just say "latestversion" as it means little -- folks have said that when in fact they'd somehow found and installed a year old version! There's always a version NUMBER, and that's the only definite way to say which version -- it is easy enough to find, On screen, in the DLL properties, in the Logs, in the documentation. What about oher add-ons which might be using the key? And why are you identifying it as the '<' key not the ',' key? are you sure it works? Pete

It certainly sounds like either faulty potentiometers or, perhaps more likely, bad definitions of those two axes in the Registry, possibly caused by the original installation or another driver. If the values you see coming in on the Axis assignments tab in FSUIPC are misbehaving so much there's really nothing FSUIPC can do about that -- those are the values actually being read from the device. Since a "full reinstall" of FSUIPC merely replaces the one FSUIPC DLL with an identical FSUIPC DLL, no. It will make n difference. FSUIPC does not store things away in Registries or anywhere else. Everythng is cntained in the program (the DLL) and its settings (the INI file). You'd probably be better off trying to uninstall the joystick device and driver (eg via the Windows device manager) and reinstalling, or even allowing Windows to select a suitable default driver. For CH devices you should find a lot of help over at the CH Hangar, http://www.ch-hangar.com/. There's also a lot over in Bob Church's "stickworks", http://www.stickworks.com/, including a lot of downloadable files and programs for helping sort stuff out. Regards Pete

It works okay here. What version of FSUIPC are you using (in fact what version of FS?). FSUIPC makes no distinction between any of the normal keys. '<' is not special, though on my keyboard it is really the ',<' key, with ',' being the normal use. Perhaps there's another program which is using it ahead of FSUIPC, so that FSUIPC doesn't see it? Or maybe you already used it in the Hot Keys tab? Regards Pete

With FS9 I don't think you can set the airspeed directly. With FSX you can set it, but only at the same time as setting initial position. The value is the Course setting, or "OBS" as Microsoft calls it. For NAV1 it is 0C4E, for NAV2 it is 0C5E. Pete

Yes, that's correct. Yes. you are correct. I misread the page number. Method 2 is there, on page 45, it starts several paragraphs from the end of that page. there's a heading "Method 2:" Pete

Sorry, I don't follow any logic at all in what you are saying. In any case, FSUIPC uses standard Windows DirectInput calls, same as FS, and folks report the same problems without FSUIPC in FSX. It's some problem with Windows 8 and certain joystick drivers. Pete

The whole point of separating the processing of the requests from the actual individual read and write is to allow many reads and writes to be accumulated for processing all at once. The actual read/write calls merely add a request to a list inside your own program. Every Process call involved a Process Switch, with FS being interrupted so that FSUIPC can process the list of requests -- whilst this happens your program is frozen. What you are doing works, but it is extremely inefficient. It slows FS down and it cripples your own program's performance. If you are writing the program only for your own use and are happy with the results, then it isn't a worry. But it makes things look worse than they should be. Regards Pete

Is 11D4 still zero? There's no way to make the interface operate correctly if so. Pete

No, that is the FSUIPC4 run-time log, showing that last time you ran P3D your old copy of FSUIPC (4.823) was working okay. There must be an Install log, else how did you first install FSUIPC4? You should have downloaded and run the current Installer, for version 4.86. Pete

It only asks once, at the end, it never "keeps asking"! All of the installation actions are performed before it ever reaches the request for the registration. It logs everything it is doing and displays the log whilst it is doing it. There is no way it can possibly bypass any of that before getting to the registration stage. And what version number do you think is the "latest version"? Just saying "latest" is no help at all I'm afraid. Folks have said that when installing a year or more out of date version. There will be an Installer Log saved in the FSX and/or P3D Modules folder. Show it to me. You can paste it here. Pete

Depends why you have the problem in the first place. FSUIPC treats all axes the same, toe brakes are just two more axes to be assigned and calibrated. Regards Pete

That used to happen occasionally, and was always okay on 2nd or 3rd try, but was fixed a while ago. Your 4.853 is actually out of date and unsupported. Always look for updates when you find a problem. The current earliest release available is 4.86 (install that first), and there's a later one in Download Links (4.869). Regards Pete

Really? FSUIPC4 or FSUIPC3? Which version of FS? The visibility tab is omitted by default in FSUIPC4 (on FSX and P3D) because the facilities it offerred never worked correctly in FSX. There are problems in Simconnect which I never ovecame. Programs like Active Sky have managed to solve the problems quite well by using all sorts of tricks, but FSUIPC is not and never was intended to be a weather generating program. If you are talking about FSUIPC4, then you CAN enable the visibility tab and try things out, but please told come to me with problems. It is enabled by a parameter in the INI file. Check the documentation, it is all explained in there. Regards Pete

It works fine. Check it with FSUIPC logging or with FSInterogate. You don't show how you've defined "g", maybe you are interpreting it incorrectly due to a bad declaration? Note that it isn't updated in slew mode (as documented), but it is either 0 or 1. Regards Pete

Odd then, that you didn't know what a menu was, and hadn't even seen the Modules entry which is where FSUIPC's options are accessed before. If you know so much why say you understood nothing? I don't think it is condescending to speak simply and at a low level to someone who says or implies he knows nothing by saying "I have no idea what any of that means"!. I've never thought of it as the "in-flight menu" specifically, as it is the only menu I know of in FS. All other options are presented in dialogues or sub-menu drop downs from it. Thanlk you for logging 11D4. Here is the problem: 11D4 provides FSUIPC with the pointer it needs to connect into most of the parts of FS9 which it needs to in order to support the Application interface. I've never seen that being zero, not ever before, but it is catastrophic for FSUIPC's nterface. I can only think that your FS installation is corrupted somewhere. Maybe you need to try repairing it or reinstalling even. Regards Pete

Hmm. Interesting. I'm not sure whether this means it ONLY works if you first set a flight plan, or whether it was a change in SP1, SP2 or Acceleration after the initial tests on 3130 were done. I wonder ifyou can change the tail number and airline name used by ATC too (offsets 313C and 3148)? Seem less likely because they are paint jobs too. Obviously it is more useful to be able to change the flight number in any case. Thanks. I'll update the doc ready for the next release, whenever. Regards Pete

Really? What about the WideServer.log in the FSX Modules folder? Maybe you should paste both logs here so I can see? If it is anything to do with WideFS, the logs will show. Don't forget there are always two ends to a connection. Merely checking one end is not sufficient. As certainly described quite clearly in the WideFS User Guide, in FSX the WideServer part in incorporated into FSUIPC4. It merely needs activationg, first by Registering it with its own Key in the FSUIPC4 Installer, ad then on the main FSUIPC4 options tab in FSX -- though that will probably already be enabled by default. Documentation is supplied both for FSUIPC (in the FSUIPC Documents subfolder in Modules) and for WideFS (in the ZIP you downloaded). Everything is explained in both places. Regards Pete