cteixeira Posted October 5, 2022 Report Share Posted October 5, 2022 Hello Need some help configure arm spoilers when control sent when range entered/exited. When the axis is in the range, they will not arm. I’m using a leveler on my CH throttle quadrant. I’m on FBW320 stable version (0.82). Attached config files and logs. Thanks Sincerely Carlos FSUIPC7.ini FSUIPC7.JoyScan.csv FSUIPC7.log Link to comment Share on other sites More sharing options...
John Dowson Posted October 6, 2022 Report Share Posted October 6, 2022 15 hours ago, cteixeira said: When the axis is in the range, they will not arm. They will only arm when the spoiler axis enters the range. As the range starts at -16384, the axis will never enter the range from below, only from above. Try increasing that to -16000 or so. Also, you need to activate logging for Events to see the controls logged, as they are non-axis events. John Link to comment Share on other sites More sharing options...
cteixeira Posted October 6, 2022 Author Report Share Posted October 6, 2022 Hello Tried as you suggested but still not working. Thanks logs.zip Link to comment Share on other sites More sharing options...
John Dowson Posted October 7, 2022 Report Share Posted October 7, 2022 I do not need to see screen-shots, just your ini and log files are enough. And you assignment screenshot also differs from what your ini shows, and so is confusing: 2=GR,B,-16254,-11573,66066,0,66067,0 -{ DIRECT: SpoilersEntering=SPOILERS_ARM_ON, Leaving=SPOILERS_ARM_OFF }- i.e. from is not -15734 but -16254. The log file shows no spoiler axis movement at all. This is because you used the aircraft "Airbus A320 Neo Asobo" which is not using your A320 profile, and so has no axes assignments. Either add that aircraft to your profile or go back to using the "TAP-TNR". You also have a missing device to which you have assignments: Quote F=<< MISSING JOYSTICK >> F.GUID={848D94B0-177F-11ED-8001-444553540000} This has been re-recognised as device G, to which you also have assignments. This is being caused by your throttle quadrant being recognised twice, once with a new and once without: Quote 296 Device acquired for use: 296 Joystick ID = 0 (Registry okay) 296 0=CH THROTTLE QUADRANT 296 0.GUID={848D94B0-177F-11ED-8001-444553540000} ... 296 Device acquired for use: 296 Joystick ID = 0 (Registry okay) 296 0= 296 0.GUID={848D94B0-177F-11ED-8001-444553540000} The registry entries for that 2nd entry without the name should be removed. You could try disconnecting, removng any drivers you installed, rebootung and then reconnect to see if that solves the issue. Otherwise I can provide you with a script to remove this from the registry completely and then you can re-connect and try again. This is why you keep having to re-assign to that device, as it is continually recongised as a new device. Anyway, I have attempted to correct a few things in the attached ini if you would like to ty with this, and show me a log file with the spoiler movement. Otherwise, we can correct for your throttle quadrant first. John FSUIPC7.ini Link to comment Share on other sites More sharing options...
cteixeira Posted October 7, 2022 Author Report Share Posted October 7, 2022 44 minutes ago, John Dowson said: I do not need to see screen-shots, Sorry about that. 44 minutes ago, John Dowson said: And you assignment screenshot also differs from what your ini shows, and so is confusing: That is because I tried to define the range several times. That explains why the screen-shots calibration numbers are different from the configuration file 49 minutes ago, John Dowson said: This is because you used the aircraft "Airbus A320 Neo Asobo" which is not using your A320 profile, and so has no axes assignments. Either add that aircraft to your profile or go back to using the "TAP-TNR". Do not know why this happened. I only realised the problems when I update MSFS to the latest version (sim update X), and remember that FSUIPC would not recognize axis at all. All I did was update FSUIPC to version 7.3.10, when you release it, and when I tried to assign axis again, I could not arm spoilers with the range enabled. 49 minutes ago, John Dowson said: You could try disconnecting, removng any drivers you installed They are all default windows 11 drivers 1 hour ago, John Dowson said: I can provide you with a script to remove this from the registry completely and then you can re-connect and try again. If you can send thank you. Then I try to the new fsuipc.ini Carlos Link to comment Share on other sites More sharing options...
John Dowson Posted October 7, 2022 Report Share Posted October 7, 2022 1 hour ago, cteixeira said: If you can send thank you. Then I try to the new fsuipc.ini Can you try this one first - just start MSFS/FSUIPC, once it has started exit and show me your updated FSUIPC7.ini and FSUIPC7.log files and I'll see if a registry edit is needed. John FSUIPC7.ini Link to comment Share on other sites More sharing options...
cteixeira Posted October 7, 2022 Author Report Share Posted October 7, 2022 Ok, will try later in the evening Thanks Link to comment Share on other sites More sharing options...
cteixeira Posted October 7, 2022 Author Report Share Posted October 7, 2022 Hello Only start FSUIPC/MSFS and press fly button on LPMA and exit. Attached logs Thanks Carlos FSUIPC7.ini FSUIPC7.JoyScan.csv FSUIPC7.log Link to comment Share on other sites More sharing options...
John Dowson Posted October 7, 2022 Report Share Posted October 7, 2022 Looks like you need to remove a registry entry...I'm finishing now (got to take the dogs for a walk!) - I'll post you a regedit file tomorrow. John 1 Link to comment Share on other sites More sharing options...
cteixeira Posted October 7, 2022 Author Report Share Posted October 7, 2022 😁I have time Link to comment Share on other sites More sharing options...
cteixeira Posted October 8, 2022 Author Report Share Posted October 8, 2022 Hello I did some research about registry problems and joysticks, and I found this thread: https://forum.simflight.com/topic/92411-usb-hid-weirdness-after-adding-a-device-access-to-other-devices-is-lost/ Did the same, unplugged 4 of my usb devices that are in the same hub, rebooted, deleted all registry entries attached, rebooted. Started MSFS, had to assign all axis, and I’ve managed to arm and disarm spoilers only with “spoilers Arm toogle”. It’s not the best way, but it’s better than it was. Carlos FSUIPC7.zip HKLM_SYSTEM_CurrentControlSet_Contro_MediaProperties_PrivateProperties_Joystick_OEM.zip Link to comment Share on other sites More sharing options...
John Dowson Posted October 9, 2022 Report Share Posted October 9, 2022 You still have the same issue - the throttle's GUID is being associated to two devices, one with the name 'CH THROTTLE QUADRANT' and one with an empyt name: Quote ,,, HIDscanning completed N, x00, x068E, x00FA, , -1, -1, 0, {NULL}, {NULL}, {848D94B0-177F-11ED-8001-444553540000}, Y, N N, x00, x0E8F, x0003, , -1, -1, 0, {NULL}, {NULL}, {848DE2D0-177F-11ED-8005-444553540000}, Y, N N, x00, x28DE, x11FF, , -1, -1, 0, {NULL}, {NULL}, {848D94B0-177F-11ED-8001-444553540000}, Y, N N, x00, x294B, x1900, , -1, -1, 0, {NULL}, {NULL}, {848E30F0-177F-11ED-8010-444553540000}, Y, N N, x00, x045E, x02FF, , -1, -1, 0, {NULL}, {NULL}, {89A6C650-17F8-11ED-8001-444553540000}, Y, N N, x00, x068E, x00F2, , -1, -1, 0, {NULL}, {NULL}, {848E5800-177F-11ED-8011-444553540000}, Y, N ,,, REGscanning completed N, x00, x068E, x00FA, CH THROTTLE QUADRANT, -1, 0, 0, {NULL}, {848D94B0-177F-11ED-8001-444553540000}, {848D94B0-177F-11ED-8001-444553540000}, Y, Y N, x00, x0E8F, x0003, USB Joystick, -1, 1, 0, {NULL}, {848DE2D0-177F-11ED-8005-444553540000}, {848DE2D0-177F-11ED-8005-444553540000}, Y, Y N, x00, x28DE, x11FF, , -1, 0, 0, {NULL}, {848D94B0-177F-11ED-8001-444553540000}, {848D94B0-177F-11ED-8001-444553540000}, Y, Y N, x00, x294B, x1900, Alpha Flight Controls, -1, 2, 0, {NULL}, {848E30F0-177F-11ED-8010-444553540000}, {848E30F0-177F-11ED-8010-444553540000}, Y, Y N, x00, x045E, x02FF, Controller (Xbox One For Windows), -1, 4, 0, {NULL}, {89A6C650-17F8-11ED-8001-444553540000}, {89A6C650-17F8-11ED-8001-444553540000}, Y, Y N, x00, x068E, x00F2, CH PRO PEDALS USB, -1, 3, 0, {NULL}, {848E5800-177F-11ED-8011-444553540000}, {848E5800-177F-11ED-8011-444553540000}, Y, Y This looks to be an issue with a phantom xbox one controller entry, the same as reported in this thread: The final solution in that thread was to leave the controller with an empty name, so you are now doing. I don't think there is much else to be done, but I will look into this issue further when time permits. John Link to comment Share on other sites More sharing options...
cteixeira Posted October 9, 2022 Author Report Share Posted October 9, 2022 5 minutes ago, John Dowson said: I don't think there is much else to be done, but I will look into this issue further when time permits. Ok, thanks for the info. I do have a Xbox controller too. When you manage to know what's going on (controller without a name) , please say something. Thank you again Sir. Link to comment Share on other sites More sharing options...
John Dowson Posted October 9, 2022 Report Share Posted October 9, 2022 Yes, your xbox one controller is recognised ok: Quote 141 Product= Controller (Xbox One For Windows) 141 Vendor=045E, Product=02FF (Version 0.0) 141 GUIDs returned for product: VID_045E&PID_02FF: 141 GUID= {89A6C650-17F8-11ED-8001-444553540000} 141 Details: Btns=16, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U65535,V65535,X65535,Y65535,Z65535 Its the phantom one that is causing issue, same as in the previous post I refeenced: Quote 125 Product= Controller (XBOX 360 For Windows) 125 Vendor=28DE, Product=11FF (Version 0.0) You could try running the attached regedit script to remove this, but I suspect windows will just add it back. I may look into getting FSUIPC to ignore such entries if this is going to be an issue, John removexboxcontroller.reg Link to comment Share on other sites More sharing options...
cteixeira Posted October 9, 2022 Author Report Share Posted October 9, 2022 3 hours ago, John Dowson said: You could try running the attached regedit script to remove this I don't have any entries on that registry path. Do you want me to run your removexboxcontroller.reg? Link to comment Share on other sites More sharing options...
cteixeira Posted October 9, 2022 Author Report Share Posted October 9, 2022 2 minutes ago, cteixeira said: I don't have any entries on that registry path. Do you want me to run your removexboxcontroller.reg? ops..wrong path. Will try Link to comment Share on other sites More sharing options...
cteixeira Posted October 9, 2022 Author Report Share Posted October 9, 2022 If they are not there, they cannot be removed: Link to comment Share on other sites More sharing options...
John Dowson Posted October 10, 2022 Report Share Posted October 10, 2022 No point running it if the entries are not there, but it won't do any harm either. Can you set a Log->Custom value of x200200 and show me a log with that logging added. Link to comment Share on other sites More sharing options...
cteixeira Posted October 10, 2022 Author Report Share Posted October 10, 2022 Hello Here they are. Carlos FSUIPC7.ini FSUIPC7.JoyScan.csv FSUIPC7.log Link to comment Share on other sites More sharing options...
John Dowson Posted October 11, 2022 Report Share Posted October 11, 2022 Thanks. I'll take a look at the log in detail when I get time to see if I can do anything about the phantom xbox controller. Link to comment Share on other sites More sharing options...
cteixeira Posted October 11, 2022 Author Report Share Posted October 11, 2022 Ok, thank you Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now