John Dowson

I don't know - do you have your assignments in FSUIPC or ProSim? You could try using FSUIPC's logging features to see if you can spot what is different in the logs when you connect the sismo modules. Or, as the problem only occurs with the sismo modules running, maybe ask on the sismo support forums about this. I have no knowledge or experience with Sismo, sorry. Maybe some other Sismo users can assist... John

Why is this a problem? If you have used this program for the PMDG 737 with FSX or P3D with FSUIPC4/5 or 6. then you should be able to update it to work with FSUIPC7 / MSFS. The specific PMDG offsets have always been read-only. The change with the PMDG 737 from the FSX/P3D versions is switching from using distinct custom controls to using the Rotor Brake control to implement custom controls. John

No. WideClient requires a connection to FSUIPC, which is only running when the FS/P3D is running. John

Really - where? Controlling anything other than pushback? Most of the ground services functions can only be controlled through the menu system or via ATC. But what service were you looking for? For which aircraft? Such things in MSFS are controlled in a very different manner from other FSs and can be very aircraft dependent. Pushback controls were previously reported as working - see For other services, if you see an MSFS control that can be used (that is not available in FSUIPC7), then you can assign a keypress to that control in MSFS, and then use that keypress in FSUIPC/lua. MSFS currently doesn't provide an API to control the ground services, apart from the standard aircraft pushback controls (which work with mixed results). Also no SODE for MSFS for these reasons. John

