Pete Dowson

What did you expect? As I carefully explained, it simply adds more logging. And this is it: Which does definitively show that you had FSUIPC4 checked and the Check existing registration(s) selection checked. There's really no way possibly for the above log to show what it is showing without that selection. Pete

Neither of those are at all useful. Does the FSUIPC4.LOG show anything? Pete

Please download this updated installer and try that. It simply adds log entries about exactly what it thinks is going on at the registration dialogue stage. Install_FSUIPC4949_.zip Then let me see the Installation log please. Pete

It sounds like both options are selecting the "just check" entry. When you looked at the contents of the folder, was there an FSUIPC4.KEY file there? This has not occurred before, and I can see no possible reason for it. The ONLY way error code 16 can occur is when the Installer is simply checking the existing KEY file, and finding no FSUIPC entry. (code 32 = no WideFS, and 48 = neither, assuming you ask also for WideFS checking). I'll make an installer with additional logging to see what is going on. Pete

Yes, of course you can get the G-force from the offset in which the value is placed. That is why FSUIPC provides all the data listed -- for applications to read. You can read it n a program interfacing to FSUIPC or via a Lua plug-in Module. You can also monitor it in the Log and/or display it on screen using the Monitor facilities in the FSUIPC Logging tab. Pete

Hmm. Nothing wrong there. The error you report occurs if you have not previously Regstered and, instead of checking "Just enter new registration" you wrongly checked the "Check existing registration" option. Can you please confirm you are actually following the dialogue correctly? Pete

Is this the FSUIPC mouse look option, or the one in P3D itself? Have you been to the P3D support forum? I have noticed a number of reports of problems with mouse click recognition in 3.1. Possibly this is one of those? FSUIPC itself won't be doing anything differently. Might be worth reporting over there? Pete

What are the FSFX packages? I'm not aware of any requirement for FSUIPC by any FSX or P3D PMDG product. There is no way FSUIPC is anything to do with that. FSUIPC changes nothing to do with recognition of FS versions. And Uninstalling it is simply a matter of deleting the FSUIPC4.DLL file from the Modules folder. I would have thought the ORBX installer would need you to make that choice in any case -- it has probably been updated for P3Dv3 recently. Pete

No, sorry. FSUIPC can only see 1-32 (which it knows as 0-31). The only way with FSUIPC would be via a Lua plug-in using the HID device functions. Pete

You'd need to know how to drive that display -- i.e. with a driver, or possibly writing your own. If it's a standard USB or serial port device that you could even use a Lua plug-in to do it. But FSUIPC doesn't not contain display drivers for every conceivable type of display, I'm afraid. Pete

Sorry, I don't know C#. Isn't the example of the interface in the SDK of use? Once you know which offset to use, what would be the problem? Have you considered using Paul Henty's .NET DLL? It makes such things much easier -- see the SubForum about this, above. Pete

Hmm. FSUIPC wouldn't know or care about you changing any of that. Do you have anything using FSUIPC, or any Lua plug-ins being used? Pete

Are you writing a program to interface to FSUIPC? If so you'd need to display the text using offset 3380/32FA and use FSUIPC or Windows hotkeys to detect a reply. With a Lua plug-in you'd simply use ipc.ask. Pete

Current supported version is 4.949. That happens when there is already a profile for that aircraft. Take a look in the Options dialogue title bar -- the aircraft name will be there. Pete

Not sure why the Ocean should have anything to do with it, but it sounds like your system is so overloaded that SimConnect communications a failing. Two things to try. First disable FSUIPC's autosave (or any other autosave program you might be using) -- the PMDG save routines do freeze the sim whilst collecting data and creating files. Second you can try extending the timeout in FSUIPC so it isn't quite so critical of SimConnect responses. This is the "SimConnectStallTime" value in FSUIPC4.INI, and it defaults to 1 (1 second). Try increasing it. Initially try 10, then, if that works reduce it until it fails again, then increase it one notch. Pete

Saitek devices are a real pain. Try uninstalling it completely using the Windows device manager, including any driver, then re-booting. If that doesn't help, check some of the entries in the FAQ subforum. Pete

Sorry, I do not know what a "New Application Access Key" is, and it isn't needed for FSUIPC4 to work. If you want to use any of the FSUIPC4 user facilities you need to purchase a registration key from SimMarket, but this is not needed for almost all applications. FSUIPC won't do anything to "boost" FSX. I don't know where you are getting all this misinformation from? Pete

All of the Logging facilities are available whether you have Registered or not. Did you not look? Pete

Sorry, what do you mean by "exit" in this context? I do not understand. And what is =(2 alphanumeric), etc. Do you mean those accented characters are actually on a standard US/UK keyboard as 2, 7 and 0? FSUIPC does not send characters but keycodes. I suspect accented characters are actually multiple keys in effect. maybe e then ' perhaps. I don't know. If you can find out what is actually sent for those keypresses I can see what can be done. I think there are free programs you can find which simply show the keycodes being sent when you press keys. I can't locate one offhand, but that might be useful for you. I find it a little puzzling that LevelD products would be dependent upon characters only available of specific language keyboards though. Maybe you can tell be what the equivalent is for a UK/US keyboard. Surely it is documented? Pete Pete

They are being obtained in any BGL which is being processed, for add-on sceneries as well as stock. The latter would override the former usually, because the airport BGLs contain "deletion" commands to delete lower layer entries. If there are some missing it seems most likely that they are either missing or incorrectly provided in the relevant BGL file. If you have an example, please find the entry in the Log file (Runways.txt) and post me that complete entry, and if possible a copy of the identified BGL and I can check it here. For the file, ZIP it and send as attachment to petedowson@btconnect.com. Pete

Yes, as noted in the Read Me, but there isn't one for a Quiet mode. But t easy enough to add. I'll do it once I've caught up with my work backlog. Pete

Ah, my bad, didn't realise that. Thanks Umberto! Pete

Thanks, Dario. Note, however, that's for a Lua plug-in program. For a simple assignment to a switch you'd select <custom control> and enter 69749 for the control number and that other number for the parameter. Incidentally, that second number makes more sense as 0x20000000 in Lua, or just x20000000 as the parameter entry. It's a single digit in a 32-bit binary value. Pete

Please send me your registration details (not here -- to petedowson@btconnect.com) and I will check them for you. Pete

Seems that the Installation was not successful, then. Re-running the Installer won't accomplish anything. Please find the Install Log, which will be next to the Installer, wherever you ran it. Paste the log into a message here. Pete