John Dowson

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

Can you try the attached version please: FSUIPC7.exe

You can use the attached script. Take a look at it and change to set: maxNoViews - to the number of custom views you have defined joynum - to the joystick number that has the button you want to use button - to the button number that you want to use to cycle the views The script should be auto-ran, e.g. add the following to your FSUIPC7.ini file (or you can use your profile-specific [Auto.xxx] section): [Auto] 1=Lua cycleCustomViews See the Advanced User guide for further information on the automatic starting of lua files. John cycleCustomViews.lua

I have checked those offsets and they do not change when using custom views. There don't seem to be any controls or presets to select or cycle through custom views, so it seems only keys (default is left alt + view number) allow you to change this. Therefore the only way to assign a cycle custom control to a button would be to implement this in a lua script. If you are not familiar with lua, I could provide you with a basic script that you can customise for your needs. John

So the issue is that you get full power reverse thrust in the B787-9 rather than this be limited (to -4096), but this is ok in the PMDG 737? I will take a look at this and get back to you, but it may take a few days. John

Your install log looks ok. Can you try re-installing SimConnect, as this seems to be corrupt. Re-install all three versions, which you cand find (SimConnect.msi) under D:\Applications\Games\Steam\steamapps\common\FSX\SDK\Core Utilities Kit\SimConnect SDK\LegacyInterfaces Run the SimConnect.msi under FSX-RTM, FSX-SP1 and FSX-XPACK. If that doesn't work, try 'Verify Integrity of game files' for FSX from the Steam app.

You really shouldn't need to reboot, restarting FSUIPC7 should be sufficient. I will look at your files and do some testing here later in the week and get back to you. John

Go to Log->Offsets... and log offsets 0x0270 and 0x026F, both as UB and also check Display->Normal Log File. Open the logging console (Log->Open Console) and see what is logged in those offsets when you change your custom views, If you see the values change, you can also write the same values to those offsets and that should change the custom view. I can help with this, but first you need to see if those offsets change, and if so what values are logged for each custom view. I will also look into this in more detail later. John

I have sent it to you via PM. John

It is very strange, and I have no idea what could be causing this. There is no change in the installer except for the updated files. But presumably you already have your key file if this is a re-install. If not, you can either manually create it, or I can generate one for you and PM it to you if you let me know your order number. John

Do you mean in MSFS to the Load Previous/Next Custom Camera binding (with default keys K and shift+k)? Are these not working then? If they are working, you can assign your button to the key press used there. Otherwise try logging offset 0x0270 (also maybe 0x026F) and see if that changes when you cycle your views. If so, you can use that. John

Then the installer IS crashing - or being stopped. Do you use any anti-virus software? If so, please check that for any messages and also try installing with that disabled.

Then your browser has cached the previous download. Try clearing your browser cache. The links are correct and contain the correct version. I believe this is due to changes in the pause indicator offset 0x0264, but you should ask DVA. John

You don't need the parenthesis - they just indicate that the =n is optional. Did you try without the READY option? As the READY option already delays until the FS is up and ready-to-fly, I suspect the DELAY parameter can only be used when READY is not being used. Although this should be documented as such if this was the case. I have enabled debug logging for this in the attached version if you could try this please. Try with 'DELAY=10' (or whatever numbers that you want to use) option and show me your log file as well as the ini you used. FSUIPC7.exe

It is not a pop-up window. It is the 2nd to last page in the installation dialog. I cannot see how this page cannot be displayed. What is the last page you see in the installation dialog before it closes? Your installation log looks fine. John

Licenses sent. John