John Dowson

Your keypresses are not being recognised for some reason, but I don't think this is an issue with FSUIPC, and certainly nothing in the latest build. If you remove the FSUIPC5.dll (just rename it temporarily), does P3D see your keypresses? John

You can retrieve your registration details from your SimMarket account. John

Your key for FSUIPC4 remains valid for FSUIPC4. It is not valid for FSUIPC5. Please make sure all 3 details (name, address, key) match those from your SimMarket registration email - best to copy and paste to make sure. John

By the way, how are you detecting that the normal/toe brakes are applied? Are you seeing any messages from P3D (or via offsets)? Engaging the parking brake will set and lock the normal brakes. I think you just need to take the "repeat" off of your parking brake assignment. John

Just noticed that your parking break is assigned as a repeat (not a release!) - try changing this to a simple press (so you click once to activate, then again to release) - I corrected my previous post.

First, you are using an older unsupported version of FSUIPC - can you please update to the latest release, which is 5.155. Could you please do this and resend your log file (this will also tell me the state of your controllers in P3D). You only have parking brakes assigned (to repeat of button 0 on your yoke, which I presume is the left trigger that you mentioned), and no assignments to differential brakes. You could also try activating logging for Events (non-axis controls) and Button and key operations (from the FSUIPC logging tab) and activate the parking brake to see what is logged. You could also try logging Axis controls to see if the differential brakes are assigned to an axis somewhere. Try not to move your other axis while logging this. Please post again and attach the generated log file with this info. Maybe also try with a default aircraft rather than the PMDG 737 NGXu that you are currently using. Cheers, John

Hi Angelo, I've just checked this with 5.155 and P3D key commands seem to be working as expected... That is an old post from April 2019 and references FSUIPC 5.151. Not sure what the issue was there, but its certainly not relevant any more. You could try activating logging for Buttons and key operations and Events (non axis controls) to see what FSUIPC is receiving/sending. Cheers, John

Hi Kevin, could you please attach your FSUIPC .ini file together with your .log file and I'll take a look. Cheers, John

First, you posted in the FAQ section. This section is not regularly monitored for new posts so please post all new support requests in the main support forum. I have moved this post for you. Are you pressing the 'Rescan' button to set a different axis? If so, and the axis doesn't reset/change, then that axis may be "jittering". If this is the case, you can click the 'Ignore Axis' button to ignore that axis while you assign other axis. There is also a section in the User Guide entitled 'The Easy Step-by-Step Way to Calibrate Your Controls'. Please review this if you have not done so already. Cheers, John

Yes, a license for WideFS is valid for FSUIPC4 and FSUIPC5. However, an FSUIPC4 license is not valid for FSUIPC5. John

Hi Stephan, 1. when you create a profile for an aircraft, it will be created with all the current settings, so you don't have to configure again. You can just add to (or change an) existing settings. Under the covers (in your .ini file), it will duplicate your [Axis] settings for the profile (plus any changes) and create an empty [Buttons] section (plus any changes). General button (and key) assignments still apply to aircraft using a profile unless overwritten by that profile. 2. Yes - deleting your .ini will remove all assignments and a default one will be created next time you run P3D. You can also edit (e.g. in Notepad++) and remove assignments/sections/profiles as required. The format of each item/section is described in the Advanced User Guide. Cheers, John P.S. No problem!

This is because you are not using profiles, only general assignments that apply to all aircraft. When you re-assign your Fuel Cut Off for the 747-B, this will replace your assignment for the 747-400 (if using the same button). You will need to set-up a different profile for one of the aircraft (if not both). Please see the User Guide, section "User profiles for all control setting". Cheers, John

You have quite a few of these messages logged, which is not a good sign. This is usually a sign that the system is overloaded and not giving enough time to FS or SimConnect. Is your system heavily loaded? I see that you are also using a PMDG aircraft. Do you get the same error when using other (default) aircraft? Are you using the auto-save facility?

You don't need a registered version of FSUIPC to to use the 3rd party interface (to allow 3rd party applications to communicate to the sim via the FSUIPC API/offsets). Is this from the ACARS log? Sounds like its at least connecting to FSUIPC. Are there any errors in the FSUIPC4 log file? Are you running ACARS at the same privilege level as FSX-SE? i.e. if you run your sim with admin privileges, you also need to run programs that connect via FSUIPC with admin privileges. Sorry, but I know nothing about ACARS. Have you tried their support? John

Just checked and it looks like this was a mistake caused by the word processor deciding to auto-number.... I'll change it back to going from bit 0 for the next release. But as I said, the actual bit used hasn't changed! Cheers, John

The only change in the documentation seems to be the bit numbering - it went from 0-12 in the 5.15 documentation and 12 was Instant Replay (Recording Playback was 11), and it the later documentation the bit numbering starts at 1. The actual bits used hasn't changed. Not sure why I changed the numbering...it seems that sometimes we count from bit 0 and others from bit 1. Sorry for the confusion. John P.S. Latest version is 5.155

Hi Luke, bit 11 is not set, for Instant replay its bit 13 - bit 11 is Recording Active. Try monitoring the offset as U16 hex (to log). If you then look at the log, you should see the value together with the log of the mode. John

Take a look at offset 2900. John

Can you not just load the auto-save flight and then save it again with an appropriate name....

Yes, sorry - don't know what happened there. Also looks to be the wrong version (or at least the document). I've just re-packaged and uploaded, so please try again. Sorry about that. John

FYI, FSUIPC 5.155 has been released, containing this fix. John

I will not be including the version number in the zip file name, for reasons that Pete has already explained. The version properties of the installer should reflect the version of FSUIPC that it installs, but I sometimes forget to update this. I'll try to remember in future. I will close this topic.

I think its worth releasing this as a new version (5.155) once its verified. If you could push the changes I'll merge them into the 5.154 release and release later this week. John

Glad you've solved your issue, and thanks for posting the solution!

You can download from SimMarket, or from here: http://fsuipc.simflight.com/beta/FSUIPC5.zip Once the file is downloaded, you will need to extract/unzip it. This is usually achieved by double-clicking the file in Windows explorer. If that doesn't work for some reason, you can right-click and select "Extract All...' (or something similar). Once extracted, there will be two files - a manual (in pdf format) to guide you through the installation and registration process, and an installer (a.exe). Read the manual and run the installer. The registration process starts (in the installer) once FSUIPC has been installed. John