John Dowson

Hi Alan, could you try the 5.151b version posted in this thread (in second to last comment): Its a dll file but named as a .txt - just download it, rename to FSUIPC5.dll and use it to replace the existing one in your modules folder. Thee are only some minor changes in this version, but I would be interested to know if you still get the .NET framework error with this version (was it a COM error?) Thanks, John

FSUIPC5 requires a new license - it is a different product (a near complete rewrite) to FSUIPC4 due to the change from 32-bit to 64-bit. Your WideFS license is still valid. Note that WideServer is now part of FSUIPC5 and so the WideServer application is not needed with FSUIPC5. John P.S. You posted in the FAQ section. I have moved it for you, but please post all support requests here in the support forum.

Hi Alan, does it also crash if you disable Radar Contact? John

If there are key commands, you can assign buttons directly to those. However, reading your earlier post it seems that this works for other aircraft for you, but not the PMDG ones, no? You could also try mouse macros. You will probably need to play around with the mouse control codes - I have had success for left/right knob turns with the mouse-wheel up/down codes, but you will need to try them. I don't have any PMDG aircraft, sorry.

Have you tried activating your lua on the button release as well?

Hi Onno, first, you are using an old unsupported version of FSUIPC5 - can you update to the latest supported version, 5.151. If you still get error 1332, you can manually edit the Modules folder permissions yourself to allow full access, by right clicking on the folder properties: select Security-->Edit-> Add, enter Everyone as the object name, then 'Check Names' and 'OK'. Then give 'Full Control' to the 'Everyone' group just added. Alternatively, as your P3D installation is under the 'Program Files' folder (which is why you are having this issue), you could run P3D as administrator, which would then allow FSUIPC to write to the modules folder. Regards, John

Hi Pietro, your dll looks fine. Enabling logging in SimConnect is defined (for FSX) here (yes, from 2006 and for FSX, but still valid!): For P3D its the same - create the SimConnect.ini file in your P3D documents folder. I will be away from my sim/dev PCs (travelling/working) for the next 8 days so it may take me longer to respond during this period. Cheers, John

The versions are the same, its just that some features are disabled in the unregistered version. If its crashing with the unregistered version, it will also crash in the registered version. Also no point upgrading unless you are going to use some of the features it brings - check the user manual for this. Let me know how it goes with the NoWeatherAtAll flag set. Cheers, John

Hi Ray, the bits I had used to flag for ground/airborne were already in use elsewhere, creating a conflict. Sorry about that. Please try this version: FSUIPC5.txt Cheers, John

Hi Pietro, if there is no FSUIPC in the Add-on menu, then it is not loaded/started which is strange as your installation looks fine. Can you post your DLL.XML file from the Appdata\Roaming L-M folder for P3D4 please (C:\Users\User\AppData\Roaming\Lockheed Martin\Prepar3D v4\DLL.XML). You can also activate SimConnect logging to see why the dll is not loaded. See the FAQ thread for details on how to do this and re-run P3D. Then find the SimConnect log file and show me that please. It should show why it isn't being loaded (assuming your DLL.XML is correct). Thanks, John

This is the FSUIPC support forum. I think you need to post on the support forum for the E-Jets 175/195. John

Hi Ray, please try this updated version (still 5.151b): FSUIPC5.txt This contains some corrections for AI trafiic transitioning from air-to-ground and ground-to-air. Cheers, John

Hi Pietro, the file you attached is the FSUIPC5 install log, which shows that FSUIPC5 was installed correctly to your sim. Can you not see the 'FSUIPC'...'entry in the 'Add-ons' menu? I do not know what you mean by 'we where not able to have P3D v4 connected at PRISIM A320'. Maybe you need support from 'PRISIM A320'? Regards, John

