John Dowson

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

I don't know why Edge is doing that - nothing has changed in the release process...you can always try downloading from www.fsuipc.com

This looks to be a browser caching issue - try clearing your browser cache and retry... John

This looks to be a browser caching issue - try clearing your browser cache and retry... John

I don't know (I don't use VR) - why don't you try it? There is a trial license available in a post at the top of this forum. FSUIPC7 doesn't do anything special for VR - your controller assignments will be the same as for none-VR. John

I haven't looked at the SDK changes in detail yet - this will have to be after the release I'm afraid as I'm still not enrolled in the beta program. But this should work in the current release, and has been available since I released the FSUIPC WASM module, which handles lvars/hvars/calculator code, over a year ago. You can also use offset 0x7C50 for setting lvars, activating hvars and calling presets. 😁 Yes, unfortunately! I had planned this holiday for 2-3 weeks after the SU10 release, to give me time to review the SDK changes and update and release FSUIPC7 before I went away, but the delay in the SU10 release has made this a bit more tricky...hopefully I will geta chance to at least re-build and update anything important and release before I go away. Cheers, John P.S. v7.3.8 has been released.

First, you posted in the Download Links sub-form, where it explicitly states NOT for support requests. Please take care to post in the correct forum for your issue. v4.977 is the latest and only supported version of FSUIPC for FSX. FSUIPC5 is for P3Dv4 only, and has been discontinued, replaced by FSUIPC6 which is valid for P3Dv4 and P3Dv5. John

Ok, thanks for the update. What was the issue? Regards, John

Error 10061 is a windows socket error 'Connection Refused'. Is WideServer enabled and active on the server (i.e. in FSUIPC7? Can you show me your FSUIPC7.log and WideServer.log files as well please. What are you using WideFS for? It is also possible to run FSUIPC7 on a client machine. Depending on your use case, this may also be a solution (and negates the need for the WideServer license). There is an appendix in the Advanced User guide that shows you how to set this up. Other than that, please show me the additional files and I will look into this further, but probably not until Monday now. John

What does this mean? Can you please be more explicit in what you have tried and what occurred, and answer my direct questions. Also attach your updated files, otherwise I cannot help you. I would like to see an FSUIPC4.log file generated after you ran the simconnect installer. Did you try running as admin? If so, where is the log file from this? How did you install FSX? I think you may need to uninstall and re-install using the Steam client. But let me look at the log files first. John

Try the macro file in the first message in that post I referenced, and then assign to the macro:lvar and give a parameter, although I am not sure what the parameter values should be. Try 1 to activate and 0 to turn off, which is standard, and if that doesn't work you can try listing the lvar values (there is a control available for this - List local panel variables) to see how they change when you manually start the ignition and engines. As for your mouse macros, I am not sure why they aren't working. It could be that mouse macros don't work for the FSLabs A32x (not sure, I don't have this aircraft), or that the mouse action (3 - Left single click) is not correct. You could try changing it to use a click followed by a left release, i.e. However, I think you will be better off looking at the custom controls provided by the aircraft. The FSLabs A32x aircraft use the Rotor Brake control with the parameter indicating the actual function. There should be a tutorial on how to use these with FSUIPC on the FSLabs forums - see this post: John

How did you manage that? When you install FSUIPC6, it should detect FSUIPC5 is installed and remove that... You could just remove FSUIPC5, but maybe first try the following: - uninstall FSUIPC6 by using the provided uninstaller (in its installation folder) - then re-run the FSUIPC6 installer -this should detect that FSUIPC5 is installed and uninstall that before re-installing itself Otherwise, you can just remove the FSUIPC5 entry from your DLL.xml file - uf you don't know where that is, the location should be in your FSuipc5/6 installation log files. You can also just rename/remove/delete the FSUIPC5.dll - that will also stop it being loaded! John