John Dowson

To receive keyboard input, either FSUIPC7 or MSFS must have the focus. As I have said, please show me your log file when MSFS has the focus, as you have said that the keys aren't being seen for this. The log file you attached shows the keys being seen and the controls being sent (but I have no idea which app had the focus when you did this). Keyboard input will NOT BE SEEN if neither MSFS nor FSUIPC7 has the focus - the input will go to the app with focus, there is no way to receive such input. John

Those keys are recognised. Could you activate logging for Buttons & Keys, press each of those key assignments and then show me your log. This is what I see pressing those keys when MSFS has the focus (with no assignments to them): L: F7 (here I held the key down a bit longer and so a second repeat keypress was detected): Ctl + F: Please attach you full log (not extracts or a continuation) and your FSUIPC7.ini. John

No, What are thes? I can see that there is an MSFS control entitled 'SET ENGINE CRANK MODE and one for 'SET ENGINE NORM MODE'', but these aren't available via SimConnect. I will try adding these at some point to see if this is just missing from the documentation, but I doubt it. In this is the case, then you can assign keys to these controls in MSFS, and then assign buttons/switches in FSUIPC7 to those key assignments. Similarly, there is an MSFS control SET ENGINE IGN/START MODE - is this the control that you are after? Again, seems to be MSFS internal only. John

What keys are you using? When MSFS has the focus, only key input events seen by SimConnect will be recognised. For example, try pressing the standard letter keys - are you saying that FSUIPC7 doesn't see those when MSFS has the focus?

Hi Hermann, I just looked at this in the Cessna Citation and the offsets are populated as expected - this is what I see with the CJ4 when I log those offsets and move my throttle through its full range:: How have you assigned your throttle axis? Maybe you can attach your FSUIPC7.ini and I will take a look. You can also try logging those offsets (as I did, as S16), to see what the values are for you when you move your throttle axis. John Later: Also checked in the 747 with the same results. Are you using any mods? If so, try without.

@spokes2112 Happy Christmas Ramon! And, as Pete says, thanks a lot for all your contributions over the past year, you have helped out a lot, especially with your lua wizardry! Regards, John

You cannot use profiles provided by others as-is. Every device has a different GUID and distinct windows ids. Even if you had exactly the same devices as another user (and you haven't even specified what controllers you are using), you would need to manually update the ini to replace the GUIDs and IDs used. Then, if you corrected this, you would have the problem that you would not know which control had been assigned to what button or switch. So its not so easy, and you would have quite a bit of work to do even if someone had an A320Neo profile and was using exactly the same hardware.

What exactly did you try? For example, are you using usb3 hubs or usb2, and if the former did you try switching to usb2?

First, you should always give your posts/support requests an appropriate title. Using your forum username isn't very helpful - I have changed it. This implies that no registry entries for P3Dv4 ot P3Dv5 have been found on your system. Do you have either version installed? Have you ran the version you have installed? It needs to be ran at least once to generate the registry entries. If that's not the issue, try uninstalling and re-installing the P3D client for the version you are using. John

An FSUIPC4 license is not for FSUIPC7. Your FSUIPC4 license is for FSUIPC4 only. Your WideFS7 license is for WideFS7 only. For FSUIPC7, you need an FSUIPC7 license. WideFS7 is compatible with FSUIPC7. You should be able to register that during the FSUIPC7 installation process without having an FSUIPC7 license. John

P3Dv4 (and FSUIPC5) are also both 64-bit.

To add to what Pete has said, to have different calibration for the same axis (to be used with different controllers) for the same aircraft (and thus the same profile), you would have to have two different ini's that you could switch depending upon which controller(s) you were using. John

First, you posted in the FAQ section where it explicitly states 'Not for Support Requests'. I have moved your post this time, but please raise all support requests in the correct forum. You have also not attached any files (e.g. your install log or your FSUIPC4.log file), so I have no idea what your version of FSX is. However, if you are using a 'boxed' version, its almost certain that you need to install both of the FSX service packs (SP1 and SP2). There have been MANY similar support requests about this.... So, please check your FSX version, and install any service packs that may be needed, and try again. If you still have issues, post again and provide the information that we need to be able to assist - please read the following before posting again: John

Sorry - v7.0.2 is the latest official release. There is a v7.0.3 pre-release out (posted somewhere in the forums), but for now just update to 7.0.2. John

Yes, looked like MSFS crashed so FSUIPC7 then exited. You need to raise a crash report with MSFS/Asobo via zendesk. John

@westhielke Could you please try with the attached ini, which I've cleaned-up a bit, but I don't think this is related to your issue. FSUIPC6.ini Also try moving to a USB 2 port. We have had several reports of USB 2 devices no working correctly on USB 3. Also check that, if using an external hub, it is correctly powered. John

@b777200lrf & @B77X Could you try the dll posted in this similar support request: John

There are no 'custom' offsets as such in FSUIPC. There are 'free' offsets available for use to do what you want with. These can be used to populate with data from lvars, but unfortunately there is currently no access to lvars in FSUIPC7. This is the next facility that I would like to look into providing, when time permits. John

Hi Paul, first, its probably MSFS crashing, not FSUIPC7. If FSUIPC7 crashes, it should not affect MSFS as its running in a separate process. To verify this, you can uncheck the option 'Exit with FS', and then FSUIPC7 should remain running when MSFS crashes. Also, the log file should show FSUIPC7 exiting normally if MSFS crashes, as it will just lose the connection and exit gracefully. When MSFS crashes, you should also check the Windows event viewer to see if there is a crash log. if so, you need to raise a support request with Asobo/MSFS via zendesk, and include the crash report from the event viewer. John

Thats interesting as most people find that the increments/decrements are too small and need to increase them! However, the procedure is the same. You can use offset 0x0BC0 with the Offset Sword Increment/decrement controls to specify the granularity you require, as explained in this post: John

Hi Hermann, I'll take a look. Is this a general problem for all aircraft or for a specific aircraft? John

@jockoflocko Sorry for the late reply. I see you have worked out the issue - you have to be 'ready-to-fly' to be able to calibrate the axis, not just connected to the sim. I'll think of adding a pop-up message/warning (or maybe disable the calibration tab) when not in the correct state, to make it a bit clearer. John

What happens when you click 'Yes' to run?

First, you are not using the latest version of MSFS - can you please update to v.7.0.3. Only the latest version is supported. If it still crashes, can you provide more information - as well as the event log, can you attach you FSUIPC7.log and FSUIPC7.ini files and provide a brief description of what was happening when the crash occurred. Thanks, John

It IS there. Pete posted the contents - if you see something different then please post a screenshot so that we can see what you can. If you are not seeing the extensions, it is because of your Explorer view settings, but the files should be there non the less. We need this information from you to help you.... 32/64 bit is mentioned. Win versions are only mentioned when applicable. John P.S. Another possibility is that you have some antivirus software running that is removing/quarantining the exe. So check your antivirus settings/history.