John Dowson

Glad you resolved your issue - strange though... did you install additional drivers or software for use with the Fenix A320? Are your Fenix A320 assignments still working ok?

I am not going to give a step-by-step guide - I provide extensive documentation so that I do not have to do this individually for every user. So, please try reading the User guide and trying for yourself. You can assign to the flaps inc/dec controls which function correctly in the Asobo A320 - just try it, it is not that difficult... John

As i don't have this aircraft I cannot investigate any further. Someone also asked about this on the Asobo forums but with no response. May be worth asking about this on the SimWorks forums/support. John

Yes. How you do this depends upon whether your rotary has one or two buttons (a fast and a slow button) in each direction. For the latter, it is just a matter of assigning to the slow/fast increments for each button. If your rotary only has one button in each direction, you can use a lua script to trigger virtual flags for fast/slow movement in each direction, and then assign the the slow/fast flag accordingly. A lua example plugin script is provided that does this - see the lua examples zip file in your FSUIPC7 installation folder. There is also a specific version of this script available (in another forum post) that is specific to the HoneyComb Bravo, which controls the trim wheel as well as the rotary in this manner. John

Ok, thanks for the update. John

Throttle controls are dependent on the aircraft that you are using. You can set up a general throttle assignment by assigning to 'send direct to FSUIPC Calibration' and selecting the Throttle control (or individual Throttle1 and Throttle2 controls) and then calibrating, but any given aircraft may need a profile-specific throttle set-up for that aircraft using the controls (or lvars) that are available for that aircraft. I suggest that you read the user guide section 'The Easy Step-by-Step Way to Calibrate Your Controls' and take it from there. If you require further assistance, please pause a separate support requests in either the main support forum or the FSUIPC7 specific sub-forum, describing the issues you have together with details of the FS version (P3D, FSX, MSFS2020) and aircraft that you are trying to configure. John

