John Dowson

Some events take a parameter (e.g. all *_SET events), others not. If you do not know, check the documentation: https://docs.flightsimulator.com/flighting/html/Programming_Tools/Event_IDs/Event_IDs.htm Those presets are incorrect as those events do not take a parameter. They will work, but the parameter is not necessary and is ignored. If you want different/alternating commands to be sent on successive keypresses, you would need to overload the key press assignment (i.e. have both assignments on the same keypress) and then use an offset condition to only send one of these at a time, depending on the state of the offset. So, for the ignition switches, for example, you can use offset 0x02C0 (TURB ENG IGNITION SWITCH EX1:1) for the left switch, and 0x02C1 for the right switch. These offsets will hold 1 when the switch is off/NORM, and 2 when on. You cannot currently read the value of an Input Event- this is something I would like to add. You need to determine if there is something else that also holds the value (a simvar or lvar) and use that - as I showed above with the ignition switch. It is easier to use an axis for such controls, and you would assign the axis value to an offset and use a lua script to pick-up changes to the offset value, calibrate this to the required range and then send the input event with the calibrated parameter. If using a rotary, this will use buttons and you need to use button assignments, and you will need to know the current value so that it can be incremented/decremented. Note that LIGHTING_PANEL_1 is also available as an lvar, so it would be easier to use this. Just add that to a free/spare FSUIPC offset (using the facilities provided), and then you can just assign your rotary buttons assigned to the offset inc/dec controls.

Please let me know your order number (do not post your key details) and I will check your key here. John

Please post what you have used. This helps others who come across this topic. If posting for help, you should always post the solution once found. John

Try looking at the Offset Stratus documents for the heading - there are several... As I suggested in your other post w.r.t. the altitude, ty logging the offset values. Writing to thee offset may work (if writeable) to update the heading, but it may not - this can be aircraft dependent, You need to use what works for your aircraft. You should always specify the aircraft for such questions. John

It seems that admin privileges are needed to run the uninstaller. When the installer is ran, it is windows that either asks for the permissions to be elevated or requests an admin login. The installer code only has access to this user's details, so if you change to an admin login, it is not possible to retrieve the user details from the standard user account. Therefore you need to follow the instructions in the README.txt. If this is not possible, then you would have to manually install the auto-start component and maybe also the WASM module. John

@Capholland Please note that this issue is already documented in the README.txt included in the zip file: The only possible thing I can do with this issue is to see if I can get the installer to run without admin privileges, as these are not even necessary. I think I have looked at this before (hence that note in the README on this issue), but I will check again when I get time. John

No idea - perhaps @andresb can explain what solved his issue. Note if using 7.4.11, please tune your connection parameters as described in this post: If not using 7.4.11, please update and then tune this parameter. John

Which aircraft are you actually using? There is no Asobo C510, as far as I am aware. I have the Cockspur C510 Mustang, and for the starter/ignition switches for this aircraft you should use the Input Events, not presets: ENGINE_Starter_1<;FLOAT64> ENGINE_Starter_2<;FLOAT64> ENGINE_Starter_Disengage<> ENGINE_Ignition_1<;FLOAT64> ENGINE_Ignition_2<;FLOAT64> Input Events are used to control the B-type variables, which you cannot use via calculator code.

Ok - please let me know if/when you hear anything back. John

But is that the target altitude or the actual altitude, and is that calibrated or not? As I said, FSUIPC has several offsets for altitude, try logging them and see which one matched (with any conversion applied) to the one in the FMC. I suspect you need the AUTOPILOT ALTITUDE LOCK VAR:3 simvar (Selected Altitude in FCU), which is held in offset 0x0798, or AUTOPILOT ALTITUDE LOCK VAR:1 (Autopilot constrained altitude value) in offset 0x07D4. Try logging these, as well as the other offsets, and apply appropriate conversion (i.e. divide by 65536 to get meters then multiply by 3.2808 to get feet) before comparing it to the displayed value. Are you using the development or stable version of this aircraft? Note also that the altitude of the FMC also works differently in managed and selected modes - see https://forums.flightsimulator.com/t/altitude-management-with-the-a320-on-autopilot/477984/2 (for example). There should still be an offset that holds the displayed value though... John

This has already been reported - see It will be a false positive. The RefistrationChecker.exe was recompiled with the latest VisualStudio update for this release, no other changes. I do not understand why this is now being flagged by BitDefender. Thanks for reporting this. John P.S. You posted in the main support forum - please use the specific FSUIPC7 sub-forum for all issues with FSUIPC7. I will move your post.

