John Dowson

No - I don't have anything configured/assigned for this aircraft. For aircraft that I have for support purposes, I only look into assignments on request (and when I have time!). This looks like quite a complicated aircraft and I would need to spend quite a bit of time to learn how to control this. For example, I don't know how to activate the Autopilot in the cockpit - I can't seem to move the AP engage switch in the VC, but I suspect this is something to do with the state of the aircraft (I can see/read that it needs turn knob in detent and one yaw damper powered, as well as main/essential power on - I would need to read/investigate on how to do this...!). However, there do seem to be quite a few lvars as well as input events available for the auto-pilot: Input Events: AUTOPILOT_PITCH_SELECTOR<>=2.000000 AUTOPILOT_KNOB_VERTICAL_SPEED<>=0.000000 AUTOPILOT_TURN_KNOB<>=50.000000 AUTOPILOT_HDG_SEL<>=0.000000 AUTOPILOT_ALT_SEL<>=0.000000 AUTOPILOT_ENGAGE_SWITCH<;FLOAT64>=0.000000 AUTOPILOT_NAV_SELECTOR<>=0.000000 Lvars: 417188 [INFO]: ID=529 FSS_B727_PDSTL_AUTOPILOT_HDG_ENG_SW_IsDown = 0.000000 417188 [INFO]: ID=530 FSS_B727_PDSTL_AUTOPILOT_HDG_ENG_SW_MinReleaseTime = 0.000000 417188 [INFO]: ID=531 FSS_B727_PDSTL_AUTOPILOT_ALT_ARM_SW_IsDown = 0.000000 417188 [INFO]: ID=532 FSS_B727_PDSTL_AUTOPILOT_ALT_ARM_SW_MinReleaseTime = 0.000000 417188 [INFO]: ID=533 FSS_B727_PDSTL_AUTOPILOT_ALT_ENG_SW_IsDown = 0.000000 417188 [INFO]: ID=534 FSS_B727_PDSTL_AUTOPILOT_ALT_ENG_SW_MinReleaseTime = 0.000000 417344 [INFO]: ID=1130 FSS_B727_PDSTL_AUTOPILOT_HDG_ENG_SW = 0.000000 417359 [INFO]: ID=1131 FSS_B727_PDSTL_AUTOPILOT_ALT_ARM_SW = 0.000000 417359 [INFO]: ID=1132 FSS_B727_PDSTL_AUTOPILOT_ALT_ENG_SW = 0.000000 417406 [INFO]: ID=1322 FSS_B727_WASM_SET_AUTOPILOT_HEADING_LOCK_DIR = -999999.000000 417469 [INFO]: ID=1573 FSS_B727_PDSTL_AUTOPILOT_HDG_ENG = 0.000000 417469 [INFO]: ID=1574 FSS_B727_PDSTL_AUTOPILOT_ALT_ARM = 0.000000 417469 [INFO]: ID=1575 FSS_B727_PDSTL_AUTOPILOT_ALT_ENG = 0.000000 417609 [INFO]: ID=2044 PMS50_AUTOPILOT_INSTALLED = 1.000000 417609 [INFO]: ID=2045 PMS50_AUTOPILOT_VERSION = 3.000000 417609 [INFO]: ID=2046 PMS50_AUTOPILOT_TOGA_ACTIVE = 0.000000 417609 [INFO]: ID=2047 PMS50_AUTOPILOT_MANAGE_MANUAL_ARMING = 1.000000 417609 [INFO]: ID=2071 PMS50_AUTOPILOT_ALT_ARMING = 1.000000 417609 [INFO]: ID=2085 PMS50_AUTOPILOT_CAPTURED_ALTITUDE = 0.000000 417625 [INFO]: ID=2142 FSS_B727_AUDIO:autopilot_disconnect = 0.000000 So you should try those - you can see what values are needed by activating in the Virtual cockpit then re-listing the lvar/input event values and see how they change. If there are both input events and lvars available for a button/switch, I would try the input events first, although an lvar update may be sufficient. Let me know how you get on - any issues let me know and I can investigate further. John

Yes. This just means that any lvars detected after the initial scan will not be known to FSUIPC, i.e. if you try and list them or use them with an lvar function (e.g. adding to FSUIPC offsets, using directly in a macro or in a lua lvar function) then they will not be seen or updated. You can still use such lvars via presets/calculator code. This should not be an issue as any lvars you want to use should be loaded and available after the first scan. Note also that if you create lvars via the various mechanisms for this in FSUIPC, a scan will automatically be performed and the lvar will be available. You can also force a scan if/when required (via the Add-ons->WASM->Reload menu option, or via lua (ipc.reloadWASM()) or a specific add-on control Reload WASM). John

It is likely that your WASM module is crashing - see the following FAQ entry on how to confirm this and how to prevent this (or at least make this less likely to occur): John

