John Dowson

Licenses sent via PM. John

You are not running FSUIPC... The MSFS desktop icon is used to start MSFS, not FSUIPC. It looks like that when you installed FSUIPC7 the installer didn't detect your MS store version and so defaulted to a steam install. Could you please show me/attach your InstallFSUIPC7.log file (located in your FSUIPC7 installation folder), and let me know where your MSFS UserCfg.opt file is located. If one exists under <your user account>\AppData\Roaming\Microsoft Flight Simulator\UserCfg.opt then the installer will think you have an MSFS steam installation. If this is the case, remove or rename that file, manually run the FSUIPC7 uninstaller uninstallFSUIPC7.exe (in your FSUIPC7 installation folder) to remove FSUIPC7 from your system and then try to install again. After installation, check your installation log file to check that the MS store version of MSFS was detected. You can also try manually starting FSUIPC7, either before or after starting MSFS, by double-clicking the FSUIPC7.exe in windows explorer.

I don't have the 738/739, bur check the SDK for custom controls to control the fuel cut-off levers. For the 737, you would use the following: See the following FAQ entry on how to use custom controls with PMDG aircraft: Alternatively, you could try the following PMDG presets - these are for the 737 but may also work with the 738/9: PMDG_B737-7_FUEL_CUT_OFF_LEVER1_DN PMDG_B737-7_FUEL_CUT_OFF_LEVER1_UP PMDG_B737-7_FUEL_CUT_OFF_LEVER2_UP PMDG_B737-7_FUEL_CUT_OFF_LEVER2_DN Not sure why you would want to bind these controls to axes as they are standard events fir buttons/switches, not axes controls. However, you can assign them to an axis if you wish. You would normally do this using the right-hand side of the axis assignment panel, to send the desired control when entering or leaving an axis range. Yes. You need to create an FSUIPC profile for the v738/739 and make the assignment profile-specific. Please see the provided documentation on using profiles. John

