John Dowson

When did it crash? Can you post the log file please.

By 'not working', do you mean that you cannot see your button presses, or your previous assignments are lost? If the latter, then maybe your joystick ids have changed (and you are not using the joy letters facility). That would also affect your axis though! If its the former, then check your log file to see if your devices are recognised.

Thats very strange. Did you try a different aircraft? Are you sure FSUIPC is running (can you see it in the 'Add-ons' menu?) If you already have FSUIPC installed, you can just replaced the FSUIPC5.dll file. The files attached in the posts above are dll files, just download them, rename to 'FSUIPC5.dll' and copy (replace) to your sims 'Module' folder (which is'D:\P3Dv4\Modules\'). If you've re-installed the sim, you may first need to re-install by running the (latest) installer first.

No need to uninstall/reinstall - just rename your ini file (with p3d closed). When you restart, a new one with default values will be generated.Or see P47 of User Guide - 'Resetting Defaults'. Cheers, John

I've looked into the Distributed COM events and think this is a bit of a red herring... Anyway, here's another version to try - 5.151a. In this version, I've simplified the interfaces to the PDK used by FSUIPC (now using only one frame event rather than 2). Can those with this problem please give this a try and report back: FSUIPC5.txt (Again, its a dll file renamed to *.txt to prevent virus-checking problems - please download, rename and install). Thanks, John

Hi Mike, here's another version to try - 5.151a. In this version, I've simplified the interfaces to the PDK used by FSUIPC. Please give it a try and report back: FSUIPC5.txt (Again, is a dll file renamed to *.txt to prevent virus-checking problems - please download, rename and install). Cheers, John

Hi, the FSUIPC5 installer will currently only install FSUIPC5 in the Modules folder of your P3D folder (wherever that is). If you want to move it to a separate location and use the xml add=on installation method, that is possible but you would have to do this manually (its pretty easy - I can post instructions if needed). I will be releasing an updated installer for FSUIPC5 later this year which will default to the newer 'add-on' installation method and so allow you to select an installation directory outside of the main P3D folder. Cheers, John

Hi Robert, can you check that you have controllers disabled in P3D please. Can you also activate logging for 'Buttons and key operations', 'Events (non-axis controls) and 'Axis controls' (from the FSUIPC logging tab), and provide the FSUIPC5.log file exhibiting your problem. Cheers, John

Is that the full log file? The log stops even before FSUIPC open a SimConnect connection to the sim, no aircraft loaded, etc. Did the sim crash on start-up? Thought the crash was when taxiing. Please also try different (default) aircraft, and different locations to try and narrow down the problem - it may well be an incompatible add-on or corrupt file somewhere. John

Hi Mike, GoT will be tonights viewing for me! I've looked a bit into the Distributed COM errors and I also don't think they're related to the P3D crash. Can you reproduce the crash or was it a one-off? Do you have the FSUIPC log file produced at the time of the crash? Cheers, John

Hi, another user posted a similar problem with a CTD after Distributed COM errors in this post: I am looking into this and will report back if I find anything. The above post also contains a link to version 5.150 if you want to revert back to that for the time being to see if this helps. Regards, John P.S. Could you post the Distributed COM errors that you received please, may be useful...

Registration codes can be retrieved from your SimMarket account. John

The problem still exists in P3D with complex aircraft (e.g. PMDG). The time taken to save can also depend on many things - active virus scanning can slow things down to unacceptable levels, and disk speed (SSD or not), fragmentation of available space, etc. Note that FSUIPC just calls the sim's facilities to save the state. Cheers, John

FSUIPC4 is no longer under development. However, I can add this to the feature request list for FSUIPC5 (for P3Dv4) if folks think this useful. Cheers, John

Here's 5.15: FSUIPC5.txt Rename to 'FSUIPC5.dll' once downloaded. John

Roman - yes, sorry... better to enable both options! Paul: no keypresses were logged, so keypresses are not getting to FSUIPC. I see you are using Linda (started from your ipcReady.lua script presumably). You have this in your log file: This looks like its waiting for a response, so this maybe grabbing & blocking keyboard input. As a test, can you disable Linda (e.g. rename your ipcReady.lua to ipcReady.disabled) and also your LaapATCv2.1.lua (by removing from your '[Auto]' section) and re-test. Thanks, John

Hi Patrick, thats interesting...a new feature in 5.151 does use the PDK distributed com interface, so if thats not working it could cause a problem. This seems more to be an issue with your windows installation though. I'll investigate further, and I'll build (and post) a 5.15 version for you (later today) to test. However, 5.15 also uses the PDK, but maybe not distributed COM (I'll check). Cheers, John

The log file is there - you need to configure explorer to show hidden folders and files: Control Panel -> Appearance and Personalization -> Folder Options. John

Hi Paul, sounds strange - keystrokes not handled by FSUIPC are passed directly to the sim. Try activating logging for 'Button and Key operations' in the FSUIPC logging tab. Start your sim and issue some of your short cut commands, then stop the sim. Post your log and ini files. Cheers, John

Did you try disabling Active Sky (as_connect) by editing the dll.xml, as explained in Pete's last post above?

Hi Colin, your log file after the crash, together with the ini. would have been useful! Have you tried the other solutions in this post before posting? i.e. removing wx files, and also disabling weather? If not, please do so. Was the change only from FSUIPC 5.150 to 5.151, or is this also with P3D updated from 4.4 to 4.5? What add-ons are you using? Were any of these updated? So, please try solutions mentioned and report results, and if you are still having problems, post your ini and log files together. Also, if its a CTD, then the windows event log information would also be useful. Thanks, John P.S. what do you mean by 'lags very hard'?

Sorry, those images are specific to CH throttle calibration software. If you want a reverse zone back from idle on the same axis, then you can set that up in the throttle calibration page - just make sure that 'No reverse Zone' is not checked, and set your idle value (as well as Max (full) throttle and reverse (min) values). Check the calibration section starting on page 40 of the User Guide. John

All axis can be reversed by selecting the 'reverse' check-box in the axis calibration screens. For throttles, there is an option to calibrate with or without reverse zones ('No reverse Zone' tick-box, top-left on throttle calibration page). Please check the user manuals. Also, this FAQ entry on setting reverse thrust: John

Hi Gil, no problem, glad you found the issue. Rather than clearing out p3d settings, its better to just disable controllers in P3D. Otherwise you may find that P3D will automatically re-assign (usually when it thinks its found a new axis). Cheers, John

Hi Gil, I'm not sure I understand your problem. Button 7 on the Saitek flight yoke is spring loaded (no?) and sends a button press when pushed to the right and a release event when released. You have programmed the gear toggle for the press only, so the press will activate the control and the release does nothing. So, each time you activate it it will toggle between gear up/down on the button press and do nothing on the release. I therefore don't understand what you mean by 'and lowers the ger when it is released'. Maybe you can activate 'Button and key operations' and 'Events (from non-axis controls) in the logging tab so that you can see what is actually being sent on both the press and release. If FSUIPC isn't sending anything on the release, check you don't have controllers enabled in P3D. Please post your log + ini file once generated and I'll take a look. Btw, is this with a default aircraft or an add-on? If an add-on, please try with a default aircraft first. Cheers, John