Pete Dowson

That's certainly a good idea. You would eventually get into lots of problems with add-ons if you let it instal into its default "Program Files" place. Yes, exactly right. Installers (at least those with "install" or "setup" in their names) never have to be run "as administrator" in any case, and certainly FSUIPC's installer has never needed this. All programs recognised as installers by Windows automatically get enough administrator privileges to do their job. Regards Pete

When it isn't installed it does not provide any interface to anything which may be wanting to use it! When it is installed it does provide the interface. As I explained already. Possibly. I do not use PMDG aircraft but from what folks have said I know they are extremely sensitive compared to others, and there could be timing issues I suppose. Maybe, on a less powerful or more overloaded system, the additional loading on SimConnect of having FSUIPC running too makes the aircraft's timed computations for A/P feedback control go awry. However, there are a huge number of users with both PMDG aircraft installed and also running FSUIPC. In fact many of them use the macro facilities in FSUIPC to gain hardware button and switch control over much of the PMDG cockpit. So all in all I really don't think it can simply be due to FSUIPC's normal quiescent interface actions when unregistered -- it is doing far less then. You do know you can use the Logging facilities in FSUIPC even if it is unregistered? Try checking the Weather logging. You'll see it reads the weather regularly, so that it can supply such data to anything which asks. But unless you have something writing weather through its interface, you won't see any attempts on its part to change anything. Regards Pete

If FSUIPC is not user registered, it is actually doing nothing of its own accord. none of the options are enabled. It then merely acts as an interface for other programs, modules and some gauges. By removing it you merely stopped whatever it was doing it from using the FSUIPC interface to make such changes. Regards Pete

Just look inside the Macro files (the ones with filetype .mcro) in your FS Modules folder. They are text files, like the FSUIPC INI file. If the macros are dependent upon a specific Gauge file, it will show the name in the "Module" line. Try creating a macro with one of the other IFly aircraft and see if it uses the same gauge. If so, then the original macros you made for that gauge should work okay -- although there is one other possibility. If the gauges have the same name but are loaded from a different place and are at different revision levels, that could also explain it. Details of the gauges used by an aircraft are contained in its PANEL.CFG file, and the correct Panel folder is determined by the "Panel=..." line in the Aircraft.CFG Again, all these files are text files in the same sort of format as FSUIPC's INI file.file. Regards Pete

No. I haven't had time to look at that yet. I'm not sure how to do it either, yet. It is very different. Regards Pete

