John Dowson

I'll leave this for other PMDG users to answer (hopefully). You don't say which version of FSUIPC or P3D you are using (or PMDG),. There was an update for the PMDG 747 SDK back in April, and a corresponding update to FSUIPC5 and FSUIPC6, so check you are on the latest versions. If you are, it may also be worth asking on the PMDG forums. John

Your ini's show that both your FSUIPC5 and FSUIPC6 are out of date. Could you update both please - only the latest versions are supported. They also show that your devices are recognised multiple times with different GUIDs. I think it would be worth cleaning these as its hard to tell what assignments are being used, especially without seeing you log and joyscan files. Could you attach both your FSUIPC5.Joyscan.csv and FSUIPC6.joyscan.csv files, as well as an FSUIPC5.log and an FSUIPC6.log and I'll let you know what needs to be removed. AFTER you have updated both version please!. Also re-attach both your ini's. John

But maybe it also affects one of these buttons? I am only suggesting disabling your assignments in MSFS to test to rule this issue out. You can also try activating logging for buttons and events, and produce a short log file where you activate your strobes and the other actions occur. This will show what events are seen. Maybe also another log file when you start on the runway and it works as expected.

The Pan View axis is still available. However, something strange is happening with that axis as if I remove my assignment to it, it no longer appears in the drop-down. Very strange - I will look into it. For the time being, if you select <custom Control>, then enter 66416 in the custom control pop-up, this should assign to Pan View. John

Ah, then that could be why you had assignments to your new device when it was connected. You should certainly activate this. Maybe be a good idea to manually remove the previous assignments first. If you need any help, activate the joyletters facility (change ini parameter AutoAssignLetters in [JoyNames] section to Yes), start P3D/FSUIPC briefly, then attach your .log, .ini and .Joyscan.csv files.

This could be related to a know bug/issue in MSFS with certain controllers/devices that have a constant pressed down state, such as the Honeycomb Alpha yoke and also I believe the TH HOTAS Warthog. Its known to effect heading bug increments but can also can effect other areas. See https://forums.flightsimulator.com/t/heading-increment-bug-10-degree-instead-of-1-explained/290173 for details. To check if this is the issue, try temporarily removing your MSFS assignments to that device, or disconnect the device.

But in the 747-400F, the switch is activating the same macro. Therefore it is the macro that is behaving differently in the different aircraft, no? And, if its a mouse macro, its most probably due to the fact that the rectangle Ids have changed. So you will need to make a new macro for that series of aircraft. Thats because the 400F is already assigned to a profile, as I have tried to explain many times. If you want to create a new profile for that file, you will have to remove it from the existing profile first. To do this, you need to change this line: 1=PMDG 747 so that it sub-matches ONLY those aircraft you wish to use for that profile. As you are extending this, you will probably want to add multiple entries to cover different liveries. You can always just give the full tile of each aircraft if you are finding the substring match difficult, or look into changing the ini parameter ShortAircraftNameOk=Substring to something that works for you. But the profile system is working as expected. You just need to understand how profiles are assigned, re-organise your profile assignments to remove the ones that don't currently work in the profiles they are in, then create a new profile based on the existing profile that mostly works, and then re-do the assignments/macros that need changing. John

@jaxx Please see the following: They were the wrong way around and I added a correction to this and raised with Asobo, and it now looks like this has been fixed. I'll check this and remove the correction I added for the next release. John

I know nothing about MSAddon Linker. if you use that to launch MSFS, then can it also launch FSUIPC7? Alternatively, if its ok to start this after MSFS, then you could use FSUIPC's run Programs facilities to start this. Or you could manually change the provided batch script to start MSFSAddon Linker instead of starting MSFS. It wouldn't if you are not starting it. This I don't understand. So it is running? What launched it? Your installation looks fine, and I don't think using MSFSAddons linker should affect the batch start-up script (and it is working for Katoema!). Can you try starting by double-clicking the file MSFSwithFSUIPC7.bat (located in your installation folder). Using this there will be a command window created (maybe iconized) - please check that for errors. Also, if you can right-click your standard MSFS start-up icon, select Properties and tell me what it says in the URL field please.

Can you please attach your installation log, and also an FSUIPC7.log file please and I'll take a look.

You can create a new profile based upon an existing profile, and then just modify any assignments that need changing for that aircraft. Then as you did not get a menu asking for the profile selection (new, new based, on, etc) then that means that the loaded aircraft has already been assigned a profile, that profile name will appear in the FSUIPC options title bar. As the substring match assigned to your PMDG 747 profile is/was 'PMDG 747-400', then this will be loaded for both the 747-400 and the 747-400f. But again, this contradicts what you have previously said. I think you are failing to understand how profiles work, and the distinction between axis profiles and buttons/key assignments. When you have an aircraft assigned to a profile, in the axis assignments you will automatically see the profile as only the profile axis assignments are used. However, with button and key assignments, general assignments are used and then update (and replaced if necessary) by the profile specific assignments. This is why when you go into the button or key assignments panel, no profile is selected, and so if you add/modify or review any assignments, this will apply to the general profile (i.e. all aircraft). However, if you check the profile specific checkbox, the buttons/keys for that profile are loaded and then any updates made will apply to the profile specific assignments. This allows you to make both general and profile specific key and button assignments when an aircraft is already in a profile. John

