John Dowson

Its usually beneficial to also install the x86 ones as well. Although not needed by FSUIPC, this can prevent issues with older 32-bit programs. Also does no harm. No problem, glad everything is now working. John

You should set this option in the [General] section of your FSUIPC7.ini file: DisableMSFSMonitor=Enum You may also need to install the combined VC++ redistributable package. Please see the README.txt file provided in the FSUIPC7 zip file you downloaded. John

Nothing looks too bad in your ini, but I would recommend two changes for your DC-6 profile. First, change your [Profile.DC-6] section to the following: This will then match all PMDG-DC6 variants. Secondly, create a profile specific calibration section for your DC-6. To do this, with the DC-6 loaded open the FSUIPC axis assignments panel, go to the calibration tab, check the profile-specific button and then click 'Ok' to save. But I doubt these changes will solve your issue. If you still see the same problem, I need to see your log files. Generate one with your current ini (updated with the proposed changes) and one with a default ini (i.e. temporarily rename your current ini). For both tests, activate logging for Axes Controls, load the DC-6 and move the throttle from min to max and then back again, then exit FSUIPC7. Show me / attach both logs (as well as your updated ini). Note also that when you are using a default ini, you will have to re-assign your throttle in MSFS or it won't have any affect. When you are using your current ini, make sure that you have no assignments to your throttle in MSFS. The easiest way to do this is to switch profiles (in MSFS) - use an empty one for FSUIPC and you can (probably) use the default one when not using FSUIPC (by which I mean with a default ini file, i.e. throttle not assigned. John

Hi RAlpaca, please try the attached lua script. To use, save it to your FSUIPC installation folder and then add it to auto-start either from your general [Auto] section or to your [Auto.xxx] (where xxx is a profile name) if you want to use it for a specific profile, e.g. for my 'Cessna' profile I would use Then, in FSUIPC, delete any calibration you have set on the throttle (from the UI) - either in the general or profile specific calibration settings, whichever you are using for the aircraft. Then assign your throttle to 'Send to FSUIPC Offset' and give the offset value as 0xA000 (if you are using this offset already, change to use a new free user offset and update the throttleAxisOffset variable in the script to match). Then try the script to see how it works for you. I suggest you initially try with the the logging console open (Log -> Open Console), and you can see what %age is being used and the values sent. I've commented the lua so you can change some values to suit your needs. Once you are happy, you can disable the logging in the script by setting the LogActive variable (in the script) to false. Let me know how it goes. John ThrottleControl.lua

