John Dowson

FSUIPC key mappings are visible from the 'Key Presses' tab, where you can review and delete your settings, or program new ones. Check the User Guide from p28. Regards, John

Hi. Active Skye ambient turbulence at aircraft is at offset 8638, and precipitation at 8640. From the offsets documentation, ActiveSky offsets are: 8638 4 ActiveSky needed: Ambient turbulence at aircraft (0-1000), 32- bit float 863C 4 ActiveSky needed: Exported ambient visibility (metres), 32-bit float (-ve if not supported) 8640 41 ActiveSky needed: Exported precipitation type (0 none, 1 rain, 2 snow, 3 hail), 8-bit integer (Byte) 8641 41 ActiveSky needed: Exported precipitation rate (0-4), 8-bit integer (Byte) 8642 41 ActiveSky needed: In cloud flag (non-zero if aircraft is in cloud), Byte ** the byte offsets (8640, 8641, 8642) are 1 byte not 4 (obviously!) - I'll correct the documentation for this [I did strikethrough the incorrect '4' size above, but the strikethrough is not so obvious on that number!] ** Cheers, John

Yes, thats the idea. However, seems strange that the 'PMDG_737NGX_Event_IDS' document (?) seems to specify this event id as 70316. What is the control with event id 70320 in that document? It may be worth clarifying this discrepancy on the PMDG forums, but I would go with the header values rather than the documentation in this case. Cheers, John

Hi Reinhard, did you check the 'Offset Mapping for PMDG 777x' document? All offsets specific to the PMDG Boeing 777 are documented there, with 6 offsets for the CDU. Regards, John

The log doesn't show much. You say the sim crashed 'on take off or mid air' but the log file you posted shows the sim shutting down just after start-up (89 seconds). Crashes on start-up (or shortly thereafter) are usually due to corrupt weather or scenery files. I see you are using Active Sky, so please try with that disabled (from dll.xml), as well as the other tests posted above. Can you also make sure that you start with a default aircraft (and switch to the PMDG 737 later) as this can also cause issues (see https://www.avsim.com/forums/topic/526406-must-i-start-p3d-with-a-default-aircraft/). John

Could you please supply your FSUIPC log file at the time of the crash. Generally such crashes are due to either an incompatibility somewhere or a corrupt file (usually weather or scenery). Have you tried re-installing the P3D client? I'm not sure what add-ons you have running as you have not supplied much information, but you could try disabling one by one to see if any have an incompatibility with P3D 4.5. Crashes can also be due to a corrupt weather file (wxstationlist.bin), although that usually causes a crash pretty quickly. You could try removing that from your Appdata\roaming P3D4 folder - a new one will be re-created when you start. You can also try completely disabling weather by adding NoWeatherAtAll=Yes to the [General] section of your FSUIPC5.ini. Please try these actions and report back - also including your FSUIPC5.log file. Cheers, John

If you post your ini file, I could check if you have anything there that would be sending a flaps control.

Hi Jeff, glad is all working for you now! Joy devices are always numbered, you have to manually activate or assign letters to use the 'Joy Letters' facility (which you should do!). Your ini file looks ok. A few minor things though: 1. You have 3 devices recognised (yoke, pedals, throttle) with ids 1, 0 and 3. However, you also have quite a few assignments to a device with id 2, which is no longer recognised. This can occur if your joystick ids change (by, for example, plugging them into a different port/hub). To prevent this problem in the future, you should really consider either activating the 'AutoAssignLetters' option, or manually assigning letter to your joystick devices yourself (e.g. 'T' for throttle, 'Y; for yoke, etc). See P21 of the user guide for details. Once done. you can manually remove the assignments to your device with id of 2, to clean-up your ini file (although not strictly necessary). 2. You are using 'ShortAircraftNameOk=Substring', so you could edit your ini to shorten your profile names so that they are selected automatically (see p27 of the Advanced guide). Happy Flying! Regards, John

Hi Mustafa, you can try logging 'Events (non-axis controls)' to see what commands are being sent (from the FSUIPC logging tab), but this won't tell you what is sending the command. Maybe also 'Buttons and Key operations' to see if anything is being triggered. That this only happens 'occasionally' is suspicious.... Have you tried the PMDG forums? Cheers, John

I meant "Joy Letters" - see p21 of the User Guide (related to the AutoAssignLetters parameter). You can either post your ini file as text or simply attach to a comment.

Hi Beck, you can try re-installing, but as FSUIPC is only a single dll I don't think this could be caused by it becoming corrupt. Are you using 'Joy Letters'? If not, your joy ids (and maybe even guids) may have changed, invalidating your assignments. You can manually edit the ini file to correct the ids (or correct the ids in the registry) if thats the issue. You can post your ini file if you have doubts and I'll take a look. John

So its crashing when loading/on start-up. When you re-installed 4.4 did you re-install the correct version of your add-ons? Try again without ActiveSky, and also with NoWeatherAtAll=Yes. You should also start with a default aircraft really as well - especially it seems if you use the FSLabs A320 (see this thread: https://www.avsim.com/forums/topic/526406-must-i-start-p3d-with-a-default-aircraft/). John

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