Btw, are you using the "JoyLetters" facility? If not, it is possible that the same joy id number has been used. Please check the user manual on how to activate/use this facility if not already.

It won't work for the 800 version as you have the profile set-up for {PMDG 747-400 only: change to: [Profile.PMDG 747] 1=PMDG 747 It should have matched your 400f though, which is strange... What do you actually mean by this? As I have said, when you check the profile specific box, if a profile is defined for that aircraft, it will load the profile and show the name in the dialog title. If there is no current profile defined, then you should see a menu I have previously described. If this is not the case, then tell me what happens . If you are using mouse macros, its quite possible that they will not work between different variants if the rectangle codes for the screen area are different. If thats the case, you will need separate profiles and mouse macros. You can also activate logging for events in fsuipc to check what fsuipc logs.

Yes, of course. All your settings are saved in the ini. I'm sorry, but it is. If you select the profile check box and do not see the menu with options 'Cancel', 'New...', 'New, based on...' and your existing profile names, then this implies that a profile is already assigned to that aircraft, and the profile name will be displayed in the FSUIPC options title bar. I really can't help you unless you show me your FSUIPC6.ini. I'll be away until Monday (most probably) now. John

Please read the section User profiles for all control settings in the FSUIPC User Guide. But the profile name is not important. Its the names you list under the profile that match the aircraft names, and how it matches depends on the ShortAircraftNameOk ini variable (which you should set to Substring) - again, see the user guide. Then check your profile settings. If you select the profile check box and you are not prompted to select a profile or create a new one, this implies that you already have a profile assigned to that aircraft, which seems to contradict your earlier statement. I think you should read the documentation to get a better understanding of how profiles work. If you still have issues after that, please attach your FSUIPC5/6.ini (you don't even say which version of FSUIPC you are using!). John

You can delete the CH throttle assignments if you wish. But really, it does no harm leaving them there. They just won't be used (unless you reconnect that device). If you aren't going to use it again, it may be worth removing those assignments just so that your ini is a bit cleaner/more readable. I suspect that those switches have numbers outside of the range that fsuipc supports (0-31). You can check this in the windows game controller config window. If thats the case, you cannot assign using the UI, and you have to use lua to access (which is why LINDA can see them, as that is a lua based system). There is an example lua provided called HidDemo.lua (in the lua examplex zip file in your FSUIPC documents folder). You can use that, but you will need to edit to provide the correct product and vendor ids. I'm not sure thats correct. There are known issues with the Honeycomb when using MSFS due to the way some of the buttons continually fire, and folks seem to be using FSUIPC to get around this. I'm not sure what the Honeycomb software you mention does, but usually if you are assigning in FSUIPC you don't want any additional device software running, so I would try without that first. What does this software do? I've ordered a honeycomb flight alpha yoke, but I don't think its arriving now until mid January. Its better to disable controllers completely as P3D has a tendency to automatically re-assign. If you haven't disabled controllers, check the assignments again. Did you make any assignments in FSUIPC after you plugged it in? FSUIPC won't do anything unless you make assignments. If you didn't make any, then the assignments must be coming from P3D. John

You should also check that you don't have any assignments in MSFS - are you using an empty profile for that device?

What is the difference between you FSUIPC6.ini and FSUIPC5.ini? Maybe you can attach them both. When this occurs, if you go into the FSUIPC axes assignments dialog, can you see any movement on the throttle axis? Are you using a usb 2 or 3 connection? Maybe try changing the usb connection. However, if its fine in FSUIPC5 it should really be the same in FSUIPC6 as there is very little if any difference in axes handling. It may also be worth checking that you have power management disabled on your usb hubs, as windows has a tendency to re-activate this on updates. Can you also activate logging for axes events, and produce a log file showing your issue and also attach that. John

Yes, you will automatically get a 10euro discount when you purchase from SimMarket, as advertised on the sales page: John

Difficult to tell without further information. Could you activate event and button logging and produce a short log file showing your problem, and attach that as well as your FSUIPC7.ini file and I'll take a look.

Ok. Thanks for the update.

Yes. And this is the expected behavior, as described by Thomas in a previous post. I also proposed a couple of work-arounds for this - maybe you can review those suggestions? I'm not familiar with Mobiflight, but I see Thomas has just responded.... Was the initial problem with the control due to the FBW mod then? If so, maybe let them know. John

Ok. That maybe thats the reason for the difference....although I hope not. If so, I think you need to report to the FBW developers.

I'm slightly confused by this now. Now I understand that you are using an unregistered version, so only the offsets are available (and not direct assignments). In the current released version, offset 0x2F80 is not available, but should be ok in v7.0.3c that I posted earlier. Are you sure you are using that version? If you can see the control (with the correct parameter) being sent, you must be. But I have no idea why this works for me and not for you. Are you using the A320Neo FBW mod by any chance?

Don't do that just to test this....I can provide you with a temporary license to test if needed....