John Dowson

Its Alt + F (not 7). If its running, you should see an icon in the system tray (maybe hidden). Did you see the FSUIPC splash screen at all? Steam main screen? Does it start MSFS? You should see an MSFS splash screen for 30 seconds or so, then the MSFS window should appear. The FSUIPC splash screen should appear after two minutes, then sit in your system tray. Can you tell me what you see please? If the created link doesn't start it, can you try: - running the MSFSwithFSUIPC7.bat file directly (from you FSUIPC7 installation folder) - starting MSFS manually, then running the FSUIPC7.exe

Maybe ask them?

I don't know - you need to ask PMDG. In FSUIPC we just provide access to the data they provide. John

As I said, you should try the LINDA support and forums. The A320 is a popular add-on and I'm sure many people use this with FSUIPC/LINDA without issues. I just can't help you with issues involving LINDA as I don't use this. John Later: also check that your controllers are off in P3D. You have this in your attached log: But that may be due to the old version where this was incorrectly reported.

Hi Jean-Luc, first, your FSUIPC6 is quite out of date - I can only support the latest version is which is 6.0.10. You can download from www.fsuipc.com or the Downloads -< Updated Modules section of this forum. I think you also need to update your LINDA installation as I believe you need 3.2.6 for P3Dv5. If you still get errors after you update, you should initially try the LINDA forums & support as I can really help with LINDA. John P.S. 24KB is a very small file and doesn't really need zipping!

In about 40 minutes....hopefully!

You need to download the latest key file. Already many posts about this unfortunately. I do publish the information - it is (was now!) a beta, and as such you should try to follow the announcements on each release as to what to do. Once released, (and out of beta) this won't be an issue..... The key file you need is on the FSUIPC7-beta announcements page: John

There is no key file valid until 3rd November. 3rd November is the build date of the FSUIPC7 version, not the expiry of the license.

You shouldn't do that. It will create problems and a mismatch between your installation location and your registry settings, and the uninstaller won't work. If you want to change the directory name, simply re-install to a new folder, then move any required files across ()e.g. .ini, key), and then remove the old folder. Ah, so you did re-install? Ok, I'll add quotes around the start command, although should be: start "" "F:\MSFS2020\Community\0AA - FSUIPC7\FSUIPC7.exe" Can you try that please. Remove the splash screen, or just the animated dots? I've added this as when you start MSFS you see nothing for around 30 seconds before the MSFS screen is displayed. You can edit to remove the splash or the animated dots, to suite your needs. John

Use to set the elevator axis position, from -16383 to +16383, as stated in the documentation. If you do this, you may want to (temporarily) disable any joystick axis assigned to the elevator - you can do this in offset 0x310A. Yes, but if there is a joystick axis assigned to the elevator axis, then this can send values overwriting what you set, which is why I suggest that you temporarily disable the input from any elevator axis assigned. Sorry, can't help with this - I don't have PMDG aircraft and don't fly airliners (yet!), but presumably you need to gradually extend the elevators once you've hit the rotation speed....

No. It is always free. However, there are additional facilities provided when using a registered/licensed version. Why wouldn't it connect? Did it detect MSFS was running? Are you using auto-connect? Are you using a registered version? Note that the latest installer doesn't come with a key file (license). You can download one from the FSUIPC7=beta announcements page, valid until 8th November. In the calibration tab if the axis assignments panel, click the slope button and then adjust until you have a slope of 0. However, as you are editing the ini anyway, you can just remove them there - just look for the SlopeRudder parameter also in your [JoystickCalibration] section and remove that line.

Took a look...! - button 1: switch between voltmeter and outside air temperature displays - button 2: switch between various times (universal, local, flight, elapsed) - button 3: start/reset ET,; Hold to reset FT button 3 is inoperative, so there will be nothing you can do for this. Buttons 1 and 2 don't send any known events. Looking at the controls available in MSFS, there doesn't seem to be anything related to them there either. So I think you are out of luck. I've also checked the published variable lists and there is also nothing there that could be linked to those functions. It is the type of thing that mouse macros are generally used for, so you could wait to see if MSFS provides such an interface somewhere down the line (and then the mouse macro functionality implemented in FSUIPC7). . You could also raise a new feature request via Zendesk, asking for either new key events to be added to the SDK for these 2 (or 3) buttons, and/or for additional simvars to be made available to both read the current state and also write to update. John

Offsets aren't related to buttons. You can program/assign any function that you want to a button. What functionality do you want to assign to them, i.e. what should they do? Later...ah, sorry - you mention it in the tile - OAT/VOLT/SELECT...but I don't know what this means. Could you be more explicit?

It goes in %APPDATA%\Lockheed Martin\Prepar3D v5 -see https://www.prepar3d.com/SDKv5/sdk/simconnect_api/configuration_files/configuration_files_overview.html, and for an example: SimConnect.xml file: https://prepar3d.com/SDKv5/sdk/simconnect_api/configuration_files/simconnect_xml.html

