Pete Dowson

I strongly object to you saying it was an "FSUIPC4 problem"! There's nothing changed in FSUIPC4 that reinstalling it would affect. Possibly you simply made bad settings, so simply deleting the INI file, the only file containing all of your settings, would have also sorted it. The whole of the program called "FSUIPC4" is contained in the one module, FSUIPC4.DLL, and reinstalling it does not destroy your settings -- there would be a furore if it did! Pete

That's a log from a perfectly working FSUIPC version 4.50 which is very much out of date and totally unsupported. It is not possible that any recent version produced that log. Version 4.50 of FSUIPC is getting on for three years of age too, so maybe you've never used a later one since then? Who says they are missing? They are all addressed in that DLL.XML file. You can see the names if you peer closely. There's probably only a minor glitch in that file which is stopping things, maybe a missing bracket or something. XML files are pretty unforgiving. i hate the things. As far as I'm concerned they are another mistake of Microsoft in their efforts to make things as complicated as they can (much like side-by-side libraries like SimConnect). If you want to start from scratch I would start from a fresh install of Windows if I were you. Reinstalling FSX almost always seems to make a worse mess than you had before, because it is almost impossible to get a clean uninstall of SimConnect.. Pete

Best to use Profiles in the first place -- check them out in the User guide. For multiple liveries of the same aircraft you need to set ShortAircraftNameOk=Substring (instead of 2No") in the FSUIPC.INI file, then find all the mentions of your aircraft in section headings (like [Axes.<name of aircraft] etc) and replace the name with something short, like A320 or Wilco or whatever you need to identify the whole group. Appropriately named Profiles would save you that. The latest versions of FSUIPC default to Profiles, but only if folks haven't already set up aircraft specific settings. Regards Pete

Version 4.727 is clearly available on the Download Links subforum as I stated! All of the latest versions are there. Other folks don't seem to have a problem finding stuff there. Check the thread entitled "Updated Modules". That is probably because you used an inappropriate editor. Those ".." parts you see are the new line codes. Your editor is probably looking for a "return" code. I'm afraid I can't easily check it for you pasted in that form. So that DLL.XML is faulty -- probably a result of some earlier failed install of another program. There appears to be a number of other DLLs you need loading, so if you can find a way to paste the original DLL.XML properly then I'll try to fix it for you, or else Zip it and send it to petedowson@btconnect.com. Pete

I assume this is invoking a menu in FSX's Add-Ons entry? There's a problem in that once the menu opens FS is "modal", meaning only that mode, menu mode, is operative. The main functions of FSUIPC, in the main thread, directing the keystrokes, are not able to run. Trying to program menu access from FSUIPC is therefore always problematic. It will sometimes work and sometimes not depending on how fast it is able to operate, obeying the parameters from your INI file, compared with FS's reactions to the keypresses it is receiving. I'm not sure what might be going on there. There shouldn't really be any difference. Maybe the timing is slightly better that way, but it would surely depend on all sorts of other things. No, in matters of timing like this there are too many factors at work. The only solution i can think of which has worked for other applications, even as far as, for instance, opening up the fuel or payload menus and entering values, is to make your button invoke a Lua plug-in which sends the required keystrokes. That gets around the "modal" nature of menus because all Lua plug-ins run in separate threads. Please look in the Lua stuff installed for you in the FSUIPC Documents subfolder in FSX Modules. The Lua introductory document lists those examples I mentioned: "Fuel737.lua" and "Payload737.lua". Those are much more ambitious that you needs but will show you how to do it. Regards Pete

The installation log shows that part went okay. So now we need to find out if FSUIPC is actually being run or not. First, please go to the Download Links subforum and get the latest interim FSUIPC4 update (4.627 as I write this). Place it in your FSX Modules folder. Then run FSX again. If still no FSUIPC menu entry in Add-Ons, close FSX, and look in the FSX Modules folder for an FSUIPC4 Log file. If there is one, then at least FSUIPC is getting loaded. Please paste the Log here. If there isn't one, then it isn't even being loaded, so the most likely problem in an error in the DLL.XML file. You'll find that in this folder: C:\Users\Todd\AppData\Roaming\Microsoft\FSX Try renaming it, then re-rerun the FSUIPC 4.703 installer (don't worry, it won't overwrite 4.727 or later). That will make a new DLL.XML file. Try FSX again. If that works, then there was an error in your DLL.XML file before you installed FSUIPC originally. If there are other Modules to be loaded we'll need to fix it, so paste your original, renamed, DLL.XML file here and I'll take a look. Regards Pete

Hmm. Maybe, but I'm afraid I don't know much about it. You still need to ask the folks who implemented it. Thanks. I wouldn't know where to start looking. Folks use FSUIPC in all sorts of ways and I can't really diagnose problems with software I don't have nor know how they work. Normally the best source of support for an addon is the add-on producer. Regards Pete

No need to shout! ;-) If you search the FSUIPC4 Advanced User's guide for "wilco" you'll find this section, which should help: Regards Pete

