Pete Dowson

Apologies for the delay in replying. As announced, I have been away on holidays. Well, part of your reasoning is correct except that there is no "Reverser=" parameter for you to add this to in the [Axes] sections, which is where the scaling is performed. The reverser parameter is in the Calibration section, not the assignments, and your values are most certainly incorrect for calibration. Why not simply calibrate it? That would do it all for you. That's the purpose of calibration, to match the input range to the output range needed. The calibration of the axis is doing the job for you. Your arithmetic adjustments are non-existent and not needed. Regards Pete

Apologies for the delay in replying. As announced, I have been away on holidays. Folders are irrelevant. You only show the Client log, half the story. Please show the corresponding Server log. Pete

Apologies for the delay in replying. As announced, I have been away on holidays. There are utility programs which record and restore undocked FS windows, or you could investigate doing it with a plug-in using the Lua EXT library. See the "TileSix.lua" example provided in the Lua package in your FSUIPC Documents sub-folder. Pete

Apologies for the delay in replying. As announced, I have been away on holidays. Sounds like a corrupted INI file or some problem with the aircraft not providing a name through SimConnect, assuming you are using Profiles or aircraft-specific assignments. FSUIPc itself won't lose things set in a properly formatted INI file. Maybe you should paste your INI file here and state which aircraft it is you have problems with. Pete

Apologies for the delay in replying. As announced, I have been away on holidays. No trouble here assigning TO the Enter key. The main keyboard "Enter" key is recognised as "Rtn" and the Numpad Enter key as "Enter". Don't you see these words appearing in the box in the Key Presses tab? But maybe you don't mean that? What are you trying to do? Assign a keypress to a different keypress (makes no sense to me), or a button to an Enter keypress? The latter works fine here too, "Rtn" or "Enter" depending on the actual Enter key pressed. Pete

I don't know any way apart from seeing if the Window exists and is visible. There's no facility in the Lua libraries to do that at present. Some of FS's panels and windows actualy exist all the time and are simply made visibile or invisible. They also have two incarnations -- docked and undocked. Treatment is different for the two modes, as undocked windows are top-level ones and easier to find. The docked ones are child windows. Why would you need to know in any case? Pete

From a Lua plug-in, and just as storage? Why not use the Lua global variable facility intended for such things? Look up the ipc.set and ipc.get functions. You use a named variable which can be accessed by other plug-ins. Just choose a name wisely so it won't clash with anyone else's. Regards Pete

Sounds like you really do have a corrupted FSX installation. Are you sure that's a good thing to do? Anyway, sorry, I don't know about SP2. I have Acceleration installed, and the "Programs & Features" list in the Win7 Control Panel only lists that, it doesn't even list FSX base or SP1, whch were naturally installed beforehand. So my guess is that when you uninstall Acceleration it reverts to an fSX entry, and so on. But whether that is true with SP2 I don't know. Regards Pete

You have multiple assignments to that lever then, for sure. The only assignments you are showing in the INI file fragment are these: and they are all unique, so I conclude that you have controlers enabled in FS, and some (this one at leastr) also assigned in FS. Regards Pete

