John Dowson

When you run the installer, the first thing that should happen is that windows should show a 'User Account Control' window that ask you to grant permission for it to modify your system. Check your task bar to see if that window is iconised for some reason. You can also try right-clicking and 'Run as administrator'.

No - you shouldn't need that.

Download an install (copy to your FSUIPC7 installation folder) the 64-bit GoFlight drivers from fsuipc.com.

Just download and run the installer. You can select where to install FSUIPC7 - you can install it anywhere you like, but you should not install it in a windows protected folder, such as under Documents or Program Files. There is no need to install or copy any dlls, unless you have GoFlight or PFC devices that require the drivers I provide. As for how to use, you need to refer to the manuals provided. I can help with specific issues, but you need to consult the manuals for an overview. Unfortunately they are only available in English for FSUIPC7. There are some manuals available in French for FSUIPC4 - most of this will still apply, but there are many new facilities relating to the use of the lvars/ hvars and presets/calculator code (via the FSUIPC WASM module) that are only documented un the FSUIPC7 manuals. John

Ok - if using reverse on the axis range, you have to configure idle to be at around -8000 in the EFB throttle config, and then you get reverse thrust in the -8000 - -16384 range.

First, there are now quite a few (423) MF presets available for the ATRs. These are relatively new and are not available in the events.txt file that comes with the latest version of FSUIPC7. The latest file that includes these events is attached - you can use it to replace the one in your FSUIPC7 installation folder: events.txt (The ATR presets start with MSATR) For the throttle configuration, this depends on whether you want a reverse axis on the throttle axis or not. If you want a reverse axis, then just assign your throttle axis/axes to Throttle 1/2 Axis Set Ex1. If you have a reverse axis configured in the EFB, then this will give you the full range of the throttle movement, including reverse. If you don't want to use the reverse range of the axis, simply go into the EFB and deselect/uncheck the Throttle Hardware has reverse axis option. This will then give you the range between F1/G1 (depending on state of Idle Gate) and full power (i.e. no reverse). You can also use a preset to control the throttle and limit its range (i.e. no reverse) without going into the EFB to uncheck for reverse thrust. This will depend on your throttle axis range, but for a standard range of -16384 - +16384, then the following preset (added to the myevents.txt file) will give the range between F1/G1 (depending on state of Idle Gate) and full power, even when the EFB throttle config is set to use a reverse axis: MSATR THROTTLE1 LEVER SET2#@ 16384 + 0.74414 * 8000 - -8000 max 16383 min (>K:THROTTLE1_AXIS_SET_EX1) MSATR THROTTLE2 LEVER SET2#@ 16384 + 0.74414 * 8000 - -8000 max 16383 min (>K:THROTTLE2_AXIS_SET_EX1) (what this does is add 16384 to your axis value to give a range between 0 - +32768, then scales this to give a range 0 - +24384, then subtracts 8000 to give the axis range as -8000 - +16384, idle to full) To assign to these presets, once added to the myevents.txt file, check Select for preset and assign to the preset on the axis in the left-hand side of the panel, as you would to any other axis control. However, I do think it is (probably) better to just assign to Throttle 1/2 Axis Set Ex1 and then calibrate in the EFB, either with or without the reverse thrust. NB I'm not sure how to get into reverse thrust yet even when using the axis - it doesn't seem to go into revere even when full reverse set on the lever (I am probably missing something here...). Therefore probably better to use the no reverse thrust EFB config option for the time being. I will look into reverse thrust config another day, but If anyone has reverse thrust working, on an axis or otherwise, please let me know how this is configured on the ATR... I also find it useful to set a switch (or button) for the throttle idle guard, using the presets MSATR_ENG_IDLE_GATE_FLT_PUSH (on press and MSATR_ENG_IDLE_GATE_GND_PULL (on release) - note that MSATR_ENG_IDLE_GATE_TOGGLE is also available. For the condition levers, you can use the following presets (again, add to your myevents.txt file): MSATR CONDITION1 LEVER SET2#@ 16384 + 10923 / near 0 max 3 min (>L:MSATR_CONDITION1_POS) MSATR CONDITION2 LEVER SET2#@ 16384 + 10923 / near 0 max 3 min (>L:MSATR_CONDITION2_POS) If you assign an axis to those presets, this will give you the 4 discrete positions (0-3) over the full range (-16384 - + 16384) of the axis. Also make sure that you do not calibrate the throttle axis in FSUIPC - make sure that you have a profile-specific calibration section, and reset the calibration for the throttle on pages 1 and 3. John [N.B. I have added a '2' to the preset names to distinguish them from the MF presets, which are documented on the HubHop site but don't appear yet in the events.txt file]