It could be that this issue is created by an old bug relating to the total number of connections used by simconnect clients - this is an old issue known in FSX and has been confirmed over at FSDeveloper. ( Discussion, An improvement in the same thread). To check if this is the cause, you could try modifying the maximum number of clients (MaxClients) in the SimConnect.xml file. You could first try reducing this to see if you can provoke this issue to occur earlier, and if this works then you can set to the maximum value which seems to be 255. John

Hi Roman, that's interesting and could well be related. It also makes sense to what I have observed while developing FSUIPC7 for MSFS, when FSUIPC was reconnecting many times due to stalled data. When you say simconnect dies completely, does this mean that there is not even an error reported in the SimConnect log file (when activated)? And presumably its not just the client requesting the connection that then fails, but all simconnect clients already connected? FSUIPC can automatically re-connect if the data it is receiving is stalled for a configurable amount of time and a message is logged each time a connection is opened or closed, so it is easy to determine the number of connections FSUIPC7 has used. Not sure about other simconnect clients though, but the simconnect log would be the place to determine the total number of clients and number of connections made by each. Another strange thing about these reports though is that different users are reporting different symptoms/failures. Some users also report loss of controls in the FS (include mouse operations!), others loss of all flight controls, and some (like this post) just a failure in certain areas. But I think anyone experiencing such issues after a long period should certainly look into this as a possible cause. It might be worth (following the advice in that link you posted) to initially adjust the maximum number of SimConnect clients (MaxClients) to a lower number, to see if the failure can be forced earlier. If thats the case, then it could then be increased to 255. Thanks, John

Can you also change the following parameters in the [General] section of your ini: InitialStallTime=10 NormalStallTime=1 to InitialStallTime=30 NormalStallTime=-2 which are the new defaults in FSUIPC7.

Yes, of course. For 50% rudder deflection at 100% joystick with linear response, remove the slope completely, open your FSUIPC7.ini and fine the rudder entry under [JoystickCalibration] (or in a profile specific JoystickCalibration section if you want to apply this there) - here's mine: Rudder=-16384,-750,750,15648 then just double the max/min values: Rudder=-32768,-750,750,31296 then when your joystick is at max/min deflection (sending values near -16384 or 15648), these will be calibrated using the extended range and so halved, giving you a +/- 50% rudder deflection.

When you create a new profile, there will be no buttons or keys section until you create a profile specific assignment for such, so there is nothing to remove. The generic profile is always applied for buttons/keys, and these will only be overwritten if you create a profile specific assignment instead. This is all explained in the documentation.

Not in the ini you posted, as I said. It was the FSUIPC7.exe attached, not the installer. I'll be releasing an updated installer later today (or tomorrow), also with a new version of FSUIPC7.exe (which will again be different from the above).

Its ok, checked them an it seems that there is an issue with the ini comments for FSUIPC added controls which I will look into. So you have nothing assigned in FSUIPC7 to do with axes or reverse, so how was this previously working?

Hi Martin, how were you activating the reverse thruster? You have very few assignments, no axes or key assignments and only 3 valid, as well as 4 possibly invalid, button assignments, all assigned to your HOTAS throttle: Controls 1061 - 1064 are for engine 1-4 autostart - I'm not sure why these aren't commented correctly - are they working? An unrelated question - are you using a Steam or MS Store installation? Seems to be the latter, but FSUIPC isn't detecting your FS Path correctly. Could you please try the attached version - just run it and close, then attach your FSUIPC7.log file. Thanks, John FSUIPC7.exe Later: sorry, it is reported: 78 FS UNC path = "\\PILOT\MSFSPackages\" just some earlier logging for the MSFS install was commented=out, which confused me. You can continue to use that version if you like - it will be released later today (or tomorrow), with an updated installer.

I have no idea. Are you using a registered version of FSUIPC7? If not, please uninstall FSUIPC7 using the uninstaller (located in your installation folder), download the latest installer and re-install. If you are then still experiencing your issue, please start a new topic and attached your FSUIPC.ini and FSUIPC.log files. John

If it only occurs after 10 hours or so, its certainly not due to anything in your ini file! There is a related post where the sim stops responding to all controls when using PMDG but after 7 hours: and also a post in the LM forums on this: https://www.prepar3d.com/forum/viewtopic.php?f=6312&t=139856&hilit=freeze+after+7+hours&start=15 Although this issue occurs with FSUIPC running, it has also been reported without FSUIPC running but with other SimConnect clients. It therefore seems to be a SimConnect issue and not related to FSUIPC.

@Mallinoi Did you try adding LuaTrapKeyEvent=No To the [General] section of your FSUIPC6.ini in v6.0.10? This will revert v6.0.10 to the previous behavior (6.0.8) where keys acted on in lua are also forwarded to the FS. In v6.0.9 and later, keys handled in lua are masked and not seen by the FS. John