FSUIPC3 is compatible with the FS9.1 update (which was made available on October 9th 2004) but not FS9. FSUIPC3 is now available for free - see https://fsuipc.com/. But be aware that FSUIPC3 is no longer supported. For Go Flight modules, you need to use the FSUIPC 32-bit GoFlight drivers, available from the same location - just copy the dll to your FSUIPC3 installation folder. Note that I have never used FSUIPC3 (before my time!) but I believe the GF driver should also work with this version. For FSX, you will need a registered copy of FSUIPC4, and also the 32-bit GF driver. There is certainly no issue running FSX/FSUIPC4 on Windows 11. If FS9.1 also runs on windows 11, then so should FSUIPC3 (as it is an embedded dll) and the GF drivers. John P.S. GF devices are also supported by FSUIPC's lua interface. Lua scripts will be needed to support any GF devices that have displays. See the User Contributions section of this forum for some lua scripts for GF devices.

Ok, thanks, Just want to check that the PMDG 777 thread is started/stopped correctly when needed (on the client PC/installation).

Your looks fine, although looks like you were using the Fenix A320 rather than the PMDG 777 so I couldn;t check if that thread was started/terminated correctly. John

Sounds like your WASM module is crashing - please see the following FAQ entry:

Looks likes you attached that log when FSUIPC7 was running, and it ends after less than 0.5 seconds and doesn't really show much...very strange - did FSUIPC7 crash?

Sorry, I should not have suggested this as the SDK for the 777 is different from that of the 737. The 737 presets use the custom control (via the Rotor Brake control): For the 777, the custom control is the following: To use custom controls in PMDG aircraft, see the following FAQ entries: To use the custom control in a preset, you have to use the first method (i.e. via the Rotor Brake Control). Create two additional presets: My_PMDG_B737_EFIS_CPT_BARO Dec#19108 (>K:ROTOR_BRAKE) My_PMDG_B737_EFIS_CPT_BARO Inc#19107 (>K:ROTOR_BRAKE) My_PMDG_B737_EFIS_FO_BARO Dec#25808 (>K:ROTOR_BRAKE) My_PMDG_B737_EFIS_FO_BARO Inc#25807 (>K:ROTOR_BRAKE) Sorry, but if you ask for help with something that is clearly documented, you will be referred to the documentation. Documentation is provided so that I do not have to answer the same questions repeatedly. If I do not understand what you are asking, I will of course need clarification and further information - I am not a mind reader...And I support FSUIPC7 and can show/help you how to use this - I do NOT support MSFS, PMDG aircraft or any other specific aircraft, although I do help out with assignments when I can...and if I have the aircraft, but this is not something that is included when you buy FSUIPC. Things ARE complicated with MSFS - there are so many different ways to assign, and every aircraft is different. I just supply the tools to help you with this. You need to learn how to use them.

The view controls have not been working since MSFS was released - from the README.,txt file: You can also control use using the camera presets (under MobiFlight -> All vendors -> All Aircraft -> Camera). Or you can set the simvars CAMERA STATE, CAMERA SUBSTATE, CAMERA VIEW TYPE AND INDEX:0 & CAMERA VIEW TYPE AND INDEX:1 individually via offsets 0x026D, 0x026E, 0x026F & 0x0270. John

You use the exe I provided to replace the current one in your FSUIPC7 installation folder - iy will use the same installed WASM as the previous release (i.e. no WASM update). Ok, good to know, thanks - probably due to the PMDG 777 thread now running. Could you please show me your FSUIPC7.log file from this version, on the client machine, so that I can check a few things. You should raise a support ticket for this. Also ask if lvar access when running across a network can be added as this should be possible and relatively straightforward, as the .Net dll that SLC uses for this already allows for this. Regards, John

