John Dowson

Where is your Community folder? The installer thinks that it is here: C:\Program Files (x86)\Microsoft Flight Simulator\HLM_Packages"\Community\ which is a very strange path...especially that strange double-quote... Do you have a steam install or an MS store install? If the former, please show me this file: C:\Users\josem\AppData\Roaming\Microsoft Flight Simulator\UserCfg.opt If you have an MS Store installation, remove/delete that file and re-install. John

You still have some assignments to virtual buttons that should be removed (although these should not be having any affect): Your log also shows an error in your Rotaries.lua: Other than that, your log shows the events being sent as assigned, although its difficult to tell as you have obviously changed your assignments when doing this, and I can only see the assignments as they were when you exited. It is always better to provide a matching FSUIPC7.ini and FSUIPC7.log file for each test. Could you switch to using the Baron G58 for your tests - it is in the same profile as your Britten Norman Islander, and I can check/verify that here. In fact, I have just tested and all of the avionics master controls work - Toggle Avionics Master, Avionics Master 1 On/Off/Set, Avionics Master Set. So please try in that aircraft, or is this problem specific to the Britten Norman Islander?

But I already answered this...this is only possible if pressing the button emits an event or changes something (i.e. simvar or lvar) that can be picked-up by FSUIPC, and you would need a lua script to intercept that and send the key press. FSUIPC does not react to mouse operations in the FS, only to the data it receives from the result if that mouse operation, usually an event. If the switches are animated, then the first thing you should try is to set logging for Events (non-axis controls) and flip the switches in the VC and see if any event is logged. The PMDG aircraft for P3D use custom controls, and the FSLabs uses the Rotor Brake control with the parameter indicating the switch and the mouse action, See if any of those are logged. If so, then a simple lua script can intercept these and send the key press. Many aircraft (GA) have a PTT button on the yoke, but this generally doesn't do anything as default ATC does not require this (it uses menu options). Toy would assign this by button to PTT for the ATC system you are using.

The current license only expired today. I will generate a new one tomorrow or Friday. I like to leave a day or two between the expiry of one trial license before I generate the next one one. Sorry for the inconvenience. John

What aircraft are you using, and does the PTT button in the VC actually work? I thought this was inoperative on most, if not all, aircraft... If there is a functioning PTT button in the VC, you need to see if activating this emits an event (it will be a custom event - there are no standard events for PTT) or changes a simvar or lvar. If so, you could use a lua script to pick up this change and then send the key press - which would go to the FS, vPilot would have to have this registered as a hot key to pick this up. If you let me know what FS and what aircraft you are using (and if I have this aircraft), I could take a look to see what, if anything, is emitted or changed.

What do you mean by this? The PMDG offsets only report state, you cannot write to them. If the offsets are not holding the correct data, then there is nothing I can do about this - they are just populated from what is received from the FS. I believe those offsets to now be correct, according to the SDK header file that I have, Offsets 0x65EA (MAIN_NoseWheelSteeringSwNORM) and 0x65FD (MAIN_annunSPEEDBRAKE_ARMED) are correct, and those inbetween are assigned based upon the latest NG3 SDK header file. I am not that familiar with the 737, so cannot verify those offsets (it is not clear to me what they should contain), but if there are any issues, nothing can be done until the SDK has been published, and then (assuming the SDK header file is correct - if not I will update once published) it will be an issue for PMDG. Maybe ask about this on the PMDG forums, but I don't think this will be supported (by PMDG) until the SDK is released, but you may get a response from another PMDG user. John

What was the problem? Is everything now working as expected?

