John Dowson

Thats fine, but you should delete the contents of the [General] section and let that get rebuilt, as many of the parameters no longer apply. You can manually remove any aircraft from profiles if you like, or remove profiles completely if you are no longer going to use them. But they do no harm. Sorry, but don't know what that file/link is you posted, but its not your FSUIPC7.ini file.

Have you installed the MobiFlight WASM module?

No, as that is for MSFS only. You say you have purchased FSUIPC5, which is for P3Dv4, so use that. I don't know Pilot2ATC, but I suspect it works with the unregistered/free version of FSUIPC anyway.

FSUIPC is only an interface to pass controls that it receives to the FS. How the FS responds is outside of our control. Yes...unfortunately. Many events sent to the sim can result in different events received, which also don't include the actual event sent. I'm not that familiar with the A320, or the MB events or this aircraft/mod, but maybe your question should be asked on the MB AS320 mod forums, if that is what you are using. Other that, I would at least need to see your FSUIPC log and ini files to comment further. John

This is about the 100th time this has been reported...please, if you have an issue, first check the documentation and then check for previous posts of the same problem before you post. The solution can be found in the provided README.txt: Not also that you should not install as admin, unless you installed MSFS as admin for some reason. Please read the provided README.txt (as the name implies!) and also the Installing and Registering FSUIPC document provided. John

They didn't get replaced. You specify the [Auto] section. FSUIPC writes the [LuaFiles] section with the .lua files it finds in your installation folder. If wasn't obvious that it should have been 1=Lua HidDemo and not !1=HidDemo.lua then I don't know what to say....perhaps I should give up providing user manuals...😞 This script has been available for many years and should work without too much trouble really...You should check the vid and pid are set correctly, and you can set the logging flag (in the script itself) as well as activating logging for lua plugins (from FSUIPC) so that you can see if it is running or not and perhaps what the error is. But as you have already stated that you will not be purchasing a license, and this functionality requires a license - and I am also very busy, I don't think there is much point assisting you with this any further, sorry. John

There are no hot keys in FSUIPC7, apart from the hot key to display/hide FSUIPC7 itself. Offset 0x0C1A was previously reported as working (as its marked in green in the offset spreedsheet) but I've just taken a look and it doesn't seem correct. I can see the value change occasionally, but it jumps back to 0, but sometimes shows other values (32, 64, 128). There are also no controls exposed via simconnect to control the sim rate, although there are some MSFS controls to increase and decrease (as well as set the sim rate). You can assign these to keys (in MSFS) and then assign buttons to these key presses in FSUIPC. However, there is no control to return to normal speed, and it difficult to know when you are at normal speed without that offset working! Here are some Asobo references to the issue, where another tool for this is mentioned that you could try: https://forums.flightsimulator.com/t/bug-changes-in-simulation-rate-are-not-displayed/8698 https://forums.flightsimulator.com/t/simulations-rate/351296/10 I will look into offset 0x0C1A to see what is happening with this, but this will take a while. I'm concentrating on providing lvar access at the moment, and am making a note of such issues and will look into them once I've released a beta of the WASM lvar access module. John

Yes, I know, thanks. I provide manuals so that I don't continually have to answer these type of questions... Your ini file has this: + The Advanced User Guide says: So, isn't it obvious that your ini's [Auto] section should be: [Auto] 1=Lua HidDemo ?

This value doesn't change until you click the Set button. Its the In / Out values that change, and then you use the Set button to set the (max in this case) in value. If the In/Out values aren't changing, make sure you have assigned Direct to FSUIPC Calibration and the flaps axis.

Hi Daniel, ok, thanks for the detailed explanation. I'll definitely look into this when I have more time. Regards, John

Why wouldn't you if nothing has changed? What message? When? Did you download the exe I posted above and try that? Please do. I have also PM'ed you a key file. drop that into the same folder as your FSUIPC7.exe. You don't need to. If you want to use anything there, documentation is provided (from that link I also posted). Your screenshots above show MANY errors.I think there must be something pretty seriously wrong with your system and should consider reinstalling Windows. Do you have any anti-virus software running (apart from Windows Defender)? If so, maybe try temporarily disabling.

You can either add them to your existing event files or create a new one for them. Note the max limit of 256 events per file. And there is also an issue with the current release v7.0.4 (and earlier) in that only one event file can be used, so if using multiple event files you need to download the latest version I attached where the event files were posted. I'll release this as v7.0.5 when I get time.

It is currently not possible to use the FSUIPC auto-save files as there are currently issues with saving and loading flight files via simconnect (which FSUIPC uses), although this is possible directly from MSFS. We are waiting for this to be addressed by Asobo. John

Yes, and you have to add it to the [Auto] section of the FSUIPC7.ini file. This is explained in the step-by-step guide for the Alpha and Bravo scripts, or see the section Automatic running of Macros or Lua programs in the Advanced User Guide. John

Yes, we are aware of it. There are issues when calibrating for PMDG aircraft in FSUIPC due to priority levels of the axis controls being sent. However, you can still assign in FSUIPC but assign to the FS control and not direct to FSUIPC calibration. However, this may be depend on the axis (e.g. throttle vs aileron/elevator). Best to just try and see what works for you. If you assign to FSUIPC calibration and calibrate, but you then suffer from a jittery axis, then this is usually a sign that different values are being received (due to the priority level issue mentioned) and you should switch back to 'Send yo FS' and not calibrate. Ok, then just leave it as it is! Then can't (or shouldn't) happen. Next time it happens, post again with your FSUIPC log and ini files and I'll take a look. Would be better if, once it occurred, you could activate logging for buttons & switches and events, and press the button again to generate the log entries (you can do this without closing the FS or FSUIPC). Then close the sim and post your log and ini files. John

