John Dowson

If its working except for the visuals, it may use a hvar (html variable type) - you would need to look at the xml code to see how it is defined. Its not possible to scan for hvars I'm afraid. Presume this aircraft is quite new as it doesn't appear in the MF HubHop preset list yet. Maybe worth checking and/or asking about this on the MF discord server if you can't find anything.

FYI, I have release FSUIPC 7.3.18 and WASM 1.0.2 and WAPI 1.0.2. No API changes in the WAPI. John

FYI, 7.3.18 just released - available from the usual locations. Finishing for the evening now (dogs need walking!). Any issues, I can help tomorrow. John

You shouldn't need to do this either...you either installed into a different folder or must have removed your FSUIPC7.key file manually. I hope you have not lost your settings, stored in your FSUIPC7.ini file. If you have changed installation locations, you can copy this file from its old location to the new one and everything should be restored. Btw, I have just released 7.3.18. You should update to this version now. John

No - don't use that side! Assign to the preset on the left, as you would to any other axis control.

Top right, below This side to send button controls. This was added to enable presets to be sent presets for button controls, but presets can also be assigned to an axis when this is checked. If you can't see this checkbox, then your version of FSUIPC is out-of-date. The latest version is 7.3.17, and I will be releasing 7.3.18 later today. I recommend that you update to this version once released.

Options -> AutoSave... An update does not change any settings - something else must be going on. John

Many complex aircraft, such as the Fenix A320, implement their own systems and many of the standard controls don't work. You need to use lvars or hvars, or a combination of different variable types. The easiest way to do this is to use presets - and there are many available (>100) for this aircraft. You can use the MF HubHop site to search for a preset - see https://hubhop.mobiflight.com/presets/. To assign to a preset, check the Select for Preset checkbox in the assignment dialog. For example, for the strobe lights, you have the following presets available: FNX320_LIGHT_STROBE_AUTO FNX320_LIGHT_STROBE_TOGGLE FNX320_LIGHT_STROBE_ON FNX320_LIGHT_STROBE_OFF See the WASM section in the Advanced User guide for further details on using presets. John

Do you notice this regardless of the aircraft being used, or only for specific aircraft (e.g. for complex aircraft/airliners or 3rd-party add-ons)? I have done some tests with the current MSFS release 1.30.13.0 and the latest FSUIPC7 beta with various aircraft (including the PMDG 737) and see no noticeable drop in FPS (with WASM also installed and running). If there is a performance issue introduced in the SU12 beta then this must be addressed by MSFS/Asobo - I don't see what I can do about it here. I hope they fix this in another beta release, or before its released officially, otherwise I will raise this with Asobo once released. If there is an updated SDK for SU12, I will rebuild FSUIPC7 and update for this once released - but I doubt this has anything to do with any performance issues.

But this is the bottom of the axis, i,.e., no axis values below this. This is your calibration (from page 3 of the axis calibration tab - take a look there): So you have your axis range from -16380 to -512 calibrated for reversers, -512 to + 512 for idle, and 512 to 16380 for forward thrust. If you are not using reversers on an axis, you need to check the No Reverse Zone checkbox (top-left of the calibration tab in page 3) and calibrate for this. The No Reverse Zone applies to the axis range, not the button. Why don't you just try this as advised?

