John Dowson

Yes, of course - that flap lever is an up/down control. You can also use the flap axis on the Bravo - the far right axis. Sorry, but not sure what this means... Up should move the flaps up one position/notch, and down should move the flaps down one position/notch. You could try searching to see if there is a specific preset available for the flaps in the aircraft that you are using and use that - see https://hubhop.mobiflight.com/presets/. Otherwise, if you let me know the aircraft you are using, I can take a look here and advise - if its a default aircraft or an add-on that I own. John

It is normal for a small freeze when saving data for a complex aircraft. This is nothing to do with FSUIPC - that just calls the SimConnect function to save the state. However, if its taking that long, this is usually due to anti-virus interaction. Try removing the flight-save folder from anti-virus scanning - that should improve things somewhat, but you will most probably still get a delay, but should only be a second or two. Also, to get around this issue, there is a control function that you can use to activate/de-activate the auto-save function (only works when the auto-save function is active), which is Auto-Save Toggle (1151). You can use this to disable auto-save on take-off and approach, which is where this pause causes the most issues/frustration. John

No, I am afraid not. FSUIPC only receives axes positions (as well as buttons/switches) on change. The standard way to get around this is to always start with your levers in the zero position. John

Could you please also activate logging for Buttons & keys as well as Events, and produce a short log file (i.e. load a plane, turn your selection rotary to the required position and then try to inc/dec, then exit FSUIPC). If you do this with the logging console open (Log -> Open Console....) you may be able to determine what is happening and fix this yourself, otherwise attach the log and I will take a look (you can compress/zip it if too large to attach directly). John

Maybe the FBW A320 has changed? I would ask about this on the FBW discord channel. There has been no change in how FSUIPC activates hvars (or uses calculator code) for quite a while. You could also try the MF preset A320_Neo_EICAS_2_ECAM_CHANGE_PAGE_HYD - this just activates that hvar though so you will probably get the same issue, but you can ask about that on the MF discord channel. John

First, look for the offsets which hold the fuels tank quantities - you probably want to use the fuel tank level offsets starting at 0x0B74 or 0x1244 (not sure why these are duplicated....). I would monitor them first (using Log =>Offsets) to verify that they are changing as expected. Then create a lua script and use event.offset to receive the level every time it changes. When it reaches a certain level, you can then send the control (using ipc.control) to switch fuel tanks, and maybe also start monitoring the level in that tank as well to switch to the next tank when the level drops below a certain quantity / %age - you can so this for as many tanks that are available. See the FSUIPC Lua Library document for details on how to use these functions. Note also that the script should be auto-started from your FSUIPC7.ini, most probably only in the profile for the aircraft for which you want to use the script. See the Advanced User guide for automatic running of Luas. John

As I keep saying, they are available in the forum from that link I posted. I will also add a link to www.fsuipc.com. This would be useful for many support questions as I could then post a link to the relevant html section of the documentation for support requests that are covered by the documentation. Well, I should be able to export the original documents to html format (and maybe tweak a bit), rather than pdf. This has been on my to-do list for a long time, but unfortunately I don't have much spare time after dealing with support request and keeping up with FS updates.... I would also like to start a wiki for questions/answers, but again, its a matter of resources (mainly time!)...just me supporting many products, both freeware and payware... Not many users actually look at the current resources available - documentation, FAQ, User Contributions, contents of the support forum... John

We do - they are here: I have not put them on www.fsuipc.com as I don't think they are needed....this has never been a problem before... In an ideal world, I would also have the manuals in html format on the website. If only I had time to do such things....! John