I'm not sure how an unregistered FSUIPC4 or even a registered one has anything at all to do with hovering your add-ons? Have you tried the support forum for the products you are using which don't work for you? Regards Pete

There are a lot of old threads on interfacing to assorted Garmin Aviation devices. This thread is the first involving an Android device. Would you like to post a constructive help for other such users to the User Contributions subforum, please? Then it won't get lost as it scrolls out of sight like the others. Thank you, Pete

I have moved your Support request to the Support Forum. For some reason yuo posted it as a User Contribution instead -- those are for solutions, not problems! That message has not existed in FSUIPC for at least 5 years! You must use a current version of FSUIPC -- for FS9 the earliest supported version is 3.99. Regards Pete

Sorry, I'm trying but I cannot work out what you are saying the problem you have is. You can assign throttles and get them working, but ... what? No. The left/right axis on your joystick or yoke is aileron. The rudder controls control the rudder, for balanced turns. Most toe brakes on pedals are reversed. Before calibration you must check the "REV" option, or the will only be "off" when fully pressed and "on" when released! And to get a decent null zone just follow the steps to correct calibration as ennumerated in the FSUIPC user guide. Regards Pete

Really? Have you tested with 4.727? I need you to use the same version as me and get the crash details from the Windows error log, as adviced earlier in the thread. Else I cannot do anything. judging by your Log it isn't anything to do with any Trust problem in any case. THere isn't a "CTD" for the Simconnect trust bug, and even if there were one of the symptoms is that FSUIPC is never loaded so cannot produce a log. If you peruse the more recent messages in this thread you are adding to you will see how it evolved and what the reason was. Although it isn't relevant anyway, it is there, just probably in a different menu. It's related to the version of Internet Explorer, not Windows. However, it is certainly still there in IE8, in the same menus -- Tools-Internet Options-Content. And that's in my Windows 7. I can't see that it would have moved much in IE9 though I'm not willing to instal it just to check (I use Firefox or Chrome not IE, and of course those don't deal in publishers and certificates, only IE does). According to the Log, your problem is that you seem to have uninstalled parts of FSX before reinstalling it, but of course you could not uninstall SimConnect SP2/Accel. So it is still there, and programs like FSUIPC which prefer it will try to use it. SimConnect SP2 is not compatible with FSX SP1 or earlier. You can see all this for yourself, here: The best answer is to install FSX SP2 or Acceleration again. If you must stick with an older buggier version of FSX then you will probably either need to reinstall Windows in order to get rid of SimConnect SP2, or, for FSUIPC only, use the fiddle in version 4.727 as described in one of the earlier messages in this thread in order to force FSUIPC to use SP1 or before. i.e. this suggestion: But for this you must get version 4.727 or later, of course, as this was only added very recently. Rehgards Pete

Yes. If you want help interpreting the Log, show me the bits and I'll try. Pete

Sorry, I've no idea. Perhaps the same problem? Perhaps you are running FS9 at a different privilege level to the programs wishing to access it? Certainly there's no question about it -- FSUIPC3 is running fine in your FS9 installation. Of course I think FSC wants to access other things in FS than FSUIPC, so be sure it isn't something to do with access to folders. Pete

Only other idea is as in my reply to the thread "Saitek Multipanel in FSUIPC", near here. Sounds like FS9 is not terminating correctly, but crashing instead. It re-writes its CFG file on termination. Try loading it, setting your needs, then terminating it immediately. Turn joysticks off in FS9 and assign and calibrate everything in FSUIPC. Pete