Yes, as I said, the section is [MacroFiles] and that is simply an index to the files on disc. The macro actions are assigned to Keys and Buttons in their own sections, see the bold parts in your own settings: In Keys the M means Macro, the number following that is the file number, the number after the : is the macro number in the file, and the last number is the parameter for it, if any. In Buttons it is the same but starts with a C to indicate Control (as opposed to K for Keystroke -- the right and left parts of the Button Assignments tab. In the Macro files themselves, doesn't it identify the Gauge name which processes these mouse macros? If each model uses different gauges then the macros are not transferable -- each macro you make relates to CODE within the Gauge, and different gauge code will have the functions in different places. FSUIPC has to know where is the code to call when you press the key or button. Regards Pete

No, there's a section called [MacroFiles] which simply assigns index numbers to each macro file you have in your Modules folder. Macro assignments are in the [Keys...], [Axes ...] and [buttons ...] sections, which can be specific to each aircraft, as I said. I've really no idea what you are talking about here. Mouse macros are saved in macro files, with the name you provide and a filetype of .mcro. That's where they are stored. The [MacroFiles] index numbers those files, and the macros are related to Buttons and Keys in their respective sections. Please explain. Don't rush off and do anything yet ... Pete

If you have the parameter "ShortAircraftNameOk=Substring" in the [General] part of the FSUIPC INI file, all you need to do is go through the INI, finding each [... ] section heading which mentions the aircraft name and edit that name to a shorter name which contains a part which occurs in all of the IFLY 737 names, possibly, for example, "IFLY 737"? You only then need one section of each type, like [Keys.IFLY 737] ... [buttons.IFLY 737] ... [JoystickCalibrations.IFLY 737] ... [Axes.IFLY 737] ... so just delete those others which you don't need. Be sure to keep the ones in which you've done all the work. They'll presumably be the largest? Regards Pete

Re-installing FSX seems to be about the best way to guarantee future problems. It is all to do with the Registry and the use of the Side-by-Side library installation of SimConnect. I think they made a bad job of the uninstaller, which only does half of the job, leaving the Side-by-Side part in a mess such that on re-installation things get knotted up and no longer work correctly. The best solution it seems, when faced with FSX re-installation is either DON'T, or to reinstall Windows first. Anyway, I'm glad you found another way. Certainly installing under a different log-on user name hadn't occurred to me before. Regards Pete

Okay. That certainly confirms that FSUIPC4 has never run in that installation of FSX. The DLL.XML file is perfect. So that leaves only four possibilities: 1. The FSX Modules folder you are looking at is not the one relating to the FSX session you are trying to run. I know this seems ridiculously unlikely, but it has happened where folks have reinstalled FSX in a different place. 2. You are running FSX under a different User login to that for which FSUIPC is installed (i.e. user "Brian"). (The revised installer for 4.638, which i did ask you to try, would have dealt with such a possibility. Remember? I said "You could also try renaming that file, then downloading and running the Installer for FSUIPC 4.638, which tries to do a better job on the DLL.XML. You'll find that later version in the Download Links subforum here, and also a later FSUIPC DLL (4.664)."). 3. You have, maybe unknowingly, refused permission for FSUIPC4 to be loaded at some point, in which case it may now be listed as a "banned" program in Windows. For this you need to run Internet Explorer, go to Tools-Internet Options and find the content-Publishers lists. If "simFlight" or "Peter L. Dowson" are listed as "untrusted" you'll need to remove them from that list. 4. Something else is stopping SimConnect: loading it. In this case I need a SimConnect log. To get one of these please see the Thread about it in the FAQ subforum. Regards Pete

Hmm. I don't know those. But there's also the Leo Bodnar boards which seem to be popular: Leo Bodnar [LATER] I looked at the "pulse generator", but that seems a bit limited for toggle switches. As it says "The 2120 will product one pulse when you flip the toggle switch ON. And a second pulse will be generated when the same toggle switch is flipped to OFF." So it's like pushing a button and releasing it. You can't even have the button held, and there's no advantage to the toggle over a momentary button. Really you want the switch to press the button in one position and release it in the other. And with buttons you normally want the option to have them "repeating whilst held" which you can't do with a pulse. It seems that device is more complex than you real;ly want, don't you think? Regards Pete

Yes, correct, assuming you are looking at the correct files -- Windows defaults to hiding extensions for "known filetypes" like INI and LOG. It calls them things like "configuration settings" and "text files". I pointed you to the button to press to do this, the one which looks like <>, just one from the end of the row of buttons just aboveyour Forum message edit area, just to the right of the Quote button, which you seem to have found okay. The advantage of the code quotes is that is preserves the layout. Anyway, as far as I can tell the file looks okay, so FSUIPC4 should most certainly have run. Could you please double-check the files present in the FSX Modules folder, please. Something isn't making sense. There should be FSUIPC4.DLL, FSUIPC4.LOG, FSUIPC4 Install.LOG, FSUIPC4.INI and maybe FSUIPC4.KEY, as well as the subfolder "FSUIPC Documents" Turn off the Windows Explorer folder option for hiding file extensions so you can see the whole filename. Regards Pete

They are not blocked for registered FSUIPC users. But I can't offer support for their modules. I don't really like them much -- I think VRInsight's are smarter -- but if they hadn't reneged on an agreement I would have probably added support as I did for VRI. If FSUIPC sees the buttons and switches, you can program them. If not, then maybe the only way is by using the FSUIPC Lua library facilities for COM and HID devices. The problem then is to work out the protocol Saitek are using. You'd really need a USB monitoring program to do that for display outputs, but for switches and knobs you'd probably be able to work it out just by logging what arrives.. Regards Pete

Okay, this is done. Wideclient 6.844, now available in the Download Links subforum, provides the following additional facility: Regards Pete

Well, you may need to change the Widecliemt.INI file. Look: ********* WideServer.DLL Log [version 7.638] ********* ... 16209 Broadcasting service every 1000 mSecs ********* WideClient Log [version 6.841] Class=FS98MAIN ********* 1250 Trying to locate server: Need details from Server Broadcast 1250 Failed to connect: waiting to try again Seems that the broadcasts from the server are not reaching the Client. This can only be due to one of three things: 1. The two PCs are in different workgroups. The names need to be the same. XP and Vista/Win7 have different default workgroup names -- but you said you'd fixed that? 2. One of the operating systems involved doesn't support broadcasting (Win95/98/Me, maybe original XP before SP1). 3. The broadcasting and listening ports are blocked by firewalls (9002 is the default port used by WideFS for this). You don't HAVE to let them connect automatically by broadcasts. Please see the User Guide -- you can supply the ServerName, or ServerIPAddr, and Protocol parameters to Wideclient, and it will then not wait for a never-arriving broadcast. Regards Pete

Registration is done in the Installer. That is the only and best way. There's little point in having loads of extra code in the run-time program. The installer will not affect anything you've set already. It never touches INI files, for instance, and only replaces FSUIPC if it is the same or later than the one you have already. Regards Pete

WideClient can't connect if FSUIPC isn't running, so are they really separate issues? If you think so, why is that? When you say "looked at module folder and can tell that it has not even started upon running FSX" can you please say how you can tell? I don't mind folks doing their own diagnostics, but it would help me to know how you arrive at conclusions, please. If FSUIPC is not being loaded at all then it can really only be a badly formed DLL.XML. Seems there's a lot of folks installing this "superbug" who are experiencing this so I woner if it is to do with its installer. Perhaps you can find and show me the DLL.XML file (paste it into a message here, but please do enclose it in the code parentheses -- use the <> button above). You'll find the DLL.XML file in this folder: C:\Users\Brian\AppData\Roaming\Microsoft\FSX You could also try renaming that file, then downloading and running the Installer for FSUIPC 4.638, which tries to do a better job on the DLL.XML. You'll find that later version in the Download Links subforum here, and also a later FSUIPC DLL (4.664). Regards Pete

I think the Elite hardware uses its own elite-provided driver, doesn't it? You'd need to ask them. Regards Pete

Something wrong with the model then if that gets blown around with parking brakes on by anything much less than hurricane force! I'm afraid there's no extra braking you can apply by controls, but you could try looking through the Aircraft.CFG file to see if there's anything you can do there. I'm afraid I'm no help with that -- you'd need to go to one of the aircraft modeller's forums for advice. Regards Pete

Did you not see any of the documentation that was installed for you when you installed FSUIPC? The AddOns menu is the last one, to the right of 'Help', in the main menu bar at the top of the screen. If it is hidden just press "ALT" to bring it up. I'm sure you must have seen the menu before? It is used to load aircraft, load flights, set options and so on. Do you always end a flight instead and go back to the initial selection dialogue? FSUIPC should be listed in the AddOns menu. If it isn't then it either isn't being loaded (probably a DLL.XML file corruption), or you have a SimConnect problem. That's the FSUIPC install log. It doesn't show anything wrong, Is there an FSUIPC4.INI file there? ("configuration settings" probably -- it sounds like you have Windows Explorer set to hide filename extensions from you. You really want to turn that off -- check folder options in Explorer). If there is no FSUIPC4.INI file and no run-time log, FSUIPC4.LOG, then FSUIPC4 has never been run. This is usually caused by bad installers which corrupt the DLL.XML file which SimConnect depends on. Two easy things to try: download and run the updated installer for version 4.638 -- you'll find it in the Download Links subforum here. Then whilst you are there you could download the 4.664 updated DLL too and copy it into the FSX Modules folder. Then you are bang up to date. See how it goes. Let me know. Regards Pete

As I told you yesterday morning, but you seem to have forgotten already, the FSUIPC SDK is downloadable from the usual places -- including here in the Download Links subforum, and of course in the main place you get FSUIPC -- www.schiratti.com/dowson. Why not use Google to find things? It would be faster. You seen to have spent two days already,. Regards Pete

No, that is the list of FS controls, the things you can assign to keypresses, buttons and axes inside FS and inside FSUIPC. Please go to FS, Controls - Assignments and see similar lists there. The FSUIPC list is more complete and uses the actual internal "event" names of FS. No, you must send the FS control number 66080, which is also known as "Gear down" and you can assign it in FS or in FSUIPC's assignments dropdowns. It might help if you looked at the right documentation. If you are writing a program to interface to FSUIPC you need the documentation in the SDK, not the user documentation supplied and installed with FSUIPC. Pete

If all those things are true -- same workgroup name and no firewalls, then I have no idea. I would need more information. There are three relevant logs -- FSUIPC4.LOG and WideServer.LOG in the P3D modules folder, and WideClient.LOG in the WideClient folder. And can I assume you have not edited the INI files in either? Please paste logs into a message in this thread. Make sure P3D is closed first, please. Pete

The only "parameters" are those ranging from 0 to 16384 from min to max braking (0 to 100%), or the equivalents in floating point values. When the parking brake is set, both left and right brakes are automatically at their maximum, 16384. There's no more maximum maximum to set! If your aircraft is that light then it should not really be flown in a strong wind -- folks with light aircraft have to tie them down with guy ropes! Regards Pete

Registration is performed in the Installer. Just run the installer and enter the details when the facility is presented. There's actually an "installing and registering" guide included in the ZIP file, right next to the Installer program which you must run. Please read that. Regards Pete