There is an easier way... You can create a preset for this and assign to that - add the following to a file called myevents.txt in your FSUIPC7 installation folder (create this if it doesn't exist): BSBonanzaMixtureAxis#100 $Param 16384 + * 32768 / (>L:BKSQ_MixtureLeverPosition_1) Then in the axis assignment dialog, check the Select for Preset checkbox and then assign to the preset BSBonanzaMixtureAxis. Note that preset calculator code assumes your raw axis values go from -16384 to +16384 - you can adjust if that is not the case.

Yes, but you need to use a lua script. You need to assign the axis to Send to FSUIPC Offset with Offset Dword Set and use an offset free for general use (e.g. 0xA000). In your lua script, which should be auto-ran (preferably in a profile [Auto] section), you can use the event.offset function which will set a handling function to be called when you move the axis lever, and in the handling function you can calibrate the value (i.e. convert the axis input value, passed as a parameter to the function) to a percentage value, and then set that value in the lvar using the ipc.writeLvar function. It should be straightforward but if you are new to lua and have issues then I can help you with this. See the FSUIPC Lua Library document in how to use these lua functions, and there are plenty of examples out there,

Pete has retired, although he does respond in the forums occasionally. I am sorry but there is no chance of this happening - as it says on the download page for this: The source for this isn't even available for anyone to update. John

I doubt it very much... I suspect so... This surprises me a lot... It would help if you gave an example. All PMDG 737 specific offsets are documented in the Offset Mapping for PMDG document, and all general offsets are documented in the FSUIPC Offset Status document. There just aren't and can't be any other offsets. The only undocumented offsets as such, are those that are used internally or have been allocated to other people or programs. They are usually only documented as "Reserved" or something similar, with the actual purpose defined by the person or aircraft/program they are reserved for (and usually free for general use if not using the program or aircraft they are reserved for). John

This sounds strange - what do you see in the In and Out boxes in FSUIPC's axis Assignment window? Maybe you need to calibrate the axis in windows calibration first? If you want to use scaling to do this, then try with 3=AV,256,F,65919,0,0,0,*-2,-16384 (or maybe *-2,+16384) John

WideClient is the same for P3D and MSFS, and the WideServer component in FSUIPC6 and FSUIPC7 is also the same...are they running on the same PCs? It is also 3 months since you last posted - was it working ok during this period? Can you also please check in the Windows Event Viewer to see if there are any com-related events reported there, and if so show them to me. You also didn't post your WideClient.ini - as I said, I need to see all 4 files from the same session to make any sense of any issues with WideClient connections. Maybe try using different ports to see if that makes a difference, although I doubt it. I will run some tests with WideClient and MSFS here later in the week and let you know if I find anything. What do you use WideClient for on the slave PC? You could possibly try using FSUIPC7 in the client PC instead - see Appendix 4 of the Advanced User manual on how to do this. This doesn't provided the same functionality as WideClient, but may be an alternative option, depending on your use. John

It is not related to your button config. Now you have multiple assignments to throttle 1 & 2: This can be problematic - only have one assignment to each throttle. Assign either to Throttle1 & 2 using Direct to FSUIPC calibration, or to Axis Throttle1/2 set with Send to FS as normal axis. But your issue is because you have calibrated with a reverse zone - try calibrating with no reverse zone if using a button for reverse. Also, can you update to the latest beta (I will release this within the next day or two) as this will help with some other issues I see in your log, available here: John

It probably isn't - I am just used yo seeing two com ports (one virtual) in the VRInsight section, but I guess you aren't using SerialFP2 so this is ok. They are just standard events, nothing to worry about. The event logs don't tell me much unfortunately, just that FSUIPC has hanged. If you don't get the issue when not using LINDA, then the problem is either in LINDA or in FSUIPC's lua script handling. First, continue without LINDA for a while to confirm this. If this is due to LINDA, you are probably better off asking about this on the LINDA support forum. But, before you do this, could you activate Lua Plugins logging and turn off logging for Events and IPC Writes, and show me a log file generated with this logging activated when it hangs,

Compress/zip them. Please try the latest beta release first, link posted in my previous comment.

I need see your FSUIPC7.log file, not the installation log file. Also, please check the windows Event Viewer and see if there are any faults or exceptions reported there, and if so please show them to me. When did this start then? Looking at your ini, it seems that you are only using FSUIPC for LINDA and a VRInsight device, which entry also looks incorrect. Try without LINDA and maybe remove the [VRInsight] section from your FSUIPC7.ini file as well. Also check that you are using the latest version of the PMDG 737

I cannot help with issues with SU12 beta as I do not yet have this installed. Make sure that you are using the latest release (7.3.17), or the latest beta available here: If you get the same issue, please show me your FSUIPC7.log (with lua debug logging activated) and FSUIPC7.ini files, as well as your RAAS lua script. Log and ini files are located in your FSUIPC7 installation folder. If you don't know where that is, use the File->Open Installation folder option from the FSUIPC7 main menu. John

I have still not had time to re-organise my hard disks to install the SU12 beta - I will do this when I get time. I will check the performance in the released version. Maybe try with the WASM disabled to see if this is a WASM or FSUIPC issue. Temporarily remove the WASM from your community folder and then see that sort of FPS drop you see when FSUIPC7 is running.

Yes, strange. But I cannot help if you are not providing the files I requested.

If everything is running at the same privilege level, then you need to contact Pegasus support for this issue, I cannot support third party products. As I have said many times now, I have nothing further to say on this topic. I will leave this topic open so that ither users can post any solutions found for this, but I will not be commenting again on this topic. John

You will not see the same values as written, as the offset status document says: However, you should see the same values in those offsets if writing the same value. Can you please add monitoring to those offsets (in FSUIPC), activate lua debug logging and generate an FSUIPC6.log file showing your issue. Attach that with your lua script and your FSUIPC6.ini file and I will take a look. John