No, not that I am aware of. Certainly there are no specific offsets for the PMDG DC6. I don't know if there are any custom controls - take a look at the aircraft documentation 9sorry, I don't have this aircraft). Looking at the MobiFlight preset list for this aircraft (see https://hubhop.mobiflight.com/#/list and set PMDG as provisor and DC_6 as aircraft and you will see the MF presets available) it seems that this aircraft uses the Rotor Brake control with the parameter indicating the actual control. You should have a document with the aircraft that explains what these controls are. For example, looking at the preset PMDGDC6_CABIN_HEAT_TOGGLE, this uses the calculator code '21401 (>K:ROTOR_BRAKE)' (although the close bracket is actually m,issing for this in the preset page!"). To use that in FSUIPC7, you would assign to the Rotor Brake control with a parameter if 21401. Some presets may use lvars or hvars, or even more complex calculator code. It is relatively straightforward to access these in FSUIPC7, but does require some knowledge on how these are ued (see the Advanced User Guide). For the next FSUIPC7 release, hopefully early next week, I will be providing direct access to MobiFlight presets (i.e. they will be available in the controls drop-down menu for button assignment). This has been implemented but not yet released. Alternatively, you can install the MobiFlight WASM module and use the MobiFlight presets by using event files. Some event files are provided in the EventFiles sub-folder of your FSUIPC7 installation, but there i not one available for the DC-6, you would need to create your own. To do this, create a file called DC6.evt in your main FSIOPC7 installation folder, and and add the preset names that you want to use, in the format: where <presetName> is the actual name of the preset you want to use. The event listed in such a file will also be assignable in the button assignments drop-down menu. Of you wait a few days for the next FSUIPC7 release, you will not need to use the MobiFlight WASM as FSUIPC7 will use the calculator code directly for these presets via its own WASM module. John

If ALTITIDE was previously and embedded dll and is now a standalone program, that will explain why it is no longer receiving keypresses directly. However, if this is the case and keyboard input is received by ALTITUDE from MSFS, then it should get this via a SimConnect interface. I think the P3D IVAO client did use FSUIPC offsets, but not the new client for MSFS - at least according to this post: I think you need to talk to IVAO (or ALTITUDE) support about this issue. Please update this thread again if you fund out anything. John

There is offset 0x32F8 which can be used to inhibit certain operations, and offsets 0x310A and 0x341A to disconnect main and auxiliary axis, but none of these will help with a steering axis. If you want to do this, you would have to write a lua script to handle your steering axis. If you did this, you could then monitor for a ctrl key press to stop sending the steering controls when received, and continue when released. John

FSUIPC only sends keys to the FS. Can you please explain how this is working for you in P3D?

Yes, but not yet released. As as I said, will be included in the next release.

👍

Ok, thanks. So changing the id of your yoke also changes the id if your phantom xbox controller. Very strange... I will maybe come back to this when i have more time, but for now, either go back your previous FSUIPC7.ini if you have that saved, or change your [JoyNames] section to the following: If its all working with that (an an empty yoke name), then we can leave it at that (for now). Thanks, John

Please show me /attach your FSUIPC7.log and FSUIPC7.ini files. John

Well, you can use things as they are but I am still not happy that you have an empty device name for your yoke. We could try forcibly changing the device if in the registry. This may be possible via the ini. Can you try changing your [JoyNames] section to the following: Make those changes with FSUIPC7 closed down, then run it once, exit and show me those files again. Thanks. Thanks for the kind offer but no need really - all part of the support service. John

Does that version not crash? If so, please keep using that version. It looks like the OEMName string is being returned as a unicode string for some reason: OEMName found with length 0: 'F' (460041004E004100540045004300200043006C00) That hex string looks like unicode for 'FANATEC Cl' (only the first 10 letters logged). It is very strange that you are getting a unicode string returned. Not sure why this is, I will take a look in more detail when time permits, but if that version is working ok for you I will consider this closed (for now). John

If this was the case, then it looks like you either had a bad calibration configured, or maybe dual assignments (i.e. assigned in MSFS and FSUIPC7. By starting with a fresh ini, you will have lost all of your assignments in FSUIPC7 and will have to start again. If assigning in FSUIPC, please check that you do not also have assignments in MSFS as this can create conflicts. I recommend starting with an empty profile for your controllers in MSFS if assigning in FSUIPC. Yes, please do. John

What isn't working - all the assignments or just the trim wheel ones? This is correct, as documented. I don't know. What aircraft are you using? Maybe the trim control doesn't work for that aircraft? Have you tried in a different aircraft? For any issues, logging is your friend. Try activating logging for Buttons & Keys, Events and also Lua Plugins. You can see what is being logged as it happens by opening the log console (Log->Open Console). You can post/attach your log here and I can take a look. John

Yes, still an issue with xbox 360 controller being recognised, an empty device name, and the same id being assigned two two devices....very strange... Could you try the attach FSUIPC7.ini. This may work, if it allows matching on an empty name string - not sure: FSUIPC7.ini Please try that and report back. Also (if that works or not), could you add the following custom logging (Log->Custom) parameter: x200000 Then exit FSUIPC7, restart, exit again, and show me the generated FSUIPC7.log file.

This will be the issue. You are assigning your button to the back space key, so this is sent to the FS when you press the button. If you have removed the Back Space assignment in MSFS, then this is not going to have any affect when MSFS sees the key press. I presume this was still when you had this assigned in MSFS, no? You can do one of two things: 1. Add back the Back Space key assignment in MSFS, or 2. Assign your button to the control/event that the back space was assigned to in MSFS. This will then send the control directly, and no need for the key press assignment in MSFS (i.e. better). I would recommend keeping the default MSFS key assignments - you only need to remove these if/when assigning keys in FSUIPC. Any further issues, please show me your FSUIPC7.ini file, and an FSUIPC7.log file generated with logging activated for Buttons and Keys as well as Events. John

You didn't include the first line, which is essential, and you also had additional spaces. Please try the attached. John removexboxcontroller.reg

If they are not in the SDK, then probably not. You could take a look at the PDK, but I doubt even that would provide such information (its probably something you would need to derive, somehow, from the appropriate BGL file. Otherwise, seems like a question for P3D support - try asking on their forums. Sorry I can't be of more help, John

Hmm, very strange... Yes please.

Ah, ok. I will take a look when time permits... John

Also check that the mixture control and/or propeller pitch isn't being changed/affected, and check that you don't have any dual assignments, i.e. when assigning in FSUIPC, make sure the MSFS assignments are empty, or at least there are no conflicting assignments.

Hmm, strange. Not sure which version that was, but could you try the attached please, keep the same logging (registry logging) as earlier, let me know if it crashes or not and show me your FSUIPC7.log file as well (crash or not). Thanks. Thanks for the kind offer but really no need - all part of the support service! John FSUIPC7.exe

I don't know why your xbox controller is being given the same GUID (by windows) as your Yoke: Can we try without the xbox controller? Disconnect it (unplug if wired, power off if not) first, then remove the registry entries for this device. To do this, first run regedit and backup your registry (always do this before making registry changes). Then, save the following text as a .reg file (e.g. removeXboxController.reg): Then double click the file (in windows explorer) to tun it and remove the xbox controller registry entries. These will be recreated when you next connect the controller. Once you have done that, reboot, download and use the attached FSUIPC7.ini file (i.e. use this to replace your current one). Then run MSFS/FSUIPC7 (still without connecting your xbox controller) and see if things look ok. If not, show me those 3 files again (FSUIPC7.ini, FSUIPC7.log, FSUIPC7.JoyScan.csv). If everything looks ok, try connecting your xbox controller again - do this with FSUIPC7 shutdown. Once connected, start FSUIPC7 and check your assignments again, Any issues, show me the 3 files. John FSUIPC7.ini