Hi Alan, the usual cause of such crashes is a corrupt weather file, so you first need to eliminate that as a possibility. If you have a wxstationlist.bin file in your Appdata\roaming P3D4 folder (where your PREPAR3D.cfg file is), then please remove it. It will be regenerated when you start P3D. If the file isn't there, or if the problem persists, can you try adding NoWeatherAtAll=Yes to the [General] section of the FSUIPC5.INI file. If that solves your issue, then it could be another corrupt weather file somewhere.. If it doesn't solve your issue, then as you are using an unregistered version it may be something to do with Radar Contact as it looks like that is all you have that is using FSUIPC. We can look into this once the weather has been checked. Btw, do the crashes occur in a certain area or under certain conditions, or do they seem random? what do you mean by 'regular' - on every flight? Cheers, John

Hi Ray, you can try this version (v5.5151b): FSUIPC5.txt (its the dll - download & rename to FSUIPC5.dll). I've added the total ground AI at offset 02A2, and airborne AI at offset 02A4, both 16-bit (U16). No filter by airport I'm afraid. You can get the distance from you in the readable offsets previously mentioned, but only the first 96 each of airborne/ground. Cheers, John

FSUIPC4 will not work with P3Dv4. FSUIPC4 and P3Dv3/FSX are 32-bit whereas FSUIPC5 and P3Dv4 are 64-bit.

FSUIPC5 is a different product to FSUIPC4 and requires a new registration key/license, available from SimMarket. You cannot re-use an FSUIPC4 registration key with FSUIPC5.

Hi Mustafa, great, glad you got it sorted. Yes - I checked that link after I posted and found out that it is no longer available from there. Its on my list to rectify when I get a chance - I'll try and find out where this can be found an either update the link or attach directly (license permitting). Thanks for the heads-up though. Regards, John

Profiles are aircraft dependant. Also, you cannot really share files (the ini file) as your joystick ids (and GUIDs) will be different from other users using the HOTAS Warthog. So I'm afraid your request doesn't really make much sense. It should be relatively straightforward to assign and calibrate your joystick. Please review the User Guide first, and then following the instructions. One thing - before you start assigning and calibration, it is really worth using the 'Joy Letters' facility before you start. This will assign a fixed letter to your joystick device, which will prevent problems later if your joystick id changes (if, for example, you disconnect and reconnect to another USB port). See the 'Joy Letters' section of the User Guide on how to do this. You can also do this after you have assigned/calibrated your joystick device. When you start to assign & calibrate, you should do all general assignments first (e.g. aileron, elevator, rudder, etc). Once you have your general assignments done, you can start using profiles, which are assignments/calibration for a specific aircraft (or set of aircraft) that augment and/or override the general assignments. Again, check the user guide for details on how profiles work. It really is worth reviewing the documentation before you start, and if you run into any issues or have questions, you can post in this forum. Cheers, John