You cannot do this. Offsets are in FSUIPC7 only, and calculator code is executed in the FS. To change an offset that holds a simvar (a-type variable), then you would just set that variable and this would then update the corresponding offset. As I said, use the key assignments dialog. And if the key presses are not recognised, you will have to try with a keyboard hook. Looks like you haven't taken @ark1320's comments into account. You don't need the '>' symbol when reading an simvar (only for setting), and the k event TOGGLE_STARTER1 does NOT take a parameter (at least according to the documentation https://docs.flightsimulator.com/flighting/html/Programming_Tools/Event_IDs/Aircraft_Engine_Events.htm). So they should be: C510_Starter1_On#(A:TAILWHEEL LOCK ON, Bool) 0 == if { (>K:TOGGLE_STARTER1) } C510_Starter1_Off#(A:TAILWHEEL LOCK ON, Bool) 0 == if { (>K:TOGGLE_STARTER1) } but then they are exactly the same! If you want a toggle function on a button for this, then you would need to know the current state of the ignition switch. Maybe try TURB ENG IGNITION SWITCH:index or TURB ENG IGNITION SWITCH EX1:index (see https://docs.flightsimulator.com/flighting/html/Programming_Tools/SimVars/Aircraft_SimVars/Aircraft_Engine_Variables.htm). Also maybe take a look how these work in the presets defined for other aircraft - for example, this is the calc code for the C208 Engine Starter Switch Start preset: 1 s0 (A:TURB ENG IGNITION SWITCH EX1:1, enum) != if{ l0 (>K:TURBINE_IGNITION_SWITCH_SET1) } (A:GENERAL ENG STARTER:1, Bool) ! if{ 1 (>K:SET_STARTER1_HELD) } I can and do help out with preset definitions when I have time, but I am very busy at the moment with various issues and don't really have time for this at the moment. The best place to discuss presets for specific aircraft would be on the HubHop discord server, in the msfs2020 channel. Otherwise I can take a deeper look maybe later in the week (or next week), when things calm down a bit... If you only want your assignments to work when the tailwheel lock is off, it is better to remove this check from the actual presets and add this as an offset condition to your assignments. So remove this check from your preset code for the time being. Once your assignments are working, you can add an offset condition to your FSUIPC7.ini. To do this, find the assignment, e.g.: 46=PS,14,CPC510_Starter1_On,0 -{Preset Control}- then add an offset condition for the tailwheel lock which is 0x2A90: 46=D2A90=0 PS,14,CPC510_Starter1_On,0 -{Preset Control}- John

If you have updated to 7.4.11, please see this post: If not using 7.4.11, please update to this version and then follow the instructions in that post to tune the DetectToConnectDelayAuto ini parameter. John

But why are you registering again anyway? You only need to do this once, to generate your key file. When you update FSUIPC7 you do not need to re-validate your registration - your previous key details will be shown in the registration page, and you can just Skip. But if the key won't validate, please see the section Invalid Key Details in the Installation and Registration guide. John

But as it says in the very first post: Note that time-limited/trial licenses are not validated by the FSUIPC7 installer. To use the trial license, you just need to download it and copy/move it to your FSUIPC7 installation folder and you are good-to-go. Sorry, but why are you doing this with the trial license - just use the key file as provided. If you have purchased a license and it will not validate, please see the section Invalid Key Problems in the Installation and Registration guide. John

That is interesting! I also used to have the phantom xbox controllers issue but I haven't seen this for a while. I will need to go over the old posts on this subject to refresh my memory... However, if it is due to FSUIPC7 trying to connect when MSFS is starting-up which is seems like, then could you please try with the latest version of fSUIPC7, 7.4.11. With this version, please tune the DetectToConnectDelayAuto parameter, as described here: Once you have done that, please try again and see if these phantom controllers have disappeared, If not, try increasing the , DetectToConnectDelayAuto parameter again by 5 (seconds) each time, to see if you can arrive at a value where these controllers disapear. John

The RegistrationChecker program was recompiled with the latest version of VisualStudio in release 7.4.10 - this was the only change. This has happened many times before and is always the result of a false-positive by the anti-virus software, I do not know how to investigate this issue "more serious" - what do you expect me to do? What you can do, as a BitDefender user, is to report this false-positive at the following link and this will be investigated/corrected by BitFinder: https://www.bitdefender.com/business/support/en/77209-343054-resolving-legitimate-applications-detected-as-threats-by-bitdefender.html From that page: The installer does non of those things mentioned, so I do not know why it is being flagged. John

