John Dowson

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

After you have assigned an axis to 'Direct to FSUIPC Calibration, you should then calibrate that axis in the calibration tab. Please check the 'Axis assignments' section of the user manual. You can share profiles between aircraft. If you click the 'Profile specific' option in the assignments tab, you can select a profile to be applied and the aircraft will then inherit that profile (i.e. all assignments and calibration). You can also do this by manually editing the ini file. See the section on profiles in the User Guide. You could manually edit the ini, removing any profile sections that you think are duplicates/not needed, and then re-assign existing profiles to your aircraft (either directly in the ini or via the FSUIPC assignments tab). You are also using 'ShortAircraftNameOk=Substring' so you can shorten the aircraft name strings to also match more aircraft than specifying each one individually - check Appendix 2 in the Advanced User manual. You have two separate axis controls ('R' and 'S') assigned to control the rudder in some profiles, whereas in others the 'S' axis is assigned to your ailerons. I only mentioned as you might want to check those assignments (or maybe just delete the '3S' assignments to '{ DIRECT: Rudder }' if not needed). Note also that button assignments (i.e. those under [Buttons]', not profile specific) are inherited by all profiles, and then the profile specific button sections override/augment these. So you can have most of your button assignments not assigned to a specific profile, and then re-assign for specific profiles where needed. This is not the case with axis assignments, only profile specific ones will be used when a profile is assigned to an aircraft. Let me know how you get on. Cheers, John PS Yes, I was just asking you to check/confirm that this is disabled!

You also have 2 axis assigned to rudder in several of your profiles for some reason : 6=3R,256,D,3,0,0,0 -{ DIRECT: Rudder }- 7=3S,256,D,3,0,0,0 -{ DIRECT: Rudder }- Maybe be ok if thats what you intended but seems a little strange assigning two axis to the same control. John

You ini file indicates that you have assigned your axis 'direct to FSUIPC Calibration' for all your profiles, but you have only actually calibrated in a couple of your profiles, e.g for 'PMDG 737'S' you have: Aileron=-16380,-130,512,16380 Elevator=-16380,-512,512,16380 Rudder=-16380,-512,512,16380 You have no calibration for your 'AEROSOFT AIRBUS' profile, which os the one used in your test. Can you either calibrate each axis (in each profile which doesn't have calibration) or change your assignments to 'Send to FS as normal axis', and repeat your tests please. Also check that you don't have the P3D AutoRudder option enabled. John

Hi Paul, when you 'fully uninstalled the sim', did you also remove 'generated content', as explained in the P3D Download and Installation Directions' (last page)? I ask as your symptoms sound like it could be a corrupt weather file, probably the wxstationlist.bin. Usually this would cause P3D to crash as soon as SimConnect is asked to read the weather. Can you check your user Appdata\roaming P3D4 folder, where your PREPAR3D.cfg file is. If the file is there, please delete it - it will be re-generated when you next start P3D. FSUIPC now removes this file automatically when it shuts down correctly. If that doesn't sort your problem, it could be one of the other wx files. Please make a safe copy of the .wx files in your P3D files folder, in Documents, then delete one at a time, testing after each. Before that, you could try disabling weather completely by adding the following to the [general] section of the ini file: NoWeatherAtAll=Yes Let me know how these tests go. Regards, John

Hi Dieter, that log file doesn't contain anything! You haven't activated the required logging options (see above comment), and you pressed the 'New Log' button which cut the log short. Can you activate those logging options, reproduce the issue and then post the complete log file - don't press the 'New log' button (this simply stops the current log file and starts a new one). Thanks, John

Hi Ray, it doesn't look like this information is easily accessible via Lua. You may be able to differentiate between airborne/ground traffic by counting the number of non-zero entries in the ground/airborne traffic data offsets at E080 / F080, but I'm not 100% sure. I'll take a look in a bit more detail later in the week (and check with Pete!). Cheers, John

Hi, first can you check that you have controllers disabled in P3D. If they are disabled, can you activate 'Axis controls', 'Events (non-axis controls' and 'Buttons and key operations' from the FSUIPC logging tab, make a short (as possible) test flight that exhibits your problem, and then post you FSUIPC5.log file as well as your FSUIPC5.ini file. Cheers, John

Hi Dieter, first can you check that you have controllers disabled in P3D. Can you also activate logging (via FSUIPC's Logging tab) for Axis controls, Events & Button and key operations. Start your sim and reproduce your issues, then post/attach your log file. Thanks, John

What is 'dx'? The 'ctrl' key only augments additional keypresses, same as the shift, alt and cmd/wnd key. So FSUIPC expects another keypress with the 'ctrl'. It cannot be used/assigned on its own. John

That is the only version of FSUIPC5 available. There are various SDKs available which are free for personal use. Check the Download Links -> Useful Additional Programs section. John

Glad its now working for you. 127 is the limit for macro files. The general idea with macros is to try and have only a few macro files per aircraft, split by functional groups. Macro files can hold multiple macros, with a maximum of 2000 numbered parameters per macro file. You should try merging your macros into fewer files before using them for assignments.

Yes, you need a registered version to use the lua interface. John

Hi Jason, FSUIPC should be installed on your sim/P3D system only, and WideClient on the client pcs. Anyway, seems like you have it sorted now. Also, just fyi, WideFS is WideClient + WideServer. WideServer used to be a separate program, but it is now part of FSUIPC since FSUIPC5. Cheers, John

Hi Mustafa, so something is sending a 'decrease flaps command', but I'm not sure if thats related to your issue if you are seeing 5/full. You do have a button on your yoke assigned to this. It would be helpful to see the whole log (with appropriate activations) to try to determine where that originates (ie from your button assignment or not). As to the other events, many add-on aircraft re-purpose P3D events for their own use, so they may be internal to your PMDG add-on. These are generally 'noise' in the log and can be excluded using he 'DontLogThese' parameter (see bottom of page 13 onwards in Advanced User Manual). John

Hi Jason, re-installing the scenery should not affect FSUIPC, and the latest FSUIPC version should be ok with all P3D versions from 4.1 onwards. Is that the full install log ? Seems to be cut short, unless it can't find your P3D installation. If thats your full install log, then it seems that P3d isn't installed correctly. Try re-installing the client only, then re-install FSUIPC and attach the log here. Cheers, John

Hi Jason, if fsuipc isn't in the 'Add-ons' menu, it isn't running, If it isn't running, WideClient can't connect. You need to determine why FSUIPC is not running. Try downloading and running the latest installer. This should re-install FSUIPC and leave any settings you have. Cheers, John

If thats the ini file now, then you have reset, no? There are no assignments there (apart from a few macro assignments to buttons). Change AutoAssignLetters=No to AutoAssignLetters=Yes or manually assign. As I said, please review the user manual to understand this. I will be making this a default value in a future release as its quite a common problem. The only advantage of 'No' is that it allows the user to assign the letters, which may have a relevant meaning (e.g. 'T' for throttle' 'R' for rudder, etc). For the people who don't manually edit the ini file, this is not relevant. John

Also, previously 10 macros, now 3? What are you actually doing? I think maybe you need to reset (i.e. start from scratch), and re-assign. If you do this, please activate Joy Letters before you do so (or after, before you disconnect your usb devices!). And with macros, please remove references to them in your assignments before you remove the macro file. John