In-game Fix for 10-Degree-Increment Bug (DI/HSI) in the Piper Arrow III?



  • Everyone with assigned permanent-state switches on their peripherals suffers from not being able to adjust e.g. the heading bug of the DI/HSI in increments of 1 degree. Instead, the dial knob turns in increments of 10 degrees (whether you click the knob with the mouse, use the mouse wheel, or the assigned knob on your peripheral) making operating instruments like these a farce.

    Is there anything JF can do on their side to prevent this from happening in the Piper Arrow III at least? To my surprise I heard that Aerosoft's CRJ is not suffering from this, and it is uncertain whether World Update 4 will bring any in-game fix to this issue.

    Unbinding all permanent-state buttons on my peripherals is not an option for me, same for using third-party software for mapping.



  • @Leonard-McCoy said in In-game Fix for 10-Degree-Increment Bug (DI/HSI) in the Piper Arrow III?:

    Everyone with assigned permanent-state switches on their peripherals suffers from not being able to adjust e.g. the heading bug of the DI/HSI in increments of 1 degree. Instead, the dial knob turns in increments of 10 degrees (whether you click the knob with the mouse, use the mouse wheel, or the assigned knob on your peripheral) making operating instruments like these a farce.

    Is there anything JF can do on their side to prevent this from happening in the Piper Arrow III at least? To my surprise I heard that Aerosoft's CRJ is not suffering from this, and it is uncertain whether World Update 4 will bring any in-game fix to this issue.

    Unbinding all permanent-state buttons on my peripherals is not an option for me, same for using third-party software for mapping.

    Why is using 3rd party for I/O mapping not an option? It's FAR superior, it offers automatic profile switching, and 1000x better flexibility for how you use your hardware. Also keep in mind that pretty much every higher fidelity aircraft that comes out is going to have some or most of its functions based on variables not available in vanilla MSFS, the CRJ is a prime example of that, it uses hordes of LVAR's, and the WT CJ4 is using HVARS, expect this on all the more intricate planes from here on out, so with that in mind, seems like it's a no brainer to get on the bandwagon for a 3rd party tool.



  • @sluflyer06 which one you suggest?



  • @sluflyer06 said in In-game Fix for 10-Degree-Increment Bug (DI/HSI) in the Piper Arrow III?:

    @Leonard-McCoy said in In-game Fix for 10-Degree-Increment Bug (DI/HSI) in the Piper Arrow III?:

    Everyone with assigned permanent-state switches on their peripherals suffers from not being able to adjust e.g. the heading bug of the DI/HSI in increments of 1 degree. Instead, the dial knob turns in increments of 10 degrees (whether you click the knob with the mouse, use the mouse wheel, or the assigned knob on your peripheral) making operating instruments like these a farce.

    Is there anything JF can do on their side to prevent this from happening in the Piper Arrow III at least? To my surprise I heard that Aerosoft's CRJ is not suffering from this, and it is uncertain whether World Update 4 will bring any in-game fix to this issue.

    Unbinding all permanent-state buttons on my peripherals is not an option for me, same for using third-party software for mapping.

    Why is using 3rd party for I/O mapping not an option? It's FAR superior, it offers automatic profile switching, and 1000x better flexibility for how you use your hardware. Also keep in mind that pretty much every higher fidelity aircraft that comes out is going to have some or most of its functions based on variables not available in vanilla MSFS, the CRJ is a prime example of that, it uses hordes of LVAR's, and the WT CJ4 is using HVARS, expect this on all the more intricate planes from here on out, so with that in mind, seems like it's a no brainer to get on the bandwagon for a 3rd party tool.

    Obviously I'm not willing to go to such lengths. A third-party tool should also not be a requirement to run the simulation as intended.



  • “, it offers automatic profile switching, “

    I wasn’t aware of that! Which one?



  • @sluflyer06 said in In-game Fix for 10-Degree-Increment Bug (DI/HSI) in the Piper Arrow III?:

    Why is using 3rd party for I/O mapping not an option? It's FAR superior, it offers automatic profile switching, and 1000x better flexibility for how you use your hardware.

    Not true for a lot of dedicated software. Thrustmaster's Target software provides these features, as does Saitek's. And despite people's irrational aversion towards dedicated controller software (probably stemming from days of yore), the software that comes with your controller is actually very good. Except for Honeycomb, which have decided to not give you any software for MSFS at all.

    Of course, nothing wrong with using 3rd party software.



  • @Leonard-McCoy said in In-game Fix for 10-Degree-Increment Bug (DI/HSI) in the Piper Arrow III?:

    A third-party tool should also not be a requirement to run the simulation as intended.

    And a third party addon manufacturer should not be required to fix bugs in the main sim, but this is what you're asking for, nevertheless. And there's nothing wrong with that, i think.

    So it comes down to whether or not you want to fix your problem. If that's the case, then you will have to use some software, be it the one that comes with your controller, or some other 3rd party software.



  • I wish there were a way to disable input acceleration completely. Even without the 10-degree bug, I find it super annoying when I'm trying to turn a selector to 140 and it goes 137, 138, 139, 150, 160, 170, etc.

    Though I guess this discussion is better suited for the msfs forums



  • @weptburrito I use FSUIPC 7, a development from the classic FSUIPC plugin from FSX, P3D, etc.



  • @Cristi-Neagu said in In-game Fix for 10-Degree-Increment Bug (DI/HSI) in the Piper Arrow III?:

    @Leonard-McCoy said in In-game Fix for 10-Degree-Increment Bug (DI/HSI) in the Piper Arrow III?:

    A third-party tool should also not be a requirement to run the simulation as intended.

    And a third party addon manufacturer should not be required to fix bugs in the main sim, but this is what you're asking for, nevertheless. And there's nothing wrong with that, i think.

    I'm not sure what you're arguing here. There is a difference between an inquiry and a requirement. Obviously, I inquired with JF here whether anything could be done on their side to address this (admittedly sim-wide) issue for their add-on at least (since Aerosoft was apparently able to do so with their CRJ).



  • @Leonard-McCoy

    @Leonard-McCoy said in In-game Fix for 10-Degree-Increment Bug (DI/HSI) in the Piper Arrow III?:

    There is a difference between an inquiry and a requirement.

    There also is a difference between convenience and requirement. You don't require to map all those controls to your hardware in order to fly. You just need a few basics and you're good to go.

    I am simply trying to show the contrast between your hard line approach to not using third party software to solve your problem, and your suggestion that JF should mitigate what essentially would be a third party bug for them. I'm not doing it to get you to stop asking. On the contrary. As i said before, i think that's a perfectly reasonable suggestion. All i'm trying to do is maybe change your mind towards third party software so you can hopefully get the sim experience you're after 🙂



  • @Barabba I have tried both SpadNext and FSUIPC7, SN is far superior and allow you more control assigning multiple functions to a single switch, for instance.



  • @Cristi-Neagu said in In-game Fix for 10-Degree-Increment Bug (DI/HSI) in the Piper Arrow III?:

    @sluflyer06 said in In-game Fix for 10-Degree-Increment Bug (DI/HSI) in the Piper Arrow III?:

    Why is using 3rd party for I/O mapping not an option? It's FAR superior, it offers automatic profile switching, and 1000x better flexibility for how you use your hardware.

    Not true for a lot of dedicated software. Thrustmaster's Target software provides these features, as does Saitek's. And despite people's irrational aversion towards dedicated controller software (probably stemming from days of yore), the software that comes with your controller is actually very good. Except for Honeycomb, which have decided to not give you any software for MSFS at all.

    Of course, nothing wrong with using 3rd party software.

    I didn't know those software can bind to LVAR's and do conditional actions and stuff, that's really cool.



  • I've noticed something strange today. When I started up the Piper in take-off mode using the EFB today, the increment bug failed to materialize. I could adjust all the dial knobs in the aircraft including the heading bug in increments of 1° whether I was using the mouse, mouse wheel or the Honeycomb Bravo dial knob. Since I never usually go flying skipping the entire start-up sequence from cold and dark, I'll do some more testing trying to find out whether it was just a fluke.



  • @Leonard-McCoy Next time you get the bug, open up your control settings and scan through all the controllers looking for a permanently on control. That will be what's causing it. It sounds like something you actuate during preflight. The magneto switch is the usual culprit on Honeycomb controllers.



  • @sluflyer06 I didn't mean lvars, at least when it comes to Thrustmaster's and Saitek's software. But they do allow you to change an always on switch into a pulse control, which no longer triggers the bug.

    But there might be ways to have Thrustmaster's software directly interact with lvars. I'm not sure, though.



  • @Cristi-Neagu said in In-game Fix for 10-Degree-Increment Bug (DI/HSI) in the Piper Arrow III?:

    @Leonard-McCoy Next time you get the bug, open up your control settings and scan through all the controllers looking for a permanently on control. That will be what's causing it. It sounds like something you actuate during preflight. The magneto switch is the usual culprit on Honeycomb controllers.

    I was using all my assigned permanent-state switches, of which there are plenty, as usual.



  • @Leonard-McCoy Well, let's hope the fix from Asobo comes soon. They claim they fixed the "mouse interaction". What that means exactly, and if it fixes the problem, is anyone's guess.



  • Asobo fixed this issue in the most recent update (WU4).