John Dowson

Ok - thanks for the explanation. The Rotor Brake method is just another way to use custom controls, just more limited - you can only send mouse operations and not actual values. If you take a look un the FAQ section, both methods are described, but the Rotor Brake one is deprecated in favor of the custom control method. With the switch unlocked, have you tried sending a parameter of 3 to using either one, or maybe both, of the EVT_FIRE_HANDLE_ENGINE_1_TOP & EVT_FIRE_HANDLE_ENGINE_1_BOTTOM custom controls? And then once out, you can use the same control and send a parameter of 3 or 4 to turn the handle. You just need to play around to see what works. I can take a further look tomorrow. John

License sent.

Please do not attach images - just attach your FSUIPC7.ini file so that I can see your assignments. However, if calibrating in FSUIPC, it is (usually) better to assign using 'Send direct to FSUIPC calibration' and not 'Send to FS as normal axis'. But this is nothing to do with your issue. If you are flying a prop aircraft, then this is normal behavior due to the propeller torque effect and p-factor - see https://forum.flyawaysimulation.com/forum/topic/25992/how-come-my-plane-turns-to-left/. You would normally adjust the trim to compensate for this. If there is a button that is triggered in this off position (which hopefully is the case - you can check in the FSUIPC button assignments window), then reverse thrust is normally achieved by assigning this button press to Throttle Decr on repeat, and to Throttle Cut on release (to stop reverse thrust). John

This is very strange, especially as FSUIPC has nothing to do whatsoever with the visuals. Have you tried with various aircraft? Did you get the dialog to activate FSUIPC for P3D after it was installed? What happens if you disable FSUIPC? i.e. when you start P3D, click the Options button, and then disable in the Add-ons section before you continue. Do you get the same issue? I suspect so, as FSUIPC will already have been loaded. So now exit P3D and restart it, and FSUIPC will be disabled. Do you then get the same issue? What ither add-ons do you have installed? Can you show me/attach your add-ons.cfg file, which will be under [USER]: AppData\Roaming\Lockheed Martin\Prepar3D v5\ John

Do you have an actual issue? If things are working as expected, then there is no point in me looking at your file. If you have an issue, then explain what that issue is and then I may take a look at your files, id needed. This support request has already gone on quite a long time already, especially as this script for rotaries has been around a long time, is included with each version of FSUIPC, and there are already numerous support requests on using this script. That depends on which control you are using, as there are several got the heading bug. For example, the heading bug inc/dec controls take no parameter, but the set control does (hopefully that is obvious). John

What do you mean by 'Lua Log Entries'? You can see the lua documentation provided in your documents folder: FSUIPC Lua Plug-Ins FSUIPC Lua Library LuaFileSystem Lua Plugins for VRInsight Devices Lua License Example are also provided in the Example LUA plugins.zip file and are described in the Lua Plug-Ins document. For any other lua documentation you require, see the official lua documentation: https://www.lua.org/docs.html No. For simvars (A-type variables) and controls (actually called events in MSFS and also accessible as k-type variables), see the MSFS SDK Documentation: https://docs.flightsimulator.com/html/Programming_Tools/SimVars/Simulation_Variables.htm For other variable types (l:vars, h:vars, b:vars, etc), you can use the Dev tools provided by MSFS to inspect the code of the current aircraft. For example, see the following article on how to use these dev tools to discover input events: https://www.badcasserole.com/uncovering-input-events-using-the-msfs2020-model-behavior-dialog/ John

Ok, thanks for the update. If you deleted the FSUIPC6.ini file, did you redo your settings/profiles/etc? This seems such a drastic action to take, and I would never recommend this to fix in an issue (if this did indeed fix the issue, of which I am doubtful). Temporarily rename or moving it out of the installation folder for a test is ok though.

Ah, ok. That would make a difference (such as de-activating the logging you had set), but I would be very surprised if anything in the ini could cause this issue. And if anything in the file had changed, then you must have done this via changing the settings in the UI (or editing directly). Doing this would also delete all your assignments, if you are using a registered version of FSUIPC6. The Rotor Brake control/event is one way to use the custom controls provided by the PMDG SDK. To understand how these work, see the following page: The parameter 97903 indicates a mouse-move event (03) on the following control: So that event just looks like the mouse moving across the HUD, which is nothing to worry about, and is emitted by the aircraft.

