John Dowson

This is usually because you are using an aircraft variant (e.g. different livery) that is not using a profile that you created for a different version of that aircraft. This is because when you add/create a profile for an aircraft, the full aircraft title is used, and as each variant has a different title, if you use a different variant then it will not match the profile. To get around this, there are two options: 1. use substring matching for profiles. This is activated by default, but to use this you need to change the aircraft name (in the [Profile.xxx] sections of your FSUIPC7.ini) to a substring that matches all aircraft variants. If you attach your FSUIPC7.ini I can take a look and recommend the changes you should make. 2. Use the ini paramater UseAirLocForProfiles (see the Advanced User guide for details). If you set this to Yes, you would have to re-attach your aircraft to the profiles they use, but you should only need to do this once for each profile/aircraft (and also a goof idea to remove the old aircraft names/titles from the profile sections, but not strictly necessary). John

Yes - and remember that the preset file (events.txt) that comes with FSUIPC7 is generated at the time of release, and is out-of-date (compared to the presets on the MF HubHop site) shortly after release, as the site is updated frequently. You can always download and install the latest events.txt file from the MF HubHop site if there are presets available there not available in FSUIPC7. I also recommend that you submit any new presets you discover to that site to share them with the community. Thanks @Moderate Chop! John

No puedo ayudarte con LINDA; Prueba el foro de soporte de LINDA: https://www.avsim.com/forums/forum/429-linda-support/?ct=1659519971 John

It should be...what ATC software are you using? What have you tried? Try searching this forum for PTT and you will find many previous requests like this... John

Take a look at the offset documentation - this tells you what each offset area is used for. If you want to use offsets for your own purpose, then you should choose an offset in an area that is designated as free for general use. Of course - just change the script. However, it is fine to used offsets reserved for another application if you are not using that application, so you can just leave it as it is. Lvar values are not held in offsets, but you can add them to an offset (one that is free for general use!) using lua if you so wish. Yo see what lvats are available, you can use the FSUIPC-added control List local panel variables. Just assign a button or keypress to that control and when you press the assigned button/key the available lvars will be listed in the FSUIPC6.log file. I can't help with Linda - try the Linda support forum: https://www.avsim.com/forums/forum/429-linda-support/?ct=1659519971 They look to be messages generated from the state of simvars (or possible lvars). For example, Parking Brakes On will be displayed when the BRAKE PARKING POSITION simvar, held in offset 0x0BC8, has a value of 32767. If the value is 0, it would display Parking Brakes Off. I doubt that there is anything that actually holds the messages themselves. John

I cannot help with this as I don't have the MD-82. Ask on the MobiFlight discord server, or on the aircraft support forum. Maybe some other FSUIPC users who have this aircraft can help....maybe @Moderate Chop? The log file shouldn't be that big...make sure that you only have logging activated for what you are investigating or are having issues with (e.g. Events and buttons & Keys only). But I don't need to see this anymore as you say the presets for the MD-82 are now working for you. John

The license has been updated.

So the selection has changed to the views. How do you select this normally? i.e. how do you select what the increase is applying to (COM frequency - which COM, active or standby, AP altitude/speed/height, etc)? I am not familiar with this control or on how to change/select to what it is applied to. The standard method is to assign directly to the inc/dec control of the system/systems that you want to control. You then add an offset condition on the selection switch (which would have a button for each selection position) so that the correct control is sent depending upon the position of the selection switch. John

zip/compress it.

I don't see any assignments to presets in your MD82 profile, although you have some for the Fenix A320. Try adding some assignments to presets and test them. Start with the attached FSUIPC7.ini - I have added a [WAPI] section and enabled Debug level logging, and adjusted the names for your aircraft profiles so that you don't need to add each variant that you use. Make sure FSUIPC7 isn't running when you copy the attachment to your FSUIPC7 installation folder. Any issues, re-attach your updated FSUIPC7.ini as well as your FSUIPC7.log file. FSUIPC7.ini John

No - you can assign to any event, with the parameter of the Rotor Brake control indicating the button/switch as well as the mouse action, as indicated in these instructions. Note that these days it is easier to use the presets for the PMDG 737. These come with FSUIPC7, but you can use the MobiFlight HubHob site to search and see what is available for this aircraft: https://hubhop.mobiflight.com/presets/ John

Yes, a new license is required for FSUIPC7. As you have purchased previous versions, you will automatically get a 10euro discount on checkout. Probably not.... The PMDG 737 for MFS is quite different to the P3D version. The custom controls for this aircraft have changed to use the Rotor Brake control (with the parameter indicating the control number as well as the mouse action). See the following FAQ entry on how to use custom controls for the PMDG 737 for MSFS: Also, if you use the PMDG offset area in FSUIPC, this is not available in the current release but will be available in the next release, and there is a beta version available with these offsets available in the following topic: Note also that the offset allocation has changed - there is also a document available with the beta release that gives the offset information available for the MSFS PMDG 737. John

