John Dowson

I don't know where IVAO and VATSIM take the altitude information. FSUIPC holds the altitude in various offsets, e.g. 0x0570 - Plane Altitude 0x3324 - Indicated Altitude (Altemeter reading) I have not had any reports of these offsets being incorrect, but I'll check them. I'm currently having some issues downloading/installing the latest update, but I'll check once resolved. John

As well as what Pete has said, I think for the FBW A320 you need to initially set-up the throttle via the flypad/EFB. See, for example, For the DC6, you should try the *_EX1 throttle controls, i.e. THROTTLE_AXIS_SET_EX1, or THROTTLE1_AXIS_SET_EX1 THROTTLE2_AXIS_SET_EX1 ...etc You can also try activating logging for Events and Axis Controls, then move the throttle in the UI to see what events/controls are logged, and then use those. For a full list of the controls/events, see the Controls List for MSFS Build 999.txt document which is generated when you run FSUIPC7 and located under your Documents folder in an FSUIPC7 folder, with the rest of the FSUIPC7 documentation. John

Please try the attached version, v7.2.5a. This version has been updated to SDK 0.14.0.0, and offset 0x3124 can be used to determine the connection status - it will contain 0 when disconnected and 110 (currently) when connected. I have also added some new events from the legacy gauges.h, but I still need to revise/update to the latest SimEvent status documentation. John FSUIPC7.exe

