John Dowson

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....

FSUIPC only recognises HID joystick type devices directly for assignments. Other HID type devices can be programmed using lua. So it depends how your device is recognised by Windoiws...sorry I can't be of more help. There are plenty of arduino users using FSUIPC, so maybe they can help with that.

Ah, ok. But writing to the offsets via mobiflight should have the same result. Sorry, that was wrong. As above, it should be 0=low, 1=off, 2=low, 3=med, 4=hi.

Then I don't understand. If the control is sent with the correct parameters (0=low, 1=off, 2=med, 3=hi) (1=off, 0 or 2=low, 3=med, 4=hi), then this works in the A320Neo, as long as the autobrake buttons are active. Maybe you can try the same controls just using FSUIPC (i.e. without mobiflight) to see if that works.

Ah, ok. Then the additional offset won't help. However, sending the controls (with parameters as previously mentioned) works for me, as do the inc/dec controls (and the MSFS only hi/med/lo ones). I'm not sure why you can't send to the sim, but presume this must be related to your mobiflight configuration which I can't really help with I'm afraid. You could try logging events (as well as buttons and switches maybe) to see what is being sent.

@asessa Would you like me to add that additional read-only offset to reflect the true autobrake setting? Alternatively, I could add a new ini parameter (allowed in both the the [General] and also the [Profile.xxx] sections) that when set would ignore the simvar update to 0 received after a non-zero value was set, so the current offset should hold the correct value. But, both changes would come with a warning as the value may not always reflect the correct setting in all situations (e.g. if you start FSUIPC7 the initial setting will be unknown), but should correct itself one a Set Autobrake Control was sent. Let me know.

Ok, thanks Thomas. I'll increase the value of the allowed parameter for the write to that offset to 6. @asessa If you (or anybody else) would like the the additional offset to show the current autobrake setting for the A320Neo then let me know, although thus wouldn't be able to show the correct value in all situations. I'll also raise a zendesk ticket to see if anything can be added to reflect the current autobrake setting.

Hi Thomas, So 6 is now the max value? For offset 0x2f80, FSUIPC currently only allows for a max value of 5. Can you confirm this and I will update to 6 (although this offset is currently disabled for writing, its activated in v7.0.3c posted above). Ok, yes - they need a simvar to hold the actual state if the current one cannot be used. Do you think it worth adding another read-only offset to show the actual autobrake state (derived from0x2F80 but ignoring the second reset to zero) to handle this for the A320?

It seems that when you try to change the value to anything other than 0 or 1, it automatically changes back to 0 afterwards. I will raise this with Asobo. I guess I could ignore this second update (back to 0), but that would mean that FSUIPC7 is not displaying the value that the sim variable holds, so I'm not sure this is a good idea. I could add another offset, which would display the autobrake setting as determined by fsuipc (i.e. updated as offset 0x2F80 but ignoring any second control setting this parameter to 0). For the time being, I'll post about this on the asobo forums and maybe raise a zendesk ticket, depending upon the response. John

Ok, took another look when in the air (and the buttons active). It seems that the control/offset is working, but with some peculiarities. Sending the Set Autobrake control with the following parameters results in the following actions: param 1 - autobrake off, offset holds 1 param 0 - autobrake low, offset holds 0 param 2 - autobrake low, offset changes to 2 then back to 0 param 3 - autobrake medium, offset changes to 3 then back to 0 param 4 - autobrake high, offset changes to 4 then back to 0 When a param of 2,3 or 4 is sent, I can also see a second Set Autobrake Control being sent with a parameter of 0. Not sure where this is coming from at the moment, I will investigate but this is probably the cause of the offset not holding the correct value, even though the control has actually changed the autobrake setting. The incr/decr controls also work, as do the MSFS set hi/low/med controls. So thats the same as what I have found, This I don't understand. All work ok in FSUIPC, except for the offset status not reflecting the correct state, which seems to be due to the additional control being sent. I don't think FSUIPC is sending this, but I'll check.

Just took a look at the Neo and it looks like the autobrake control is not currently working, or at least its not updating the AUTO BRAKE SWIOTCH CB variable. I'm not familiar with the A320 so I can't tell what the current autobrake setting is, even after clicking on the Auto Brk Lo/Med/Max switches, Updating the offset will send the control (although I don't know if this has any effect), but sending the control won't be reflected in the offset being updated (as the sim var is not updated). I will raise a zendesk ticket for this. There are also a few other controls available that I have also tried which have the same effect: Decrease Autobrake Control Increase Autobrake Control There are also the following additional controls available only in MSFS: Set Autobrake Hi Set Autobrake Med Set Autobrake Lo You can try these (in MSFS) to see if they work for the A320Neo. If so, you can assign a keypress to them (in MSFS), and then assign your buttons/switches to those keypresses in FSUIPC/mobiflight. Where can I see what the current autobrake setting is in the A320Neo - should the lights on the switches turn on?

Did you try running FSUIPC7 after doing this? It shouldn't uninstall earlier versions.... It shouldn't make a difference installing individually oir installing the combo pack (if installing the correct versions). If its still not working, uninstall 2015, 2017 and 2019 and try again with the combo pack.