Pete Dowson

These sorts of fiddles are a big cause of pain and problems! The thing is FSUIPC needs to recognise what it is running with! It would have helped more if you actually showed me the log files -- that's why log files are always produced, to provide information to solve problems! I understand the first files with the extra " FSX" part. That means it recognised that you'd renamed Prepar3D to FSX. This action is documented. It also means that you need to make a copy of your FSUIPC4.KEY file, renamed the same way ... i.e. FSUIPC4 FSX.KEY. However, I completely fail to understand why you also have files with " P3D" in the name! That can only happen if you also have run a copy of Prepar3D renamed rto "P3D.exe"! Have you also done that? Why? If you have you need another copy of FSUIPC4.KEY renamed as FSUIPC4 P3D.KEY. Please refer to the FSUIPC4 Advanced User's document. The section "Muliiple INI files" on page 48 explains. Pete

Master Caution doesn't make a sound itself. Do you mean a fire bell, or what? You need to identify the aircraft type and the cause of the sound you are talking about. I suspect the answer is to do with your specific aircraft. Pete

What actually happens when you enter you registration details? Is there no response to this on screen, rather than the log message? Didn't you find the FSUIPC4.KEY file as I suggested? Or have you never registered before? If you did register before, why are you re-registering? Pete

If you were already registered for FSUIPC4 with FSX, why did you buy it again? It's the same version of FSUIPC4 which deals with both FSX and P3D! Maybe you registered originally for FSUIPC3 which is different, for FS9 and before? Pete

Yes via the message offsets. See the offset list. Check 32FA for the control and 3380 for the text. Pete

Sorry, I don't think I can. I don't know anything about IVAP nor how that is involved. And I don't know what "pan look" is. Does mouse look with P3D assignment work dfferently? Pete

:razz: :razz: :razz: I hadn't heard that one before! Thanks! Pete

Correct. There are no "letters" provided by FS. You need only to interpret the sign. If -ve it is S or W, if +ve it is N or E. Pete

FSUIPC doesn't know and there's no variable available in FS to tell it. I can only think you work it out using normal Windows tools, maybe to see if there are any sizing borders or title bar. I don't really know, it would need some research into Window properties. Pete

Yes, that looks good! Pete

As per the offsets documentation in your FSUIPC Documents folder (did you look?), the latitude and longitude values are available in two places: 0560, latitude in FS units as a 64-bit integer 0568, longitude in FS units as a 64-bit integer 6010, latitude from GPS in 64-bit floating point format. 6018, longitude from GPS in 64-bit floating point format. Pete

Sorry, I don't know why the installers are failing. You could try right-clicking on the msi file and selecting "run as ... administrator", though msi files should assume that in any case. Pete

To finish your error message after the ... it says "or doesn't check correctly". Unless you cancelled the registration at the dialogue, this latter does actually mean you made an error. Please make sure all three parts are EXACTLY correct. If you aren't sure and you are already registered for FSX and P3D, then refer to the FSUIPC4.KEY file in eitther your FSX or P3Dv1 Modules folders -- it is a text file, so open it in Notepad. Then cut and paste. Alternatively just copy the FSUIPC4.KEY file to the FSX-SE Modules folder, which is all the Installer would do in any case had you simply responded "Not now" to the registration option. If you do have any further questions about Installation, please do find the FSUIPC4 Install log and paste its contents into a message here. The reason the log is produced is to make it easy to diagnose these things. Pete

Okay. Your FSX-SE installation failed to install SimConnect. I have seen that before -- it happened to me once. I reported it to DTG but they could not reproduce it. I think it might be related to privilegs needed by the Steam based install process. You can try to rectify this by installing it yourself. Go to C:\Program Files (x86)\Steam\steamapps\common\FSX\SDK\Core Utilities Kit\SimConnect SDK\lib and execute the SimConnect.msi file you find there. When it indicates success, you can re-run the FSUIPC4 installer. Please also report this failure of the Steam installer for FSX-SE to DTG on the FSX-SE forum on Steam Pete

Hi Paul, There is a facility in FSUIPC to restore focus to FS, specifically for the keypress control. Please see my last answer to your question in the main forum, i.e. thread http://forum.simflight.com/topic/78544-help-with-sending-key-presses-with-control-1070-via-0x3110/ Pete

Paul, there IS a control in FSUIPC to restore focus to FSX. It is 1125. Here's the text from the History document describing all this (it was introduced in version 4.70 in April 2011. Hope this is useful! Pete

Where does it say that? What version of FSUIPC are you trying to install? I could tell if you hadn't chopped off most of the Install Log. Please NEVER supply partial files, essential information is missing!!! I suspect you are trying to install an out of date version of FSUIPC, but I can't help otherwise without the full log!!! Pete

Event trapping in Lua can be cancelled too. And it is pretty easy for a Lua program to read some sort of parameter file f that's the way you want the keys defined. On your original post: Yes, of course. ipc.keypress or ipc.keypressplus. Pete

Nevertheless, the entry is there. Maybe you used some migration tool or other addon which made that false entry. Pete

