John Dowson

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

Currently not. It is listed in the offset spreadsheet document (for FSUIPC7 / MSFS), but it has not yet been allocated to an offset. I can add this for you (if using FSUIPC6 or FSUIPC7 - other versions are closed for development). Which version are you using? John

When you minimise, it goes to the task bar not the system tray. To get the window back from the task bar, you have to click the FSUIPC task bar icon. If in full screen mode, you would have to exit this first using alt+enter. As Pete says, best to close to the system tray instead (either by clicking the X close button or the File -> Close menu option), especially if using MSFS in full screen mode (i.e. no task bar). I will look into also un-minimising from the task bar with the open/show hotkey.

FSUIPC just logs all events seen by SimConnect. Many aircraft (more in MSFS2020) and especially add-on aircraft can continually log events. Also, some controllers (notably the new Honeycomb bravo and alpha) have always on buttons, which, if assigned in the FS (FSUIPC assignments don't have this problem) can also continually be activated and send such events. So, if the controls are something that is actually being sent by one of you assignments, then you need to look into which button/assignment is sending those and check that assignment. If it is just something that the a/c model is using internally, then you can ignore such events using the DontLogThese ini parameter. Check the Advanced User guide for details. It goes in the [General] section, and for some versions of FSUIPC it can also be used in the [Profile.xxx] sections, but I can't remember off-hand if I added that in FSUIPC5 (for sure in FSUIPC6 and FSUIPC7). John

Did you check available lvars? The following are available (in the FBW mod version): A32NX_ECAM_ALL_Push_IsDown A32NX_BTN_TOCONFIG A32NX_BTN_CLR Not sure about the stock A320Neo. The MobiFlight spreadsheet is a good source of information on lvars, hvars and calculator code to use - see https://docs.google.com/spreadsheets/d/1jTXlcHaJWx0B7TB63Pmma7bKwpxsxXJO6EJ3ECt7zpc/edit#gid=172455454

New one posted, valid until 5th August.

No, as FSUIPC4 was closed for future development quite a while back.

There was an issue processing the command when enclosed in quotes which resulted in the parameters not being passed. I'm surprised this issue hasn;t been picked-up before - it must have been there for years!

Btw, you have set-up all your assignments in a profile, and don't have any general assignments for axes or buttons. It is generally better to set-up a general profile first, for all your main axes and button assignments. Then you can create profiles with this as a starting point, and change/add whatever is needed for that profile. Doing it this way, you will at least have basic controls assigned for all aircraft. As it stands, if you load any other aircraft apart from the Cessna 152, you will have no assignments.