Offset 0x3124 (FS version) is set (to 110) when connected to the sim. I will i[date this offset to show the correct version and also reset this to 0 when disconnected, so that it can be used to monitor the connection state. SDK 0.14.0.0 has just been released, so I'll include this once I have updated to the latest SDK. I will update and release in the next few days.

@thomasl123 Also, please do not hijack unrelated threads. This thread was for an issue with the [Programs] section which is now resolved. I will now lock this thread.

That looks like a fault in FSUIPC7 as MSFS has crashed. Check your FSUIPC7.log file and it will probably have exited normally when MSFS crashed. A fault is generated as the simconnect connection is no longer available. If you look for other events, there will most probably be an MSFS CTD event before the FSUIPC7 one. If you don't think that is the case, please show me your FSUIPC7.log file.

BUS LOOKUP INDEX is read-only. This value changes when other controls are used, e.g. ELECTRICAL_BUS_TO_BUS_CONNECTION_TOGGLE. I added this to see if it could be used to control the batteries in the A320 as described in this post: However, it seems that these simvars are read-only Presumably you are trying to control the batteries in the FBW A320, no? If so, you can try the calculator code specified in the MF spreadsheet for A32NX_OH_ELEC_BAT1_TOG 10 6 (>K:2:ELECTRICAL_BUS_TO_BUS_CONNECTION_TOGGLE) 10 (>A:BUS LOOKUP INDEX, Number) (A:BUS CONNECTION ON:6, Bool) ! if{ 0 } els{ 1 } (>L:A32NX_OVHD_ELEC_BAT_10_PB_IS_AUTO) (L:XMLVAR_Momentary_PUSH_OVHD_ELEC_BAT1_Pressed) ! (>L:XMLVAR_Momentary_PUSH_OVHD_ELEC_BAT1_Pressed) A32NX_OH_ELEC_BAT2_TOG 11 6 (>K:2:ELECTRICAL_BUS_TO_BUS_CONNECTION_TOGGLE) 11 (>A:BUS LOOKUP INDEX, Number) (A:BUS CONNECTION ON:6, Bool) ! if{ 0 } els{ 1 } (>L:A32NX_OVHD_ELEC_BAT_11_PB_IS_AUTO) (L:XMLVAR_Momentary_PUSH_OVHD_ELEC_BAT2_Pressed) ! (>L:XMLVAR_Momentary_PUSH_OVHD_ELEC_BAT2_Pressed) (see https://docs.google.com/spreadsheets/d/1jTXlcHaJWx0B7TB63Pmma7bKwpxsxXJO6EJ3ECt7zpc/edit#gid=172455454) My MSFS is updating at the moment (and still 30GB to go....) so can't test this, will check it later. John

Is there an FSUIPC4.log file in your FSUIPC4 installation folder, i.e. under C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Modules ? If so, can you please show it to us? Thanks, John

Yep, not sure what happened... One thing you should do though is change the following settings in your FSUIPC7.ini file in the [General] section: TrafficStallTime=1 InitialStallTime=30 NormalStallTime=1 to TrafficStallTime=-2 InitialStallTime=120 NormalStallTime=-2 This will prevent FSUIPC re-connecting when data stalls, which can cause FSUIPC7 to run out of simconnect connections in some circumstances. Changing the traffic and normal stall times to a negative number will tell FSUIPC7 to just log a message when data stalls rather than re-connect. John

Well, I don't know what you did, but the WASM is now installed and working: 126469 Lvars/Hvars received - checking aircraft autos.... If you re-installed, it would install the WASM module by default. John

I will update to not enable the WAPI if the WASM module isn't installed to prevent this. The problem is that with the WAPI enabled, it doesn't start luas until the lvar/hbar lists are received, and as you have not installed the WASM, this will never happen.

Your log shows that you do not have the WASM module installed: 281 *** FSUIPC WASM module not detected - not adding WASM menu But you have activated the WAPI in your FSUIPC7.ini@ [WAPI] EnableWAPI=Yes Either install the WASM module (you can download the latest installer to do this - it has been updated to 7.2.4), or disable the WAPI if not using lvars/hvars/calculator code. John

Are you sure? Lua scripts are now not started until the aircraft is loaded and ready to fly,and if using the WASM module, lua scripts are not started until after the lvars have been received from the WASM module. Are you using the WASM module (i.e. do you have the WAPI enabled in your FSUIPC7.ini file)? Load an aircraft and get ready-to-fly. If your luas aren't started, shutdown MSFS and show me your FSUIPC7.ini and FSUIPC7.log files. Note I also just release v7.2.4, so you should update.

I have now added these simvars to offset 0x05D6: IS GEAR WHEELS - bit 0 / 0x1 IS GEAR SKIS - bit 1 / 0x2 IS GEAR FLOATS - bit 2 / 0x4 IS GEAR SKIDS - bit 3 / 0x8 This has been added to version v7.2.4 attached, which I will also release officially shortly:FSUIPC7.exe John

👍

Ah...this was corrected in v7.2.4.a posted to a similar support request the other day. However, I have noticed a small error in that version, should be corrected in the version below - can you please try this, v7.2.4b: FSUIPC7.exe You may need to change this line: Run5=CLOSE,C:\Simulator Control Program\GSControl MS-FS V10.1.4.exe to Run5=CLOSE,"C:\Simulator Control Program\GSControl MS-FS V10.1.4.exe" John

Please show me your FSUIPC7.ini. If the programs that you are starting take arguments (or contains spaces), the program command must be enclosed in double quotes. If the parameters contain path specifications (or spaces), then they must also be enclosed in double quotes.

What isn't working properly? As I said, this topic is for the Gear Floats issue, which I will look into adding. If you have any other issues or questions that are not related to this, can you please raise them in a separate topic, and provide enough information for me/us to help you. Your past few posts are rather short and cryptic and I don't know what you are trying to ask... John

All the FSUIPC manuals are installed under your windows Documents folder, for FSUIPC6 in a subfolder called FSUIPC6. John

Try activating logging for buttons and also events to see if the control is being sent in the second press. If its a sticky button, the second press may be a release, and if that's the case you should send the control on the release as well. Otherwise, check what control (and parameters) is sent when you arm/disarm using the UI, and use those controls.

No. Updating FSUIPC does not change any of your assignments.

I'm sorry, what does this mean? These were populated the last time I checked.... The topic of this post is 'IS GEAR FLOATS'. If you have other issues/questions, can you please raise them in a separate topic.

Sorry but I'm not sure what you are asking or trying to do. Are you using FSUIPC7? What is 'SendControlToFS'? The control available in MSFS are listed in a document in the FSUIPC7 documents folder called 'Controls List for MSFS Build 999,txt'. However, some controls listed are accepted but not implemented.

@imperial321 Please try the attached version, v7.2.4a. The show/hide hotkey should now also restore the FSUIPC7 main window if minimised on this version. FSUIPC7.exe John

To clarify, I will add the following simvars: IS GEAR FLOATS IS GEAR SKIDS IS GEAR SKIS IS GEAR WHEELS to a 1-byte bit-oriented offset. I can post a version here for you to test, if you let me know which version you are using. John