When the FSUIPC installer is run it explicitly enables full user access to the Modules folder (which it also creates for FSX and P3D if it isn't already there). Of course other programs may need access to other FS folders. The best answer, with least ensuing problems, is to always change the FS Install folder when first installing it. My FS9 is in E:\FS9, my FSX in E:\FSX and my Prepar3D is E:|P3D. My E: drive is separate from both my system drive (C:) and my development drive (D:). Regards Pete

Maybe that's why it doesn't link? For FS9, WideServer.DLL needs to be in the FS Modules folder, next to FSUIPC.DLL and all the other FS Modules, otherwise it can't be loaded. This isn't so with FSX which has a different mechanism. Regards Pete

FSX does not itself support any functions related to the Caution system or Fire subsystems. If those are operative in the aircraft then they will be programmed by individual methods specific to that aircraft. I don't know if you'll be able to assign buttons or not, you'll need to check with Wilco or the documentation. Maybe there are keyboard shortcuts, or else you could investigate mouse macro or Local Variable (L:Var) methods. Regards Pete

ALL things to do with FSUIPC and WideFs on the FS PC are always in the FS Modules folder. Surely you've seen that? You must have placed WideServer in there in the first place! The log will be right next to it in the same folder! And similarly, Wideclient.EXE is placed wherever you placed it on your client PC(s), and next to it will be its INI file and its Log file! Everything is always kept together so you need never wonder where things are! I'm afraid after tomorrow I'm away till January 15th, so you'll need either wait or look in the Logs yourself. And read the WideFS user guide. There's lots of help there. I assume you've not found that either? It'll be in the same ZIP file from which you obtained WideServer and WideClient. Regards Pete

Well of course, but you must post to the Support Forum, not the FAQ subforum. I've moved it for you, and deleted the duplicate (you posted twice). You'll only get general support questions answered here, in the Support forum. That's what it is for! FSUIPC can be used to assign all normal DirectInput joystick buttons. Possibly that Saitek device has local buttons not included in those basic 32 DirectInput ones, but used only by its own software. If that is the case then you'd either have to write a Lua plug-in to handle it as a COM-connected HID device, or maybe use something like the SPAD add-on driver, or maybe LINDA. Searh on Google. You'll find those. You could also ask in the Saitek support forum. I'm afraid I can't support Saitek devices directly. Regards Pete

This is what i mean. You want to use the GPS in FSX, not make your own like, for example, the RealityXP GPS add-on gauges. So you do want the full GPS interface, not just the static data which is certainly more readily available direct from compiled databases. Yes. i have a full 737NG cockpit will all instrumentation and displays driven by separate PCs. FSX is only used for the flight model and the 3D scenery world. I also have a Piper GA cockpit with analogue instrumentation -- again no panel on the FS screen. But I Never got into GPS's on aircraft -- FMS and IRS on the 737 and good old raw VOR and NDB navigation on the GA aircraft! ;-) I'll take a look at the GPS interface in January. If it isn't a lot of work I'll add it. Regards Pete

Not the "aircraft section", but the name returned by SimConnect for that aircraft. The aircraft name is obtained from the AIRCRAFT.CFG file. I think we checked that and found it was okay? So it must be a problem in SimConnect itself, part of FSX. It is unfortunate that you never bothered to refer to your original thread on this subject, for whch I just had to do a search. Why didn't you read my last reply there? Why start a new thread on the same subject so forcing a lot of wasting of time searching back for clues as to what this is about? As far as i can see you are the only person with this problem, so it is either a corrupted FSX instalation or a strange behaving aircraft. But please also read the last reply to you in the original thread, to which you never replied. There is no way I can fix this in FSUIPC -- the aircraft name is the only way I have of relating your aircraft to your profile settings. If there is no aircraft name, it is not possible. Regards Pete

For some reason you posted your support question to the User Contributions subforum. I've move it for you to the Support Forum. There cannot be many differences? It will surely usually be a matter of settings, not language Note that the SDK deliberately only includes the sources, not the project folders with bad settings. If you can make a project work with MSVC Basic then you should easily be able to make the source supplied work fine? Regards Pete

All that is correct for both buttons and key assignments. You can have both non-specific and profile specific buttons and keys active at the same time. The latter only override the former when the same button is programmed in both. It has always been that way. it is designed so you can have common functions fr all aircraft as generic and specific aircraft or profile functions merely augmenting or overriding those. The only section this doesn't apply to is the axis assignments because extra axes not intrended for this aircraft might have adverse affect. This isn't a problem for buttons and keys which are only active when pressed or toggled. The user guide does tell you this. You just swap between the two using the check box, as you've found and as you could have read about. I've no idea why you enabled every single logging facility and made such a huge boring log file, and even posted it!? All I needed to see was the line showing the aircraft name, which is there ok: All I asked was to see the log, not for you to change or set any options!! The default logging would have shown all that was needed, and much easier! Pete

I didn't realise you were only interested in static information, not the full GPS capabilities. If you only really want the static information which is fixed by the BGLs, why not use my freeware MakeRunways? Many of the sorts of add-ons you are talking about do. It only needs re-running when you update the scenery. Pete

The only time I've seen anything like this is when SimConnect is supplying no name for the aircraft, so its profile can't be referenced. This afflicted an A2A aircraft user, and has only been reported just recently. The thread won't be far below. Can you give any more information? Like the FSUIPC4.LOG file? And maybe show me the INI file. You can paste both into a message here -- easier than uploading. Regards Pete

It would have been useful for you to state which button/toggle it is you have the problem with. I can't immediately see a problem with the INI, but not knowing even which device or buttonmakes it harder. Ah, sorry, I miread the error message. The one i referred to is "this has multiple actions ...". "Mixed actions" is a different problem. It means that on "Press" you have assigned to a Keypress and on "Release" to a control. or vice versa. This is okay, it will work, but you can't then edit it in the dialogue because that has one or the other for both press and release. you see? [LATER] Aha! Looking again through your INI, the button responsible for this is: 128=P3,26,K0,8 129=U3,26,C65546,0 which is rather odd as "K0,8" is a NULL keypress. Try deleting line 128. Regards Pete

Is this with ALL aircraft, including defaults, or just your "selected aircraft" as you said originally -- i.e an add-on one you normally use? The first log is no good because you pressed the button on the logging page to start a new log. Please do not do that. It only confuses matters. It also dates back to before I asked you to try logging, and the axis logging was not exabled, so it doesn't help in any case. In the second log you showed, you have enabled logging for the axes and they show clearly in the log. And you said they worked. So everything was normal, and the log shows nothing out of the ordinary, of course. The INI file also shows nothing wrong. For more direct feedback, so you can see what is going on, you can run FSX in Windowed mode (ALT+ENTER) and make its window a little smaller, and enable the Console log in FSUIPC's logging options. Then you will see what happens exactly when you move the axes. I see you have 11 separate axes assigned on three different devices: So far I really cannot see how ALL 11 of the axes suddenly stop working. That would be amazing and would surely indicate something really serious wrong somewhere in the system. I'm not sure how to narrow it down to a cause. It's a complete new problem, never reported before. Do you have any FSX add-ons running? If you reload or change aircraft does it persist? I am away from Wednesday night for over three weeks, so I'm not sure we can reach any sort of solution in the short term, but please do continue to try to narrow it down. Incidentally, so you are using the same version of FSUIPC as me, please get the very latest interim update, 4.859m, from the Download Links subforum. Regards Pete

Okay, I had a quick look. The problem isn't with LuaCom, but with Lua5.1.dll. It is compiled using an earlier version of the MSVC run-time library than Prepar3D 1.4. -- MSVCR80.DLL to be precise. This is the same as that used by FSX so there's no problems there. If i find my MSVCR80.DLL and put it next to Lua5.1.dll in the P3D folder I still get an error, but a different one -- "not a valid application". I think this is misleading. I think the error derives from a clash between the MSVCR100.DLL library already in use by P3D and the older one. I had the same problem with FSUIPC4 when Lockheed Martin moved on to the newer library. This was a significant change between 1.3 and 1.4. I got around it by recompiling FSUIPC4 with static library options instead of dynamic -- i.e. compiling the library functions needed into FSUIPC4 rather than calling them in the DLL. This is a link-time option for any MSVC project. So, I'm afraid you've no option but to download the source of Lua5.1.dll and recompiling/relinking it with such an option. I suspect this would be useful to others too, so if you do it please consider letting me host it or at least link to it in my SubForums. If you are not in a position to do it yourself, and no one else has done it for you by the time I get back mid-January, let me know and I'll try to do it for you. Regards Pete

Sounds like they are asleep. All going into FSUIPC options will do is re-scan all connections, just as it will be doing in any case when you first start FS. You should find they 'wake up' if you waggle them several times before starting. But also check the Windows power management on all the USB hub devices in Windows Device Manager. By default Windows limits the power to devices making them unresponsive. And only with that one aircraft, or all aircraft? How and where you ASSIGN rather than calibrate is more important. And do you have joysticks turned OFF in FS, or only de-assigned? Regards Pete

"Suddenly stopped"? Like as if the wires pulled out mid-flight? Assigning in FSUIPC to the same FS controls as in FSX does exactly the same thing as assigning in FSX. The use of this is smply so that you can have different assignments for different aircraft. You did not. In any case it would be better to simply paste the contents into a reply here. You can also use FSUIPC logging facilities to check what is happening. You will see there is an option to log axis events. Regards Pete