John Dowson

There is no event function associated to lua globals. No, you would have to use polling to do this - maybe on a timer, and use this to determine if the lua global variable value changes and then call your function. Otherwise, to use an event callback, you would have to use a free offset, i.e. write the lua variable value to a free FSUIPC offset in the server and monitor that offset in the client with event.offset. John

Please see the FSUIPC Lua Library document - the ipc.set finction is documented as follows: Given the above, why not? John

I have the Alpha and Bravo on my flight system, but I don't have the C510 installed there yet - and haven't used this system for quite a while now and everything will need updating. I also don't fly this aircraft - I purchased to help others out with assignments as it is quite different from most other aircraft. Ok, I can look into the assignments needed for the batteries and the alternator. As I said, I don't currently have this fully configured - only a couple of assignments on my development system. However, I will take a look and get back to you. Looking at your ini, these assignments are wrong: and should be: Did you manually change this? John

👍No problem! 😎

Try the attached version, 7.4.12d. Add the following to the [General] section of your FSUIPC7.ini file: MaxCustomControlNumber=96323 John FSUIPC7.exe P.S. As your question/issue is with FSUIPC7, please use the sub-forum dedicated to FSUIPC7 / MSFS for such posts. I will move your post.

What event/control numbers are those? Third-party events start at number 69632, and the first/lowest custom event number shown in that web page is this one: EVT_MD11_PED_CPT_RADIO_PNL_XFER_BT_LEFT_BUTTON_DOWN 69644 i.e. event 69664. If you look at the log file you posted, you will see this: So this is the range you can use for third-party events (also known as custom controls). Looks like the TFI Design MD-11 uses third-party control numbers from 69644 to 96323, so you currently won't be able to use those above 84232. This is currently a hard-coded maximum. For the next release I will add an additional ini parameter so that the max custom control/event number can be specified. I will release the next version shortly after SU15 is released, which should be any day now. Once I have made this change, I will also post details in this topic and can maybe supply you a beta version to test (if not released yet). Your log file shows errors when using custom events above 84232: These other errors in your log file: are because you are trying to use buttons assigned to presets before everything is loaded. You cannot use presets/lvars/hvars until the WAPI has established a connection and the initial set of lvars have been received, which is logged here: So you need to wait a short while (an additional 7 seconds or so) after the aircraft is loaded before you try and operate it via FSUIPC7 assignments to presets. John

I have added a new ini parameter that goes in the [JoyNames] section that will allow you to ignore a device, which hopefully should help with this issue. I have attached a beta release below if you could try it. To use this to ignore the phantom Xbox controller, add IgnoreDevice=0x28DE,0x11FF to your [JoyNames] section. I have only added this to the HID scanning which should be sufficient, but if there are still issues I can look into ignoring in the reg scanning as well. FSUIPC7.exe John

Are you using "profiles in separate files" then? The usual reason for profiles not loading is that the aircraft name doesn't match the names of the aircraft in the profile entry, usually due to a different livery being used. To prevent this, when you add an aircraft to a profile, you should edit the name of the aircraft in the profile section of the ini file to a shorter substring to catch all variants of the aircraft. This is my entry for the C510: The profile used is not logged, but if general button or key definitions are overridden by a profile, then this should be logged. If you are having issues, please explain and attach both your FSUIPC7.ini, your FSUIPC7.log and also your profile ini, if using profiles-in-separate-files. John

Yes - I don't understand why that one is fine and the other not, very strange, I would like to release this a new version ASAP but SU15 should drop any day now so I am holding on for this, but if it doesn't drop in a day or two I will release anyway. John

As already noted many times, there is now a false-positive report in Windows Defender since the recent update (1,409.80 from 06/04/2024 or maybe a day or two earlier or later, depending upon when the update was pushed). This is definitely a false positive and I have reported it to Microsoft and am awaiting a response. There is nothing that I can do about this at the moment. To download and install FSUIPC7 (on Windows 11, 10 should be similar), you will have to temporarily allow this threat. To do this, go to the Windows Security panel and select the Virus & threat protection page, ant then select Protection History. Select the entry for the installer (should be the first entry), and then under the Actions menu select Allow. This will allow you to download and run the installer. Once you have installed FSUIPC7, Go back to the main Virus & threat protection page, click on Allowed threats, select the entry just added (will be Trojan:Win32/nyonm) and click Don't Allow. You will need to do this to install FSUIPC7 for the time being. Hopefully Microsoft will resolve this issue soon. Note that when downloading from fsuipc.com you may also get an 'insecure download blocked' warning. This is a separate issue and is because the fsuipc.com site is still on http and not https (sorry, haven't had time to update this yet, been on my to-do list for several years...). Just click Keep (or similar) in your browser. The file itself will still be downloaded over https so this is not an issue. For other users who are experiencing this, there is no point posting about this as it is a known issue. I will update this topic when I get a response from Microsoft or have any new information. It also seems that the latest beta release doesn't have this issue (no idea why!), so you can also use/try this if you do not want to allow the current installer to run, available here: https://fsuipc.simflight.com/beta/Install_FSUIPC7beta.exe John

Thanks - please update if/when you get a response. Thanks, John