Yes, by using the key assignments panel, and checking Select for Preset. Are your key presses recognised in that window? It has been reported that some special keyboard-type controllers (i.e. controllers that send key presses but are not actual keyboards) can have issues with key assignments. To fix this, you can use a keyboard hook by setting: UseKeyboardHook=Yes in the [General] section of your FSUIPC7.ini file. Don't set this if the keys are recognised without this setting. Not sure what this means... FSUIPC7 normally receives key presses from MSFS to trigger its key press assignments. It only sends key presses when configured to do so, and will only get the key presses from windows (not MSFS via simconnect) if a keyboard hook is being used. I don't have time to look into your other questions at the moment, I will take a look tomorrow. But why are you checking the status of the tail lock before controlling the starter/ignition? And rather than checking this in the preset, you can use an offset condition in offset 0z2A90 (see Advanced User guide for details on how to use offset conditions). More tomorrow.... John

What anti-virus software are you using? This is a false-positive and needs to be reported to the provider. You should add an exception to allow the RegistrationChecker.exe to run. Note this is a known issue with McAfree and has also been reported with other anti-virus software. It is also documented in the provided README.txt: It is also documented in the Installation and Registration guide, under Installation Problems. Please also note that you do not have to validate your registration each time you update FSUIPC7. This needs to be done once and only once, and a successful validation will generate an FSUIPC7.key file that contains your registration details. On subsequent updates, your details from the FSUIPC7.key file (previously generated) will be used to poulate the fields on the registration page, but you do not need to validate these again - just press on Skip. John

See I now consider this topic closed. If anyone is still having issues, please create a new topic and describe your issue there and attach your FSUIPC7.log and FSUIPC7.ini files. Make sure that you are using the latest available version (currently 7.4.11) and that you have configured the DetectToConnectDelayAuto and/or DetectToConnectDelay properties correctly for your system, as shown in that topic I referenced above. John

See John

