Heading bug changing when toggle landing gear using binded key
-
Had Anyone experienced bug that heading bug jump to ~122º (or other position) when toggling landing gears using some binded key?
It happens only with PA28R Arrow III (not turbo) and using binded key (e.g. "G" key or some other device button). Toggling landing gears with mouse don't trigger the bug.
Piper Bundle Version: 0.5.8 (MSFS Marketplace)
-
Had Anyone experienced bug that heading bug jump to ~122º (or other position) when toggling landing gears using some binded key?
It happens only with PA28R Arrow III (not turbo) and using binded key (e.g. "G" key or some other device button). Toggling landing gears with mouse don't trigger the bug.
Piper Bundle Version: 0.5.8 (MSFS Marketplace)
-
Had Anyone experienced bug that heading bug jump to ~122º (or other position) when toggling landing gears using some binded key?
It happens only with PA28R Arrow III (not turbo) and using binded key (e.g. "G" key or some other device button). Toggling landing gears with mouse don't trigger the bug.
Piper Bundle Version: 0.5.8 (MSFS Marketplace)
@andrelimasantos Yes, same problem here. It's puzzled me for ages, how and why it is happening, but you're right - it's the G key, bound to toggle landing gear.
-
Hi there, fine folks at JF.
I wonder if you could hurry this one up a little. Toggling the gear on long finals ( or anywhere in the circuit ) and the aircraft suddenly heading off in the wrong direction is exasperating to say the least.
Another issue - recently, I've found it increasingly difficult to keep the aircraft trimmed while climbing. The vertical speed can vary from between zero and 1000 ft per minute, and never settles down. Trimming always has been one of this model's few weak points, but it seems to have got worse recently. Maybe a SU is responsible, but could it be looked into, please ?
-
Hi there, fine folks at JF.
I wonder if you could hurry this one up a little. Toggling the gear on long finals ( or anywhere in the circuit ) and the aircraft suddenly heading off in the wrong direction is exasperating to say the least.
Another issue - recently, I've found it increasingly difficult to keep the aircraft trimmed while climbing. The vertical speed can vary from between zero and 1000 ft per minute, and never settles down. Trimming always has been one of this model's few weak points, but it seems to have got worse recently. Maybe a SU is responsible, but could it be looked into, please ?
@paul_k said in Heading bug changing when toggle landing gear using binded key:
Hi there, fine folks at JF.
I wonder if you could hurry this one up a little. Toggling the gear on long finals ( or anywhere in the circuit ) and the aircraft suddenly heading off in the wrong direction is exasperating to say the least.
Another issue - recently, I've found it increasingly difficult to keep the aircraft trimmed while climbing. The vertical speed can vary from between zero and 1000 ft per minute, and never settles down. Trimming always has been one of this model's few weak points, but it seems to have got worse recently. Maybe a SU is responsible, but could it be looked into, please ?
Looking at 10.4 and 10.5 this should have been fixed. If it isn't, worth submiotting a support ticket.
https://support.justflight.com/support/solutions/articles/17000115071-pa-28r-arrow-iii-msfs-changelog
-
@paul_k said in Heading bug changing when toggle landing gear using binded key:
Hi there, fine folks at JF.
I wonder if you could hurry this one up a little. Toggling the gear on long finals ( or anywhere in the circuit ) and the aircraft suddenly heading off in the wrong direction is exasperating to say the least.
Another issue - recently, I've found it increasingly difficult to keep the aircraft trimmed while climbing. The vertical speed can vary from between zero and 1000 ft per minute, and never settles down. Trimming always has been one of this model's few weak points, but it seems to have got worse recently. Maybe a SU is responsible, but could it be looked into, please ?
Looking at 10.4 and 10.5 this should have been fixed. If it isn't, worth submiotting a support ticket.
https://support.justflight.com/support/solutions/articles/17000115071-pa-28r-arrow-iii-msfs-changelog
@derek said in Heading bug changing when toggle landing gear using binded key:
@paul_k said in Heading bug changing when toggle landing gear using binded key:
Hi there, fine folks at JF.
I wonder if you could hurry this one up a little. Toggling the gear on long finals ( or anywhere in the circuit ) and the aircraft suddenly heading off in the wrong direction is exasperating to say the least.
Another issue - recently, I've found it increasingly difficult to keep the aircraft trimmed while climbing. The vertical speed can vary from between zero and 1000 ft per minute, and never settles down. Trimming always has been one of this model's few weak points, but it seems to have got worse recently. Maybe a SU is responsible, but could it be looked into, please ?
Looking at 10.4 and 10.5 this should have been fixed. If it isn't, worth submiotting a support ticket.
https://support.justflight.com/support/solutions/articles/17000115071-pa-28r-arrow-iii-msfs-changelog
It's already been reported by the OP, and acknowledged by Martyn - see posts above. Definitely not fixed yet.
-
Just noticed this same problem. Still persists with a freshly reinstalled 10.5 version. It happens with any keyboard key or other controller device button bound to landing gear toggle. Really irritating, hoping that things like this will still get fixed.
-
Same problem here
-
@andrelimasantos Thanks for reporting this issue. It will be fixed in the next update.
Hi @martyn
The bug persists in MSFS Marketplace version (bundle).
I have not received any updates since I purchased it (APR 2022).With these many updates released by Asobo/Microsoft new bugs are to be expected, buy we haven't had any updates from JustFlight about Pipers on MSFS Marketplace.
Actual manifest file content versions:
"title": "PA28 Arrow Bundle"
"package_version": "0.5.8"
"minimum_game_version": "1.26.5" -
Apologies, I thought this had already been fixed in the previous update. I can confirm that it's definitely fixed in the update that we're aiming to release next week.
