Pete Dowson

WideFS consists of the Server, which is built into FSUIPC4, running inside FSX, and the Client, which is implemented by WideClient.EXE running on the Client PC. There is no way you can "load the FSUIPC wide" (as you say) except by running FSX with FSUIPC4 installed. If you have purchased a WideFS registration and have registered it on the FSX PC, then as well as the WideClient.LOG file from the Client PC there will be a WideServer.LOG file in the FSX Modules folder. You need to show that as well. So your Client PC is "ALLAN-PC", running what version of Windows? What is your FSX PC running? Hmmm. Two points there: 1. If your "two screens" are on the same PC, then WideFS is nothing to do with it -- WideFS is for use over a network, with the screens on different PCs! 2. Aivlasoft's EFB doesn't use FSUIPC and so doesn't need and cannot use WideFS. It has its own Networking facilities built in. Regards Pete

I don't know what to say. There is and cannot be any possible relationship between the scenery which is loaded and the connection or otherwise of a joystick. I suspect you are just having the same sort of Windows 8 problems with some joystick drivers, and which seems to be widely reported by others. I am refusing to move from Windows 7 which sems to be the best Windows version ever, by far. Regards Pete

That looks fine and should work exactly the same assuming the [JoyNames] section has been revised on the new PC.(as indicated by the date/time stamp on the INI file). What is wrong? Pete

You can send any command, by number (and optional parameter) via offset 3110, as documented. To get a keystroke on your Client PC running WideClient.EXE just send the KeySend control with an appropriate number and program the keycode for that KeySend in the WideClient INI file. Please see the WideFS tech document for full details for that end. There are different options on the Client depending how the target program expects the keypress to arrive. The numeric equivalent of the added FSUIPC controls, which you need for offset 3110, is listed in the FSUIPC Advanced User's guide, towards the back. Off on holiday now. Bye & Regards Pete

WideClient runs under Windows, including Windows 7 which you say you have installed ok..If you don't want to use WideFS on that computer (I would have thought that it IS effectively a PC if it runs Windows properly). But if your "Area 500" has no facilities for Networking, then connecting as a Network is obviously out, so is WideFS. If you only want it for "GPSout" then just use a serial port device. There are no PCs with serial ports these days, but there are plenty of USB-serial port adapters. I'm on holiday now -- just leaving. Bye Pete

This has to be my last email before I go. My wife is getting the car out, ready to depart! 1. Check the [MacroFiles] section of the FSUIPC4.INI file. All your .mcro files should be listed. 2. If the MD11 file is listed, then your macro will certainly be in the assignment of FS controls dropdown by the name Md11:Fuel3cut. I think you must be looking in the wrong place. The drop down for assignments is in alphabetic order, and there is one in Keys, one in Buttons and Switches, and one in Axes, for assignment as you wish. Bye Pete