That is everything available from the PMDG 777 SDK. If there are no specific offsets for throttle or auto-throttle, maybe the 777 is using the provided simvars in which case you can use the standard/general offsets for this. Otherwise look at the available lvars, which can be added to spare/free FSUIPC offsets if required (for both read and write - PMDG offsets are read-only). I can see these lvars that may be of use: Throttle1_Pos Throttle2_Pos XMLVAR_LeverThrottleHidden1 XMLVAR_LeverThrottleHidden2 MCPAutothrottleSwitchOnLeft MCPAutothrottleSwitchOnRight MCPAutothrottleSwitchOffLeft MCPAutothrottleSwitchOffRight There are no "Input Events" available for the PMDG 777. There may be some H-vars (HTML variables), but you would need to inspect the throttle behavior to discover these (see https://www.badcasserole.com/uncovering-input-events-using-the-msfs2020-model-behavior-dialog/). But Hvars don't hold values and are only for controlling HTML elements in the UI, so most probably not relevant. If none of this is sufficient for your needs, you can ask PMDG about this. John

I have corrected for this in the attached version, 7.4.17b, if you could try it. Please show mr your FSUIPC7.log file from the client PC after using - and please exit FSUIPC7 before attaching files. John FSUIPC7.exe

I have discussed this with Steve, the SLC developer, and it looks like there are currently restrictions when using SLC on a remote/client PC: SLC will need an update to handle lvars on a remote machine. Ok. Looking at your log file, there are a few issues I need to fix when running FSUIPC7 on a client machine: - I need to update the PMDG 777 thread to be able to use the remote connection - WASM / WAPI facilities are disabled as no WASM installed - the WASM is on the server machine and these facilities should be available (this was previously working, but I think a recent change in initialization order has broken this) I will look into these issues, but I'm afraid that this will not fix your issues with SLC. John

Ok - best to read the section Multiple Joysticks for Multiple Pilots on page 45 of the Advanced User guide.

I think this maybe the issue...Are you also running FSUIPC7 or WideClient on the remote machine as well, or just SLC? If running FSUIPC7, have you configured this for remote access on both the [General] and [WAPI] sections (as explained in the appendix on setting-up FSUIPC7 for remote access)?

Note that another user posted a similar issue a couple of months ago: There was no resolution to the issue though as the OP didn't respond to my last post.

@lamikela1 You posted this in a very old topic and in the main support forum - I have moved your post to the specific sub-forum for FSUIPC7. That is incorrect as you have duplicate index numbers, so only one will be used. All index numbers MUST be unique, so try: John

I have no idea as I don't have SLC and know nothing about this.... What does this mean? There is a known issue with the WASM in that it can crash when using complex aircraft and complex add-on scenery. There is a FAQ entry on this with a fix - see If that is not your issue, please provide a more detailed explanation of what the problem is, and please show me/attach your FSUIPC7.log and FSUIPC7.ini files, attached when FSUIPC7 is NOT running, and also your FSUIPC_WASM.log file (see the Advanced User guide if you do not know where this is located) attached when MSFS is NOT running and after a session where you experienced your issue. John

Many MSFS aircraft continually emit some events, and these events are different for each aircraft. You can stop such events being logged by using the DontLogThese ini parameter. Ok. The 4th registry entry isn't causing any issues so you can ignore this. This is something that the MSFS steam edition seems to create on start-up. If you exit FSUIPC7 and restart it once MSFS is running, you should not see this device. What that ini parameter does is to ignore this device when detected, so it shouldn't cause issues. I also need to see your FSUIPC7.ini as this has also been modified...you now seem to be using a profile called 'Fenix A320 - Scoot (2018) 8K' which wasn't present in the ini files you previously attached... Did the 'safety no smoking' presets work: ? Do other presets work after you have determined that the seat-belt preset doesn't? If not, you may be experiencing a WASM crash. Please see the following FAQ entry on how to determine if the WASM has crashed and if so how to prevent this: If that is not the issue, then I will need to investigate further, but I can't see how this can have anything to do with the use of the IgnoreDevice ini parameter The seat belt presets you are using just change the value of the lvar L:S_OH_SIGNS between 1 (on) and 0 (off). When you execute the preset, does the lvar value change (you can list the values using Add-ons->WASM0>List Lvars)? If so, then the preset is working as expected. If not, can you manually change the value of this preset using the Add-ons->WASM0>Set Lvar menu item and does that have the desired effect? For any future logs, please activate logging for Buttons & Switches, Events, Extras and WAPI->Debug level logging. No logging for Input Events necessary. You can also ignore those other events by adding the following to your Fenix [Profile.xxx] section (where xxx is the profile name): DontLogThese=66068,65957,66519 Probably also a good idea to set Debug level logging in the WASM (via the FSUIPC_WASM.ini file) - see the Advanced User guide on how to do this / where that file is located. John

No need to see the log file as you have determined that the WASM crashed - just try with the updated parameters.

They are in the Offset Mapping for PMDG 777 document which should be in your FSUIPC7 documents folder, and is attached below. John Offset Mapping for PMDG 777.pdf

You need the IgnoreDevice ini parameter, so please leave that, If some of your buttons are not working, please generate a log file (with logging for Buttons & Keys as well as Events activated) and show me/attach that, together with your FSUIPC7.ini and FSUIPC7.JoyScan.csv files and a brief description of what button didn't work. Also, please exit FSUIPC7 before attaching files. How many 'RIGHT VPC MongoosT-50CM3' devices do you actually have - 3 or 4? Only 3 are detected in HID scanning but there are 4 registry entries - one may need to be removed.,

For all issues with FSUIPC7, please use the specific sub-forum for FSUIPC7 - you posted in the main support forum. I have moved your post. You do NOT need to run as admin. Click on what exe? The installer or FSUIPC7? Also, clicking just selects - you normally need to double-click to run... There is certainly nothing wrong with the zip file and its contents are correct. Try downloading again. And check any anti-virus software you have running as that maybe interfering. If so, disable (or add an exception) while installing.

The events.txt file (not eventing.txt) is installed in your FSUIPC7 installation folder. If you cannot see it, you probably have windows explorer set to hide the extensions of known file types. If only presets for the A320 (which one?) are there, then you are either looking at the wrong file or you are using a different file to the one installed by the FSUIPC7 installer. I don't understand why you are having such difficulties, Have you read the section 'MobiFlight Presets and the events.txt file' in the Advanced user guide? If not, start there.... John