John Dowson

I have released a new beta for SU10, including an updated WASM. Full installer available from: Install FSUIPC7-7.3.9f John

Yes - since SU10, no gauge events are being received by the WASM. This affects hvar activation as well as setting lvars (except when setting as a double) and the WASM reload. I am looking into this at the moment... John

Please be patient. I am installing SU10 at the moment as well as the latest SDK and will be preparing a new release. I will look into specific issues once this is done. John

I suggest that you wait to see if there is an update to the Fenix, and also wait until I have released a new version of FSUIPC7 updated to the latest SDK. Then, if you still have issues, provide more information - including your .ini and .log files. I will be busy tomorrow reviewing the SDK changes and preparing a new FSUIPC7 release, I can look into specific issues once this is done and not before. Please be patient. John

It us not a substantial change - it is only that the aircraft is taking longer to load and therefore longer to make lvars available. However, if the lvar never becomes available then maybe the aircraft has been updated and the lvar name has changed or is no longer available. What aircraft and lvar are you missing? I am updating to SU10 at the moment. I am finishing for the evening and will look at the SU10 release tomorrow.

8 minutes? If the number of lvars loaded aren't changing, then all are loaded and no point continuing to reload. If the lvar isn't available, then it doesn't exist and no amount of reloading will make it available. FSUIPC can only use the lvars that are provided. There is not one there by default, and yes you should copy the one from your Community folder and then edit, as it says in the Advanced User guide: It is recommended to leave this file as is, and copy to your persistent storage area and modify as and when needed from there.

No need - it is just a timing issue, and it is taking longer (somewhere in loading the aircraft) before the lvars (being used) are available.. This has always been a recommendation when using complex aircraft. The default value for the LvarScanDelay parameter is 5 (seconds), but I recommend a value of 45-50 when using complex aircraft and/or airliners. There will be nothing in the next release, but I do have some ideas to make sure that all lvars are available without having to reload, but I will look into this after I have released an updated version for SU10, now that it has been released.. The WASM menu options are enabled once the lvars have been received, indicated by the number of lvars/hvars/presets available being logged in the FSUIPC7 main window. This only occurs one you have a plane loaded and ready-to-fly, and after LvarScanDelay seconds. If the issue is that the lvar isn't available, then you just need to reload until it is.... You can always have a simple lua script that auto-runs for each aircraft and checks that any lvars you are using are available in a loop, and if not then issue a reload, followed by a short pause/sleep, and exit the loop once the lvar is available. You only need to do this for the lvar you are using that has the highest id (as that will be created last), and you can use the lua function n = ipc.getLvarId(“name”) To see if the lvar is available - it will return nil if not available.

Ok, this will also be the issue for @bangaroo. If the lvars are available on a reload, then this indicates that the scan for lvars is being performed to early. To fix this, set or increase the value of the FSUIPC_WASM.ini parameter LvarScanDelay. It is recommended to do this in an FSUIPC_WASM.ini file in your WASM permanent storage area, not the one under your Community\fsuipc-lvar-module folder, as that will be overwritten when you update/re-install. See the Advanced User guide for further details. John

Ok, thanks. Someone else also reported that the PMDG 737-700 presets are also valid for the 737-800.

First, you posted in the FAQ sub-forum where it explicitly states NOT for support requests. Please take care to post in the correct forum for support, which is here or in the FSUIPC7 / MSFS sub-forum. I am not sure what your issue is, but sounds like the offset being read is empty. Why don't you try logging the value after it has been read, e.g. zzz = ipc.readSTR(0x0130, 256) ipc.log("String read from 0x0130: " .. zzz) xyz = string.sub (zzz, -22) ipc.log("Last 22 chars: " .. xyz) I don't know what you mean by this - you are not using any lua numbers...but if you want to use a string as an integer, you can use the lua tonumber(string) function.

Yes, sorry - thought you were using a serial port device. For the newer USB HID devices, you need the PFChid64.dll driver for use with MSFS / FSUIPC7.

Could you try the attached beta please, 7.3.9e. This should automatically re-write your ini to use the preset name when assigned to an axis, although you may have to go into the axis assignment dialog and click 'OK' to update. Thanks, John FSUIPC7.exe

Thanks @joeherwig. I thought I had removed axes assignments to presets as I wasn't sure if this was that useful and am uncertain about the performance when controlling an axis using calculator code. I added the preset checkbox to allow presets to be used in the right-hand side, but this also has the effect of allowing the preset to also be assigned to the axus input. This isn't an issue in itself, but I think there may be some issues when reviewing an axis assignment to a preset - I will check this and also update the documentation for this. Cheers, John

