John Dowson

None of the throttle controls seem to work any more in the TBM930 (via simconnect). I have tried various controls, the axis ones and also including the throttle 10/20/30/.../90, throttle inc, throttle dec, and non seem to have any affect. The only thing that seems to work is F2 and F3 keys for throttle dec and throttle inc respectively, but sending these controls via SimConnect has no affect. This was previously working so must have broken in a recent update, SU7 maybe. Not sure what to advise at the moment - maybe try assigning this in MSFS, or try one of the TBM 930 mods to see if this is fixed in one of them - maybe the Mugz mod fixes this. There are various reports of the throttle being broken since SU7, e.g https://forums.flightsimulator.com/t/fixed-reverse-throttle/479301/8 John

Also, are you sure that it is IAS/TAS that you need? No wind element can be derived from IAS/TAS. You would need TAS and GS. The wind only affects GS not the craft’s airspeed. The difference between IAS and TAS is caused by air density. At low altitudes they are pretty nearly identical, but at higher altitudes the measured airspeed (IAS) is lower than the true airspeed (TAS) because there’s less pressure. John

Hi, sorry for the delay in replying. This is an area of FSUIPC that I am not that familiar with (at the moment!), but I have discussed this with Pete. First, it seems that you would like one of two options: 1. Adding NMEA out sentences for $GPMWV / $GPMWD, or 2. Add IAS/TAS info, via custom NMEA sentences, so that wind info can be calculated from external sources Is this correct? For 1, I am not sure that this information is available. There are simvars for ambient wind relative wind velocity: AMBIENT WIND DIRECTION: Wind direction Degrees (TRUE, not relative) AMBIENT WIND VELOCITY: Wind velocity Knots AMBIENT WIND X: Wind component in East/West direction. Meters per second AMBIENT WIND Y: Wind component in vertical direction. Meters per second AMBIENT WIND Z: Wind component in North/South direction. Meters per second STRUCT AMBIENT WIND X: (latitude), Y (vertical) and Z (longitude) components of the wind. Feet per second RELATIVE WIND VELOCITY BODY X: Lateral speed relative to wind Feet (ft) per second RELATIVE WIND VELOCITY BODY Y: Vertical speed relative to wind Feet (ft) per second RELATIVE WIND VELOCITY BODY Z: Longitudinal speed relative to wind Feet (ft) per second I could possibly construct a MWC sentence using these ambient wind simvars - from the NMEA 0183 protocol: MWV Wind Speed and Angle 1 2 3 4 5 | | | | | $--MWV,x.x,a,x.x,a*hh 1) Wind Angle, 0 to 360 degrees 2) Reference, R = Relative, T = True 3) Wind Speed 4) Wind Speed Units, K/M/N 5) Status, A = Data Valid 6) Checksum However, I have no details on the sentence to be used for MWD - from the same document: MWD Wind Direction & Speed Format unknown Do you have any details on how to construct such a sentence? Or would just adding the MWV sentence suffice? For 2, do you have any information on the custom sentences required? IAS is already included in the RPY sentence (as speed KIAS*10). but not TAS. John

Yes, but that was not the issue. It seems quite a few ACARS systems use the FSUIPC offset 0x0BC8 to determine the state if the parking brake. The OP wants the value of the lvar L:A32NX_PARK_BRAKE_LEVER_POS to be used instead, so I provided a lua script to spoof offset 0x0BC8 with the value of that lvar, i.e when that offset is read from an external app, it is actually reading the value of the lvar. The script wasn't working initially, not sure why, but the OP has resolved the issue and it is now working. John

So your P3D windows go black when you select any menu option? That does sound like an issue with P3D... The P3D windows will go black when you open FSUIPC - this is normal. If the FSUIPC main window isn't being shown, it is because it is positioned outside of your screen dimensions. If that is the case, remove the ini parameter OptionsDialogOffset from the [General] section of your FSUIPC6.ini file - this is the ini parameter that saves the position of the FSUIPC main window. John