Olvidé decirle que necesitas reiniciar FSUIPC7 después de que se hayas habilitado el WAPI, ya que los presets solo se cargan cuando se inicia FSUIPC7. De todos modos, me alegro de que ya esté funcionando. Un saludo, John

Add-ons -> WASM -> Enable Esto generalmente está habilitado de forma predeterminada... No sé por qué está deshabilitado...

This cannot possibly have any effect whatsoever. It is just a log file, and is cleared/newly generated each time FSUIPC/P3D is ran. That is a huge log file and I am certainly not going to go through that in detail, especially as you are using many Rotor Brake/Custom controls. What issues does it "definitely show"? Looks ok to me, on a quick scan. The difference between the two log files is that in the first one you had logging for Events (non-axes controls) activated, and in the second one not: I don't think this is an issue with FSUIPC, but you could possibly be accidentally triggering an assignment that is doing this. To narrow this down, you can use Event logging, with the logging console window open, and see what events are logged at the time, and just before, your issue occurs. Then track down where that event is originating, John

👍

En su archivo FSUIPC7.log: presets no se cargan porque WAPI está deshabilitado; habilítelo para usar presets.

compress/zip it

Please try the attached version, 7.3.26b, and add ObeyThrottleLowerLimit=Yes to the [General] section of your FSUIPC7.ini file: FSUIPC7.exe

I can confirm this behavior. The max reverse throttle value is defined by the simvar THROTTLE LOWER LIMIT, held in offset 0x0B00. It seems that this value is correctly set - it is -4095 for the 787-9 (and -6092 for the PMDG 737), but it seems that the aircraft is not respecting this limit. This is a problem with the aircraft, not with FSUIPC7. However, I can add a fix for this - I can add a new ini parameter (ObeyThrottleLowerLimit) which, when set, would inhibit the sending of a Throttle Decr controls, as well as the individual Throttlen Decr ones, once the lower limit has been reached. I can take a look at this over the weekend and will post and updated version here for you to test. Regards, John

Mira abajo donde entras tus comentarios...

License sent via PM.

Adjunto los archivos FSUIPC7.log y InstallFSUIPC7.log (no pegar)

Has marcado 'Select for preset', y con este el menú debería mostrar los presets disponibles. Si esta lista está vacía, esto implica que no se pudo cargar el archivo events.txt. ¿Instalastes este archivo? ¿Puedes verlo en tu carpeta de instalación de FSUIPC7? Instalar de nuevo y comprobar la installacion de este archivo; lo mejor es aceptar las opciones de instalación predeterminadas.

I am not that familiar with the 737, but I have just taken a look and it seems that top/bottom refer to the top and bottom parts of the handle, which use different controls. You can see this if you set logging for Events (and open the logging console) and use the mouse to control the handle, you will see the following logged (note the UI uses the custom controls via the Rotor Brake control method): I do not know how this handle is supposed to function, so do not know why this is and cannot really advise further on how to set this up. Note also that this is a 3-byte array, and so holds 3 distinct values, for the engine 1, engine 2 and APU handles respectively. These values are held in offset 0x6C44, 0x6C45 and 0x6C46, so you can try logging those offsets (as U8) to see what values they hold as you change the position of the handles.

Yes - I took a look at the input events in the model behavior panels and also couldn't see anything, and I saw your post on the MF discord channel. You could try asking in the Horizon Simulations discord channel (https://discord.com/invite/Peyby68DTs), and If this is currently not supported they may enable this in a future update.

Sent.

Thinking about this, 62615 may be the deluxe version. If there is no update available, show me your FSUIPC4 Install.log. You most likely need to install the 3 simconnect dlls, from the *.msi files under Steam\steamapps\common\FSX\SDK\Core Utilities Kit\SimConnect SDK\LegacyInterfaces - run the SimConnect.msi under folders FSX-RTM, FSX-SP1 and FSX-XPACK. If that doesn't work, try 'Verify Integrity of game files' for FSX from the Steam app.

That is because you have assigned to both the press and release - I left this as that is how you had it. If you only want one control sent, remove the assignments to the release, those starting with CU - and in bold below: John