Sorry, i don't know anything about the panel. I assume their driver is the part interfacing to FSUIPC, so if you remove that you aren't left with much. If it is a standard USB HID device, like the GoFlight devices, it would be possible to program it using the COM and HID facilities in the FSUIPC Lua libraries -- you could run HidScanner to see what that tells you. You can get that in this thread in the Download Links subforum: Latest Lua Package. But you'd need to write your own Lua program that way. Alternatively, search out a program called SPAD ("Saitek Panels Advanced Driver") which might handle it. Google should find it for you. Regards Pete

The FSUIPC install and run-time logs show everything is fine as far as FSUIPC is concerned. It is working. If your "FTG-ACARS" program, whatever that is (I don't know it at all) won't connect then it is either because you are running it and FS9 at different privilege levels (one "as administrator" and the other not) -- which is not possible to tell from logs -- or because of some other requirement of that program which you have not met. You probably need to send your logs to FTG-ACARS support to get them to help you resolve the matter. Regards Pete

As others have pointed out, there's something seriously wrong with your PC, that's pretty much a certainty. Windows 7 64-bit and FSX work excellently together, as if they were made for each other. Since updating from XP and the awful Vista I've had no problems whatsoever with FSX + Acceleration and many many add-ons, and that goes for 4 PCs all running Win7-64. The only times I've seen a blue screen with Win7 was when I overclocked a little too much! Think of FSX as a benchmark test for your PC. Nothing else you're likely to run, other than specifically designed stress tests and benchmarks will stress it anywhere near the same. PC restarts and blue screens can only be caused by faults in drivers or hardware. Nothing else has enough privilege to cause them. It may even be as simple as a faulty memory module, or a badly seated one, or some BIOS setting wrong, or overheating. There are ways to nail it down reasonably accurately, but it takes patience and forethought. Regards Pete

Most add-ons by now require at least SP1, and as Andy says, more and more SP2. And now you have FSUIPC installed and trusted the trust bug should not reoccur. To be even surer, go to Internet Explorer. select Tools -- Internet Options -- Content -- Publishers -- Trusted Publishers, and make sure SimFlight GmbH is listed there. If not, right click on FSUIPC4.DLL, select Properties -- Digital Signature, select the certificate and click -- Details -- View -- Install Certificate. Click Next or OK all the way through. Then go back to Internet Explorer and find the Certificate in the Other Publishers list. Export it to a file, and go to the Trusted Publishers section again and import it. Sorry that's so complicated, but that's the way MS manage certificates. Note that it might be slightly different depending on which version of IE you have installed on your PC. I think I will add this hint to the FAQ for the trust problem. Regards Pete

What do you mean by "not working"? Is there an FSUIPC. Log file in the Modules folder? Show it to me if so. Pete

Hmm. Sorry, don't know what the difference might be. Acceleration contains SP1 and SP2 versions of SimConnect. Both are actually not only faster than the original, but also more likely to avoid that Trust bug. Since I've never been able to reproduce the trust bug on any of four different systems I'm not really in the best position to advise. But don't forget that the SP1 and SP2 updates to FSX are free and can be applied separately. That's another alternative route. However, all of my attempts to reproduce this elusive problem have been with the full Acceleration. The contributions to the forum only represent a minute proportion of all FSX users, and not a very large proportion of FSUIPC users. Even allowing that there will be folks with the same problem not reporting here, it is still a very much minority problem. I know that's no comfort to those who actually get it happening, but it does explain the lack of a proper solution. Microsoft certainly knew about the problem before they ceased FSX development (and in fact before SP2 was released), but no one in the FS team could reproduce it either. Sorry if this is not the answer you wanted, but I have to be honest. Regards Pete

Both FSUIPC versions are very old and totally unsupportable. You need at least 3.99 for FS9 and 4.70 for FSX. There are later versions (3.997q and 4.727) in the Download Links subforum, but you need to run those installers first. Regards Pete

If Saitek don't know what is wrong with their driver, tell them to contact me. I'd be grateful for someone there to -- they don't respond to my requests to sort this mess out. Regards Pete

I'm sure it would have continued okay in any case. That's just a trust check which SimConnect sometimes throws up. Regards Pete