casv
-
Posts
12 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Gallery
Downloads
Posts posted by casv
-
-
Thank you John. I will wait for this updated version to test.
-
51 minutes ago, John Dowson said:
I have the Bravo and know how it works. Can you please attach your FSUIPC7.ini file please, rather than images.
I will look into this later, but I suspect that this is an issue with the aircraft - FSUIPC is just sending the Throttle Decr control/event, and it should be up to the aircraft to know when the limit is reached. So I suspect that the underlying issue must be fixed by the aircraft developers, but it may be possible to use a lua script instead, which would stop sending the Throttle Decr control/event once the limit was reached. I will look into this later and get back to you.
John
Hello John.
FSUIPC7.ini file is attached here.
Thank you.
Kind regards.
-
Yes, that is my impression. However I am not sure about the value -4096. I am just using these settings as in the attached picture. Same settings is fine with PMDG 737. I believe Asobo B787-10 and Kuro B787-8 behaves same like the Horizon B787-9 one, since they almost stop when landing on the runway with the thrust reverser handler active.
I am using of latest FSUIPC v7.3.25.The throttle handler has reverse handlers but act as a button when dragging them backwards. See link below.
-
Hello,
I am having issues to use the thrust reverser with Horizon B787-9 using a button on my Honeycomb Bravo. Behavior described on this link
https://www.avsim.com/forums/topic/638913-horizon-787-9-v10-released/?do=findComment&comment=5025126
I use these settings just like this
It is working with PMDG 737 for MSFS but not with Asobo/Horizon/Kuro 787 AAU2.
Perhaps you may know why?
Kind regards
FSUIPC7 Thrust reverser breaks built-in MSFS SIM limitation?
in FSUIPC7 MSFS
Posted
Just tested your updated version, looks like that it is working fine. I was on the runway with the parking brake set to on. And the plane does not move backwards with the reverser active. (That was the case prior to this issue). I guess that this version is good now. Thank you.