Please refer to the MF HubHob site (https://hubhop.mobiflight.com/presets/) and read the description of the presets. For example, the TBM930_BLEED_AIR_OFF preset describes your issue and a workaround: Auto and Max work the same way but by setting the lvar to different values. Once you have modified the TBM930_Interior.xml file, you can create 2 new presets (in a file called myevents.txt file) to set the lvar value and then assign to those presets. John

Hi Rick, I'm not sure about this... looking at the WideFS Technical guide, it may be possible if you switched to using an IPX/SPX connection (if that is possible), and then ensure IPX/SPX is associated to only the network card that you are using with WideClient. See the WideFS Technical guide for details. I'm afraid I'm not that network savvy (especial on windows), but I think a better solution would be to look for a windows solution that forces an application to use a specific network. Google turned up this: https://www.howtogeek.com/117890/how-to-force-an-application-to-use-a-specific-network-card/ John

👍

First, you posted in the main support forum. As your question is relayed to FSUIPC7 / MSFS, I have mived your post to the FSUIPC7 sub-forum. Please use this sub-forum for any support requests for FSUIPC7. Yes - we refer to this as compound button conditions, and is described in the Advanced User manual, starting on page 21. You can assign separate actions for key/button press and release. See the user guide - or just try it. There is a trial license available in a post at the top of this forum. John

No. That file is the interface to the WASM module and any changes would require a WASM rebuild, as well as code changes. I have only just increased the lvar limit from 2044 to 3066 lvars. This should really be more than enough and I am not planning on increasing this again - at least for the foreseeable future. John

For FSX, you were using FSUIPC4. For P3Dv5 (and P3Dv4) you will need FSUIPC6. This is a separate/distinct product and you will need to purchase a new license for FSUIPC6 (available from SimMarket). Your WideFS7 key is still valid for FSUIPC6. You will automatically get a discount on checkout if you purchased FSUIPC4 on its own, however the discount is not available on bundle purchases (i.e. if you purchased FSUIPC4 as a bundle with WideFS7). John

Done.

Please try the attached version (I gave not updated the WASM version number - I will do this when I release officially with the next FSUIPC7 release): FSUIPC7_WASM.wasmlayout.jsonmanifest.json Download and use those files to replace the ones in your ..\Community\fsuipc-lvar-module and ..\Community\fsuipc-lvar-module\modules folders. John

First, you have posted in the FSUIPC7/MSFS support forum. As you are using FSUIPC6, you should post in the main support forum. The documentation for 6.1.9 domes with the FSUIPC6 installer. The separate documentation package is out-of-date (I only update that occasionally). Please re-run the 6.1.9 installer to get the latest documentation for FSUIPC6. This functionality is for FSUIPC7 only - it is not available in FSUIPC6. That is on page 36 of the Advanced User manual - as I said, re-run the FSUIPC6 installer. No. As I said I only update this occasionally. The separate documentation package is only provided for people who want to look at the documentation without installing FSUIPC6. All current documentation for each FSUIPC version comes with the FSUIPC installer - you should not download or use the separate documentation package if using FSUIPC - just use the documentation that comes with the version toy download. John

Yes, this is definitely the case - . I will need to rebuild/update the WASM. I will post a version here for you to test when done.

I think thus was because you are a new user and your first post needed approval. You should be ok now. Note, however, this post is quite old now and many things have changed. You no longer need the lua scripts for the Alpha/Bravo for FSUIPC to recognise the buttons > 32 - FSUIPC now recognises up to 128 buttons natively (see my precious comment). John

Check your AutoSave settings (Options->AutoSave). Change the number of how many files to keep to 1 (it is probably using the default of 5). John

Ok... you could have mentioned this earlier... This is the old topic: In which my last comment was: i.e. you should have posted in that topic and we could have resolved this a lot quicker! I will PM you a new key later today or tomorrow. For the time being, you can download and use the trial license/key file, available in a sticky post at the top of this forum. John

It should be 1024. I suspect that it is a logging statement somewhere that doesn't have a buffer big enough (using sprintf rather than sprintf_s as I should...!). I will look into it and get back to you. 3066 is currently the maximum of lvars available via the WASM, as this is also restricted by the number of LVAR CDAS: #define MAX_NO_LVAR_CDAS 21 // 21 is max and allows for 3066 lvars - the max allowed for the 3 value areas (8k/8) is 3072 So you have already hit the limit. No. First, the WASM.h file is shared between the WASM and the WAPI and any changes to that file would require both the WAPI and the WASM to be recompiled. Second. as the current limit is actually defined by MAX_NO_LVAR_CDAS, this would also need increasing (you need 7 LVAR CDAs for each lvar value CDA created). MSFS seems to load/keep lvars from previously loaded aircraft, as well as from aircraft just installed in your Community folder. It is recommended to clear your Community folder of aircraft not being used (as well as anything else) before you start MSFS/ Lots of people use the MSFS Add-on Linker program (freeware) to do this.

As long as the alt key combination isn't already being used by the application as a menu short-cut, then you should be fine using the alt key as a modifier. It is the windows / win key that is problematic these days and shouldn't be used.

Ok, but maybe you could post the solution you used ai that it can help others which have this aircraft.

its John - Pete retired a few years ago... I'm not sure...I was going to suggest giving the focus to a different window other than vPilot (if it is being used as a hot-key), but that seems to be what you are doing... You could try with using the Alt modifier rather than Ctrl...Alt modifiers have a special meaning (usually keyboard shortcuts for windows' menus and menu items) and may bypass the "ding"... otherwise, you could try disabling the beep in windows - see https://bznep.ourproperty.co.uk/articles/disable-sticky-keys-warning-beep-in-windows-10/ John

Yes - you can add/subtract a number to the scaled value to shift the centre position... however, that will also shift the max/min values being outputted. It sounds like you want the input values from 16384 to 14300 to be scaled to -1 to 0, and for values 14300 to -16384 to be scaled to 0 to 1. That is not possible (i.e. separate scaling for +ve and -ve vales) using axis scaling - you would have to write a lua script. You could try just adding to the scaled value to shift the centre. This would, however, give a value > +1 for max thrust (effectively reducing the +ve thrust range and making it more sensitive) and won't reach -1 for reverse thrust, but may be useable. So if you are currently using a scaling factor of *-0.06103888176 (you don't say!), you could try *-0.06103888176,+0.872856. It may be better to change the scaling for the positive thrust only, and so use *-0.0326115,+0.4663 - that should give you a full forward thrust range between 14300 and -16384, but would only give a small negative thrust range when between 14300 and 16384. You could maybe also try explicitly setting a lower value when entering the reverse range using the right hand side of the axis assignment dialog... But for proper control (with appropriate scaling for forward/reverse thrust), you would need to use a lua script.

You could also try directing the key stroke using the windows class name - again, see the WideFS technical guide. To find the class name of the window, you can download and use Spy++. John