John Dowson

So you are using the FSUIPC SDK to send keys? Or are you using the windows SendKey function? I am confused now about your support requests in this topic. Do you require assistance or not? What are you trying to do? Your previous posts were (or seemed) to be about not seeing key presses when MSFS has the focus, and now you are talking about sending key presses. If you require any further support, can you please clarify what you are trying to do and what your issues is. Thanks, John

I think you are referring to the Mouse Macro facility, which was available in previous versions of FSUIPC. This is currently not supported in FSUIPC7 as the MSFS SDK does not yet provide facilities for this. It is generally always better to use controls/events where possible, as such assignments apply to many aircraft. Mouse macros are always aircraft specific. For the Parking Brakes, there is the Parking Brakes control, which acts as a toggle. You can just assign that to a button. If its a sticky button or switch (with different positions indicating on and off), then you can also add an offset condition (on 0x0BC8) to only send the control when required. Generally, you will find that there can be toggle controls (for on/off) or set controls (where you send a parameter to indicate the state to set). Both can be used with offset conditions (if there is an appropriate offset!) to only send the control required to maintain the state of the button with the sim. Please see the Advanced User Guide on offset conditions (P22). John

So is it working now? I'm slightly confused... Have you looked at using the Throttle Reverse Thrust Toggle control? If that is supported in the aircraft you are using, this allows you to use the full range of your throttle axis for reverse thrust when set. John

@Travis1992 Are you also using a PFC driver? Could you post your FSUIPC7.log file please? I'm still downloading 1.12.13.0.

As there is no way to specify which event to cancel, I think it should really continue and cancel all registered events for that function. I'll update this at some point, most probably for the next release (FSUIPC6 & 7 only though). John

There really are no changes between 7.0.1 and 7.0.2 that could cause this. Your log shows simconnect failing, then FSUIPC7 exiting when it detects that MSFS has closed/crashed. I think the issue is almost certainly with MSFS or the SDK, as you say. Are you using any other SimConnect clients (or Track-IR)? It could be a known issue (since FSX) with the number of simconnect client connections being exceeded - you can activate SimConnect logging to determine this, and if this is the issue you could increase the allowed number of clients (or directly do this to see if things improve). However, if this was the issue, I would have expected to see some TransmitClientEvent errors in your log. You should also raise a crash report with Asobo (via zendesk), and include the crash report from the windows event viewer. John

Why did you post the contents of the zip folder you downloaded? Try reading the README.txt (the clue is in the name!), and also please read the Installing and Registering FSUIPC7.pdf also provided.

Please see the README.txt (included in the downloadable zip file - and which you posted for some reason....), check the forums (this has now been reported many times) or try google. If you check any of those, you will find that this is due to your VC++ redistributables that need to be installed, or re-installed.

If a key press works in the sim, AND it is one that is supported via a corresponding key input event string (not all keys are supported), then it should also work via a key press assignment (to a button, for example) in FSUIPC7. However, I cannot advise if using mobiflight for that,

This is very strange then! As I said, try re-installing the client, run P3Dv5 once, then try to install FSUIPC6. If you get the same issue, let me know. John

Ok, then sounds like you need to report to Asobo via zendesk.

Then why was your XBOX 360 controller detected? Note that there are currently issues with the 360 controller and that can't be used/assigned in FSUIPC at the moment, but should be okay using via MSFS assignments. By changing to use a USB2.0 port - you cannot do this via software. I use a surface docking station, and I'm pretty sure that it has both USB2 and USB3 ports. Check the colour - if its blue, its usb3, and if black, usb2. Well, that is pretty weird! Can you attach your FSUIPC7.Joyscan.csv file, if one was generated. Maybe try with the controllers you use connected, and re-upload your FSUIPC7.log, .ini and .joyscan.csv files together and I'll take a look. John

Offset 0x0B49 (AUTOPILOT FLIGHT LEVEL CHANGE) is read-only. There is currently no control (that I am aware of) that you can use to assign this to a button. Due to this, at least for the time being, you can assign a keypress in MSFS to the MSFS control TOGGLE AUTOPILOT FLIGHT LEVEL CHANGE (or, probably better, two assignments to AUTOPILOT FLIGHT LEVEL CHANGE ON/OFF, with an offset condition on 0x0B49) and then assign your buttons or switches to those key presses. For the VNAV, please check previous support requests, as I believe this is working but not sure how or for which aircraft - without checking... John

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