John Dowson

That is what is supposed to happen (i.e. the desktop link that FSUIPC creates os ONLY used to start MSFS, not FSUIPC7), and it is MSFS that is supposed to start FSUIPC7, via your EXE.xml. There is no auto-start component in your EXE.xml, which is why FSUIPC7 isn't being started by MSFS. The issue is that your EXE.xml is not a valid xml document - looks like it has been corrupted by the AFC_Bridge installer. There is no opening 'SimBase.Document' element. However, I am surprised this isn't logged in yout installation log. But, the solution to this issue is given in the README.txt (item 3 under Problems running FSUIPC7 : You should rename/delete your EXE.xml, and let the FSUIPC7 installer create a new one. You then manually add back in the AFC_Bridge, if you also want that started. But I have corrected your EXE.xml. Download the attached and use that to replace your current one. John EXE.xml

This did not sound quite right to me, so I checked with Pete, and this is his response: John

Just tried the MSFS Add-on Linker and it seems to be working fine here (I have a steam install): If using an MS Store installation, check the Add-on linker documentation as I think there can be permissions issues for that type of installation. John

Btw, you may/should comment out the logging statements in that lua, once you have it working. It is also designed to toggle between forward/reverse thrust on a button-press and release, so one press (and release) when throttles are at idle will switch from forward to reverse thrust, and a second press (and release), again when throttles at idle, will toggle back to forward thrust. If you plan to use this on a switch/sticky-button/slider, you can update to switch to reverse thrust on a press, and back to forward thrust on release. The script also only toggles each thrust (left/right) independently, so if one thrust lever is in the idle range and the other not, only reverse thrust will be triggered for the idling engine. not the other.

No. The lua Rotaries script should be auto-ran from the [Auto] (or profile [Auto.xxx]) section of your FSUIPC6.ini file. The way it works is to change the rotary 'button press' in each direction to a fast/slow virtual button press in each direction. You therefore need to assign in the FSUIPC Buttons + Switches tab to the fast/slow event (or offset) control to each of these virtual buttons. If you turn the rotary and you see the physical button number number rather than the virtual one, you can use the ini parameter IgnoreThese to ignore those physical buttons - you can do this while the assignments dialog is open and then click 'Reload all buttons' for this to take affect. Cheers, John

PMDG offsets are read-only, you cannot write to them. To update the values, you will need to use either standard events/controls, or more likely PMDG custom controls. Sounds like a question for MobiFlight, but I thought you just configured MobiFlight to read data from FSUIPC offsets. John

Could you please explain further? Why was it 'not good'? The shortcut installed by the FSUIPC7 installer starts MSFS (and displays a splash screen for 30 seconds), not FSUIPC7. It is MSFS that starts FSUIPC7, but only if you select to install the auto-start component. Looking at your installation log, it looks like you did not install the auto-start component, and so FSUIPC7 will not auto-start with MSFS. Your EXE.xml file also shows that MSFS is only starting the ADC_Bridge program, and not FSUIPC7. John

By this, you mean that you do not have a valid license for MSFS? Well, I do not, especially as you are the only person reporting this issue. I cannot look into this any further if you are not using a valid/officially licensed copy of MSFS. John

Ok. This is very strange. Is this a new issue or have buttons those buttons never been recognised by FSUIPC? You could try the 'old' method of using such buttons (ie. those outside the 32 button limit), which is using the lua com library. An example script id provided in the Example LUA plugins.zip, called HidDemo.lua. But I do not know what could be causing your issue. If windows can see those buttons, then so should FSUIPC. You could also try the HiDScanner program, to see if that recognises those buttons. available from here: John

I believe this is due to an error with the FLT path (for MS Installs only) introduced in version 7.2.13. This is fixed in the latest beta available in this post: John

Make sure you are not running the x56 software if/when using FSUIPC. Also, if you installed any saitek drivers, try uninstalling those and let windows install the default ones instead. The saitek software and drivers are known to give issues. Regards, John

Do you mean the Heavy Division mod (https://github.com/Heavy-Division/B78XH)? Thats not FBW... Some strange things in your WideClient log: - it seems that a 2nd BAV Merlin client is being started at around the 1h44min mark: - Connection is then lost but reconnected at around the 2h 28min mark: - Connection lost again at around 5hours: Maybe the second BAV Merlin client started affected the first one? Or did you the first BAV merlin client exit due to the "Aircraft paused for too long" message and you manually restarted? Having said that, I think your issue looks to be with the BAV merlin client. As the sim/aircraft was not paused, why did this client think it was? Maybe you can contact the provider/developer of that 3rd party client to determiner what is triggering this message. Otherwise, you could try setting the ReconnectMinutes WideClient ini parameter, but as your other clients are ok I doubt it is to do with the WideServer/WideClient connection, but rather the WideClient/BAV Merlin connection... John

Yes, sorry, I was mistaken...as documented, relative paths are taken from the current default path, which will be the P3D sounds folder, and not the FSUIPC installation path - that is used in FSUIPC7, not FSUIPC6! Ok. However, I think the installation folder location would be useful, I will look into adding it to an offset - I'm surprised its not already there.... John

Hi @light_blue_yonder. Could you try the attached lua. You may need to adjust/tune for your needs. Take a look at the comments in order to know how to condigure/tune, it should be straightforward but let me know if you have any difficulties. Once it is tuned and working, it should be started from your CRJ profile's Auto section. I still don't know how to trigger the engine 1/2 shutoff guards though, and move the throttles to cut-off. I'll take another look at this when I have time. John crjThrottle.lua

Yes, I know. I don't think that can be causing a CTD. I'm also not sure why it cannot read the FSUIPC7 WASM manifest.json file. I do have this utility downloaded/installed, but haven't gotten around to trying it yet. I will do over the next few days to see if I can find out why it doesn't like the manifest. John

Not sure what this means...do you still get an FPS drop when using FSUIPC7? Your log shows quite a few SimConnect errors on mapping known sim events that should exist. This is usually a sign of a corrupt installation. I see you have a steam install - you could 'verify the integrity of game files...' in the steam client, under Properties -> LOCAL FILES. However, be aware that this could re-download the whole game. I cannot think what else could cause this apart from a corrupt MSFS installation, and those errors in the log certainly indicate that there is something strange in your installation. FSUIPC7 also reports this as the path in which you installed MSFS2020: Is this correct?

Ok, good - what was the issue? There isn't an offset for this, but why do you need it? If you want to reference from the installation folder, use a relative file path.

What about your FSUIPC7.log file? Do you gave the same issue now that you have re-installed? You did say 'When i reinstall it to c:\FSUIPC7\ all works fine'? Are you using WideFS/WideClient?

Did you read the provided documentation? If not, please do that - see the Problems running FSUIPC7 section of the README.txt, file included in the zip file that you downloaded. If that doesn't resolve your issues (which I am pretty sure will....), then you need to show me the relevant files, mainly your InstallFSUIPC7.log file and your MSFS EXE.xml file. You also posted twice - I have deleted your other post. John

So you do not see a button number in the assignments panel when you slide that button? You should only see a number when you slide in one direction - I have the X55 and its registered as button no. 134 here. Can you also try the 3 position mode switch - thus is seen (X55) as buttons 31, 132 and 133. if not, you could try adding the following to the [General] section of your FSUIPC6.ini, but it really shouldn't be necessary: EnableExtraButtons=Yes John

Some aircraft seem to continually send some events (even more so in MSFS). You can use the DontLogThese ini parameter to stop such messages being logged, best used in your profiles section, i.e.

Not sure what you mean by this...this IS the proper location... You register via the installer, at the end of the installation process. If you are using the trial license, just save that to your FSUIPC7 installation folder. That is an old post, as is the FSUIPC support request it references. And if you follow that thread you will see that this was an Asobo issue, which (I assume) has since been addressed. Your log shows that FSUIPC7 exited due to MSFS no longer being available, i.e MSFS closed/crashed and so FSUIPC exiited.

That link is to a screen-capture tool. But your issue is that you are hiding known extensions in windows explorer, so that you cannot see the file extensions. The files ARE there - see the appendix in the Installation and Registration guide.

As well as what Pete has said, the location of the ini is also logged in the file you attached: If that is under your P3Dv5 installation folder, I recommend that you re-install into a different folder. You should install outside of the P3Dv5 installation folder, and not in a windows-protected folder, such as Program Files or under your Documents folder. John

From the log you posted, it looks like the mouse macros are triggering Rotor Brake events, with the parameter indicating the actual control that is used. You could switch to using these Rotor Brake controls directly, rather than via mouse macros. See the following tutorial: https://forums.flightsimlabs.com/index.php?/topic/22402-v440-update-in-depth-tutorial-to-bind-switches-and-push-buttons-to-keyboard-or-hardware-for-the-a3xx/ John