mdee Member

Join Date: Sep 2009 Posts: 356

As far as I can tell after initial testing the problem has been solved in latest firmware (28 June 2019). Will do more testing later. (







This is how it looks like with deadzone which keeps the axes together (4 to 5). Note, this is demonstrated with V1 throttle, but I don't see how this is going to be different with V3 (I'll find out soon).



I have disabled physical locking (button press) in Virpil software to simulate what version 3 does by default (button in throttle axis merge set to 0/---, V3 does not have a physical button which can lock axis copy)





Axes unlocked, moving only one axis.











Deadzone can be set to 0 and jitter will disappear, but (at least with V1) there will be 1-3% difference in values of the axes when locked (enough to make aircraft turn), assuming that physical button (only present in V1 and V2) is disabled in software. V3 does not have a physical button which can be set up to lock the axes in the software, therefore atm it's either jitter or uneven axes values. or if the tolerances are extremely tight it may not be a problem (rather unlikely IMO due to nature of the sensors)



It's about 1 to 2% jump when axis is next to each other physically. Not as massive deal as I thought, but still an issue. Not sure if this can be fixed without physical button, but we will see, maybe a slight delay between detection of two axes being close together and merge would help.



ps. I am not trying to cause an outrage here, I am not going to cancel my pre-order because of this and I have no intention to use any other throttle than Vripil because IMO there is nothing better than it on the market (except when I decide to switch to full Bugeye setup or buy a real F18 ). It's an issue and I am looking forward to Virpil solving it. (just don't make me wait 3 months for new throttle then release V4 pls ) https://forum.virpil.com/index.php?/...test-releases/ ). By default deadzone is set to 2 which may not be enough for locked axes to keep the same value. Raise it to 3-5 and it should work as expected.This is how it looks like with deadzone which keeps the axes together (4 to 5). Note, this is demonstrated with V1 throttle, but I don't see how this is going to be different with V3 (I'll find out soon).I have disabled physical locking (button press) in Virpil software to simulate what version 3 does by default (button in throttle axis merge set to 0/---, V3 does not have a physical button which can lock axis copy)Deadzone can be set to 0 and jitter will disappear, but (at least with V1) there will be 1-3% difference in values of the axes when locked (enough to make aircraft turn), assuming that physical button (only present in V1 and V2) is disabled in software. V3 does not have a physical button which can be set up to lock the axes in the software, therefore atm it's either jitter or uneven axes values. or if the tolerances are extremely tight it may not be a problem (rather unlikely IMO due to nature of the sensors)It's about 1 to 2% jump when axis is next to each other physically. Not as massive deal as I thought, but still an issue. Not sure if this can be fixed without physical button, but we will see, maybe a slight delay between detection of two axes being close together and merge would help. Attached Thumbnails Last edited by mdee; 07-03-2019 at 11:57 AM .