I don't have the SU10 beta installed so it is difficult for me to advise and this may have to wait until SU10 is released, which should be in the next few days... However, if you could attach your FSUIPC7.log and FSUIPC7.ini files, together with your FSUIPC_WASM.log file, then I will take a look. Has this been an issue with the SU10 beta since release or has this started in a recent beta update? Did you check the SU10 beta support forum to see if others were havung similar issues? John

Any guides for using PFC controls should come with the device itself... To use this device with MSFS, you need the PFCcom64.dll (64-bit) installed in the FSUIPC7 installation folder - for FSX you would have used the PFC.dll (32-bit). These drivers are available from www.fsuipc.com. John

I cannot help you if you do not tell me what the problem is - just saying that it has not worked is of no help. What exactly isn't working? Once FSUIPC7 is installed, does it auto-start with MSFS? Can you start it manually? Once FSUIPC7 is running, you can access it from your system tray or use the default hot key combination Alt+F to show the main window?

Please supply/attach more information - your FSUIPC7.ini file and an FSUIPC7.log file with relevant logging applied, which un this case would be for Buttons & Keys and Events. John

This sounds strange: the MSFS.bat (and desktop icon link) starts MSFS in the same way as the MSFS icon and menu entries - all that .bat file does is display a splash screen for the first 30-45 seconds or so while MSFS is loading. With FSYUPC7 auto-start, it should makes no difference whatsoever if you use the FSUIPC MSFS.bat file or the MSFS-provided start options. I would like to see a log file (+ .ini) for when this occurs - and exit FSUIPC before reloading the assignments, I vaguely remember a similar issue from another user a few years which I believe I added a new ini for to resolve, but I need to check, But I cannot help if you do not show me the relevant files... Hopefully not...SU10 should be released tomorrow or in the next few days (unless there is yet another delay...) and I will update and release 7.3.9 once I have updated to the new SDK, but for the time being there is a beta available of this release in the announcements sub-forum if you would like to try that. John

Sounds like it might be an issue with your USB hubs. Try switching hubs for the GF-Pro yoke if possible, and check that you have power management disabled on all USB hubs. Windows has a tendency to revert this setting on some windows updates. Good to know, thanks! John

MSFS is a very different beast to FSX and takes some time an patience to configure correctly... But what exactly is your problem with FSUIPC7? What do you mean by this? Are you assigning in FSUIPC?? Can you show me your FSUIPC7.ini and an FSUIPC7.log file, generated when you experience this issue, and preferably with relevant logging enabled - maybe start with Buttons & Keys and Events, but if your issue is with axes assignments you will need Axes Controls logged. Do you mean that FSUIPC7 does not auto-start? If that is the case, please see Otherwise, please explain what you mean. I don't know what you mean...of course people have issues (which I am here to help with), but FSUIPC7 is stable in MSFS. Almost all reports of CTDs are MSFS CTDs, not FSUIPC7. A trial license is also available for FSUIPC7, and I recommend you always try with the trial license before you buy. John

What do you mean by this? The PMDG offsets are read-only - you cannot write to them. So 646C should report the state of the left aft low pressure annunciator, and 646D the state of the right aft low pressure annunciator. Writing to PMDG offsets will have no effect.

Could you post a link to this response in case any one else comes across this post - would be useful... Thanks, John

Great - glad you got it working! John

Yes, thanks - but far too short! The first log is for a registered version on windows 11 but ends after 21 seconds by user request - it is useless to me as it shows nothing. The second log file is more interesting, but is from an unregistered version in windows 10. All lvars/hvars have been received, and so should be available for use/assignments - are you sure the WASM menu items weren't enabled? I will look into this (i.e. on an unregistered version), but if the WASM menu items are disabled once you have an aircraft loaded and ready-to-fly (and lvars.hvars have been received) can you try: 1. Disconnecting and re-connecting from MSFS to see if that triggers the menu enable once the lvars/hvars have been received 2. Exit and re-start FSUIPC7 to see if that enables the menu items on lvar/hvar exception Note that the menu items should be available once a message similar to the following is displayed in the FSUIPC7 main window (and not before): i.e. after the number of lvars/hvars/presets loaded has been reported Also, when you attach a log, can you give some information on how and when FSUIPC7 was started and, if not auto-started, the state if the sim - was the sim in the main menu or was an aircraft loaded and ready-to-fly? Also, its not a good idea to start FSUIPC7 when MSFS is in a pause state. Its generally better to have FSUIPC7 auto-started by MSFS. I also see you are using the beta version 7.3.9c. I released an updated beta 7.3.9d earlier today so please update. John Later: after checking the code, I cannot see how the WASM menu items were not enabled after this message in your second log file: 299204 [DEBUG]: EVENT_LVARS_RECEIVED:14 of 14: dwObjectID=0, dwDefineID=17, dwDefineCount=1, dwentrynumber=1, dwoutof=1 The WASM menu items are enabled after all lvars have been received, as indicated by that message.

Ok, thank you. Regards, John