MVAMS not saving axis calibration settings
-
violinvelocity
- Posts: 14
- Joined: Tue Oct 28, 2014 10:47 am
MVAMS not saving axis calibration settings
Something developer gents might want to have a look at. Hotfix 1.0.6:
I've been on a constant struggle since day 1 of the beta release to be able to assign axes to my FSUIPC. As a very experienced FSUIPC user- it has been very frustrating to try to make the aircraft's levers match my sim hardware (one only has to look at the "complicated" Dash 8 Q400 from majestic- which has a very effective user interface to setup beta, flight idle, max... etc). Just some constructive criticism.
Finally have been able to get some movement out of assigning levers "to FS as normal axis" and "axis throttle 1 set..." - however in MVAMS, now assigning where the individual detents (MAX, IDLE, BETA, REVERSE) won't "stick"- in fact, as soon as I click assignments, any lever movement causes the assignment lines to snap back to their original positions.
Upon further investigation, trying to configure things in MVAMS doesn't seem to affect the numbers in the axis.cfg file whatsoever.
Hopefully in a future update there will be a more intuitive way to set up hardware- maybe someone could chime in that has successfully set this all up.
I've been on a constant struggle since day 1 of the beta release to be able to assign axes to my FSUIPC. As a very experienced FSUIPC user- it has been very frustrating to try to make the aircraft's levers match my sim hardware (one only has to look at the "complicated" Dash 8 Q400 from majestic- which has a very effective user interface to setup beta, flight idle, max... etc). Just some constructive criticism.
Finally have been able to get some movement out of assigning levers "to FS as normal axis" and "axis throttle 1 set..." - however in MVAMS, now assigning where the individual detents (MAX, IDLE, BETA, REVERSE) won't "stick"- in fact, as soon as I click assignments, any lever movement causes the assignment lines to snap back to their original positions.
Upon further investigation, trying to configure things in MVAMS doesn't seem to affect the numbers in the axis.cfg file whatsoever.
Hopefully in a future update there will be a more intuitive way to set up hardware- maybe someone could chime in that has successfully set this all up.