John Dowson

You have posted in the FSUIPC Client DLL for .Net forum. I am not sure your problem is related to the client dll - shall I move this post to the main forum? In fact, you probably need to contact IVAO support for your issue. Did you install it? Did you run the sim BEFORE running the FSUIPC installer? Which steam version? If using the new beta, please see this post: Is that from IVAO? Sounds like you need there support, sorry. John

First, only the latest version of FSUIPC4 is supported, so you will need to update to 4.974. Note that if you are using the latest FSX-SE beta, please see this post first: Not sure what you mean by this - an error trying to install? If not using the new FSX-SE beta, then please show your install log. As for your actual problem, please see this FAQ entry: John

The order that you press the Ctrl + shift is not important, they are just modifiers to the actual keypress. That is why the keypress codes using lua, which Ramon kindly showed you, are the same. So there is no way to change the order in FSUIPC, but it shouldn't matter. John

Our plans for P3Dv5 will be posted shortly (i.e. later today or tomorrow). John

Hi Peter, FSUIPC4 is not compatible with P3Dv4 - you need FSUIPC5. Yes - available from the Download Links -> Updated Modules section. Just run the installer. It will be installed in a folder called Modules, under your P3Dv4 installation directory. Well, if you have installed P3D in your default programs folder, then FSUIPC will also be installed there, under the P3D directory, as I said. Its relatively straight-forward to move this installation directory after you have installed, either using the DLL.xml install method or the xml add-ons one. I can help you with this if needed, but you must first install in the default location and check it is working as expected. Cheers, John

Just save your FSUIPC5.ini file, located in your Modules folder. Also save your .key file, and you can re-use that instead of re-registering. If you use any other files such as macros (.mcro) or lua scripts (.lua) or profiles in separate files, then you also need to save them. You could just save all the contents of the Modules folder, apart from the FSUIPC5.dll and FSUIPC Documents folder, which will get re-installed. Once you have re-installed P3D and ran it at least once, you can then run the latest FSUIPC5 installer (available from the Download Links -> Updated Modules section). You can skip the registration. Once complete, copy back those files that you saved into the Modules folder. John

This has happened before! I could add an (optional) timeout parameter, but the script developers must then use this and provide a default for the question to continue. Could it be that he is not seeing the question as this script is being started in the ipcReady.lua? Maybe if the script is initially assigned to a button or key press, you could activate the script once P3D is up and fully running to set the language. Once done, you could remove the assignment and add back to the ipcReady.lua? Just a thought... John

Hi Kevin, could you attach your ini file please. John

Did you enter them EXACTLY as shown in the email (better to cut-and-paste)? No, not for FSUIPC4 - Pete can, but if your existing key was working then it should still work - no new key is required. Please forward you registration details to Pete (either by email or private message, do not post them publicly) and he can check them for you. John

Hi "hecrowell", you are commenting on a topic that is over 12 years old... I think this issue is closed by now! Just FYI. John

Hi Angelo, Pete just pointed out to me that you are running a lua plugin: 103562 LUA.0: beginning "C:\Games\Prepar3D v4\Modules\ipcReady.lua" 103562 LUA Asks: "Laap first start - Actual language is French - Do you want the English version ? (Y/N)" This is waiting for a response from an ipc.ask request which looks like its blocking keyboard input. Try renaming that lua script to see if that solves your issue. John

Hi Marc, yes, we will be publishing details of our plans for FSUIPC compatibility for P3Dv5 within the next few days, and certainly before the official release. Regards, John

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?