Hi Mustafa, firstly, you are using quite an old (and unsupported) version of FSUIPC - can you update to the latest version, which is v5.151 - you are using 5.124. I think you may be getting erratic behaviour with your PMDG aircraft as in your B737 profile you have your Aileron, Elevator and Spoiler axis assigned in FSUIPC as 'Send direct to FSUIPC Calibration'. For PMDG Boeings, you should assign to 'Send to FS as normal axis' and not calibrate in FSUIPC. The PMDG aircraft intercept the FS controls, in the same way as FSUIPC does for calibration, and use them directly. If you use “Direct to ...” (or even FS controls and then calibrate in FSUIPC) then after calibration FSUIPC sends the controls on to the sim at a lower priority level (to avoid the infinite loop). This results in two, probably different, values arriving in the sim and maybe at slightly different times, causing issues. Therefore please try switching your PMDG axis assignments to 'Send to FS as normal axis' and do not calibrate in FSUIPC. Also still leave controllers disabled in the sim. Btw, even though you currently have these axis as 'Send direct to FSUIPC Calibration', you have not actually calibrated them, which can cause issues. Please make sure you actually calibrate any axis that you send for calibration. As for your joystick problem, this is because your joystick ids have changed and you are not using the 'Joy Letters' facility (see page 21 of User Guide). You should correct the joystick ids first, and once you have your device(s) working correctly, you should either manually assign letters to your devices or set 'AutoAssignLetters=Yes' in the '[JoyNames]' section of the ini (as explained in the User Guide). To correct your joystick ids, you will need to determine what your original ids were. Looking at your 'B737' axis assignments, you have these: 10=6X,256,D,1,0,0,0 -{ DIRECT: Aileron }- 11=6Y,256,D,2,0,0,0 -{ DIRECT: Elevator }- However, you have no corresponding device with id 6 in your '[JoyNames]' section. If these axis were assigned to your 'B737' device, then you would need to change (with sim closed) 7=B737 7.GUID={A79B84E0-1B33-11E9-8001-444553540000} to 6=B737 6.GUID={A79B84E0-1B33-11E9-8001-444553540000} When you restart FSUIPC, it will try to update the ids for you. If this doesn't work, you need to use the JoyIds program to update the registry (see FAQ entry However, in other profiles you have things assigned to device 7, e.g. in '[Axes.Barron 58]' you have:) 10=7X,256,D,18,0,0,0 -{ DIRECT: PropPitch2 }- 11=7Y,256,D,13,0,0,0 -{ DIRECT: Mixture1 }- 12=7Z,256,D,14,0,0,0 -{ DIRECT: Mixture2 }- So its not clear to me what the id number should be. If 6 and 7 are the same device, you could manually update all references of one to the other. To do this, best to leave the ids as currently assigned, and then change all references to device 6 to device 7. Alternatively, you will need to manually re-assign/calibrate that device again. Once you have everything back to working as it should, you should then start using the 'Joy Letters' facility to prevent such problems in the future. Cheers, John

Yes, that is correct. When you assign to 'FS as normal axis', the drop-down will contain all P3D's axis assignment controls, together with other (older) controls know to FSUIPC and some FSUIPC specific controls. When you assign to 'Send direct to FSUIPC calibration', the drop-down will only show the assignments that can be calibrated in FSUIPC. See pages 35 & 36 of the user manual for full details. John

Another tip: when assigning the axis for your PMDG Boeings, use 'Send to FS as normal axis' (not 'Send direct to FSUIPC Calibration') and do not calibrate. The PMDG aircraft intercept the FS controls, in the same way as FSUIPC does for calibration, and use them directly. If you use “Direct to ...” (or even FS controls and then calibrate in FSUIPC) then after calibration FSUIPC sends the controls on to the sim at a lower priority level (to avoid the infinite loop). This results in two, probably different, values arriving in the sim and maybe at slightly different times, causing issues. John

Hi Dieter, the issue may be due to a calibration issue between PMDG and FSUIPC, although I'm unsure as to why this would activate the spoilers. You are currently assigning all your axis 'Direct to FSUIPC calibration'. For PMDG Boeings, you should assign to FS controls and not calibrate in FSUIPC. The PMDG aircraft intercept the FS controls, in the same way as FSUIPC does for calibration, and use them directly. If you use “Direct to ...” (or even FS controls and then calibrate in FSUIPC) then after calibration FSUIPC sends the controls on to the sim at a lower priority level (to avoid the infinite loop). This results in two, probably different, values arriving in the sim and maybe at slightly different times, causing issues. Therefore please try switching your PMDG axis assignments to 'Send to FS as normal axis' and do not calibrate in FSUIPC. Also still leave controllers disabled in the sim. John

Just re-assign the button but make sure that the 'Profile specific' check-box is not ticked. This will add the assignment to the general '[Button]' section. You can then optionally delete/clear your PMDG specific assignment - with the PMDG loaded, select 'profile specific' from the 'Button + Switches' tab, activate the button and then click the 'Clear' button. John

Hi Jose, that would count as one macro, not 57. The limit of 127 is on the number of macro files. Each macro file can have up to 2000 'numbered parameters'. So, if there is only one action per number, that would be up to 2000 actions per macro file. John