Why don't you try looking at this yourself? Keep a backup/safe copy of the working script, and then try removing/commenting out (using '--') the functionality that you don't want to use...

The OP seemed to have issues setting this up in FSUIPC and so is using MSFS. He has a JetMAX 737 Throttle - not knowing this throttle (or having the aircraft) it is difficult for me to advise on what the issue was, but if he is happy with configuring the throttle in MSFS then I am not going to spend any time looking into this. However, I see the ATR bundle is on sale (for just over 12euros), so I'll probably buy this and take a look later in the week, and see how to configure with the throttles I have (Honeycomb Bravo and a Saitek X-55). Thanks for your help with this. John

Sorry for the delay - I had some windows issues with my external displays to my development laptop not being recognised via its docking station... I have set this up on my network now - and I don't see any delays! The client FSUIPC version picks-up the offset change pretty much instantaneously (or at least in < 1s). I have no issues with the pack/unpack calls taking so long... Are you running the luas in debug mode? If so, please don't do that. Also, can you turn off logging for Lua Plugins, and also turn off Log Lua Separately. Modify your lua client/server scripts to add logging using the ipc.log function, e.g. client server: Then show me/attach the FSUIPC7.log files from both client and server. This is what I see in the logs, using offset 0x0264 (the pause indicator offset): Server: Client: John

If editing the calibration options, either do this when FSUIPC7 is not running, or have the axes assignments panel open on the calibration tab and click the "Reload all settings" button after saving your changes. I didn't realise the ATRs were a payware add-on...I don't have this add-on so unfortunately cannot provide any further assistance in how to configure the throttles in FSUIPC7 for these aircraft. John

Just download and run the latest installer/version (4.977), available from either fsuipc.com or from the download links sub-forum here. If you have installed FSX from a boxed version, you will need to install the FSX service packs SP1 and SP2 first (if not included in your boxed version).

All assignments are stored in your FSUIPC7.ini file, located in your FSUIPC7 installation folder. If you have lost your assignments, then you have either re-installed into a different location, or you have manually removed/edited that file. Defining presets is a community effort driven and hosted by MobiFlight. I just provide the mechanism that allows them to be used as well as the latest events.txt file provided by MF at the time of release. If you have any questions on presets for a specifi9c aircraft, you should ask about this on the MobiFlight discord channel. John

Presets are stored in the events.txt file - did you install that component when you installed? If not, you can also download it from https://hubhop.mobiflight.com/presets/. Otherwise, please show me your FSUIPC7.log file.

What changed? I do not understand what you mean when you say "it does not load when pressing the hotkey" - could you please elaborate? Also, please attach your FSUIPC7.ini file and an FSUIPC7.log file generated with logging for Buttons & Keys as well as Events activated.

There is an auto-save toggle control called Auto-save Toggle (1151) that can toggle the auto-save feature on and off. once activated. You can either toggle this manually (or on gear up/down), or you could write a simple lua script that monitors the plane altitude (using event.offset on offset 0x0570) relative to the ground altitude (offset 0x0020) and then toggles the auto-save off when the difference between these two values is < 1500ft and back on again when > 1500ft. If you want to try that, I can help if you have any issues. Give it a go and show me the lua if you have any issues. John