From the websocket server online help (http://fsuipcwebsockets.paulhenty.com/😞 So it can be used, it is just not included or integrated into FSUIPC6 as it is with FSUIPC7. Those are questions for @Paul Henty... John

The standard controls do not work for the G1000 - you need to use Presets. The presets for the G1000 start with AS1000, so for the MFD zoom try AS1000 MFD Range Inc/Dec and the softkeys are AS1000 MFD SoftKeys x (where x is the number)

What aircraft are you using? So your encoders are button-based? This shouldn't be a problem, but the assignments can depends on the aircraft that you are using - please specify.

License sent via PM. John

Have you installed FSUIPC7? You don't say what program is giving that message, but it is (obviously) telling you that FSUIPC7 (on a client) or WideClient (on a server) is not running. This will be available from your SimMarket account. John

What do you mean by 'but it does not communicate with the PMDG and does nothing'? GSUIPC communicates to the simulator. Are you aware that many standard FS controls do not work with the PMDG 737, and you need to use the PMDG custom controls. See the following FAQ entry: What does this mean? Please read the User guide, and familiarise yourself with the Advanced User guide, especially the WASM section in how to use lvars/hvars and presets. There are also many presets available for the PMDG aircraft which you can use instead of the custom controls (which are used by the presets). See https://hubhop.mobiflight.com/presets/ So, for example, the image shows you have assigned the PgDn key to the FS control Taxi Lights On. This will not work in the PMDG 737, You should check the Select for Preset checkbox and assign to the preset PMDG_B737-7_LIGHTS_TAXI_ON - or use the custom control number directly.

Sorry, but what do you mean by this? Can you press the Set button and get the key press registered ready for assignment?

Possibly - you should always extract the installer from the zip file before running it. I have seen strange issues when running the installer from within the zip file itself. You can just install again - this will uninstall the current installation before proceeding,

If you see FSUIPC7 in the task bar after pressing Alt+F then the window must have been opened, and if you cannot see it then it is either positioned off-screen or is being hidden by another window. If you mean the Window entry from the FSUIPC7.ini file, then this is what you need to do, but make sure you do this when FSUIPC7 isn't running. John

license sent.

Ok. Unfortunately I don't have the PMDG 737 for P3D, so cannot check the offsets here. I can see if Pete has a copy and he can maybe check, but that won't be until later next week now as he is on holiday. Let me know how you get on. Regards, John

Your version of FSUIPC7 is very old - 7.2.0 from June 2021. The latest and only supported version is 7.3.21 - please update before anything else. Your WideClient also needs updating - you are using version 6.999 and the latest version is 7.160. Please always make sure that FSUIPC7 is no longer running before you attach;log files. Can you also please activate logging in FSUIPC7 for Buttons & Keys. Also, in your WideClient.ini this line: Log=Errors+ should be in your [User] section but is currently under your [Sounds] section - please correct this as well. Note also that you are using UseSendInput=Yes which is documented as: So you must make sure that P2A has the focus when using this method. You can try this, but it would be better to direct the key stokes to P2A instead - see the section Directing Key Strokes more precisely in the WideFS Technical manual on how to do this. Note you also have an error in the first line of one of your lua scripts: 155937 *** LUA Error: C:\FSUIPC7\ProSim-doors.lua:1: unexpected symbol Please correct all of the above and try again, and any issues please re-send thise files, with the additional logging enabled, and also please attach your WideServer.log file (from the server). John

Why did you post this question in a completely unrelated topic, and also in the wrong forum? You have already requested an FSUIPC7 trial license, so you must know there is a specific forum for FSUIPC7. Sorry, the lua is for the FBWA320, not the PMDG 737. My mistake. For the PMDG 737 parking brake, you need to use the PMDG custom controls - please see this FAQ entry: However, it may be easier to use the available presets. To use these, check the Select for Preset checkbox (in the assignment panels) and you can assign your buttons/switch/keys to the following presets: PMDG B737-7 PARKING BRAKE ON PMDG_B737-7 PARKING BRAKE OFF See the MF HubHop site for a complete (and searchable) list of available presets: https://hubhop.mobiflight.com/presets/ You generally activate reversers by sending a Throttle Decr control (on repeat) on a button press (once throttle is in idle position) and also send a Throttle Cut (or Throttle Set with parameter -1) on release. See this thread for further info: John

You are sending keysend numbers 1 and 2 But are looking for keysend numbers 110, 111, 112 and 113. You need to use KeySend1=... KeySend2=... And you should use different keysend numbers (i.e. 3 and 4) for the buttons used for SayIt. So, try (I also changed repeat R to a press P - do you really need repeat?) and

The lvar holds the correct value but writing to this does not update it. The MF in/dec presets work, but I don't know what can be used to set a specific value.

Ok, the install log shows the 3 simconnect versions installed, so this should be ok... You could try a clean FSX install first... Sorry, but not sure what else I can advise.

It looks like the VS uses the lvar L:A32NX_AUTOPILOT_VS_SELECTED. Try listing the lvars to see if that holds the correct value, and if so add that to a free FSUIPC7 offset. See the section Adding Lvars to Offsets in the Advanced User guide (P46) on how to do this. I don't know if writing to that lvar is working to update the VS, but you can also try that by writing to the offset that holds the lvar, and FSUIPC will try to update the lvar value. Note that the MF presets for the VS in/dec use the following calculator code: inc: (L:A32NX_TRK_FPA_MODE_ACTIVE, bool) 1 == if{ (>H:A320_Neo_FCU_AP_INC_FPA) } els{ 3 (>K:AP_VS_VAR_INC) (>H:A320_Neo_FCU_VS_INC) } dec: (L:A32NX_TRK_FPA_MODE_ACTIVE, bool) 1 == if{ (>H:A320_Neo_FCU_AP_DEC_FPA) } els{ 3 (>K:AP_VS_VAR_DEC) (>H:A320_Neo_FCU_VS_DEC) } So it looks like updating this depends on the track FPA mode - whatever that is... Later: there is also the lvar L:A320_Neo_FCU_VS_SET_DATA that may also be worth adding and checking.... - checked this and this doesn't hp;f the set value, but the lvar L:A32NX_AUTOPILOT_VS_SELECTED does, but haven't checked if it can be updated...

Shouldn't this be 0x07FA (Autopilot RPM (N1) hold value, 16384 = 100% N1) - did you try that one? Don't the same offsets also show the throttle axis value and engine N1 values when AT is engaged?

Nom that was for FSX-SE - I only have the steam version, which is 10.0.62615.0. That is because they are trying to install 10.0.61259.0 which you already have installed. Oy seems that FSX Acceleration uses 3 simconect versions: I am not sure what the difference is between microsoft.flightsimulator.simconnect and the Simconnect.dl and why these are at different versions, but I guess you are ok with the versions installed. Could you attach your FSUIPC4 Install.log file please as that will tell me the simconnect versions installed/detected in your system. But I don't think this can be related to your CTD issue.

With version 7.3.20 or 7.3.21? If its working with 7.3.20, can you try 7.3.21 again please. Before re-installing, just rename your FSUIPC7.exe to FSYUPC7.exe.7320 so that, after the newer version is installed you can easily switch back to the older version if needed. If its now working in 7.3.21, I don't know what could have caused this temporary issue... If its working in 7.3.20 but not un 7.3.21, I will need to look into the cause... Thanks, John

That is the xpack installer, not the simconnect one. If you go to your FSX installation folder. look under SDK\Core Utilities Kit\SimConnect SDK\LegacyInterfaces\FSX-XPACK and you should see a SimConnect.msi file/installer there - try that one. Ok, no problem - just wanted to confirm you had tried this to rule out the possibility of a corrupt weather file.

I am not sure if this is possible in FSX. You could try activating logging for Events (non-axis controls) and see if anything is logged in your FSUIPC4.log file, and if so then try using that. In MSFS, this is possible in the FBW and Fenix versions of the A320, but not in the default/Asobo one, as far as I am aware. John