John Dowson

You could also maybe try AXIS_COLLECTIVE_SET (the old helicopter throttle axis). Also try looking at the input events to see if there is anything there that controls the throttle. If there are any input events available (the number of input events available is logged in FSUIPC's main window), first list them (Log->List Input Events), If there is anything that looks applicable, log input event changes (Log->Input Events) and turn the throttle in the VC and see what is logged, and get the max/min values for the input event. If anything exists, I can show you how to use this to assign to your axis. You can also check for lvars to see if there is anything there that looks throttle related. John

There are multiple (helicopter) throttle axes - have you tried HELICOPTER_THROTTLE1_SET? If there is only 1 throttle, also try HELICOPTER_THROTTLE_SET or maybe AXIS_HELICOPTER_THROTTLE_SET These are the (newish) helicopter axes available: 67526 HELICOPTER_THROTTLE_INC 67527 HELICOPTER_THROTTLE_DEC 67528 AXIS_HELICOPTER_THROTTLE_SET 67529 HELICOPTER_THROTTLE_SET 67530 HELICOPTER_THROTTLE_CUT 67531 HELICOPTER_THROTTLE_FULL 67532 HELICOPTER_THROTTLE1_INC 67533 HELICOPTER_THROTTLE1_DEC 67534 AXIS_HELICOPTER_THROTTLE1_SET 67535 HELICOPTER_THROTTLE1_SET 67536 HELICOPTER_THROTTLE1_CUT 67537 HELICOPTER_THROTTLE1_FULL 67538 HELICOPTER_THROTTLE2_INC 67539 HELICOPTER_THROTTLE2_DEC 67540 AXIS_HELICOPTER_THROTTLE2_SET 67541 HELICOPTER_THROTTLE2_SET 67542 HELICOPTER_THROTTLE2_CUT 67543 HELICOPTER_THROTTLE2_FULL 67544 AXIS_CYCLIC_LATERAL_SET 67545 AXIS_CYCLIC_LONGITUDINAL_SET 67546 CYCLIC_LATERAL_LEFT 67547 CYCLIC_LATERAL_RIGHT 67548 CYCLIC_LONGITUDINAL_DOWN 67549 CYCLIC_LONGITUDINAL_UP

No. As I have said, you need to use the camera state to see if there has been a restart. MSFS does not provide any events/information when a flight is restarted, so it was never possible to detect this in FSUIPC. However, since the addition of the camera state variable (in late 2022) you could use this, as I have said. This is basically correct although a little outdated. To be more precise, the luas are started in order on initial load of an aircraft and once the available lvars have been received and are available, and are stopped/killed whenever you go back to the main menu (i.e. end the flight).

Please use the specific sub-forum for all issues/questions with FSUIPC7 and MSFS2020/MSFS2024. Previous speed issues (usually during climb) have been reported (several times) with PMDG aircraft, and this has been attributed to flaps assignment. Please see the following post: Thats for the 737 but should also apply to the 777. If that is not the issue, then I would need to see your FSUIPC7.ini and FSUIPC7.log file (with appropriate logging activated showing your issue). But please see that topic first, and at least attach your FSUIPC7.ini so that I can see your assignments. No point in posting images. John

Displaying text in (simconnect) text windows has been broken in MSFS for a long time...it did work in limited circumstances in earlier versions of MSFS but has been broken for a long time. The MSFS SDK SimConnect_Text function has basically now been removed from the MSFS SDK and it is no longer possible to use any of the text display functions (to external windows) that use this. The only way now that can be used to display text in an external window is to use the lua Wnd library. Due to this, the FSUIPC offsets for text display also no longer work (they should be marked as such in the offset status document). I have been meaning to update these offsets to use an external window as provided by the Wnd library, but just haven;t had time to look into this in detail so far. So your only option for text display in a separate window is to use the lua Wnd library at the moment (and for the foreseeable future). No, FSUIPC does not do this - if assigned to an axis, it sends the axis controls regardless of aircraft. You should be able to use axis assignments with PMDG. The issue with axes assignments in PMDG is not the assignments, but the calibration. If you assign using 'direct to FSUIPC calibration' and calibrate, this should work. But if not, you should assign using 'Send to FS as normal axis'. I think the problems are caused when assigning using 'Send to FS as normal axis' and then calibrating in FSUIPC, due to conflicting event priority levels between the PMDG aircraft and MSFS. However, I am not 100% sure on this (I don't generally use/fly PMDG aircraft, but do have some to investigate issues). I am not that familiar with the MSFS version, but perhaps this also has to do with how they are set-up in the flypad (if my memory is correct, although this may be for the FBW...). But if you have any issues, let me know and I can take a look. No problem - and thanks for your kind words. John

I have taken a quick look and offsets 0x3364 (ready-to-fly flag) and 0x3365 (in-menu/dialog flag) can't be used for this. The camera state offset 0x026D goes to 11 (waiting) then back to 2 when you restart a flight, so try that. I will look into updating the ready-to-fly offset 0x3364 to reflect the correct state, John

If you use lua auto-start, the lua is always started when the flight starts, and killed when the flight finishes. For restart, check the camera state, as advised. It will go through various values then back to 2 when the flight is ready. You should log the value of this to see what values it goes to on restart before back to 2.

Can you clarify what you mean by this? What does this mean? Do you have a reference? I'm not exactly sure what you are after, but maybe try logging the camera state offset, 0x026D. This will go through various values and then back to 2 (cockpit) (or maybe 3 - external/chase). If you log this offset, you can probably determine the value changes you need.

Yes - that is strange - maybe they are just events that are continually being sent. Many aircraft do this, and such events can be ignored using the DontLogThese ini parameter (see the documentation on using this). However, I do see that you have an axis assigned to Flaps using 'direct to FSUIPC calibration' but have not calibrated the flaps. Does this work? Usually such flaps assignment with PMDG aircraft can cause issues (especially loss of power on climb). The usual method to assign flaps for PMDG aircraft is to use the custom controls (or also preset in MSFS) to be sent on entering/leaving an axis range (i.e. using the right hand side of the axis assignment panel) - see the following topics: As for your reverser 2 issue, there is nothing I can see in the logs. One thing that can prevent the reverser activating is if the throttle is not at 0 (can be changed by setting the MaxThrottleForReverser ini parameter). So it may be worth logging the throttle values to check these are 0 - to do this, add logging for both offsets 0x088C and 0x0924 as S16. Your throttle1 and throttle2 calibrations are also different around the null zone: It is strange that the lower number is positive and not negative...although these values shouldn't really be used when calibrating throttles with no reverse zone - but maybe just set them to be the same values in the ini, just to be sure. You can also check that the out value of your throttle axes are both 0 (when no throttle is applied) in the axes joystick calibration page 3. Can you also check your assignments in MSFS are empty, just to make sure. Other than that, I will need to investigate here further as I am not familiar with the Reverser axes or how they are implemented, I won't have time today (finishing now for the weekend), but I will look into this further on Monday. John

I don't think this can have anything to do with anything in the last update, but I have attached the previous version below so that you can test with this to make sure. Just temporarily rename your current FSUIPC7.exe, download the attached to your FSUIPC7 installation folder and test with this version: FSUIPC7.exe The attached log file is of no use as there is no additional logging. Could you set logging for Events and Axes Controls and generate another log file showing your issue, and attach that together with your FSUIPC7.ini file and I will take a look. Use both Reversers 1 and 2 so that I can see any differences. Use the latest version for this! John

Note that you can do such things using calculator code (or by defining a preset for the calculator code), e.g. (A:PLANE HEADING DEGREES MAGNETIC, Degrees) near (>K:HEADING_BUG_SET)

There is no need to purchase twice... If your registration details won't validate correctly and you are sure that you have entered them correctly (using cut and paste), then it will most probably be due to not having the correct/required VC++ redistributables installed. Please see the Installation and Registration guide, section Invalid Key Details. This issue has been reported many many times and my answer is always the same. PLEASE read the documentation before posting, and also please check for similar issues. I have also moved your post to the FSUIPC7 support sub-forum. John ...etc

What aircraft are you using? Look for available presets - either using the Find Preset button in FSUIPC, or search on the MobiFlight HubHop site (https://hubhop.mobiflight.com/presets/). You can also try listing available lvars (Add-ons->WASM->List Lvars) to see if any look applicable and if so try them. You can also use logging: set logging for Events, open the logging console (Log->Open Console) and then open the doors using the virtual cockpit and see if anything is logged, and if so, you can use that. John

👍

It shows the input events that can be used for assignments, to buttons/switches & key presses natively, or via lua for axes. The same as listing available lvars (via Add-Ons->WASM->List lvats). You can also log lnput event value changes by setting Log->Input Events. This is needed to determine the values (discrete or ramge) that the input event accepts and how they relate to the function (e.g. the value for each position in a switch).

What do you mean by 'hook' in this context? You assign to input events as you would any other event type, but by checking 'Select for Input Event' (but not for axes due to calibaration issues).. Ah, no - there is no event handling function for Input Events. You can add the input event to an FSUIPC offset (via the ini file) and use the event.offset function. See the Advanced User guide on adding Input Events to offsets - basically works in the same way as adding lvars to offsets, but using a different ini section. I will look into adding an event.InputEvent lua function in a fuuture release. John

For all auto-start issues, please see

From the first post: i.e. the current trial license is valid until (and including) the 1st September. I will update/replace this license on the 3rd or 4th September. John

👍 No bother!

The size/position coordinates are only used the first time a window is created. After that, its size/position is stored in your FSUIPC ini file, under the [ExtWindow] section. To use the new coordinates, delete the entry from that ini section. You can also move/resize the window using the arrow keys and the ctrl key to toggle between move and resize. You need to give the window the focus first. John

I have no idea. There is only one version of FSUIPC, and it can either be used with or without a license. You can also download from https://fsuipc.com/. If your key is not validating, it is most likely because you do not have the required VC++ redistributables installed. Please download and install the combined (ie. for 2015, 2017, 2019 and 2022) VC++ redistibutables, both x86 and x64, from https://learn.microsoft.com/en-us/cpp/windows/latest-supported-vc-redist?view=msvc-170 John

You need to install the GoFlight driver, most probably the 64-bit version (although you don't say what version of FSUIPC or simulator you are using). The GoFlight drivers are available from https://fsuipc.com/, together with a list of supported Go Flight devices. John

FSUIPC7 is not crashing - it is MSFS that is crashing, and FSUIPC7 was then exiting as MSFS was no longer available. You will also see an exception for FSUIPC7 when the MSFS SimConnect drops, but this is nothing to worry about. So your issue is that MSFS is crashing. I cannot help with this - please see the Asobo support forums for MSFS crashes. By the way, you seem to be running FSUIPC7 from your Desktop. This is generally not a good idea - you should at least create a folder and run FSUIPC7 from a sub-folder (and preferably not on Desktop or under Documents, i.e. not in a OneDrive folder). John

As I said, once you have assigned your axes to a profile, the only way of changing this is by editing the ini, either removing the aircraft from the profile, or deleting the profile-specific axis section.

Did you read the documentation? Please see the Installation and Registration guide, section Invalid Key Issues (or the provided READme.txt). In ALL cases, this issue is ue to one of three reasons, which are: 1. You do not have the required VC++ redistributables installed 2. You aare NOT entering the details exactly as given/provided (all 3 parts must match: name, address/email and key) 3. You are using an overly-aggressive anti-virus that is blocking the validation There is absolutely nothing wrong with the validation method. You need to read the documentation. Or see one of the many many support requests, e.g. I am continually asking people what the problem was once they have validated correctly but don't get any response, and i can only assume it is due to the fact that they have either not read or nor understood the documentation. Note I have also updated the topic of this support request. Please always give an appropriate topic for your issue - 'FSUIPC7' means nothing as it applies to every single post in this forum. And please look for similar topics before posting - this one has now been reported hundreds (if not thousands) of times. John