John Dowson

The change in SU10 that caused this issue has been identified - it is due to a change made in the way a simconect function is used (RemoveClientEvent - see here for details). This should (hopefully) be corrected in a future update, but in the meantime I have added a fix so that previously functionality can be restored, and you can now calibrate again in FSUIPC7 when assigned to 'Send to FS as normal axis' or assigned in the sim. This is available in the attached beta 7.3.13a: FSUIPC7.exe John

All information on FSUIPC7 auto-start is in that FAQ entry - I have nothing more to add or say on this issue. Please read that thoroughly (there is an alternative method you can try..) - as it says in the README.txt: Sorry but I have responded to this same issue so many times now - this is why that FAQ entry exists; John

The desktop icon that is optionally added by the FSUIPC7 installer does not start FSUIPC7 - that icon simply starts MSFS and shows a splash screen for 25-30 seconds while MSFS is loading. It is MSFS that starts FSUIPC7 via the EXE.xml file. There is no AutoStart ini parameter. Please see the following FAQ entry that details how auto-start works and what to check to fix any issues: John

Thank you - but it is now John not Pete - Pete retired a few years ago. No, there are no mouse macros in FSUIPC7 / MSFS. Many aircraft in MSFS make extensive use of Lvars, and there are also new variable types that you can investigate - mainly hvars, which are HTML variables which are used to acrivate UI components. However, the easiest way to use lvars and hvars (as well as other variable types, such as z cars) is to use calculator code, and the easiest way to use calculator code is to use the provided presets, available in the control assignment dialog boxes by selecting the checkbox Select for Preset. The presets provided are from the Hub Hop resource which is a community driven effort led by MobiFlight - see https://hubhop.mobiflight.com/presets/. Also see the Advanced User guide on how to use lvars/hvars/presets in FSUIPC7, in the WASM section. Looking at the preset list, the following look applicable for replacements to APU_BLEED_AIR_SOURCE_TOGGLE and APU_BLEED_AIR_SOURCE_SET for the FBW A320: A32NX_APU_BLEED_OFF_OFF A32NX_APU_BLEED_ON_ON and maybe: A32NX_OH_APU_BLEED_TOG There are many other bleed controls - please take a look at the MF Hub Hob site. It has a good search interface and you should be able to locate the presets needed for the items you need, and the presets you see there should be available for assignment in FSUIPC7. John

No - the PMGD offsets are just populated by the (client) data received from the aircraft - nothing is changed. John

There is no problem installing FSUIPC4 on multiple computers. If the registration validation is failing - and you have already registered with the same details, then you must be entering them incorrectly. Note that all 3 components must match - your email address, name and key. You can also just copy your FSUIPC4.key file across from your original installation to the laptop and use that. One other possible cause could be out-dated VC++ redistributables. You can check what VC++ redistributables are installed and maybe download and install the latest combined package from https://learn.microsoft.com/en-us/cpp/windows/latest-supported-vc-redist?view=msvc-170 - make sure you uninstall any of the 2015, 2017, 2019 and 2022 ones already installed before installing this combined package. If your issue persists, please let me know your FSUIPC4 order number and I will check your details here - but if they have previously validated ok, there really shouldn't be an issue. John

I have no idea - I just add this data as provided by the PMDG 737 SDK. This is therefore a question for PMDG - try their support. John

Ok, thanks for the update. John

What do you mean by 'disappears'? Do you see the FSUIPC7 splash screen? Is an FSUIPC7.log file generated - if so, please show it to me. Otherwise, please update your VC++ redistributables to the latest combined package and try again - uninstall any of the individual packages already installed. Instructions and a link to the VC++ redistributable download page can be found in the README.txt file. John

Yes, you can do that, and many people do use this method to reduce sensitivity. However, you will lose the full range of the axis. John