The add-on.xml file is created in a fixed location, regardless of where you select to install FSUIPC6. It is always created under your windows Documents folder, under Documents\Prepar3D v5 Add-ons\FSUIPC6. Then this sounds like either Windows or maybe some other anti-virus software is preventing the installer from creating the necessary folder and/or file. You can either stick to the DLL.xml method, or try manually creating the add-in.xml file in the correct location (and removing the DLL.xml file or the FSUIPC entry in that file). The file contents are as follows (change the Path to point to your installation folder): <?xml version="1.0" encoding="UTF-8" standalone="yes"?> <SimBase.Document Type="AddOnXml" version="4.0" id="add-on"> <AddOn.Name>FSUIPC6</AddOn.Name> <AddOn.Description>Flight Simulator Universal Inter-Process Communication version 6</AddOn.Description> <AddOn.Component> <Category>DLL</Category> <Path>D:\Prepar3D v5 Add-ons\FSUIPC6\FSUIPC6.dll</Path> </AddOn.Component> </SimBase.Document> Then no license file (FSUIPC6.key) was found in your installation folder. Re-run the installer and make sure that you register at the end of the installation process. Or, if you have previously registered, you cam copy/move your FSUIPC6.key file to your new installation folder. John P.S. If using OneDrive, that could be interfering. Try disabling that while you install...

The latest and only supported version of FSUIPC4 is v4.977 - please update. What changed? If FSUIPC4 is sending a keystroke, you need to check the key assignments in FSX-SE to see what that keystroke is assigned to - maybe that has changed? I am not familiar with this control, but looking at the documentation for this it says: Used in conjunction with "selected" parameters to increase their value (e.g., radio frequency) So it looks like you need to use something else to select the parameter that you want to increase before using this control. John

As @Moderate Chophas indicated these lvars and presets are working, there must be something else going on. Check that you are using the latest version of FSUIPC7, which is v7.3.7 - if not update first. Also check the WASM module is enabled. If that is the case and it still isn't working, show me your FSUIPC7.log and FSUIPC7.ini files. preferably with Debug level logging activated on the WAPI, as well as Event and Button & Key logging activated. John

This shouldn't be an issue - there should be no problem mixing assignments between FSUIPC and MSFS or other software. But why don't you just try it - there is a trial license available in a post at the top of this sub-forum. It has currently expired, but I will generate a new one later today. John

No idea - hard to tell with so little information. Try activating logging for Buttons & Keys as well as Events, and check the preset is being sent when you press the button. You can also try executing the calculator code for the preset using the Add-ons->WASM->Execute Calculator Code... menu item to see if the preset is working. If it is, then there is something wrong somewhere - you can attach your log and ini files and I will take a look. If the calculator code for the preset isn't working, I can't help with that - try the MobiFlight discord server. John

Try reading the manuals...especially the section on the WASM in the Advanced User guide. Your FSUIPC7.log (and FSUIPC7.ini) file is in your FSUIPC7 installation folder. You should review the installation nd registration guide for an overview of what is installed and where. John

Ok - so that shows that the lvar L:SWS_ENGINE_Switch_Ignition_1 is being held in offset 0x66C6, and you have a button assigned to set the lvar value to 1 on press and 0 on release (as I suspected). Your macro file isn't being used. In fact, it can't be - as well as the contents being invalid, the filename contains more than 16 characters. From the Advanced User Guide, section on macro files: But if this is working, then its not an issue. Just delete that duff macro file. John

As I said: Remember to also set Debug level logging in the WAPI (instructions above). John

Hi Matt, In the latest version, the WASM should be enabled by default. This is usually due to timing, i.e. the information on lvars has not yet been received by FSUIPC. This occurs LvarScanDelay (a WASM ini parameter) seconds after the aircraft is loaded, and defaults to 5 seconds but should be increased (to 45-60 seconds) if using complex aircraft. No point doing this. Better to disconnect from MSFS and then re-connect. But, you really shouldn't need to do this. There is a possible problem that can occur if/when using multiple WAPI/WASM clients. This has been fixed in the latest beta release, so if your users are using multiple WASM clients then they should update to this version, available here: There really is no point re-installing FSUIPC7 for this issue. If this problem persists, then you should activate Debug level logging in the WAPI, by adding the following to the [WAPI] section of the FSUIPC7.ini file: LogLevel=Debug This should then show the data being received in the FSUIPC7.log file, and the WASM menu items should be enabled once this/these lines are logged: If the problem persists, show me the log file and I can take a look. You can also activate Debug level logging in the WASM (see the Advanced User guide) and attach both the FSUIPC7.log and FSUIPC_WASM.log files. John

👍😎

You need to opt-out of the beta program in steam (you must have opted-in, no?). To do this: You can opt out of the beta at any time by doing the following: • Open Steam • Open the Library tab • Right click on Microsoft Flight Simulator X: Steam Edition [g2610build] • Select Properties from the menu • Select the Beta tab at the top • From the drop down menu, select NONE - Opt out of all beta programs • FSX: Steam Edition will now update back to the LIVE version of the software • In the Steam Library, your game will be listed as Microsoft Flight Simulator X: Steam Edition No. FSUIPC4 was closed for new development many years ago. We provide a version that works with the beta, but with reduced functionality (e.g. no mouse macros). There will be no further updates. There is really no need to use this beta - this is the description: i.e. it was only released to allow more data to be collected for the development of MSFS2020. John

Your log only shows two offset control assignments on a button press and a release (same button), most probably setting the value of the lvar L:SWS_ENGINE_Switch_Ignition_1 (to 1 then 0), although I can't tell as I haven't seen your latest ini file: I see no use of that macro file. John

You are using the latest FSX-SE beta. I am surprised that FSUIPC4 is working at all! Please see that post I previously referenced as you are using the latest beta. Mouse macros will not work in this version. If you want to use Mouse macros, you should opt-out of the beta and revert to the pre-beta release (62615)))). John