Okay, that's better. And the error you get reported is clearly in there, if you had but searched: Cannot edit the DLL.XML file to activate FSUIPC. And the reason for this is also very clear. There's a section for FSX, which was okay, a section for Prepar3D (v1), which is where the error occurs, and finally one for Prepar3D v2. The error occurs because there will be no DLL.XML path for P3D v1. You have a registry mixup with an installation entry for V1 pointing to your V2 as well as a separate entry for V2. Look: Looking in registry for Prepar3D install path: HKEY_LOCAL_MACHINE\SOFTWARE\LockheedMartin\Prepar3D Parameter"SetupPath" Not there, so looking in: HKEY_CURRENT_USER\SOFTWARE\LockheedMartin\Prepar3D Parameter"AppPath" ... >>> OK! FOUND Prepar3D! <<< ... AppPath=D:\Program Files (x86)\Lockheed Martin\Prepar3D v2\ just after this you can see the proper V2 path being found: Looking in registry for Prepar3D v2 install path: HKEY_LOCAL_MACHINE\SOFTWARE\Lockheed Martin\Prepar3D v2 Parameter"SetupPath" ... >>> OK! FOUND Prepar3D v2! <<< ... SetupPath=D:\Program Files (x86)\Lockheed Martin\Prepar3D v2\ The result of this mess is that the Installer tries to install for P3D v1 and P3D v2, both in the same folders. This does not harm (copying the files in twice doesn't hurt), but you'll get the DLL.XML update error because the path to the V1 CFG files no longer exists. So, it does not harm. If you want to tidy it up (as it should have been tidied by the V1 uninstaller) then you'd need to delete the Registry section called HKEY_CURRENT_USER\SOFTWARE\LockheedMartin\Prepar3D Pete

NO I do not!!! The libraries you are using are in FSUIPC and WideClient ONLY. They are not general purpose Lua libraries for the general user, they are purpose specific libraries for FSUIPC and FS. The reference document for the library is in the Lua package installed in your FSUIPC Documents folder, in the FS Modules folder, the place where it is clearly defined in the Install instructions that you should look!! Have you never even bothered to find and refer to the FSUIPC User Guide either? That's in there too! :-( Pete

The reason for this will be in the part of the Install log you didn't bother to show me! Next time you paste files in, please paste the whole file!!!! The message probably relates to an install attempt for another installation altogether. Maybe your Registry also has pointers to P3Dv1. I seen that happen before, especially with folks who updated to v2 but never actually managed to completely uninstall v1 and then used the same folder for V2. Pete

This must be in a part of the Log you didn't bother showing, then, because obviously all is well with P3D install in the part you showed: Now checking DLL.XML ... ... There is a previous DLL.XML, checking for FSUIPC4 section. ... FSUIPC4 section already exists but will be replaced. (for FSUIPC4, without Loader) ... FSUIPC4 section of DLL.XML written okay If you only show me part of things, how do you expect me to help? Well that is certainly not an installation error! Do NOT post screenshots please! Just tell me what the error says, and show me the FSUIPC4.LOG file from after the crash. It could be one of a number of things, but I can't tell without information. Pete

What had the keyboard focus at the time? It will be that window which receives the keystroke. You can easily test using a little Lua, thus: ipc.writeUD(0x3114, 0x4c) ipc.writeUD(0x3110, 1070) Save as, say "test3110.lua", assign a button to it, and press it whilst FS still has focus. Then the log looks like this (with button logging adding to what you have): 1261455 Button changed: bRef=0, Joy=101, Btn=0, Pressed 1261455 [buttons] 22=P101,0,CL115:R,0 1261455 JoystickValues PCnum=0, dwCount=1, data[2]={00000065 00000001} 1261470 LUA.0: beginning "E:\Steam\steamapps\common\FSX\Modules\test3110.lua" 1261486 WRITElua 3114, 4 bytes: 4C 00 00 00 L... 1261517 WRITElua 3110, 4 bytes: 2E 04 00 00 .... 1261517 FSUIPC Control Action: Ctrl=1070, Param=76 1261517 SendKeyToFS(0000004C=[L], KEYDOWN) ctr=0 1261517 LUA.0: ended "E:\Steam\steamapps\common\FSX\Modules\test3110.lua" 1261517 Sending WM_KEYDOWN, Key=76 (Scan code 38), Ctr=1 1261548 KEYDOWN: VK=76, Waiting=0, Repeat=N, Shifts=0 1261548 .. Key not programmed -- passed on to FS 1261548 *** EVENT: Cntrl= 65574 (0x00010026), Param= 0 (0x00000000) ALL_LIGHTS_TOGGLE 1261580 Button changed: bRef=0, Joy=101, Btn=0, Released 1261580 JoystickValues PCnum=0, dwCount=1, data[2]={00000065 00000000} 1261642 SendKeyToFS(0000004C=[L], KEYUP) ctr=0 1261642 Sending WM_KEYUP, Key=76 (Scan code 38), Ctr=1 1261673 KEYUP: VK=76, Waiting=0 Regards Pete :

Sorry, but I am not familiar with Lazarus Delphi. But doesn't is come with a Debugger? Have you tried checking WHERE it is failing, i.e. which line? Without such basic detail I don't expect anyone could help. There are certainly no error messages like that from FSUIPC, so it is all to do with the language and the library functions you are using! Pete