John Dowson

You shouldn't need an email with https://filetransfer.io/ - select the 'share as link' option and post the link.

Then its not off at all. There are various versions of this script available, for different devices The one included in the Example Lua Plugins.zip is the original that is provided as an example and will need to be edited - it is for a GoFlight RP48 by default and handles 4 rotaries. The one on the post I referenced is specifically for the two rotaries in the Honeycomb Bravo.

Ok, so that is why that is controlling the trim. Delete that assignment. You are using the wrong Rotaries.lua script. You need to use the one in that post I mentioned, which has been adapted for Bravo. Please check files before using them! The first lines of the file you were using would have told toy something wasn't right: Here is the correct file (the same one as in that post I referenced):Rotaries.lua John

Please show me / attach your FSUIPC7.ini file as well as the Rotaries.lua fille you are using. The furthest left is the speed brake, no? And as that is an axis, it is very perplexing that this is triggering button assignments...I suspect it is assigned as an axis in MSFS... What do you see in both the FSUIPC' Axes and Button assignment panels when you move both the trim wheel and that axis? Are the virtual buttons recognized on the axes and not the trim wheel? I would like to know if you see those button offset assignments in FSUIPC when turning the trim wheel or using the left axis, or in neither. And please double-check your assignments in MSFS2024. You need to check both in the general and aircraft-specific sections - this is causing a lot of issues for people....

