John Dowson

Yes, they should. Not sure what is causing this - can you check the Power Management settings on your usb hubs (using Device Manager) and make sure that Allow the computer to turn off this device is unchecked. This has been reported previously for FSUIPC7, and I added an extra ini paramater which when set will automatically perform an axis scan when a simconnect connection is established. I can look into adding this ini parameter to FSUIPC6 to see if that helps, but this will be sometime next week. John

You need to multiply by -1, so it would be: BSBonanzaMixtureAxis#-100 $Param 16384 - * 32768 / (>L:BKSQ_MixtureLeverPosition_1) John

No - FSUIPC7 is for MSFS2020 only. There are other versions for FSX (FSUIPC4) and P3Dv4 & 5 (FSUIPC6). John

If the response problem is with the Oi4FS/OC devices/driver, then I think that they should be the first point of contact for this issue - not having or even knowing anything about this software, I cannot really comment on this. And if there is no issue with FSUIPC7 itself, I cannot investigae/look into this issue. John

? Sorry, but it is not clear to me what your issue is with this description - can you please elaborate. For example, I do not know what "tap at the bottom" means. It would also help if you could attach your FSUIPC5/6.ini and FSUI{C5/6.log files, the latter generated with Axis controls logging enabled (if your issue is with axes assignments) and when you experience (and rectify) the issue. John

This would indicate an issue with the external apps, and you need to contact the developers of these apps. Your logs show no issues in FSUIPC, and you are not using the FSUIPC WASM module. I would suggest that you contact the developers of SimBitWorld about this issue, I cannot support 3rd-partt FSUIPC applications, If there is an issue in the SDK (which I doubt - this has been stable for many years), then they should contact me for support on any FSUIPC SDK issues. Sorry I cannot be of any more help. Your log files show no issues with FSUIPC. John

Thanks - I had forgotten about that! John

Wasn't my previous message clear on what to do: ? When I say "try with the default values", I just mean with these not specified in your ini file, as anything there will take presidence. No point in looking at your logs until you try this. John

Ok, but if that is controlling the display, then you need to see if that can be configured to show 3dps. Ok, but it can be quire complex, especially for non-programmers, to control the GF display via lua. There is an example script provided (in the lua examples zip in your FSUIPC documents folder), and there are probably other posts on using this library if you search the FSUIPC forums. u suspect that you don't need to the GFDisplay.exe. And you could also try asking in the Go Flight support forums, presuming they supply the GFDisplay.exe. Cheers, John

7.3.18 has been released - can you please update to the released version. I see you are using a VRI device. Your log shows FSUIPC is hanging when trying to close the DevCom threads for this device: However, the threads look like they have been forcibly terminated, so I am not sure why it isn't exiting correctly. Can you remove the following entries from the [General] section in your FSUIPC7.ini file (if they exist) and try with the default values (10ms) for these: ComReadLoopTime, ComWriteLoopTime. If you get the same issue, try reverting to the previous values by setting: ComReadLoopTime=20 ComWriteLoopTime=20 John

I have tested here now and haven't found any issues, Are you still experiencing these problems?

How are you driving the display? As far as I understand, you should be able to display any text up to the length the display can handle - usually 5 characters or digits. Take a look at the lua gfd library for handling GF displays in FSUIPC/lua. As I don't have any GF display devices, it is difficult for me to advise any further. John

Many people use this throttle with FSUIPC. Just download it (from FSUIPC7 v7.3.18) and try it - an trial license is available here: See the User manual and how to assign and calibrate, and make sure you have removed any assignments in MSFS - best to create a new empty profile for the device in MSFS, although you can gave some assignments in MSFS and others in FSUIPC if you like. If you have any issues, first check/search this forum for any possible solutions (most questions have been asked before!), but if you can't find anything relevant then post again and I can help. John

I don't think this is the case....from the PFC.DLL User guide: This seems to imply that 9600 is the rate that is needed. John

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.