John Dowson

Could this be related to the new feature that scans for lvars and automatically pushed new lvars to WAPI clients? When this happens, all lvars are dropped and reloaded and must be re-registered for a callback (n the lvars-available callback function)? Note also that there is a new WASM/WAPI version available here: You can monitor them manually by just listing them in either FSUIPC7 or the WASM Client application. For better monitoring, you can add them to an FSUIPC offset (using the FSUIPC7.ini [LvarOffsets] section) and then monitor the offsets using FSUIPC7's Log->Offsets feature. John

What has changed? Is it still ok with P3D? If this was working ok, then something must have again changed in your system Network connections issues can be difficult to pin down....I can only suggest that you try the usual techniques - make sure everything is up-to-date, reboot everything, try with girewalls disabled, etc...

Ah, sorry - thought you were talking about 7.3.18b for some reason, not 7.3.17b.... The errors were caused when shutting down FSUIPC7 - this was fixed a while ago but not sure what version, bur should certainly be resolved in the latest beta. Cheers, John

They look to be from 7.3.17 not 7.3.16b (unless I forgot to update the version)....there is also a version 7.3.18c available which you can try, available here: Any issues, please comment on that topic. John

Still a few issues in that version though - please try the latest beta, v7.3.18c (and WASM 1.01, WAPI 1.02), available here: John

Great - glad its all working again! Cheers, John

This should be fixed in the latest beta, available here: John

Ok,, thanks for the update. Glad you found a solution. Are these events in the MF Hub Hop site? I only update the events.txt file on releases - it is up to you, the user, if you want to update between releases. No point sending me the file as I update this from the MF Hub Hop site before release. You can submit them to the Hub Hop site if not already there. A later beta version is available, 7.3.18c, which contains the latest evemts.txt file as of yesterday, available here: John

There is now also a later beta version, 7.3.18c, available here: John

No - also for the current release.

These have nothing to do with your issue but indicates a possible issue with your P3D installation. Try re-installing the P3D client. I have now finished for the weekend - I will take a further look on Monday if this doesn't fix your issue. John

What is not clear in the documentation that I referenced: ?

Yes, unless UseKeyboardHook=Yes is used, in which case a global windows hook is used and the key presses/releases are received from Windows. I can't comment on how HidMacros gets its input (haven't looked at the code), but FSUIPC will fet it direct from windows before any processing by other applications when UseKeyboardHook=Yes is used. Ok, doesn't surprise me really. I'm not sure how this works when using multiple keyboards...I don'r know how windows handles multiple keyboards as they are not Hid joystick type devices, which is what I am familar with. I know very little about other types of Hid devices, sorry. I think this is the issue.... I think someone needs to update HidMacros to be compatible with MSFS - would seem to be the obvious solution. Unfortunately I am not in a position to look into this. You could maybe ask about this on the Asobo forums, or maybe over on avsim. Sorry I can't be of more help. Regards, John

Can you please try the latest FSUIPC7 beta (which includes a WASM and WAPI update), v7.3.18c, with the SU12 beta, available with a full installer from here: Any issues with the SU12beta can be reported here or in the Announcements post. Thanks, John

Could you please try the latest beta release, available here: Not 100% sure this will fix your issue though...please let me know! You should be able to remove this now as well, but test with this if you get the same issue. Thanks, John

I have no idea as you provide no supporting information - why can't you register? No - you only need to purchase a license once. I suggest you read the provided Installing and Registering FSUIPC7 document. I provide documentation so that I do not continually have to respond to such requests. The usual issue is that you need to update your VC++ redistributables, as the documentation says. Please consult the documentation and search this forum for similar issues before posting a new topic. John