Looks like I forgot to remove that button....not sure how that has not been noticed before. I will remove in the next release. From the Advanced User guide: But there are and most probably never will be mouse macros for MSFS. The facilities in the SDK just do not exist to implement such a feature, and probably never will. MSFS has hvars instead (html variables), as well as calculator code that can be executed via presets. You should look into what presets are available (see https://hubhop.mobiflight.com/presets/) for the function that you want to implement via mouse macros. Presets are far easier to use than mouse macros. John

Note that you should also not modify anything in the Community\fsuipc-lvar-module folder as this would get overwritten the next time you update. You should use the WASM persistent storage area - see the Advanced User guide for details. John

You do not need to run as Administrator - the installer will request admin privileges when required. For any installation issues, you must show me/attach your InstallFSUIPC7.log file. John

I have re-installed steam on my win7 system, and downloaded and installed FSX. The version this installs is 10.0.62615. I then ran FSX once, then installed FSUIPC4. I did get some registry issues (most probably due to duff registry entries from my previous installation), but the installer detected and fixed these. I then ran FSX again and FSUIPC4 was installed and working correctly. Did you try updating your FSX installation from the steam client? If not, try that. Otherwise uninstall and re-install. If you re-install, do not install into a windows protected folder, such as Program Files or Program Files (x86). With steam games, better to install under steamapps (the default), although not strictly necessary. John

There is no Create Mouse Macro button in FSUIPC7 - FSUIPC7 / MSFS2020 does not support mouse macros. Note also that there is a specific sub-forum for FSUIPC7: https://forum.simflight.com/forum/183-fsuipc7-msfs/ John

Please ALWAYS exit FSUIPC7 before attaching an FSUIPC7.log file. I cannot tell anything from the one you attached. Please start MSFS, and let that auto-start FSUIPC7. Then, load an aircraft and click Ready-to-Fly. Wait for 1 minute. Do you see any message in the FSUIPC7 main window, and if so, what? Then exit FSUIPC7, and show me your FSUIPC7.log file. John

But I don't need to see that at the moment - that comment was for future reference. But your ini does show that you are still using the 7.3.8 beta. This has now been released, so please download the latest version. Did you install the WASM and the MF events.txt file? Both of those are needed. After you have reinstalled the latest version, if you still don't see the presets please show me your InstallFSUIPC7.log file as well as your FSUIPC7.log file. Not exactly sure what this means, but you enter the Rotor Brake parameter number in the Parameter box. When using an Offset control, you should see two boxes, one to enter the offset and another to enter the parameter. John

Ok, I found the issue. The MAIN_annunAP_Amber[2] (65F3) and MAIN_annunAT_Amber[2] (65F6) were only allocated 1 byte each. This accounts for the 2-byte difference. So, the correct offsets are as follows: Updated document attached. John Offset Mapping for PMDG 737-700.pdf

First, please don't attach images - they are far too small and I cannot see anything in them. For your assignments, I need to see your FSUIPC7.ini file. All additional PMDG offsets are read-only. You cannot/should not write to them. For control, you need to use either the custom controls via the Rotor Brake control or the available presets. For the former, see All PMDG presets should be available in the latest release, v7.3.8. To assign/see the available presets, you need to check the Select for presets checkbox. Since v7.3.8, presets have been moved to a separate drop-down menu. John

I think it would be best if you uninstalled FSX and re-installed from the Steam client. My FSX on windows 7 is currently unavailable/corrupted as I recently cleaned-out some swappable disks. I am also going to re-install FSX from steam on my Windows 7 system to see where and what it installs... John

You posted a continuation log - please don't do this, always attach a full log file as there is information I need to see. You should also exit FSUIPC7 before attaching a log file. But your ini shows that you are still using the lua hidAlphaButtons and hidBravoButton scripts. These have not been needed for a long time, as FSUIPC has supported up to 128 buttons since v7.1.0. You should remove these scripts and update your assignments to use the actual button numbers rather than the virtual ones. However, you do not have to do this, but you will see both the virtual and real button presses - the ones that you call phantom. But this is not an issue as long as you are only assigning to the virtual ones. As to your actual issue (fuel pumps not working) i would need to see a full log file, if you want to continue using the lua scripts. Note also you should update your profiles to use substring matching, so change to and to and to and to John

Strange...just downloaded from Edge here and got 7.3.8, but I don't use Edge and so had nothing cached. I will revise/check the no-cache headers.... John

Buttons 134 a 135 are for the left most switch, and there is no button 65 - see Button numbers in FSUIPC go from 0-31, 32-39 are for the POV, and then from 132-227. Can you please set logging for Buttons & Keys and Events, generate a log file showing your issue, and then attach your FSUIPC7.log file as well as your FSUIPC7.ini. John

It could be that the lvars were not yet available when the scan was performed in the WASM. If this happens again, consider increasing the LvarScanDelay parameter in the FSUIPC_WASM.ini - details in the Advanced User guide. John

Ok, thanks for the update. Rather strange though - there were no changes between the last beta and the released version. John

There is not much I can do about this at the moment as the SDK for the PMDG 737-700 has still not been published, and I have received no information in SDK updates since version 3.0.25. I will take another look at the PMDG offsets but any information that you can provide is helpful - such as what is the last offset that is holding the correct information? ...maybe try the following offsets, adjusted backwards from 65FD which has been reported as MAIN_annunSPEEDBRAKE_ARMED: 65F3 2 BYTE x 2 MAIN_annunAP[2] Boolean 65F5 1 BYTE MAIN_annunAP_Amber[2] Boolean 65F6 2 BYTE x 2 MAIN_annunAT[2] Boolean 65F8 1 BYTE MAIN_annunAT_Amber[2] Boolean 65F9 2 BYTE x 2 MAIN_annunFMC[2] Boolean 65FB 1 BYTE x 2 MAIN_DisengageTestSelector[2] i.e. adjust the offsets by 2 bytes, It would be useful to determine the first offset that needs adjusting for this (or the last offset that is valid). It looks as if a new 2-byte variable has been added but I'm, not sure where... John

7.3.8 was released yesterday and is no longer in beta. There have been many changes/releases since v7.2.12 - check the FSUIPC History document for a list of changes. However, there should be no changes that break your configuration, but check the history document to see if there have been any changes to facilities that you are using - there have been quite a few changes to key assignments using modifiers, for example. Can you generate a log file showing your issue, with logging for Events and Buttons & Keys activated, then show me your FSUIPC6.log and FSUIPC7.ini files. John

The additional PMDG offsets provided are specific to the PMDG aircraft (i.e. 747, 777, 737NGX - which one are you using?) and are defined in the provided Offset mapping documents. If they are not specified there, they will not be available. FSUIPC4 has been closed for development for many years, and I am not aware of any updates to the PMDG aircraft for FSX since it was closed - I don't own the PMDG aircraft for FSX. If you have the latest PMDG SDK header file for the aircraft, I could take a look to see if this has changed. Looking at the offset mapping for the PMDG 737, I can see that the takeoff config was added at offset 0x6c8f for the NGXu only. But this will be available in FSUIPC5 and FSUIPC6, not FSUIPC4. If this data is provided for the FSX PMDG aircraft, I could possibly add the new offsets but cannot guarantee this. Show me the header file and I will take a look. John