John Dowson

It should do when no braking is applied... No - the script controls differential braking, which activates when the brake lever is pressed and the rudder has > 16 degrees deflection. There is no differential braking without using the script, unless you have also assigned that directly to your rudder axis. as it is supposed to... Of course, as it is being steered by the rudder. Are you saying that you do not want any rudder changes deflection to be sent when on the ground? Any rudder deflection will effect the steering when on the ground. Why would that help? You can use the letter or the id/number, but the result would be the same. Note that no steering controls are being sent - only rudder controls. It is this that is steering the aircraft when on the ground. You can prevent this, but then you would also see no rudder deflection when moving the rudder when on the ground. Try the attached script for this. i.e. rudder controls only sent when airborne. Please look at the scripts and work out what is happening. If you understand them, you can modify them yourself to suit your needs. John nanchangBrake.lua

You will automatically get a discount on check-out if you have purchased an earlier version of FSUIPC, otherwise no discounts.

Does not match what? What do you mean by this? The ini file does not match anything.... it is unique to your system and set-up. Your ini looks like a default ini file - no profiles or assignments, and with one lua file recognised (PMCO_FNX32X.lua). You have to configure/set-up FSUIPC7 for what you want to use. Please see the provided documentation - start with the User guide and also look through the Advanced User guide. This will give you an idea of what you can do with FSUIPC7. Otherwise, please explain why you think you have an issue, and what you actually want to do with FSUIPC7. Also, before purchasing FSUIPC7 I recommend trying the trial license first (available at the top of this forum) to make sure it is suitable for your needs. But too late now! John

See this post on how to assign the Bravo trim wheel for default elevator trim controls (and AP functions): This uses a lua script for fast/slow trim control, and uses FSUIPC offsets to set the trim value. You can increase/decrease the delta for both the fast and slow trim buttons if required. This is the standard way to set-up a trim wheel in FSUIPC, providing the aircraft supports the standard controls. If not, you can still use the lua script (for fast and slow virtual buttons), but you would need to change the assignments to the fast/slow virtual buttons to whatever controls the trim in the aircraft (n the aircraft profile). Checked in the DA62 and those assignments are valid for this aircraft, but you probably want to increase the delta values - the current values of 24 (for slow) and 50 (for fast) seem a bit low. Just increase them to whatever feels good for you. There isn't much documentation that I know of, only this: https://docs.flightsimulator.com/flighting/html/Additional_Information/Reverse_Polish_Notation.htm John

I get a similar rate (i.e. every 800ms or so) when lua plugin logging is enabled: but if I turn off lua plugin logging the rate increases to roughly every 63ms (and faster rates if I reduce the ipc.sleep delay at line 59, which defaults to 48ms): So, what rate do you see if you turn off the lua plugin logging?

You cannot change that file - it is generated on-the-fly from the macros loaded. You need to define your own macro for GoAround for your aircraft if the default implementation isn't working, either in a PFC.mcro file (for all aircraft) or in an aircraft-specific macro file. Please see the PFChidDLL User Guide on configuring macros, as well as the FSUIPC documentation on macros and other support requests on defining macros for PFC devices. John

You can use the lvar XMLVAR_Transponder_Mode with the following values: 0 - ALT RPTG OFF 1 - XPDR 2 - TA ONLY 3 - TA/RA 4 - STBY To assign to an lvar, you can either define your own preset, use a macro or add the lvar to an FSUIPC offset and use the offset controls to change the offset value and this update the lvar. For example, to use a preset, add the following to your myevents.txt file: //HorizonSim/787-9/Controls Horizon_787_Trannsponder_Mode#$Param (>L:XMLVAR_Transponder_Mode) and assign to that preset with a parameter of 4,0,1,2 or 3 for the various positions. John

That will be the 'F' key. Did you change this> The default is to use Alt+F, which is: InvokeFSUIPCOptionsKey=70,12 Your log should also tell you what hot-key was registered, e.g. 250 Registered HotKey 'InvokeFSUIPCOptionsKey' (key=0x46, modifier=0x1) John

No, the same offset is used. What aircraft are you flying? How have you assigned the throttle? Could you show me your lua script, FSUIPC7.ini and FSUIPC7.log files please. Please add offset logging for offset 0x310A (as UB in hex), and once you have set auto-pilot please activate logging for Axes Controls.

That is because you haven't set-up the brake lever button correctly. If you are not using the joy letters functionality (you should!), then just set the brakeLeverJoystickLetter variable to the joystick number, i.e. local brakeLeverJoystickLetter = 2 I have modified in the attached to make it clear that you can use the joyletter or number. John nanchangBrake.lua