This sounds like you have installed FSUIPC7 into a windows-protected folder, such as under Documents or Program Files. If that is the case, re-run the installer and select a different non windows-protected installation folder. Did you have an aircraft loaded and ready-to-fly? The WideServer interface is only started once ready-to-fly. However, when FSUIPC7 is started with MSFS (or while MSFS is loading), it receives many different events, some indicating 'ready-to-fly', and so the WideServer interface is started prematurely (i.e. when MSFS is still loading or in the menu system). This is not an issue (and something I can't do anything about),it is on;y a problem if the WideServer interface isn't running once you have an aircraft loaded and ready-to-fly. So, if you start FSUIPC7 when MSFS is already running and in the menu system, the WideServer interface may not be started, but will be enabled. The interface will start once you have an aircraft loaded and are ready-to-fly. For any further issues or questions, please attach your FSUIPC7.ini and FSUIPC7.log files (and maybe your InstallFSUIPC7.log file as well). John

Yes - the 'D' was a typo. There should also be a .log file in the same folder - if you cannot see it, change your Explorer settings to show the extensions of known file types. Your ini file shows that you only have one lua file: There is no master_caut.lua file - you have called it master_caut.lua.txt (as the file you attached in your last comment). So your issue is that you are using the wrong file type, most probably due to your Explorer settings - change those so that you can see the actual extension type. John

Hi @Solito I have just been looking at this, and get the same as you - error 740 when trying to start TrackIR5 from the windows. However, I can start it ok when using the following: i.e. When running using a command shell. However, when doing this, TrackIR5 will not exit with FSUIPC/MSFS, even if you use the CLOSE or KILL options, as these affect the command shell and not the TrackIR5 instance. I have also investigated this before - please see John

What is there to respond to? I thought it was now working for you and the issue was that you did not enable the WAPI, which you have now done. When you first enable, you may need to disconnect and reconnect FSUIPC7 from MSFS (or restart FSUIPC7 which has the same affect). If you are still having issues, please show me your FSUIPC7.log and FSUIPC7.ino files again.

Paul Henty has posted a guide on how to determine the Rotor Brake parameter to use for the PMDG 737 for MSFS in the following FAQ entry: John

Paul Henty has posted a guide on how to determine the Rotor Brake parameter to use for the PMDG 737 for MSFS in the following FAQ entry: John

Have you tried? Your log shows you pressed a button (twice) on your yoke, but this is assigned to a 'C' keypress: The 'O' keypress (send) assignment is to your TCA Q-Eng 1&2 device: So try re-assigning your yoke button to the correct keypress. Note that the keypress will be sent to the FS - it will only be picked-up by PF3-ATC if that picks up keys from the sim, or it is registered as a hot-key by the application.

Using Add-ons->WASM->Enable - you did say 'i did all off that' when I first asked about this... You ini shows that you have not enabled the WASM - please do that. I suggest you consult the documentation before requesting support.

It looks like you haven't Enabled the WASM.... Have you done that? If not, do that. Otherwise, please show me your FSUIPC7.ini file. If using the PMDG 737, you may be interested in the latest beta version where the additional PMDG offsets are populated, available here: John

They are, using the Rotor Brake control. Maybe easier to use the available Presets - you can easily search for the available input presets at https://hubhop.mobiflight.com/presets// Attached is also a spreadsheet containing available rotor brake parameters that is available over on the PMDG support forums. I suspect this matches the preset list, although the latter would be more up-to-date. John B737_Scripts_ROTORBRAKE.zip

If you are starting the script when entering (or leaving) an axis range, it will only be sent once, assuming its not on repeat. If its being sent a second time then the range is left and then entered again. Logging the axis controls would show you this. Restarting a script would automatically kill the first thread. It is strange thar the log lines aren't showing - have you tried running with LuaDebug? You could also try increasing the LuaRerunDelay parameter - see the Advanced User guide for details.

I don't see how FSUIPC can be involved if it isn't doing anything. You could try activating logging for Events initially, and maybe also Axis Controls, and see if the log reveals anything. If you do this with the logging console open (Log->Open Console), you can see what events are logged in real-time. You can attach the log file here (zip it if its large), together with your FSUIPC7.ini file and I can take a look - but I really can't see how this could be due to FSUIPC. John

It will be in your FSUIPC7 installation folder. You can use the File->Open Installation Folder... menu option in FSUIPC7 if you don't know where that is.

Please show me your FSUIPC7.log file.

Looking at the MobiFlight preset list, there are the following input presets: PMDG B737 Eng : 46301 (>K:ROTOR_BRAKE) PMDG B737 Sys : 46201 (>K:ROTOR_BRAKE) as well as the following output ones: PMDG B737 Eng : (L:switch_435_73X, number) 0 > So you should be able to use the Rotor Brake control with parameters 46301 and 4620, or assign to the presets directly john

What do you mean by 'the wasm files'? If you mean the Add-ons->WASM menu items, then these are only available once an aircraft is loaded and ready-to-fly. You also have to Enable first. No. You don't need the MSFS SDK to run/use programs that are built with it. John

The PMDG 737 for MSFS uses the rotor brake control with the parameter indicating the function. I believe there is a list of parameter/function for the Rotor Brake control over on the PMDG forums. Unfortunately I cannot access the forums at the moment when signed in, and cannot download that file if not signed-in. There will be an update to this aircraft expected in the next 10-14 days or so when the SDK will also be published. Maybe if you create a specific topic for your issue, other PMDG/VRInsight users may be able to help... John

I do not support the MSFS beta releases. John

Then you have posted in the wrong forum - there is a specific sub-forum for FSUIPC7 / MSFS - I will move your post to that forum. And you must be using the 737-700, which is the PMDG 737 for MSFS. And what I said in my previous post does not apply - the MSFS version does use the Rotor Brake control, unlike previous PMDG airliners. But it IS in the list. It cannot not be there....check the document Controls List for MSFS Build 999.txt (in your FSUIPC7 Documents folder). You should see it listed there, and it will also be in the controls drop-down menus. You may also be interested in the latest beta which supports additional PMDG offsets for the 737 - see John

Well, the Rotor Brake control/event is certainly there, so I suggest you look again... However, you do not say what FS or version of FSUIPC you are using - this is always helpful... I presume you are not using FSUIPC7/MSFS (as there is no PMDG 737NG3 for this FS!). The Rotor Brake control is used by the PMDG 737-700 for MSFS, but the PMDG 737NG3 (for FSX and P3D) do not use the rotor brake control, they use custom controls. To use these, please see the following FAQ entry: And if you look in the PMDG_NG3_SDK.h header file, you will see these events defined: #define EVT_MPM_MFD_SYS_BUTTON (THIRD_PARTY_EVENT_ID_MIN + 462) #define EVT_MPM_MFD_ENG_BUTTON (THIRD_PARTY_EVENT_ID_MIN + 463) That FAQ entry will show you how to use those events/custom controls. John

Ok, but this does seems strange. I do have TrackIR5 on my flight system, although I haven't used it for quite a while, and not with MSFS/FSUIPC7. I will take a look at some point to see if I can get FSUIPC7 to auto-start this and let you know what I find. John