Pete Dowson

Version 4.60a is now four yesrs old and hasn't been supported for over three years. you must update. DLL like EXE files are PROGRAMS, containing CODE. They are not TEXT files!! [LATER] Since from the other one of your THREE posts on this yiou show an Install file for 4.929, I can only assume that your 4.60a version got installed by something else, maybe that old FScopilot? Run the FSUIPC4 4.929 installer again! Pete

Nothing appears wrong for the files you pasted. In the Modules folder is there an FSUIPC4.LOG file produced? If so please show it to me. It might be worthwhile getting a SimConnect log. Instructions for that are given in a thread in the FAQ subforum. To eliminate interaction with other add-ons you could try temporarily renaming the DLL.XML file, re-running FSUIPC's installer so a DLL.XML is produced which only loads FSUIPC, and seeing if that works. I notice FSCopilot is being loaded after FSUIPC. I seem to remember a problem with that, or at least with one specific version of FSCopilot, so another thing to try is with just that entry removed or disabled in the DLL.XML, or, again, with it preceding the FSUIPC4 entry. The FSUIPC installer normally puts its entry right at the end, so FSCopilot was probably added afterwards? Pete

Correct in that it is not directly supported in the normal FSUIPC parameter system. However, Lua plug-ins can be run based on Profiles and the Lua libraries include one called ext which can run programs. Pete

The FSUIPC menu entry uses standard Windows dialogue facilities. Those are supported by video drivers. In all previous cases reported like this the problem has been a bad video driver. There's no FSX.CFG references for FSUIPC excepting some "Trust" lines which mean only that you allowed it to run. What other programs are being loaded by your EXE.XML and DLL.XML files? That's a thread hanging, which implies something is using it. I need more information, especially about what programs are actually using FSUIPC, because it will likely be one of those causing this. That makes no sense. FSUIPC cannot be any different one time it is loaded to the next. You have something very odd going on. maybe one of the programs or add-ons loaded in the first run is still running and this is causing the problem? Pete

If you run ProSim737 manually, later (i.e. leaving WideClient to get itself fully sorted out first),does it still crash? It might be a driver problem, but in that case I need to know which driver that is the problem. I've updated all drivers to the latest version, but if I need to revert any of these, I need to know which. Sorry, no idea. but if you do find out please let me know. Maybe I could fix mine then, Well, it opens its log before doing anything so there certainly should be something there. Else it's Windows loading that's crashing! And if it doesn't crash till it is connected there with be log entries showing the connection attempts and the connection, as well as its action in running programs. I think you must be looking in the wrong place? The file is "Wideclient.log" and it's next to WideClient.exe and Wideclient.ini in your WideClient folder. If there's no log there's no point in adding more logging, so let me know what the current reality is, please. BTW, I thought ProSim's software used its own networking connections, not WideFS? Could there be a clash with ports? Either way, if it does, it still points to Networking problems, low level. Pete

If the PFC quadrant is one of the old types, using a serial connection, then it needs PFCFSX.DLL, which preceded most of the assignment and calibration facilities in FSUIPC and therefore needed its own. If it is a true USB device it uses PFCHID.DLL. THe PFCHID one relies 100% on FSUIPC for assignments and calibrations. It does not have any menus as such, only the one confirming it is loaded. Pete

All new versions of FS or P3D need new versions of FSUIPC. Unfortunately 2.2 was released whilst I was on holiday. Version 4.93 of FSUIPC will be released later this week. Pete

Please check the FS help where you will find out the keypresses to use for the NDB (along with all the other radios, which ALL use decimal. What other sort of numbers could they use?) Pete

I'm pretty sure this is actually explained in the chapter on Joystick Letters in the manual, but here goes with more detail. When using the letters in the assignments, FSUIPC needs to relate those to the Joystick IDs, which are numbers, used when talking to the Windows joystick routines. These are found by doing a Registry search for the GUIDs and/or Names. Rather than have FSUIPC do such a search every single time when generally they will be the same (especially during one session), the FSUIPC initialisation does it once when FS is loaded, and only again when entering the FSUIPC options. The results are recorded in the INI file so the numbers can be matched up to the letters via the names and GUIDs Pete

Sorry, I've no idea about this one. It certainly isn't related to FSUIPC. Pete

Both FSUIPC and PFCHID produce log files showing what they are doing. They are in your Modules folder. Please show me those. You seem to have something all wrong there. PFCHID has no "green crosses" and nor is there ever any COM port to select. PFCHID is purely a USB driver. It sounds to me as if you've installed the Serial Port PFC driver, PFC.DLL or PFCFSX.DLL. You most certainly don't use that with a USB Cirrus! Pete

You are running a version of FSUIPC which was released before P3D 2.2. I am surprised it doesn't cause a crash! I have been on holiday.so unable to match P3D's release date last week. Version 4.93 of FSUIPC will be released later this week and will work with P3D 2.2. Meanwhile I suggest you remove FSUIPC4.DLL from the Modules folder, or at least be understanding if it causes crashes or other problems. Pete

I think for iFly you need a utility program called iFly2FSUIPC, which maps their data to FSUIPC offsets. I expect it covers what you need in its documentation, but if not best to ask at the iFly forum I think. Pete

The only time I get a crash, and it only occurs on one out of 7 client PCs, is when FSX crashes. The other 6 PCs just go back into "waiting for connection" mode. I suspect the Networking hardware or driver in the one machine. BUT it never does this whilst things are running, only when FSX crashes, so I've never speared the time to try and find out why. As far as I recall (from my last FSX crash, some long time ago) I think that crash is also in NTDLL, but this doesn't really help much because NTDLL is a collection of hundreds of Windows functions. Perhaps you can describe specifically what circumstances this crash occurs in? The standard WideClient.log itself just possibly might be useful to start with. Otherwise, since we've no idea what the cause is, only full logging might be useful and that produces huge logs. So let's take that step afterwards. Pete