Correct. I can look into this at some point I guess (i.e. add it to my to-do list), but unfortunately I think it would be many years before I had time to look into such an issue. There are many things I need to look into that would be far more useful to a far larger audience, and my developmet time is limited due to the amount of time I am spending on support... I don't think that would be a possibility, especially without changing the HidMacros code, which I am not prepared to do. Looking at HiDMacros, it does say: so doesn't it work if you just turn-off (i.e. remove) UseKeyboardHook=Yes? If you use HidMacros to send the keyboard shortcut to the FS window, that should then send the "z" key (on numpad1) to the FS, which would then be picked up as the "z" key by FSUIPC where it can be assigned. Is that not the case? Otherwise, you could try using numlock on on one keyboard and off on the other, which would allow you to distinguish between the numpad keys on the different keyboards, but not the other keys. John

Not sure what you mean by this - the list of controls (and presets) is the same for all aircraft. The only aircraft-specific controls are custom controls, such as those provided by PMDG. If the king air 350 provides custom controls, then you can use them by selecting the <custom control> option and give the custom control number. Just checked - there are 37 presets available for the Asobo King Air 350i all starting with KA_ John

I have moved your post to the FSUIPC7 support forum - please take care to post in the correct forum for support. I have lost count of how many times this has now been raised... Please see the provided document Installing and Registering FSUIPC7 - this should contain all the information you need. If you cannot see the Assignments drop-down menu, then you have not registered your license, You do this at the end of the installation process - enter your license details EXACTLY as given, and click the Register button. If you get an error for any reason, please see the documentation - your VC++ redistributables probably need updating if the license details are entered correctly but do not validate. John

Ok. Not sure what happened - the log you posted stopped after 17 seconds and the lvars still hadn't been received. Auto lua scripts are not started until lvars are available if you have the WASM module installed and activated. Cheers, John

Which you didn't follow...no new thread! Presume you mean they didn't work... Ok. But it seems you already have a macro for this, so just assign that to a button or key to test if its working. Ok. John

Hmm, strange...but glad this is now resolved. This is also strange - the current release of FSUIPC7 is still using the WAPI v1.0.0 seemingly without issues. No problem!

All axis settings are profile specific, but the general calibration settings are applied in a profile unless you also check the Profile Specific checkbox in the calibration tab, in which case the general calibration settings are then copied to the profile from where they can then also be edited to suite the profile. Button and key assignments are always automatically inherited in any profile unless they are specifically overridden in the profile itself. Don't worry about it - a lot of people are confused by this. I will see if I can update the User guide to make this more clear - although not that many people seem to refer to this! Cheers, John

What version of VS are you using and which toolset? This seems to occur when using libraries built with a different VS toolset - see https://learn.microsoft.com/en-us/answers/questions/1130957/link-fatal-error-c1007-unrecognized-flag-zc-nrvo-i If not using VS2022 then try with that using windows SDK 10.0. 19041,0, which is what the FSUIPC_WAPI.lib is built with. Not sure what exceptions you are referring to, but there should have only been an issue/crash when calling SimConnectEnd(). There was an issue in this function in v1.0.0, corrected in v1.0.1, due to trying to drop/clear the lvar/hvar name CDA definitions which are now dropped/cleared directly after being read. Regards, John Later: it may be the MSVC toolset, not the SDK, which is v143 for VS2022. I have noticed that there is also a later SDK, v10.0.20348.0, although I am not using this yet. I may update for the next release, but I will add a README.txt and specify the toolset and SDK versions used om the next release.

Why delete it, and just not run it...or exit FSUIPC7 if it is running. Also, if your throttles are working perfectly without FSUIPC7 running, then they must be assigned in MSFS, not in FSUIPC. If this is the case, and the behavior changes when you run FSUIPC, then this implies that you have the throttles calibrated in FSUIPC7. To stop this behavior, just remove/reset the throttle calibration for these aircraft (i.e. in their FSUIPC profile). Please also attach your FSUIPC7.ini file if you have any further questions on this - I cannot tell what FSUIPC is actually doing unless you show me this file. Can you please explain further what you mean by this? Is this again just in both the FBW A320 and the PMDG 737? How are you loading your flight plan? Where do you get the dashed line? And again you say delete which I find confusing, as this implies the problem exists if FSUIPC is just installed on your system and not even running... John