Pete Dowson

Who or what are you quoting? Would you like to ask a question of your own? Pete

Do you mean Mouse macros? When you "created" them, did you TEST using the TAB key, as documented? Did you create them with the version of the aircraft you are using? If the version is changed, the location in the code which is recorded in the macros will be wrong. You must re-create them. Offsets listed in that document refer to the systems implemented in FS, not necessarily in sophisticated add-on aircraft. If the offsets are working for the aircraft you can assign FSUIPC contorls in the drop down to change them -- they controls ore named Offset ... and they are dmany for different data types and changes Sorry, I don't really understand this question. Pete .

Sorry, I've no idea whatsoever what the names in that SDK section refer to. If they are Lvars (local panel variables, often named with L: beforehand), then, yes, Lua can read the values But names are strings, so it should look like ALT_value = ipc.readLvar("AB_AP_ALT_Select") You'll need to read and understand the SDK to decide, I think. Pete

That's a common Saitek installation fault. I don't know why they never fixed it. You have to edit the Registry I think -- see the thread about this in the FAQ subforum above. Pete

These are the variables used by FS when it is controlling the sub-systems. Sophisticated aircraft like the PMDG 737NGX, the 777X and the Aerosoft Airbuses implement their own subsystems. There may be some overlap, you'd have to check. The variables you mention are available in FSUIPC offsets if you are not using SimConnect. The Lua program method is the only way to real local gauge variables (LVars) without writing a module or gauge to go inside FS. Pete

Does FS recognise the axes? If not you need Saitek support. If it does, then the most likely problem is that Windows is not assigning it an ID numberr for some reason. Take a look in the FSUIPC INI file, in the FS Modules folder. Is there a [JoyNames] section with the device listed? There is a utility you can use to assign an ID. See this thread http://forum.simflig...not-recognized/ Pete

It's DOWSON, actually. Sorry, I know nothing about any Flight1 aircraft, and certainly not "EGPWS". What is it? How is it related to anything in this Forum? Pete

I am 72 years old and have used computers since 1963. But I'm not sure where the history is relevant. I was not insulting you -- it was just that in the last message you explicitly said "So I enter name and email and paste the 12 -character key" Do you not see the difference and significance to me? Please email me at petedowson@btconnect.com. See if there is a file called "FSUIPC4.KEY" in the FSX Modules folder. If so, please rename it (KEY files won't get through), eg to FSUIPC4.TXT, and attach it. If there is no KEY file, see if you can capture a picture of the Registration screen after you have entered the details. Also include the FSUIPC4 Install LOG from the Modules folder and, if you have run FSX since installing FSUIPC, the FSUIPC4.LOG file too. I'll get back to you by email. Pete

You purchased version 4, not a specific version 4. And yes, 4.943 is the latest. I checked your order and everything is correct and works fine. I am sure you are making an error. So you did not copy and paste the name and email? Check again. ALL THREE PARTS MUST CORRESPOND EXACTLY WITH THAT SHOWN ON YOUR ACCOUNT! This is why we place the emphasis on copying and pasting all three parts. So many people spell their names differently each time, or maybe add a space or a stop. I can tell you here the exact name and email if you cannot find what you entered in your order. Pete

You buy either FSUIPC3 or FSUIPC4, not a "latest version". You download the "latest version". -- 4.923 for FSUIPC4 or 3.999z8 (or z9) for FSUIPC3. You only say "FSUIPC" not mentioning the major version which is crucial. Maybe you are using FS9 or before and bought FSUIPC4 by mistake? Or vice versa, you are using FSX or P3D and bought FSUIPC3? You need first to check that.. But anyway, I don't fully understand your description of the problem. You say on the one hand that "everything seem to work fine by installing, no error reports." but on the other that "when attempting to put the key I get the same answer". Since the key is input to the Installer, the error you are reporting must come from the installer, right? Please clarify. What is the "answer" (message? Error?) and where do you see it? The system used to generate keys is automated and there is really no way a properly entered registration will be rejected at the installation stage. There are possible reasons for it to not be accepted in the FSUIPC DLL proper, after you run FS, but not before you run it. If you tell me which version you downloaded, and give me your order number or your email address I can check you bought the right one. Pete

The name "mg_airbus_pedestal" is too long. Needs to be 15 characters or less. Pete

The Lua ipc library supports a function to read the local panel variables (Lvars) too, not just write them. The function is value = ipc.readLvar("name of Lvar") You can even declare an event ("event.Lvar") to call a function when the value changes, with an interval specified to define the polling rate. The Lua library documentation is installed in your FSUIPC Documents folder, inside the FS Modules folder. Pete

No one else (officially) uses that area. I've registered it for FSSymphony now. Pete

See the logging tab. The console window is a separate option on the left. The title bar and other Monitor options are on the right. They are entirely separate and not related to each other at all. Strange. did you report this on the ActiveSky support forum? Pete

I don't think so. No one has ever reported it here with FSX. Pete

Hmm. Getting very tight these days. Would you ever envisage FSSymphony being used on X-Plane with XPUIPC? If not then you could share part of its dedicated area, 6F00 - 6F7F. Let me know. Pete

This is not really "similar" and in fact in not at all related to FSUIPC, so I'm afraid I've no way to help. The crash is in FS's own user interface. Maybe your installation is corrupt and a reinstall would help? Pete

There's no such facility in FSUIPC4. Pete

Doesn't Aerosoft provide any controls for it other than Mouse? Pete

FSUIPC's process is a single process. Each Windows process is allowed only ONE console window, and when it is opened every part of the FS process which wants to log anything gets its output in the same log.. There is no fix. You just get the logging which is enabled in whatever DLLs are running -- ASN has one as well as FSUIPC. SimConnect also has a console logging facility which would share it too. That's not my recommended way at all. You can Monitor it to the title bar or to a normal FS dockable and sizable message window, or use one of the neat little Lua plug-ins around to log it in a more readable fashion in a window or on a client PC. Pete

When you run FS is a runtime log file produced in the Modules folder? ("FSUIPC4.LOG"). If so, please show it to me. If there isn't one then it sounds like you have a corrupt DLL.XML file which is preventing SimConnect even loading FSUIPC4 in the first place. Find that in the same folder as your FSX.CFG file. You could try renaming it, then re-run the FSUIPC4 Installer, which will make it create a fresh one. If FSUIPC4 then loads okay, the renamed one is corrupt in some way. If you post that here I can possibly check it for you. There are many third party add-on installers which make a mess of it, with just sill slips. XML is very very fussy about format, every single chracter appears to be critical! Pete

You probably need someone from SPAD to help. Is there a support forum for it at all? FSUIPC itself is only the interface. Pete

The FSUIPC facility to map throttles from 1 or 2 lever devices in order to operate 3 or 4 engine aircraft are identical in both FSUIPC3 (for FS9) and FSUIPC4 (for FSX-SE). Just do exactly the same thing. Pete

For the older PFC serial devices you need PFCFSX.DLL, and for the more recent full USB HID devices you need PFCHID.DLL. both can be installed together if needed (my cockpit has both types of PFC device). The installation is manual -- just place the contents of the downloadable ZIPs into the Modules folder. FSUIPC will load them and initialise them if it finds them there. Pete

Just installing FSUIPC cannot change anything. All your settings are in the FSUIPC4.INI file, in the Modules folder. That does NOT get changed or replaced when you "reinstall". If you want to reset everything you've done in FSUIPC4 simply delete the INI file before loading FS. FSUIPC will revert to default settings which involve absolutely no interference with any controls at all. Pete