Keystrokes sent to FS are converted to FS controls according to key assignments, so it is more efficient to assign your buttons direct to the controls you want. There's a full list supplied in your FSUIPC Documents folder. Pete

FSUIPC has intricate links into the innards of FS and P3D which need adjusting and testing with each release. The Installer does tell you this, but of course if you simply copy it over from a previous installation you bypass this warning. I had tested changes to FSUIPC for 2.2 with the Beta versions of it available before I left for holiday but was unable to test it with the final release of 2.2 until I returned from holiday. It will undoubtedly need more changes. It is VERY precarious indeed just having FSUIPC installed for a version of FS or P3D for which it has not been designed. Version 4.93 will work with it but I won't be able to get it released until Tomorrow (Tuesday 15th) or more likely Wednesday, assuming it doesn't take me too long to download 2.2 and again there aren't too many changes from the Beta. Pete

As Thomas says, you need to read it the right way. Also please do use the tools available to see what is going on -- logging and monitoring in the FSUIPC menu and the utility FSInterrogate2 supplied in the SDK. Pete

There is no such message in the FSUIPC installer, and no way it simply quits. Please be more explicit about exactly what you are doing and what you see. I suspect you are not referring to the Installation instructions because otherwise you would have sent your request to the correct Forum and not had to rely on a supervisor moving it for you. The installer creates a log file saying EXACTLY what it does. It is either saved in the Modules folder or, if it cannot find FS at all, you can save it via the "File" menu entry in the logging window. I will need to see that if you have diffficulties. That is certainly nothing to do with FSUIPC. The installer doesn't care at all about whether there is another FSUIPC installed. If the one already installed is an earlier one it replaces it otherwise it doesn't touch it, it simply carries on after telling you this. Pete

It seems, then, that the second one is merely csmetic, or local to the gauge or aircraft code. FS would only see controls passed on to FS. For a second Pitot Heater I would havce expected the same control to be used but with a parameter of 1 or 2, but if so you would have seen it logged. Most sophisticated add-on aircraft do their own thing in amny ways, some completely 9like the PMSG range) and some partially. You could see if Mouse Macro techniques work for it, or else maybe local panel variables (L:Vars). This will be to do with the way the gauge is programmed. Maybe it's an error, or maybe it is intended that way. You need to talk to Carenado support. Same again. Carenado support. You need to understand that FS commands are sent to and processed (if applicable) by FS,. Add-on aircraft programmers do their own thing and can, and do, choose to ignore the FS commands, or add their own (like PMDG did for the 737NGX), or even provide no way of implementing switches other than by mouse click. If there are no keyboard shortcuts provided by Carenado, then, as I mentioned above, there are two tools provided by FSUIPC which might help, depending on how the add-on is written -- mouse macros which only work for gauges written strictly according the Microsoft's C/C++ Gauge SDK, and L:Vars which are usually associated with gauges written in XML. Regards Pete

When there's a syntax error in a plug-in you will get an error message in the FSUIPC log pointing to the line in error. That's where to look whenever something doesn't work as you'd hoped. I always test with FS (temporarily) in windowed mode and the FSUIPC log console window open to the side so I can see what's happening in real time. Regards Pete

The only answer might be you get SB up and connected before "climbing into" your cockpit. I have a 737NG cockpit and make sure FSX and ASN are up and running, and all 7 of my client PCs are set and ready, all before getting into the pilot seat. From then on I have normal 737 controls available to me. Perhaps the on-line ATC organisation you fly with has a Forum on which you can seek more help? Pete

Obviously you install FSX before you install any add-ons for it. And make sure it all works first. Then add things one at a time and test each time, with a separate reload of FSX. I'm afraid I don't know SPAD, but as I think it needs to use FSUIPC you want FSUIPC installed before actually running it. Though I'd expect it to tell you that it needs FSUIPC in any case. I doubt whether Saitek stuff needs any specific order of installation -- at least I can't think of any reason why that should be so. But if you are worried it would be better to ask on Saitek forum. I can't support their devices. BTW I am 71 years old this year. Age is really not relevant to computer literacy. And very very few visitors here are computer programmers. Incidentally, whilst I am here most of the time to give help with FSUIPC, WideFs and related matters, I do go away quite often (eg from Saturday for 8 days), and in any case I am not so good at giving general advice. Your best bet for such is probably the FSX forum over on AVSIM.http://forums1.avsim.net/forum/121-ms-fsx-forum/ Pete

Ah, you are talking about SB3 and FS9? If you are using SB4 and FSX then there are none as SB4 doesn't use FSUIPC at all. And as you have seen, the offsets are only related to "push to talk" and "ident" and related cockpit actions. Starting and connecting SB is really not an "in-cockpit" action (there's no real world equivalent, obviously), so it seems it isn't considered for such implementation. Surely there's some documentation for SB which tells you its keyboard shortcuts if any? Are you saying it can only be operated with the mouse? Pete

I don't know SquawkBox, but if it accepts keystrokes to do as you wish then you should be able to do it through WideFS. You assign to a KeySend value in FSUIPC on the Server, and edit the WideClient.INI on the Client PC to respond to that specific KeySend by sending the required Keystroke to Squawkbox. Which method of those available for directing keystrokes (see the WideFS documentation) depends more on Squawkbox -- the way it detects the keypress. It might be better is you had WideClient loading Squawkbox as then it can direct keystrokes more specifically and reliably. Pete

Do you think you could post these details, maybe with our working plug-in, as a User Contributions subforum? That way it will remain a useful reference. Thanks! Pete