John Dowson

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

Did you install the latest VC++ combined redistributable package? This is usually the problem for such issues. So the installer is crashing? Can you check the windows event viewer to see if there is a crash event, and if so show me that? Also, is there an InstallFSUIPC7.log file? if so, please attach that. John

You posted in the Download Links subforum, where it explicitly states NOT for support requests. I have moved your post. Try the support for your ACARS program. This is not anything I can do anything about or look into - the 7.3.25 version has the correct version set. When you run FSUIPC7, does it not say the correct version? John

FSUIPC does not (or should not) overwrite anything. It will create the EXE.xml if it doesn't exist. but should only insert and FSUIPC entry when installed, and not overwrite any other enties. If you think this is occuring, can you please show me/attach your EXE.xml file that you have before you install FSUIPC7 and which gets overwritten, and I will check this here. Sorry, but I do not understand what this means. Everything goes via simconnect - this is the only way to communicate with the Sim (well, the only API that FSUIPC uses). Controls are just events. They cannot be turned on or off, you can only use/send them (or not!). Are these simvars/A-type variables? If so, you can add any simvar to a spare (free for general use) FSUIPC offset using the facilities provided - see the Advanced User guide for details. Again I am not sure I understand you. You test a control by using it - i.e. sending it to the FS to see if it has any effect. If you want to check that it is changing the value of a simulator variable, then add that variable to an offset. John

There looks to be an issue with your installed SimConnects. Can you please show me/attach your InstallFSUIPC4.log file. John

There is such a button for the 747 - B747_8_FMC_1_BTN_INIT using H:B747_8_FMC_1_BTN_INIT. You could look at the model behavior of the aircraft to see if there is anything similar for the 787-900. In fact, See the following article on how to do this: https://www.badcasserole.com/uncovering-input-events-using-the-msfs2020-model-behavior-dialog/ Otherwise such questions on presets/calc. code for specific aircraft functions should be directed to the community via the MobiFlight Discord server, using the MSFS2020 channel. Are you using the free 747-9 mod from Horizon Simulations? I do not have this installed at the moment, but could possibly install and take a look later in the week. But the MF MS2020 channel would be your best bet for such questions - and please also update here if you find a solution. Cheers, John

It has now been released. John

FSUIPC7 v7.3.25 has now been released. John

I do not understand why people keep posting this same problem, when there are now hundreds of support requests with the exact same problem. As I tell everyone else, can you PLEASE consult the documentation and then also the support forums for the same/similar issues before posting. Please first se see the provided Installation and Registration guide, section Invalid Key Problems. You will need to update your VC++ redistributables, as it says there and in the hundreds of support requests on the same subject.... John

I have cleaned-up your ini (a bit!) in the attached, if you could try this. I have removed the use of the hidBravoButtons.lua script - you should delete this, as well as the alpha script, from your installation folder. I have also moved some assignments, but not as many as I would have liked, to your general [Buttons] section. I have also re-ordered your button assignments on device (letter) and number, and removed duplicates. It should be far easier to see your assignments, and compare the assignments in different profiles. I suggest you also move more common assignments (e.g. standard light controls) to the general [Buttons] section, and just overwrite them if not needed/used in your profile section. I did not do this as you seem to have the lights set-up differently in different profiles. Anyway, please try the attached. As before, if you are still getting the issue you originally reported, please show me your updated .ini and .log files, with the same logging as before. John FSUIPC7.ini

Note also that for the Milviz Cessna 310 profile, you have assignments to both the standard controls AND the presets, e.g. for Beacon lights you have the following assigned: In fact, you have multiple assignments to nearly all buttons. I suggest that you go through your ini and remove these conflicting assignments. You would normally have all the assignments to the standard controls in your general [Buttons] assignments. These would then be overridden/replaced un a profile section, where something more specific, such as a preset, is needed. You should therefore move all of your standard assignments to the general [Buttons] section, and remove these from all your profile button sections. You also have the same multiple assignments to some buttons: e.g. magneto in your 310 profile This may be due to the fact that the GUID of the device changed, and then you re-assigned using the new letter, and so when I corrected this missing device (to restore other lost assignments), you ended up with multiple assignments. So, I suggest you open your ini in an editor and correct these issues for your button assignments. First, move all general button assignments to your [Buttons] section and out of the profile specific section (they will be inherited in profiles). Then take a look at each profile-specific button section and remove duplicate assignments for buttons. You should also take this opportunity to remove the use if the hidBravoButtons.lua script. The assignments to P65 should go and be replaced by assignments to the actual button numbers on your Bravo (device C). But better to correct all the other issues before doing this. John