It seems that the latest beta release is not affected by this - I don't know why. This is an exe rather than a zip, so is missing some documentation (README.txt and changes.txt files), but you can try downloading this if you have issues with the official release: https://fsuipc.simflight.com/beta/Install_FSUIPC7beta.exe However, there will most probably still be issues with BitDefender and the RegistrationChecker in this version. John

First, note that the gauges display the temperature in Fahrenheit, but the offset holds the temperature in Celsius. However, there does seem to be an issue. When I start the PMDG 737 I see the offset increase in value from 0 up to around 80, and if I adjust the temperature this can go above 100C! This is obviously not correct, and should be reported to PMDG. John

FSUIPC just populates the PMDG offsets with the data received from the aircraft. If it is not holding the correct value, then this can be due to one of two things: 1. The PMDG data format has changed. I can check this. 2. The data PMDG is sending is not correct. I cannot do anything about this and this should be reported to PMDG. I will take a look at 1 and get back to you. John

Ah, ok... This depends. Some add-on aircraft don't work well when assigned using Send to FS as normal control and are then also calibrated in FSUIPC7, due to the priority levels. The aircraft will intercept the initial axis control, pre-calibration, rather than the calibrated axis control. Anyway, glad your issue is fixed. John

Can you show me the InstallFSUIPC7.log please, from when you re-installed after renaming the UserCfg.opt file. Also please attach your FSUIPC7.log file, which will be in your FSUIPC7 installation folder. The auto-start issue is not fixed - you started FSUIPC7 manually. You can continue to do this to use FSUIPC7, but if you want this to be automatically started then this issue will need to be fixed. There is a FAQ entry on auto-start issues - see John

Yes, I can see this now after virus definitions update. I have allowed an exception and downloaded and checked the file, and it is the same one as uploaded and so this will be a false-positive. I will report this to windows, and also see if I can fix here. I think the problem is that the installer runs an embedded program to check the registration details and it is this that is being flagged. This program was recently updated (recompiled only) so I will try with the older version. If that also fails, I will have to remove the registration validation until this issue is fixed. Sorry about this - I will try and fix this asap....for now, please add an exception for the installer to allow it to be downloaded and ran. John

See: https://www.bitdefender.com/consumer/support/answer/13427/ https://www.bitdefender.com/consumer/support/answer/2393/

Whatever you want - User.cfg.opt.notUsed for example. Just give it a different name so it is not detected.

What is confusing about this? If that file is present, the installer will assume you are using a Steam installation. If that file is not found, then an MS Store installation is assumed. Renaming that file will therefore tell the installer to install for MS Store, not Steam. John

No, it is a false positive. I have no viruses, and SimMarket also scans all files for viruses and they have not reported anything. As the virus is reported in the RegistrationChecker program, can you not install and skip registration? Are you using BitDefender? What is it saying, and why is this different from other users reporting this issue - others users could download but had problems running it due to the issue with the RegistrationChecker program. If it is your browser blocking the download, you can tell the browser to download anyway. What workaround did they post? Can you please provide a reference. It must be possible to either disable BitDefender when downloading/installing, or adding an exception to allow the program to run. Can this not be done?

But you shouldn't install FSUIPC7 when running MSFS. But try re-launching MSFS after you have finished your flight and see if FSUIPC7 starts. If not, can you at least try starting it manually, by double-clicking the FSUIPC7.exe in windows Explorer - does it then work? Then I would expect that you are using an MS Store installation, but your log file indicates that FSUIPC7 is installing for Steam. Did you previously have a steam version installed but are now using the xbox version? If so, please remove or rename this file: C:\Users\jaked\AppData\Roaming\Microsoft Flight Simulator\UserCfg.opt and re-install. Do you know where your Community folder is - is it at that location I mentioned? John

Do you mean that FSUIPC7 is not running? Do you not see the FSUIPC7 splash-screen when MSFS is started and loading? Did you install FSUIPC7 firectly from within the zip file rather than extracting the installer from the zip file first? It looks like it: Please try extracting the installer before running it. The Community folder for your Steam installation also looks rather strange: Is this correct? Anyway, please try installing again and extract the installer before running it. Then run MSFS. Do you see the FSUIPC7 splash screen? If so, FSUIPC7 is running. If not, there may be an issue with your EXE.xml file. Please show me/attach this file, as well as your new InstallFSUIPC7.log file: C:\Users\jaked\AppData\Roaming\Microsoft Flight Simulator\EXE.xml Are you running MSFS as admin or as a standard user? If running as admin, you may need to set the FSUIPC7.exe to also be ran as admin (and also all FSUIPC7 clients). John

Again, what aircraft are you using? I don't see how FSUIPC's aileron calibration can change the display in the attitude indicator. What the calibration will do is adjust the values sent to the FS when you move the aileron axis, so axis positions below the centre will send the negative parameter range (-16384 to 0) and axis positions above the centre will send the positive range (0 - 16384). Are you sure that you weren't doing something else to configure the attitude indicator? It should be with those settings - have you tried it? There has been absolutely no change in this area for a very long time.

Sorry, but what do you mean by this? Do you see the In/Out numbers changing when you move the axis? Are the numbers registered when you press the Set button? What aircraft are you using, and which aileron axis? Can you also attach your FSUIPC7.ini file please. John