Background FSUIPC7 is designed to be able to function whenever it is started - either before MSFS is started, during MSFS start-up or when FSUIPC7 is running, and in any state (e.g. in the main menu, when an aircraft is loaded, or when MSFS is in any other state). However, the recommended setting is to have FSUIPC7 auto-started with MSFS2020. Due to the variable start-up times of MSFS for each user (mainly due to the number of add-ons it loads, but also related to your PC specification), long start-up times can cause issues when FSUIPC7 is auto-started, or when started during the MSFS initialisation phase. This is because a response is not received from the initial connection request, and this response times-out after a pre-defined (and configurable) time-limit, and a new request is sent. A few re-connection attempts at start-up should not cause any issues, but too many attempts can starve SimConnect of available connections and then prevent other add-ons/simconnect clients from connecting/functioning correctly. It is therefore best to tune FSUIPC so that the connection attempt is delayed until MSFS is ready to accept this connection within a reasonable amount of time. There are three parameters that you can tune to get FSUIPC7 to connect at the right time and to avoid re-connection attempts. These are: DetectToConnectDelayAuto : this is the time/delay used, in seconds, between when FSUIPC7 detects that MSFS is running and when it first tries to connect, and is used when FSUIPC7 is auto-started (by MSFS) only. This has a default value of 60 (seconds), so FSUIPC7 will attempt to connect 60 seconds after it has detected that FSUIPC7 is running. This parameter has a maximum value of 500 seconds, DetectToConnectDelay : similar to the above, but used when FSUIPC7 is manually started. This has a default value of 1 (second), which is designed for use when FSUIPC7 is manually started and MSFS is already loaded, i.e. in the main-menu system or with an aircraft loaded and ready-to-fly. You should adjust this to the same default as DetectToConnectDelayAuto if you start FSUIPC7 before you start MFS, or if you start FSUIPC7 during the MSFS start-up process. This has a maximum value of 300 seconds. InitialStallTime : this is the time taken between issuing a connection request and cancelling/closing this request when a response is not received,. This has a default value of 30 (seconds), and a minimum value of 15 (seconds) when FSUIPC7 is auto-started. What this means is that FSUIPC7 will close/cancel the connection request and issue another connection request if a response is not received in 30 seconds. You can adjust this time, but it is better to first try and configure the other two parameters mentioned above first. Only adjust/increase this if you have reached the maximum value of the other parameters and are still having re-connection attempts. All of these parameters should go in the [General] section of your FSUIPC7.ini file. If they are already there, you can adjust them as needed (see below), and if they are not there they should be added. They will not be present by default. What to do when using Auto-connect (recommended) First run MSFS and let that load and auto-start FSUIPC7, Ince MSFS fully loads to the main menu, open FSUIPC7 (press Alt + F) and exit (File -> Exit). Then open the FSUIPC7.log file (which can be found in your FSUIPC7 installation folder - note that if you cannot see the file extensions, you need to change your Explorer options to not hide the extensions of known file types). Here is an example extract of the relevant section of a log file: From this log file extract, you can see the current value of the ini parameters being used: and that it is attempting to connect many times before a connection is obtained. The DetectToConnectDelayAuto value of 220 is used here: i.e. the difference between detection and connection is 220 seconds. This needs to be adjusted to prevent these sim connection attempts, so find the timestamps of the Simulator detected and SimConnect_Open succeeded log message: then subtract these values and divide by 1000 (to convert from milliseconds to seconds), so (396234 - 3172)/1000 = 393. So for this installation, you would add the following to the [General] section of your FSUIPC7.ini file: DetectToConnectDelayAuto=393 If you see several 'SimConnect_Open succeeded' messages, this implies that the InitialStallTime is being reached, and FSUIPC7 is still attempting to re-connect. In this situation, use the timestamp of the last 'SimConnect_Open succeeded' message to determine the value of the DetectToConnectDelayAuto parameter - don't adjust the InitialStallTime unless absolutely needed (see below). If you find that you are still getting re-connection attempts after setting the DetectToConnectDelayAuto parameter, you can adjust the InitialStallTime parameter. Start with a value of 45 and increase (up to a max of 60) until there are no longer any reconnection attempts. If you find that it is not possible to configure this to remove these connection attempts, please post your log file here and I will take a look. What to do when manually starting FSUIPC7 You should not need to do anything if manually starting FSUIPC7 once MSFS is up and running and either in the menu system or have an aircraft already loaded. If you start FSUIPC7 before MSFS, or early during the MSFS start-up process, you need to configure the value for the DetectToConnectDelay ini parameter in the same way as I showed how to configure the DetectToConnectDelayAuto parameter in the previous section, i.e. look at your logs and determine the time between detection and a stable connection and use that, John

What offset are you using? The current aircraft altitude should be available in offset 0x0570 (or 0x6020 for GPS altitude). and offset 0x0590 for the calibrated value. For target altitudes, see 0x0798/0x0818 and 0x07D4, and indicated altitude in offset 0x3324. Try logging those offsets using FSUIPC's offset logging facilities to see which one matches the value you see in the VC. There are also other offsets holding altitude values - take a look at the offset status document for details on each of these offsets. John

This log file shows that you are using a very old (and unsupported) version of FSUIPC7 (7.4.5). Please update to the latest and only supported version, 7.4.11. And please configure the DetectToConnectDelayAuto ini parameter as explained here now several times (I will also create a FAQ topic on how to do this). You should set the DetectToConnectDelayAuto ii parameter to an appropriate value for your system. You shouldn't need to set/change the InitialStallTime - this has now been set to a minimum of 15 (seconds) when FSUIPC7 is auto-started, which should be plenty of time if the DetectToConnectDelayAuto parameter is configured correctly, but you can also adjust/increase this if your log indicates that FSUIPC7 is re-connecting a few times during start-up. John

Executing a preset is exactly the same as executing the preset calculator code using ipc.execCalcCode() - they both resolve to the same underlying function. B-type variables are Input Events, bur not all such variables are currently accessible using the Input Events interface. You cannot control B-vars directly using calculator code. No, all on one line. @ark1320 is correct in his analysis of your calc code presets and how to toggle an lvar. But looking at your presets in the myevents.txt file they fon'y make much sense. As well as the errors pointed out by @ark1320, why are you using A:TAILWHEEL LOCK ON (and also K:TAILWHEELOCK) for almost everything? Maybe you could explain one function that you want to implement and I can show you how to do that, and you can take it from there. Note that there are known issues in trying to control the ATC menu - see here for example: https://devsupport.flightsimulator.com/t/sdk-0-23-1-event-id-atc-menu-open-not-recognized/8538 John