John Dowson

Ok. Not sure why - battery, avionics, starter all work easily via Input Events. The only difficulty I am having at the moment is for the fuel cut-off triggers and the pitot heat/static switch which don't seem straight-forward - I will look into these further tomorrow. You can also use FSUIPC logging - events and Input Events, and open the logging console (Log->Open Console) to see the messages in real-time. Of course - just check Select for Input Event in the assignments panels. You can choose between Standard FS controls (including PM controls), Presets or Input Events for assignments. Thats strange, and I do not see that here. Windows normally uses the windows (or CMD) key, not the alt key, which is why it is recommended not to use this as a modifier (and I think I removed this in FSUIPC7). Yes, that seems to be the key combination for the nav log. No idea where this is defined - it isn't listed under the keyboard controls. Modifier keys just allow for more distinct assignments. Using them will not prevent anything else that is also using and receiving them. Yes. This is for receiving keys. Normally FSUIPC receives key press/release events from MSFS via SimConnect. However, for some button-controllers (i.e. controllers that send configurable key press combinations on a button press) the key presses will not be received. For such controllers, you can set this and FSUIPC7 will install a global keyboard hook and receive all key presses directly from windows and not from MSFS via SimConnect. You only need to set this option if you are using a button-controller that sends key presses that are not seen by FSUIPC7. FSUIPC7 cannot control how other programs respond to your key presses. Choose a combination that doesn't trigger other actions - there are many possible combinations. John

In FSUIPC... It certainly is - see, for example, the image on page 36 of the User guide - notice the Rev checkbox. This is for reversing an axis, and will be in each calibration panel for axes that can be reversed. No idea what this means, sorry... zip/compress them if too large to attach directly. Your upload limit will increase the more you post. It is usually much better to assign with Send direct to FSUIPC calibration and calibrate, and assign using Send to FS as normal axis only if the aircraft is having issues with FSUIPC calibration. If you assign using Send to FS as normal axis then this will also be calibrated in FSUIPC, but AFTER values have been sent to the FS and received back, which can also create issues with certain aircraft. If assigning in this way and you do not want FSUIPC to calibrate, then you must create a profile-specific calibration section (or else the general calibration section will be used) and disable any calibration settings you have there (i.e. click Reset in each of the calibration tabs). I am not going to look at your files yet - I have no idea what I am looking for! As I said, lets do one aircraft/issue at a time. If I can show you how to do that, it may become clear to you. So please let me know what aircraft you are using, what issue you are having, and show me/attach your ini and log files for this. I don't understand the issues you are having - if you had everything working with the saitek controller, it should be relatively straightforward to switch to using the Bravo. John

You are also using a very old beta version of FSUIPC7, 7.3.26g: Please update to the latest and only supported version, 7.4.11. You need a later version to assign to Input Events correctly.

I have just looked at the ini and log files you posted, and they report no devices acquired for use by FSUIPC7: So your devices are not being controlled by FSUIPC7. No idea why this is. Are your devices working and recognised by FSUIPC or not? And this is nothing to do with the aircraft you are using...If your devices are not recognised, we need to look into this first rather than assignments for a specific aircraft,,, You have raised quite a few support requests on this so I presume your devices were recognised. What has changed? John

Well, they should provide information on how to control the aircraft, whether this be standard events, lvars/hvars or input events. However, it is not difficult to detemine how any switch works, by either using FSUIPC logging (which will log events and input events. when selected) or using the facilities provided by MSFS (devel functionality, mainly behaviors console). I wouldn't expect developers to provide presets or Spad.Next snippets. These are both community-driven efforts. And as the C510 seems to mainly use Input Events, you cannot use presets/calculator code for most functions of this aircraft. And you must see the difficulty here. Your Alpha/Bravo controllers are nothing like the actual instruments in the C510, and so some mapping is necessary, and people will want to map these controls differently. For example, the Alpha uses a magneto to start the aircraft (i.e. it is for GS aircraft). There is no sensible mapping of this to engine L/R start buttons - you have to decide how you want to do this. But once you have decoded which controls/buttons to use. it should be relatively straightforward to implement/assign. I got these working using my saitek X55 controllers within a few minutes, assigned to the appropriate Input Events. I will look into assigning these on my alpha/bravo. What would you like to use, for example, for the engine start buttons on the alpha/bravo?

First, you posted in the wrong sub-forum - I have moved your post to the correct place, the sub-forum for FSUIPC7. This issue is documented in the README.txt file that comes in the zip file you downloaded (as well as in many other support requests in this forum): John

The C510 does have these input events, although I think the standard controls might also work, or at least some. Will take a look when I have time, but also need to familiarise myself with the start-up procedure first.

You may as well aslo remove these entries if you no longer use these devices: John

Note that you have no general assignments and you are not using substrings for your profiles. Therefore if you load an aircraft that does not exactly match a profile entry, you will have no assignments in FSUIPC7. Revise your profile strings - they all look a bit strange. For example, change this: to this: and this: to this: etc. Do this for all your profile aircraft, i.e. use substrings to match all variants.

You can reverse in the calibration page. But what am I looking at? You have reported so many issues. Lets do one issue at a time please. Load an aircraft you are having issues with. Activate appropriate logging for your issue (i.e. if it is with an axis, activate logging for an axis). Then reproduce your issue, exit FSUIPC7 and then attach both your FSUIPC7.ini and FSUIPC7.log files and I will take a look.

This is not a 'FSUIPC thing'... An axis is just an axis, it depends how it is configured. Configuring an axis for throttle on the Bravo is EXACTLY the same as configuring an axis on a saitek device. There is no difference as far as FSUIPC is concerned, it is just another axis on a controller. So it all depends on how it is configured. Did you re-configure you assignments for the Bravo? Did you disable the bravo in MSFS, or at least remove the default assignments? You are assigning to the wrong controls. For the CRJ, you need to assign to the _EX1 controls (i.e. THROTTLE1_AXIS_SET_EX1 & THROTTLE2_AXIS_SET_EX1, or THROTTLE_AXIS_SET_EX1). If your throttle was working on your saitek controller, then you must have been using this axis control. For each aircraft. you need to check how your axes were assigned with the Saitek and then redo your assignments with the bravo. I don't understand how you would expect it to work without doing this. Please do this., Any further issues, please at least attach your FSUIPC7.ini file so that I can see your assignments. John

Also, have you read the documentation for the C510, especially the start-up procedures? You have to open the fuel cut-off levers under each throttle - see page 27. Are you doing this before trying to start the engines?

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