Pete retired a few several years ago, although he does help out still on occasion. Please note that f you have problems with your WideClient connection to WideServer/FSUIPC, I always need to see four files, preferably with their original names (i.e. not renamed): WideClient.log, WideClient.ini, WideServer.log & FSUIPC?.ini. It is also useful/helpful to know what version of FSUIPC you are using...as you are using P3Dv5, it must be either FSUIPC5 or FSUIPC6. Your WideClient.log says it is version 6.999z4, so its WideFS6 (32bit) but I am not sure what that version is (before my time I'm afraid). I guess you are using that as your client machine is 32bit (Windows 7?), no? Anyway, if it was previously connecting ok and no longer is, it must be due to a change in your network. Consult the provided documentation - it will either be related to a workgroup name update/change, or a firewall - either on the client or server machines. Test with both firewalls disabled, and if it connects ok then, start one at a time to see which one is blocking the connection. John

Well, as I don't know what version of FSUIPC you are using, I am not sure - for FSUIPC4/5, they will be installed in an FSUIPC Documents folder under your FSUIPC installation folder. For FSUIPC6/7, they will be installed under your Windows Documents folder. The provided Installing and Registering FSUIPC document, available both in your FSUIPC documents folder AND in the fsuipc zip file you downloaded that contains the installer, details what is installed and where. They are also available from the Download Links -> Documentation section of this forum, although the ones there will not be the latest as I updated those less frequently. I don't know how to make this more obvious....I suggest you just look for them.... John

That will (most probably) be the profile name. If you want a separate profile for the PMDG 737, remove that aircraft from the profile section in your FSUIPC?.ini file - (you don't say what version of FSUIPC or FS you are using!). Then set-up a new profile for the PMDG 737... No idea - please see the section CALIBRATING FLAPS WITH SPECIFIC DÉTENTES in the FSUIPC User Guide. Any further issues or questions, please include your FSUIPC ini and log files - and it would help if you let me know what FS you are using. John

Please see the provided Installing and Registering FSUIPC7 document, section Invalid Key Problems. And please always consult both the documentation and the support forum first before asking for support. Most questions have already been asked and a solution available. This same question has now been asked hundreds of times... John

You can assign either in MSFS or in FSUIPC, or have some assignments in MSFS and others in FSUIPC - it is up to you. However, you should not have assignments in both for the same axis/button/switch, as this will cause issues, If you are assigning in FSUIPC only, you should create an empty profile in MSFS so that you don't have this dual assignment problem. Otherwise, you can keep the default assignments for your device/controller in MSFS, but make sure you remove/delete an assignment if you decide to use FSUIPC instead. Most people would use an empty profile in MSFS and assign everything in FSUIPC. You would set-up the Honeycomb Bravo as you would any other controller, so I am not sure I understand your question. For the Bravo AP functions and trim wheel, see this for a basic configuration: For the throttle axes, you would set those up as you would any other axis. It is usually a good idea to assign to the standard throttle control first in your general profile (i.e. no profile selected) using Send to FSUIPC calibration and the Throttle control, and then calibrate this on the first page of the calibration tab. Different aircraft use different throttle controls (and it also depends on the number of engines the aircraft has, of course), so you would then set-up specific profiles for different aircraft (or groups of aircraft). Please see the provided documentation (User Guide and Advanced User Guide). You can also search this forum for issues other people have had with Bravo set-up, which may help. John

It's John, not Pete... First, make sure you back-up your registry before doing anything - you should always do this before editing the registry, just in-case. Then delete completely from the left-hand side. John

This sounds like your joystick axes gave changed (in the windows registry to digital on/off axes. This is not relayed to the FSUIPC update, but maybe to a windows or driver update. To resolve, see the following FAQ entry: Although the FAQ entry is for Saitek devices, it applies to all hardware when this occurs - just use the appropriate PID and VID numbers for your device, John

That post is quite old - it is still valid but you no longer need the lua scripts to see the buttons with numbers > 32. If you are using those, please remove them and assign to the original button numbers (as opposed to the button flags that are provided by those scripts). I have updated that post to reflect this. I don't think/see how this can be caused by FSUIPC... Can yo check your assignments in MSFS - if assigning using FSUIPC, I recommend that you start with an empty profile in MSFS. I can only look into what controls/events are being sent to the aircraft, not how the aircraft model is behaving from these commands. To check that what you are seeing is not due to the controls being sent, you can activate logging for Axes Controls in FSUIPC7. I suggest you only do this once you are in level flight and your issue starts to occur. The log file will still be quite large, so compress/zip it before attaching and I will take a look. Also, make sure you exit FSUIPC7 before compressing and attaching your log file. Also attach your FSUIPC7.ini file so that I can check your assignments. Note also it is quite common to have to continually adjust trim in GA aircraft to maintain level flight (but not constantly!), but it shouldn't fall sharply to the left or right. John

I don't understand why the installer cannot read that file if it is in the correct location (I think it must be related to either windows permissions or anti-virus software blocking access), but I don't think there is anything I can do about this. There have been several similar reports. You will have to install the WASM manually. Unzip the file D:\Programme_Flugsi\FSUIPC7\SDK\FSUIPC-WASM.zip and then unzip the file fsuipc-lvar-module.zip and then copy or move the folder fsuipc-lvar-module to your MSFS Community folder. John

Ok, I will add them. However, note that these days it is a lot easier to use hvars via presets rather than maintaining *.hvar files. For example, those two hvars are assignable using the presets A32NX EFIS L CHRONO PUSH and A32NX EFIS R CHRONO PUSH without the need to add the hvars to the *.hvar file. John

Possibly, if there is a generic control for this Toggle External Power or Set External Power maybe? Have you tried these to see if they work in the King Air? However, it is not necessary to make this offset wtiteable as there are other offsets that can be used (although it would maybe make this easier). Is this the Bat Bus switch in the King Air that you are referring to - the one with the red and white striped background? If so, that is INOP in the VC, so I don't think it is possible to control this in the King Air at all (unless there is a mod available that implements this). To control things programmatically (i.e. via offsets), if an offset is not writeable but there is a control/event or preset to control, then you can use either offset 0x3110 (facility to send any control) or offset 0x7C50 (facility for presets, lvars, hvars and calculator code). John

👍

You can choose where to install Steam... Thats ok - I was saying that you should run FSX as admin if installed in that location. Yes - did you check your Windows Explorer settings - maybe it is there and the extension is hidden? Also check any anti-virus software, including Windows Defender. Such software could be blocking the creation if the FSUUPC4.ini, if it is not already present. If you have previously used FSUIPC4, your assignments and settings will be stored in your FSUIPC4.ini file. John

That lFSUIPC7 log is partial and ended after 9 seconds, and shows that WideServer wasn't yet started. Leave it running longer... Or did FSUIPC7 crash? Was it still running? If not, and it crashed, please check the Event viewer and paste any crash reports. Any further issues, please also attach your files, and not paste contents, partial or otherwise, and make sure FSUIPC7 / WideClient are no longer running before you attach logs. Any further issues, I will rake a look on Monday. John

👍

The P in the assignments line indicates Press - all button assignments are preceded by one of P, H, R or U for the button action (Press, Hold, Repeat, Unpress or release). See the Advanced User guide for the format of button definitions. Yes, try that - and if that doesn't work, use the number that M is mapped to. John

Simvars are A-type simulator variables, and some are held in FSUIPC offsets (but by no means all). To control an aircraft (buttons, switches, axes, etc) you would generally use controls or events (two words for the same thing), not simvars. Presets are provided for assignments generally not available via controls/events. These can be implemented to use lvars, hvars, controls/events (also known as kvars), simvars and other variable types. Presets are provided to hide the complexity involved with these various variable types, so you don't really need to know much about them - just stick to controls/events and presets. John