Sorry I am a bit late to this one... Looks like you have solved your issue thanks to @target11 so I won' t read this in detail, but there are a few points you should be aware of: 1. The change UseProfiles=Yes --> UseProfiles=Files just makes FSUIPC use separate files for profiles. Without this. you can still use profiles (unless you set this option to No) - there is no change in the profile functionality. The Profile folder is only created once this option is set to Files. 2. The Ignore axis button is just used in the assignments panel, it has no affect when the axis panel isn't open. If you don't have a profile for an aircraft, the general [Axis] section will be used. Also, be aware that if you, for example, create a profile-specific [Axes.xxx] section for an aircraft, but not a profile specific [JoystickCalibration.xxx] section, then the general [JoystickCalibration] section will be used. So, if you want to assign an axes for a specific aircraft in MSFS rather than in FSUIPC, not only do you nee to create an empty profile-specific Axes section, but you should also create a profile-specific calibration section and remove/reset the calibration for each axes assigned elsewhere. If you don't do this, FSUIPC will still calibrate the axes assigned elswhere. 3. I am surprised that you need to set this option. I haven't looked at the ATR yet (I will do later), but you shouldn't really need to change this option if assigned to the correct axes control and with the No Reverse Zone option checked/unchecked as appropriate for yout throttle and aircraft. I will take a look at this in the ATR later. John

There is no offset for battery 2, If using the A320neo. you could try adding the simvar ELECTRICAL MASTER BATTERY:2 to a free FSUIPC7 offset as an unsigned byte (UB). Detail on how to do this are on page 34 of the Advanced User guide. Otherwise, list the lvars and see if any of those hold the battery state, and if so you can use that.

Ok, thanks for the update Leo. I was going to look into this today and that has saved me some time! Cheers, John

The license has been updated, valid until 1st June 2023. John

Try the attached version, 7.3.21a - add ShowSplash=No to the [General] section of your FSUIPC7.ini file. John FSUIPC7.exe

There is a lua script available for this in the User Contributions sub-forum: The script should work in MSFS for the audio callouts, but the display facilities currently won't work unless they are using the Wnd library, which I doubt. You should also be able to disable the display facilities, or create your own lua from this.

I am not sure I fully understand your issue - it would help if you could attach the lua file that is causing this problem, as that would be where the solution. if any, would need to be applied....

Ok, that is the FSUIPC7 splash-screen. That is always displayed when FSUIPC7 is started, so that you know its running, as it starts and sits in your system tray. You cannot turn this off at the moment, but I guess I could add an option to do this. But I don't see why this is an issue, and if disabled, there would be no indication that FSUIPC7 had been started. If this really is an issue for you, I can add an ini file option (in a future release) for this to be disabled.

No, they shouldn't conflict as only one (the first match found) will ever be used. Just makes things a lot easier, and by using aircraft substrings, the same aircraft with different liveries will also match, and so saves you having to add an aircraft to a profile when you are using a different livery. Looks a lot better/cleaner, with one profile for the PMDG 737/777 and 757, and another for the PMDG 747. Note that you were previously also assigning the steering tiller to the same axis as the rudder (which is common) but only in some of your old profiles, You may want to consider addung this back to both of your current profiles.

But why would you want to do this? Why do you have several profiles for the 747? You only need separate profiles if the controls/assignments are different - they should be the same in all 747 variants, so you should only need one profile. Usually you would add an aircraft to an aircraft profile rather than creating a new profile. And rather than adding each livery, you should change the names used in the profile section, so if you change: to then that would match all 747-8 aircraft, or you could change to to match all 747s, and you can even add the 757 as that looks to be the same: There are slight differences in rudder/steeringtiller assignments, but I would have thought this should be the same for all 747 variants... Similarly, you probably only need one profile for the 777.