John Dowson

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.

But why do you want to trigger a joystick button press? Can you not just trigger the action that the button press would perform?

It is its own section - [Auto]. It can go anywhere - but not embedded in another section (obviously I hope!). Yes - please see the Advanced User guide, page 16. Yes - assigning to a virtual flag//button is the same as assigning to a real button, you have to specify the control and the parameter (if needed) and you can assign to both the press and release (again, if needed). John

Generally not, only for virtual buttons - see the ipc.btnPress, ipc.btnRelease and ipc.btnToggle lua functions. But why do you want to do this? Can you not just simulate the action that the button press performs when your condition is met, rather than the button press itself? John

See the Advanced User guide. section Automatic running of Macros or Lua plugins on page 39. Basically you need to add an entry to the [Auto[ section in your FSUIPC7.ini file, or in profile specific [Auto.xxx] sections if you only want to use it with specific profiles, e.g. [Auto] 1=Lua GF_166 John

So it was previously working? What has changed? Are you using FSUIPC to drive the MCP? If so, please show me/attach your FSUIPC7.log and FSUIPC7.ini files.

You don't have many button assignments, and all the assignments are assigned to change offsets in a reserved area. As they are in a reserved area, i can only verify that the assignments are actually working, i.e. changing the offset value. To do this, I need to see a log file with logging for Buttons & Keys activated, and showing that you pressed one of these assigned buttons. The log file you attached does not contain the required logging and so is useless. You should also add offset logging to the offsets you are testing: 53F4 (U8), 53DB ( U16), 5418 (U32) & 5452 (U16) - all as hex. That should cover all of your button assignments. What software do you have that is using those offsets? According to my records, the offsets you are using are reserved for the following: 5300-53FF: Mark Hastings B777 Systems Simulator 5400-5FFF: Enrico's Project Magenta If the assignments are working (and the offset value is changing as specified by your assignments), then there isn't much I can do - you need to contact the provider of the software that is using those offsets. John

There is also a lua script available that allows you to use a button to cycle between different cockpit custom views in this post:

Yes

Because there is no such type. Why don't you just follow what it says in the manual - use I32 for the type. The manual even gives an example: John

Please attach your FSUIPC6.ini and FSUIPC6.log files, the latter with logging for events set, as well as logging for buttons & keys. John