No. Windows numbers them from 1-32, FSUIPC uses 0-31. Your install log shows that you installed FSUIPC7 your your Program Files (x86) folder. You shouldn't install there as its a protected folder (and also FSUIPC7 is x64 not x86) and could give issues, so better to install in a different location. Run the installer again and select a non-protected folder (e.g. c:\FSUIPC7 or C:\MSFS Ad-ons\FSUIPC7) to install. The installer will automatically detect your current installation and uninstall that. You can copy across your FSUIPC7.key and FSUIPC7.ini again afterwards. However, I'm not sure this prevented your settings not being saved, as if the FSUIPC7.ini file exists then FSUIPC can write to the folder. If its not working after you re-install, attach those updated files (InstallFSUIPC7.log and FSUIPC7.log) together with your FSUIPC7.ini. Your install log also shows no update of the MSFS EXE.xml file. This is select by default in the installer components selection - did you uncheck this? If you want FSUIPC7 to start with MSFS, you should leave that checked. John

Did you select to have FSUIPC auto-started with FSUIPC? Please show me your InstallFSUIPC7.log file. To calibrate, you need FS running. If you settings aren't being saved, there is a problem with your installation. I'll check this when you post your installation log. Also attach your FSUIPC7.log file please (both will be in your FSUIPC7 installation folder). Yes, currently only 32 buttons are recognised (numbers 0-31) + POV buttons 32-39). I am working on extending this to 128 buttons, but this is not ready for release at the moment. For now, to assign to those buttons, you have to use a lua file that will map the buttons > 31 to virtual buttons. If you are using the Honeycomb Alpha or Bravo, there are specific scripts for those in the User Contributions section. Othgerwise, you can use the HidDemo.lua plugin included in the lua examples (located in a zip file in your documents folder). You will have to edit it to add your devices VID and PID, and have it auto-started via your FSUIPC7.ini file. Yes, they are separate. You should create an empty profile for your controller in MSFS itself initially, although you can mix and match assignments between MSFS and FSUIPC if you like, just make sure you don't assign a button or axis in both. John

Sorry, you don't need to edit the ini for this. Just assign your throttle direct to FSUIPC calibration and select a throttle axis, and with your throttle at 4% set the lower limit, and at 74% set the upper limit in the throttle calibration page..

But I thought your issue was when calling any lua script (e.g. your simple example) on a button press? If you were doing that on repeat, that would certainly be problematic as the lua is compiled before being executed and then ran, and the repeat would kill the running thread and start this again... Best to use event.button directly for such luas, rather than by direct FSUIPC asignments. Anyway, sorry for the delay in this - I've been busy working on the lvar WASM module. I can take a look at this over the weekend if its an issue, but I think i need more details on what you are actually trying to achieve. John

Maybe try logging the value of next_waypt_info after reading it to see what it contains, and/or having a final 'else' to set to "UNKNOWN" .

Sure - use the attached key file. Just drop it into your FSUIPC7 installation folder. It is valid for 5 days: FSUIPC7.key Hmm. It may be possible by assigning direct to FSUIPC and calibrating, and then manually editing the ini to change the calibration entry to decrease the throttle's value range. You would want to set the range in the calibration entry so that the value sent when at 74% physical position is the full throttle value. However, when you pass the 74%, larger values will then be sent...presumably these will be ignored (and not produce an error) but give it a go. Also, please see the User Guide for details on calibration, although you won't find details on how to do what you want to achieve. Try setting it up and if you have any issues, post your FSUIPC7.ini file here and I'll take a look (but only after you have at least assigned and cailbrated!). John

No problem. You could try looking at the MobiFlight WASM module, and adding the MobiFlight events to FSUIPC. They may have some events/controls for the functions you require (especially for the A320). Also, check out the FBW A320 mod if you haven't done so already. For information on MobiFlight WASM module and events, see: and The lvar-access (and hvar) WASM module for FSUIPC7 is progressing well, but it will be another few weeks before I can get a beta version of this out to test. John

I took a look at the code for this as well, and its just a direct copy from the simvar to the offset, as Pete says. So if its empty, we are getting an empty value/string through from SimConnect for that simvar. The code in FSUIPC6 and FSUIPC7 is the same for this offset. Try logging the offset in both FSUIPC6 and FSUIPC7 and compare the output.

There's an online converter for that: https://clideo.com/merge-wav, and also quire a few freeware programs (ask google!).

Of your throttle is jumping straight to full throttle with any movement, you need to fix the registry entry for that device. Please see that FAQ article I referenced. Remember to back up your registry first! Before you do that, you can try with other controls (but I think you will find the same result). You are currently using Throttle Set, try also with Axis Throttle Set. Note that you are using a profile (called 737 Axic) for your PMDG 737, but you don't have any axis for that profile. You should make the axis for that profile specific. To do this, open the axis assignments dialog (with the PMDG 737 loaded) and check the profile box, and select to import your general axis). A few other minor points from your ini: - you should change AutoAssignLetters=No to AutoAssignLetters=Yes in the [JoyNames] section of your ini. This will prevent problems in the future if your device ids change (even though you currently only have one device) - Change your profile string 1=PMDG 737-800NGXu PMDG House (N738PM | 2019) to something like 1=PMDG 737-800NGXu That profile will then be used with any variant of the PMDG 737-800NGXu. You can even use 1=PMDG 737 to use with all PMDG 737s. John