No. As far as FSUIPC is concerned, your controller is just a collection of buttons and axes just like any other hardware throttle, and setting up all controllers is exactly the same. What is more important is the aircraft you are setting this up for. I don't have the FSLabs A320, but I think that uses quite a few custom controls via the Rotor Brake control. You need to check what custom controls are available if the standard controls don't work. These should be documented with the aircraft, or check the FSLabs forums. You can also try logging - this should tell you if a standard event/control is used or a custom control (a custom control number or the Rotor Brake control parameter) . Activate logging for Events (non-axes controls) and open the logging console. Then you can click the function in the VC and see what is logged and then use that (i.e. assign to the event/control and parameter used). Also I think the Pilot's Deck plugin works for the A320 - you could check that out and see what that uses. John

First, you posted in the FAQ sub-forum where it explicitly states NOT for support requests. I have moved your post, but please take care to post in the correct forum for support. What have you tries? What problems are you having? Does FSUIPC recognise your throttle? If so, it should be relatively straightforward to assign. What aircraft are you using in P3D?

You can save offset data when saving a flight using the SaveDataWithFlights ini partameter - see the Advanced User guide on using this parameter. It can be controlled from the Miscellaneous option (Options->Miscellaneous...) Reload FSUIPC data - change this from Never to Always or for Autos. John

This has been reported many times already - see John

It wasn't obvious where to download the new installer in the post I referenced as it was included in a comment further down the page. I have updated this now to reference the installer in the first post. You can download from here: https://fsuipc.simflight.com/beta/Install_FSUIPC7beta.exe. John

That link is good, Your log file shows that FSUIPC7 was auto-started via the EXE.xml file: As I said in my post above, there is an issue with lua performance when FSUIPC is started this way. Can you either exit FSUIPC7 once started and restart it manually, or better to re-install and accept the default installation options, which should auto-start via the batch file and not the EXE.xml file. John

I get a 404 error (page not found) with that link.

No problem...however, I just updated the attached script, so please download again if you already downloaded.

Can you try the following lua script. To use, first save this file to your FSUIPC6 installation folder (or your Lua library folder if you have set a different folder for lua files via the LuaPath ini parameter). You then need to: 1. Have the lua file auto-started. To do this, add to your profile [Auto.xxx] section (or just [Auto] if using profiles-in-separate-files, in your profile file), e.g.: 2. Assign your rudder axis with Send to FSUIPC Offset, and use control Offset Dword Set and offset xA010 (you can use a different offset, but if you do you also need to change the offset used in the script, local variable rudderAxisOffset) 3. Open the lua file you installed and set the following variables to specify the joystick & button you are using to control the brake lever: 4. You can also set logging if you want to see what is happening by changing the enableLog value from false to true. 5. You can adjust the repeat rate for standard brakes by altering the brakesInterval value - increase for slower braking, decrease for faster braking Let me know how it goes and if you need further tuning. I have commented the script so you should be able to tune for your needs. John nanchangBrake.lua

To interface to FSUIPC, use one of the provided SDKs. Look in the SDK folder - I have attached the programmer API documentation. John FSUIPC for Programmers.pdf

Ok, interesting. So you are using the buttons at the bottom of the axis to decrement on repeat rather than the reverser (buttons). Maybe better then to send THROTTLE1/2_IDLE on the reverser buttons (9,10 in your config) rather than Throttlw1/2_DECR - or even both (i.e. an idle followed by a decr), although the throttle should already be in the idle position when you activate reversers so not that important. Does this config prevent the aircraft from jumping directly from reversing to forward motion? I will try this when time permits. Thanks, John

👍

Did you restart FSUIPC7? Presets are only loaded when FSUIPC7 is started. Also, check you are using th correct preset - the image shows that you are still using the MF preset from the events.txt file. You need to delete them - click Delete all followed by Ok. John

Then you need to reverse the axis range in the preset, i.e. //A2A SIM/Comanche 250/Engine MY_PA24_250_Carbheat_Axis#@ -1 * 16384 + 327.68 / 0 max 100 min (>L:Eng1_CarbHeatSwitch, Number) John

1. If you are assigning the preset to an axis, then you do not need to check Select for preset'(top-right). This is for sending presets on axis ranges as button controls, Remove this. 2. The correct way to send axis values to a preset is by checking Send Preset to FS, which you have done, but then you also need to check the first box below this and select the preset from the drop-down menu. 3. The following preset: PA24_250_Carbheat_Axis#@ 15 - 10.0 / 0 max 100 min (>L:Eng1_CarbHeatSwitch, Number) subtracts 15 from the axis value ("15 -") then divides by 10.0 ("10.0 /"). If you are using a standard axis, that will have a range of -16384 to +16383, and you need to calibrate this to the lvar range of 0 - 100. To do this. define your own preset in the myevents.txt file as follows: //A2A SIM/Comanche 250/Engine MY_PA24_250_Carbheat_Axis#@ 16384 + 327.68 / 0 max 100 min (>L:Eng1_CarbHeatSwitch, Number) Then assign your axis to this preset (using the left-hand side of the axes assignment panel, not the right-hand side). John