If using windows 11, you need to set the following ini parameter in the [General] section of your FSUIPC7.ini file: DisableMSFSMonitor=Enum Otherwise, please show me you FSUIPC7.log file. To remove FSUIPC7, just run the uninstaller, or uninstall from the windows app management page. To temporarily disable (i.e. not auto-start with MSFS), just rename the FSUIPC7.exe, or remove the FSUIPC7 entry from your EXE.xml (or rename that file if FSUIPC7 is the only entry). Only in the Installation folder, your Documents folder, and the EXE.xml to auto-start. You can check your InstallFSUIPC7.log to see where and what is installed. John

Yes, I know - that is what I was trying to tell you! However, still something strange going on, as the log says that 4 hvar files were loaded, with a total of 436 hvars. I don't understand this as you had 2 hvar files loaded, with 72 in each, so 144 hvars. Can you explain that? This is what I will look into - something is going amiss somewhere.... John

So you have two hvar files that match (on a substring match), A320.hvar and FlyByWire_A320_NEO.hvar. So it is loading both. It is designed to load ALL hvar files that match. Remove the A320.hvar file or rename to match the Asobo A320, whatever is correct. But there certainly is something strange going on...it has found the 2 hvar files, each with 72 unique hvars. But then it says: [DEBUG]: 4 HVAR files loaded (max client data size=8192) ... INFO]: 436 hvars loaded for aircraft 'Airbus A320 Neo FlyByWire' I will look into this tomorrow, to see if I can reproduce. John

Have you added the event file containing those events to your FSUIPC7 installation folder? If not, do that. The event file for those events is called flybywire-aircraft-a320-neo.evt and is located under the EventFiles folder of your FSUIPC7 installation. Move that file up one folder, to the main installation folder. John

I can only assume that two hvar files are being loaded. Activate debug logging in the WASM and check your FSUIPC_WASM.log - that should tell you what is going on. Any doubts, post that file here. John

All versions of FSUIPC prior to FSUIPC6 were installed in a folder called Modules that resides under the FS main folder. However, from FSUIPC6 and onwards, this requirement was removed and you are free to install FSUIPC in any folder you wish. If any documentation refers to the Modules folder, just read this as your FSUIPC6 installation folder. If you do not know where your FSUIPC6 installation folder is, then use the Open Folder button from the FSUIPC logging tab. Note that you misy have either selected the installation location or have accepted the default installation location. This used to be the prepare3d add-ons folder (Documents\Prepar3D v5 Add-ons\FSUIPC6) but I think I changed this to just C:\FSUIPC6. Either way, it is a folder that you select/confirm during the installation process, so you should really pay attention to know where you installed FSUIPC6. If you are using the add-in xml installation methid, the FSUIPC6 add-on.xml file will be under Documents\Prepar3D v5 Add-ons\FSUIPC6. We recommend that you do NOT use the same folder for your actual FSUIPC6 installation. As for recommendations, I install mine under (FlightSim)D:\\Prepar3D v5 Add-ons\FSUIPC6, but any folder NOT under your FS main folder and NOT in a windows protected folder (such as Documents, Program Files, etc) is fine. John

If you want to configure an action for a key press, you configure under "Key presses". I would have thought this was obvious.... Before anything else, please review the documentation - you should at least read/peruse the User Guide so you have an idea of the functions available. Also a good idea to take a look at thee Advanced User guide, so you at least have an idea in the various functionality available. There is no such list. For the events/controls that are available, there should be an automatically generated document (in your FSUIPC7 Documents sub-folder), called Controls List for MSFS Build 999.txt. Additional FSUIPC controls are documented in the Advanced user guide. Be aware that many aircraft, especially complex aircraft like the FBW A320, use lvars, hvars, or a combination of both using calculator code. You can find a list of MobiFlight presets for many aircraft, including the FBW A320, at https://hubhop.mobiflight.com/#/list. It maybe easier, if you are new to lvars, hvars, etcm use the presets directly. To do this, you need to install the MobiFlight WASM module. Once you have done this, MobiFlight event files can be found under the EventFiles sub-folder of your FSUIPC7 installation folder. Yo use these, copy them to the main installation folder (i.e. up one level), and you can then assign directly to these MobiFlight events/presets - but you must have the MobiFlight WASM module installed. Alternatively, you can use the preset definitions to perform the same action by using lvars, havars or calculator code directly in FSUIPC, but to do this you need to understand how to use these. Details are in the Advanced User guide, as well as in the user guide. For your specific example: Looking at the MobiFlight hubhop page, you will find the following related presets for this: PUSH_OVHD_CALLS_ALL_OFF PUSH_OVHD_CALLS_ALL_ON So, if you install the MobiFlight WASM, move the A32X-FBW2.evt file (that event is located in that file) to your main FSUIPC7 installation folder, you can then assign directly to that preset. However, looking at that preset, it simply toggles the lvar L:PUSH_OVHD_CALLS_ALL between 1 and 0. To do this in FSUIPC, you can assign the lvar to an fsuipc offset, and then use the Offset Byte Togglebits control. Please see the section on lvars and adding lvars to offsets on P43 of the Advanced User guide. A very similar example is given (i.e. adding a boolean lvar to an offset and then assigning a control to change that lvar) which you can follow and adapt to your own needs (i.e. change the lvar name). John