So you cannot read 32-bit floats or 64-bit double floats from C-Pascal? I find that quite strange... I cannot possibly allocated fixed offsets for this when they will only be used for a specific aircraft and dor such a small subset of users. But, as I said, there are mechanisms provided for the user to do this - if its a standard simvar that is held in the offset, you can dd the same simvar as a different type, i.e. as an integer, using the mechanism provided and documented in the Advanced User guide (page 34). If its a PMDG offset, then you would need a lua script (registered version of FSUIPC only) to monito that offset and pick up any changes (using the event.offset function, as already suggested) amd convertt the value to the required type and then write that value back to an offset free for general use. I can help with both of these, but you should try to do this yourself first. Note that I am away this weekend (the wife's birthday), and so will be unavailable from a few hours time until Monday morning, so I can help further then if you are having issues. John

I am trying to help, and would help further if you had a better attitude. John

Have you looked into using the custom controls? See There are also presets available for these, e.g. for the strobes you can use PMDG_B737-7_LIGHTS_POSITION_STROBE, and for the master battery the following are available (see https://hubhop.mobiflight.com/presets/😞 Note you can assign to MF presets (as well as your own user-defined presets) by checking the checkbox 'Select for Preset' rather then 'Select for FS control'. Note also the PMDG custom controls (not Rotor Brake controls) only work with the latest version of FSUIPC7 - 7.3.12, released yesterday. However, I believe nost of the PMDG presets are using the Rotor Brake control, so they should work in earlier versions. John John

FSUIPC cannot possibly cause any of the symptoms you describe. If you did no install the WASM or the auto-start component, then FSUIPC7 as no affect in MSFS at all until you run it - i.e. it makes no changes to anything in your MSFS installation. Installing the auto-start component only modifies one additional file (EXE.xml) in an MSFS folder, and installing the WASM only installs that into your MSFS Community folder. Nothing is changed in MSFS itself Uninstalling FSUIPC7 will leave MSFS in exactly the same state as it was before you installed FSUIPC7. I therefore cannot see how FSUIPC7 has anything to do with any of your issues, sorry. John

You can also use a lua script, using event.offset, to get the existing offset value whenever it is updated, convert it to whatever you like and then write the new value to a free user offset.... John

You can try adding the same simvar (ELECTRICAL BATTERY VOLTAGE) to a free user offset as another type that can be read/converted using SC-Pascal. I am not 100% sure on this (and won't have time to look into this until next week), but you could try adding this as a a 32-bit float (F32) or as an integer (I32) if they can be read in SC-Pascal. I think the original 64-bit double value would then be converted or cast to the defined type. See page 34 on how to add simvars to FSUIPC offsets. Any issues let me know, and I will take a deeper look next week. John

👍

It is not obsolete - the Rotor Brake controls still function as explained in this post, but the Rotor Brake control has now been deprecated, which means they you should move away from using this as it may be removed in a future update, although I doubt very much that this will actually happen. For clarity, instead of using the Rotor Brake control, you should now use the provided custom controls, which work in the same way as they did in P3D. Note that these are also more powerful, as they can be used with proper parameters as well as mouse codes (where appropriate). I will therefore keep this topic, but will now lock it. John

👍 Thanks for checking, John

Ok thanks - when I get it I will update the downloadable zips, but there will be no version change. Not sure, but its in the latest installer and attached here. It hasn't change for a while now. John Offset Mapping for PMDG 737-700.pdf

I have just released 7.3.12 which contains a fix for using custom controls - available from the usual places. Note that FSUIPC7, the WASM and the WAPI have also all been updated to VS2022 and the latest platform toolset. If you are using the WAPI then please update your application. John

I have just released 7.3.12 which contains a fix for using custom controls - available from the usual places. Note that FSUIPC7, the WASM and the WAPI have also all been updated to VS2022 and the latest platform toolset. If you are using the WAPI then please update your application. @Paul HentyWill the websocketserver need an update for this?

There's a trial license available in a sticky post at the top of this forum if you would like to try the full version first. I've looked into this further and it seems that the way the MSFS SDK handles custom controls has changed, and I suspect this is since the SU10 update. Currently it is not possible to send these custom controls, but I will update FSUIPC7 to handle this and post a new version. You can use the Rotor Brake control, but you can only send mouse operations to buttons/switches/rotaries/etc using this method, and not other parameters (such as heading). Not sure why the PMDG SDK doesn't mention this - maybe because the Rotor Brake control is deprecated now in the MSFS SDK.

I've looked into this further and it seems that the way the MSFS SDK handles custom controls has changed, and I suspect this is since the SU10 update. Currently it is not possible to send these custom controls, but I will update the code to handle this and post a new version. It looks like you can still use the Rotor Brake control, but you can only send mouse operations to buttons/switches/rotaries/etc using this method, and not other parameters (such as heading). Not sure why the PMDG SDK doesn't mention this - maybe because the Rotor Brake control is deprecated now in the MSFS SDK, so you should move away from using this and use the custom controls instead. I'll try and get a new version out in the next few days. John

How strange.... But it seems to have resolved itself....still no idea what caused this though, very puzzling... Anyway, glad is all now working - thats now one weird issue of my list! Regards, John