I suspect the name "B747-400 GE CF6" is too long in any case (I don't have time now to check the documentation), and it may be truncated. Take a look in the FSUIPC4.INI file, in the [MacroFiles] section, see what names are listed there. You may need to rename the file to shorten the name. (Why on Earth include '-400 CE CF6" anyway? Surely the macros will work with any of your B747s?). Best just "B747" surely. If the same of the file is B747 and the macro you wish to use is "FUEL 1 CUT" then the name in the list will be: B747:fuel 1 cut though I'd be happier if it had no spaces in it. Does the macro actually work, by the way? Looks rather frugal to me. Did you test it with the TAB key as instructed in that "green box"? I am packing now for holidays. Sorry, I cannot help further until 28th November. Others should be able to help. I've not known ANYONE to have as much difficulty over such simple things before. Sorry the documentation isn't in a language you understand. Regards Pete

I have combo here and it has always worked fine. I'll re-test when I get back on the 28th. Sorry, I am packing for holiday at this moment. Andy can help you enable logging to see what is happening. FSUIPC has never handled the radios by default -- there has never been any need. Pete

No. All of the radio facilities are passed through. FSUIPC doesn't need to do anything at all with them. There is no difference for COM or NAV or ADF or DME or TRN. If the COM button is not working I can only think it is a hardware fault. You can try logging for VRI in FSUIPC (I think this is documented in the PDF about setting it up?)), or perhaps VRInsight website has a program to test with. For more help i suggest you visit the VRI support forum. I am leaving very soon now for a holiday. Regards Pete

Yes, those steps are correct -- provided you finish by pressing "OK" so that the assignments are saved. You can then check your work by using the Logging as I suggested a while back. Of course if the add-on aircraft does not use those FS controls, then it will not work with those aircraft. Test with a default jet, like the 737. Not sure why you ask this: "yes" means "true" or "affirmative". Sorry, I don't understand. I cannot provide you with any aircraft. Test on one of the default jets. What is the name of the macro file? The name in the assignments list is <name of file>:<name of macro>, NOT just <name of macro> as you are looking for -- it cannot be, because there may be many macro files. You can have different macro files for different aircraft, all containing macros with the same name!!! As Andy says, I can tell you EXACTLY what to look for if I know what the macro file is called, and can see its contents. But it is nearly too late now -- I am going on holiday soon and won't be back till the 28th November. Regards Pete

You really didn't need to refer to a manual. As I said, assign to the FSUIPC control (it is in the drop down assignments list) by the name I gave you EXPLICITLY ("PM GC contorls (by param)"), and use the parameters 40 and 41 as I also INSTRUCTED! Yes, if you don't even know how to assign switches and buttons in FSUIPC, then refer to the FSUIPC User Guide! But I assumed you did because you referred to your use of the Disconnect control! I'm on holiday later today till 28th. Please use PM support and its documentation for further assistance. I really cannot support PM as well as my own products. But I did tell you how to do this one thing, already! Regards Pete

Did you first, on the old PC, make sure your devices were assigned using Letters rather than numbers? If not the likely thing is that all the connected controls have different numbers on the new PC, so your assignments are all mixed up. Apart from the properly prepared INI file all you might need as well are any Macro (.mcro) and Lua (.lua) files you are using. Regards Pete

As far as I'm aware the PM "A/P disconnect" action is intended just for the yoke AP disconnect button. I've programmed my MCP Disconnect Bar to use parameters 40 (disengage) and 41 (engage) written to offset 04F4 (you can assign to the FSUIPC added control called "PM GC controls (by param)"). You need the PM Offsets document from the PM site to program PM properly. I did try to include enough in the FSUIPC documentation, but it gets out of date too easily so I removed most of the values -- PM keep the documentation for their products. I use pmSounds (on two separate PCs, actually -- overhead and main cockpit), but I know nothing about it and don't use many of its sounds. There is documentation for it I think, with examples for playing things based on offset values. I've not really touched it for years. Many additional sounds I need are played using Lua plug-ins for FSUIPC or WideClient. That's why I added the Sound library to Lua -- it also allows direction to selected source directions in a 5.1 speaker setup. Regards Pete

An SPST switch has an ON position and an OFF position. When ON it looks to FSUIPC as "pressed", when OFF it looks like "released". You just program the Press to do the ON function and the Release to do the OFF function. It is really really simple. Sorry, but i do not know what you mean. Show me the .mcro file and tell me what the filename is, and I'll tell you the way it is listed in the assignments. Did you tell FSUIPC to "reload" assignments so it would re-scan the files in the folder? No one else has ever been this confused. I think maybe it is because you do not understand English very well? I am sorry for that. Perhaps you can find someone who can help you with that? Regards Pete

Why do you need any of those connections? Is this for WideFS? If so you need a Network connection. Pete

Sorry, what do you mean, "two DLLs". There will only be one XML.DLL, the one you said the installer made for you. In that case it is a Simconnect problem. FSUIPC is not being loaded. No, it cannot be. Those add-ons do not need FSUIPC at all. It sounds very much as if your FSX installation is corrupt. They are written in a combination of C and ASM, and compiled with Microsoft compilers. They are PROGRAMS. You cannot READ them, only computers understand them! :-( It looks likew you've not actually bothered to update to the current supported version of FSUIPC4 yet: 4.90 is out of date and unsupported. You are not running the current installer, though you have manually copied the latest FSUIPC4 into FSX: However, you are using the Loader. Why? Please don't! Delete the FSUIPC4 Loader from the Modules folder, then download and run the 4.921 installer. Then look in the FAQ subforum for the thread telling you how to get a SimConnect log. Do that then show me the log. However, so far it is looking like a corrupted FSX installation. I'm away now till 28th November. Regards Pete

Sorry, I don't understand you. On all default jet aircraft and many ordinary add-ons, mixture lean is most certainly the fuel "cutoff" setting -- and mixture rich is the same lever's "idle" position. With several sophisticated add-ons, like most PMDG aircraft, very few of the built-in FS controls will work at all. They all do their own thing and each needs specific attention. MD11 now, not the NGX like you said before? I wish you'd make up your mind! Thet are likely to be all different! I've no idea what you are doing, but really if setting "LEAN" activates "cutoff" then setting "RICH" should certainly do the oppoite. But maybe it's another PMDG difference. sorry, I can't say. I do not use any PMDG aircraft. It is NOTHING TO DO WITH FSX! I keep telling you, PMDG do their own controls. you need to fnd out what works with PMDG aircraft (NGX or MD11? They'll be different, for sure!). I can't tell you. You must go to PMDG support. Pete

It isn't Ctrl+Shift+F2 in any case. I don't know where you got that from. It is easy. If you have one toggle switch for all engines, asign the "cut off" position to the FS control "Mixture Lean", and the "idle" position to "Mixture Rich".. If you have separate switches for eacvh engine, assign to MixtureN lean and MixtureN rich instead, where N is the engine number, 1-4. One position will be "press" the other will be "release" on the assignments tab. If your switch is sending two "presses" when switched on and two "releases" when switched off, then it is definitely a faulty switch. If not, and there are two events happening on each press and each releases then it must be programmed for two events, maybe one in FS and one in FSUIPC? You are using the PMDG NGX? You never mentioned that before!!!! In that case I've been wasting my time -- most of what has gone before does not apply! I doubt that any or many of the FS controls work with the NGX. It has its own set of controls, completely separate!!! And provided you have the updates for the NGX installed and you are using a supported version of FSUIPC (not 4.70 -- I told you to update!), then all of its actions can be controlled by "custom controls" assigned in FSUIPC. Those are listed in the NGX SDK ".h" file, near the end of that file. (I can't really help more than that as I don't use the NGX). The logging window is NOT related to whether you check any logging action, only if you enable the console log - AS I ALREADY INSTRUCTED! Please do read what I write, and possibly even look at the FSUIPC documentation sometime. If you don't use the console log you need to view the Log file in a text editor like Notepad. However, the event logging propbably won't help with the NGX because it doesn't use FS controls. I won't be able to help whilst II am on holiday. Going tomorrow back 28th. Regards Pete

I don't know who made that or why. It is way out of date and incomplete. You should be referring to the Offsets lists automatically installed for you in the FSUIPC Documents folder (and also in the FSUIPC SDK). That folder is in the FS Modules folder and also contains all the FSUIPC Documentation (which I assume you've never looked at either?). Pete

Why not use the offset provided for this by FSUIPC? It does the same as you, but it can be more accurate catching the touch-down point and then fixing the value. Offset 030C. Just read it when on the ground. Pete

For FSX it can only do so for messages sent to FSX via FSUIPC. And it's part of the options displayed on the very front tab of FSUIPC options, and documented near the beginning of the User Guide. It is one of the few options available to unregistered users. Pete

In that case it is a simple reversal. Just check the REV option in the FSUIPC rudder calibration section. The FSUIPC "rev" checkbox does exactly the same thing as the FSX one, so there's no problem using just FSUIPC. Regards Pete

So you have never tried using FSX with keyboard controls to operate the idle/cutoff switches? Have you not looked into any of the FSX help files to see what controls them. The jet idle/cutoff switches in all versions of FS since FS4 or even earlier have been controlled by the Mixture Lean, Mixture Rich controls (Ctrl+Shift+F1 and Ctrl+Shift+F4 on the keyboard), as documented by Microsoft. To find any FS controls always try using FSUIPC Event Logging. Enable the logging and operate the control, by keyboard or mouse, then check the log. If you run FSX in Windowed mode whilst doing this you can enable FSUIPC's console log and see the results in real time. That is very much out of date and unsupported. Please update before asking for more help. Regards Pete

The version number of the PFC driver will be different, it is a separate module. WideFS for FSX consists of two parts -- the Server built into FSUIPC4, and WideClient.exe which runs on the Clients. The client program also has its own version numbers. You can find the current version numbers of them all in the Download Links subforum here. Version 4.2 of FSUIPC is very old and unsupportaed. Yes, you should. For at least two reasons. First is that otherwise you get no support. I cannot support old versions. And the other is because things are added and used by other applications and you may wish to actually use an FS addon at some stage and wonder why it doesn't work. Regards Pete

You need to rerun the FSUIPC4 Installer, then. I don't think "repair" touches any of that. It's only looking at installed files ,ie. those in the FSX folder. Sorry, I don't know anything about ENB (and don't use it), but I have read about conflicts between ENB and other programs manipulating graphics. It does interfere with graphcs, which is where G3D comes in. Your best bet is to check the relevant AVSIM forums. Pete