The window labeled "Lockheed Martin Prepar3D v5 with Wideserver: waiting for clients" is the P3D main window, the other a P3D dialog box - not sure which one. Did you get the confirm exit dialog box from P3D, or do you have that option disabled? It might, but I cannot tell from the information you have provided. Please show me your FSUIPC6.log file. John

Those all look good! Looks like you also have MSFS installed. Is everything now working ok? Looks like you haven't connected your Logitech G13 Joystick though. Are you not planning to use this?

No time wasted - glad you got it sorted. John

Well, as I said, you should just gave checked if the lvar was available and that its value changes as appropriate. Please remember this as it is always the first thing to try when using lvars. John

As I said, check the lvar is available in whatever version you are using, and check that the lvar value changes when the parking brake is engaged or disengaged. The script depends on that lvar being available and working. I haven't checked this for many months, things may have changed. I will also take a look when I get a chanve. John

His settings were included in the post: If you would like clarification from the OP, try notifying him directly (using @jkeye). John

If you have already purchased WideFS7 with FSUIPC4 (WideFS7 is the only WideFS version compatible with FSUIPC4), then you do not need to repurchase - just use the license you have. The bundle offer has (and has always) been for FSUIPC4 + WideFS7, so if you did purchase that you will already have a WideFS7 license. I should really also make the same bundle offer for FSUIPC6 + WideFS7, and FSUIPC7 + WideFS7. I will look into this. John

The standard method of doing this when no fast controls are available, is to use offsets. The Kohlsman setting is held in offset 0x0330 as a 2-byte integer (also 0x0332). You can assign to the control Offset Uword Increment/Decrement control, specifying the inc/dec value you wish to use. Try logging the offset first and manually changing the baro setting to see what sort of in/dec value you need.

What do you mean by the 'default' FBW - are you using the stable or development version? If the former, try the latter. This was previously only tested on the dev version. The MobiFlight hubhop preset list (https://hubhop.mobiflight.com/#/list) lists this lvar as belonging to the A320-SDKm so not sure which versions it is available in (but I would have thought both, but maybe this is not the case). Your log shows that the lvar read is not changing value. Can you try listing the available lvars, using the Add-Ons->WASM->List Lvars menu item. Can you see the lvar there? If so, try changing setting and clearing the parking break to see if this changes value. Check in both the stable and dev versions. John

Are you sure? If you are using it with FSUIPC4, it must be WideFS7. Anyway, check your SimMarket account. Regards, John

Not exactly. If you want to run 2 copies of MSFS at the same time, you would need 2 licenses. BUT, these would be independent, i.e. what is happening on one version of MSFS has nothing to do with what is happening on the other - they are not connected. You probably want something like WideView - see https://www.wideview.it/ John

If you only have one MSFS license, you can only run one copy of MSFS at a time. I guess if you have two license you could run two copies, but they would be independent. I am not sure what those programs are that you want to run on a second computer. If they are FSUIPC client applications, then you can achieve this by using WideFS7, or also now by running FSUIPC7 on the second (client) computer to provide WideFS-like (or light!) functionality. To do this, see Otherwise, if your applications are SimConnect based, then it should be possible to run them by setting-up a networked SimConnect connection, as shown in that link above (for FSUIPC7).

Hi Andrew, Do you really have > 400 hvars for the aircraft you have loaded (FBW A320?)? If you have any updated hvar files, could you share them so that I can include in the FSUIPC7 installation package? The ones currently included have not been updated for quite a while and are surly quite out if date... John