Its DontLogThese. i.e. under [General] section: DontLogThese=66485,69000-70999,66503,66504,66587 If it didn't work, you did do something wrong - did you check the Advanced User guide on this parameter? It shouldn't be that large. Turn off all logging in FSUIPC and restart P3D so FSUIPC starts with no specific logging. Select and load your aircraft on the runway and ready-to-fly. Then, open FSUIPC and set the logging for Axes Controls and Events. Then move your flaps leaver through the ranges and back again, then exit P3D/FSUIPC and attach the log (compress if still too big). If its too large to attach compressed (oy shouldn't be!), you can transfer using one of the free file transfer services (e.g. https://filetransfer.io/ or https://wetransfer.com/)

I mean exactly what i said - do NOT start/request a new/continuation log file - take a look at the log file you attached: John

The ini file you attached is a continuation log file and contains no useful information relating to your issue. Please attach a full log file - do NOT start a new log file. The Rotor Brake control is what the PMDG aircraft use for many custom controls (internally) - the ones in your log have a parameter of 67803 and 67903 which are a 'mouse move' (03) over the control stand trim wheel and speed brake lever: #define EVT_CONTROL_STAND_TRIM_WHEEL (THIRD_PARTY_EVENT_ID_MIN + 678) #define EVT_CONTROL_STAND_SPEED_BRAKE_LEVER (THIRD_PARTY_EVENT_ID_MIN + 679) You can ignore such events by using the DontLogThese ini parameter - see the Advanced User guide for details.

Those assignments look ok, except that the ranges for flaps 0 and 40 look rather small, try increasing them, and the lower range should be Down only, and the upper range Up only (although not strictly necessary). So try: [Axes] PollInterval=10 RangeRepeatRate=10 0=1R,256 1=1R,U,16383,14580,76773,0 -{ Entering=Custom control: <76773> }- 2=1R,B,11663,13316,76774,0 -{ Entering=Custom control: <76774> }- 3=1R,B,5702,8593,76775,0 -{ Entering=Custom control: <76775> }- 4=1R,B,2386,4604,76776,0 -{ Entering=Custom control: <76776> }- 5=1R,B,-247,1601,76777,0 -{ Entering=Custom control: <76777> }- 6=1R,B,-3306,-1068,76778,0 -{ Entering=Custom control: <76778> }- 7=1R,B,-7128,-4410,76779,0 -{ Entering=Custom control: <76779> }- 8=1R,B,-13081,-9721,76780,0 -{ Entering=Custom control: <76780> }- 9=1R,D,-16384,-14748,76781,0 -{ Entering=Custom control: <76781> }- If you get the same issue with that, activate logging for Axes Controls and Events and see what he log says. Best to do this with the logging console window open so you can see the log in real-time. You can also post/attach it here along with your ini if you can't see the issue and I will take a look. John

Pete retired over 5 years ago...

Please also see the following thread which is the same (or similar) issue (but for a different controller):

👍

If there are Linda scripts available for your device and aircraft, you should certainly try that, although beware the Linda is no longer supported. However, I would have thought it would be quite stable for P3D with PMDG as both have been around for a while. Linda is lua interface that sits on top of FSUIPC's lua facilities. Check these forums and also the Linda support forums for any issues - there should be a lot of information there if you need further assistance.

Is the script running? This is wrong, and should be: [Auto] 1=Lua display vals and for the script I attached: [Auto] 1=Lua FPS_MonitorW i.e. to auto-run lua scripts, precede the script name with Lua. Do not edit the [LuaFiles] section - this is managed by FSUIPC. John

Please use the FSUIPC7 support sub-forum for all support issues. I have moved your post. That script will not work in MSFS, as it uses the simconnect_text function which has been deprecated in MSFS and is no longer working. To display values, you need to use the lua WND library instead. I have attached a simple script that shows how to use this - try updating the display vals.lua to use this instead. When I get a chance (next week maybe) I can convert that script for use with MSFS - should have done this a long time ago really! John FPS_MonitorW.lua

If the problem occurred after the latest FSLabs update, what has changed? Did you check the release notes? Did you ask FSLabs about this? They should really ne the first point of contact. I have no idea what this means....! Try FSLabs support. If you want further assistance here, please show me / attach both your FSUIPC log and ini files, the latter with appropriate logging enabled (Buttons & Switches and Events (non-axis controls)). What FS and version of FSUIPC are you using?

To use PMDG custom controls via FSUIPC, please see those 2 FAQ entries. All the information you need is there - I am not going to explain that again here... Why are you doing this? Just open up the button assignments panel, turn your rotary or press a button, and the button should be registered and you assign the custom control. You don't need logging. This is correct. The parameter is either the mouse operation, or a value. Using a mouse operation as a parameter should produce the same effect as clicking the mouse on the rotary in the VC, i.e. a single inc/dec in each direction. When programming a rotary that controls different things based on a selector, you would need to overload the in/dec rotary (i.e. multiple assignments for each quantity you want to change) and use either a compound button assignment so that only the control is send based upon the position of the mode selector switch, or an offset condition based upon the position of the mode selector switch in the VC. To get better control, and implement both fast and slow inc/dec, you would need to use a lua script. The script would, on each rotary button press, need to read the current value for what is to be inc/decremented, apply the relevant delta value (i.e. increase or decrease this read value by an appropriate amount) and then use the custom controls to set the new value. I don't have any PMDG aircraft for P3D, but I can take a look in the MSFS version if you need further assistance, and if it works in the MSFS version it should work in the PMDG version once any control/offset numbers have been checked. I won't have time to look into this until later next week though. John

Trim wheels usually work on buttons, not an axis. Some have two buttons in each direction (one for fast movements and one for slow), others just one. For those using just one button, you can use the Rotaries.lua script to convert this to use two virtual buttons instead, to enable fast/slow trim in each direction. The Bravo trim wheel has one button in each direction. I showed how to configure the Bravo for basic operation, including the trim wheel, in the following post: That should work for quite a few aircraft, but it won't work for all aircraft, especially many add-ons, as those assignments use the default FS controls. For such aircraft, you should use a profile and override these with the specific controls for that aircraft, whatever they may be - usually using presets, input events or lvars. There are also many other ways yo assign trim, and it is up to you to decide what works best for the aircraft you are using. For example, see the following post: John

I will update/replace the trial license in a few days. For now, I have PM'ed you both the latest trial key file, valid until 1st Feb. John

@biggstuff and @Krčík Robert: I have checked both your keys, and as expected they are both fine and validate without issue. As I keep saying, read the Installation and Registration guide and follow the instructions there.

For a new PC, make sure you have downloaded and installed the latest VC++ redistributables, otherwise the registration details won't validate. Please see the Installation and Registration guide for details. And have you read the Installation and Registration guide and followed the instructions there? I am not going to check your key until you have done this. I have checked hundreds (if not thousands) of keys over the years and all have validated successfully, i.e. ALL registration issues are either due to user error or having the wrong VC++ redistributables installed or anti-virus software (see documentation for full list of known possible issues).

@Eduardo P You have cross-posted - please don't do this! I have enough to do all ready without having to answer the same question from the same person multiple times, especially when the question has been asked many times before and the answers are in the documentation.... See

If you registered once, why are you registering again? You don't need to do this - once you have registered and have an FSUIPC7.key file you can just skip registration. And if it registered once, your leu is fine an there is no point me checking it. Please see the documentation for ALL issues with registration. John

Are you aware that the (optional) desktop icon(s) that are installed by the installer only start MSFS2020 and MSFS2024 - they do NOT start FSUIPC7 by default, They are only used to start FSUIPC7 if the MSFS.bat auto-start method is selected during installation. By default, it is MSFS that starts FSUIPC7 via the EXE.xml file. To start FSUIPC7 on its own, you need to double-click the FSUIPC7.exe.... I don't understand why I keep having to explain this time and time again when this is all well documented and also in hundreds if support requests. PLEASE read the documentation! What do you mean by this? If you mean the FSUIPC7 is not running, then run it. If you have in stalled an auto-start component and it isn't auto-starting, see that FAQ entry. Then you are either looking in the wrong place or FSUIPC7 is not running. Try reading the documentation, check your InstallFSUIPC7.log file to make sure everything was installed correctly, and see that FAQ entry if its not auto-starting.

I cannot help with MSFS, only FSUIPC...does FSUIPC recognise your devices? FSUIPC will only recognise buttons/axes on HID joystick type devices. If it is a non-joystick type HID device, then the buttons/axes will not be recognised in the FSUIPC assignment panels, but you can possibly use lua to control this device. You could try uninstalling the Elite drivers and see if windows installs default drivers and if your device is recognised with those. However, if using the Elite drivers, I think you will need Elite support for this issue. Someone posted a similar issue but with FSX in 2008 but it looks like this was not resolved, see: John

As I said, by default FSUIPC7 starts iconized to the system tray, except if a new version is available in which case it will start with the main window open. There is an ini parameter you can use to control this behavior: Happy New Year! John