John Dowson

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

I have to build it for you and make it available. Take a look at the history document or the changes,txt file - both will tell you the version numbers, release dates, and the changes between each version,

Why, did this problem start after an FSUIPC update? If so, what was the previous version you were using? I don't think this has anything to do with the FSUIPC version (no change in com handling or use of VRImsight devices for many many years) but you are welcome to try.

👍

key file sent via PM.

If you are using the Steam version, the latest version if FSX-SE is 10.0.62615.0 - you should update. Once updated, re-install FSUIPC4. If you get the same problem, show me/attach your FSUIPC4 Install.log, as well as your FSUIPC4.log file. Is this the first time you have ran FSUIPC4? I ask as it looks like you have no FSUIPC4.ini file.

I have the Bravo and know how it works. Can you please attach your FSUIPC7.ini file please, rather than images. I will look into this later, but I suspect that this is an issue with the aircraft - FSUIPC is just sending the Throttle Decr control/event, and it should be up to the aircraft to know when the limit is reached. So I suspect that the underlying issue must be fixed by the aircraft developers, but it may be possible to use a lua script instead, which would stop sending the Throttle Decr control/event once the limit was reached. I will look into this later and get back to you. John

Why are you starting LINDA twice? Sorry, but can't really help if using LINDA. Try the LINDA support forum on avsim. Even though LINDA is no longer supported by the developer, you may get some assistance from ither LINDA/VRInsight users.

If your condition is filled, you can just call ipc.runlua("Window2.lua"), no? Otherwise, use virtual buttons which can be "simulated".

It can always be compressed/zipped. Also please do not start a new log file, I need to see the full file and not a continuation log file. And it looks like you forgot to add the requested offset logging. But the extract you posted shows the offset being updated according to your assignments, e.g.: 263156 IPC Offsets Control: Ctrl=x0100, Length=1, Offset=5814, Param=x1 So the buttons are working and sending the assigned control.