Binding, H-events and other information
-
Forgot to answer about the TOGA button. Just wanted it to animate and do whatever it's supposed to do :)
-
Thank you so much for sharing that link. I will usually go to great lengths to locate something like that, but I couldn't find any clear reference to the KNS81 by searching in the forums.
It's far more than a rumor that the KLN90B will be included in the Dukes. It's in the Just Flight news section, in the product descriptions, in the manuals on the store pages, and in the screenshots. I hope you will enjoy.
The TOGA button will likely only animate using the Asobo template if you use >B:ENGINE_TOGA_1_Toggle instead of >K:AUTO_THROTTLE_TO_GA. The new B:Var system is both a blessing and curse to developers.
-
Cool, looking forward to the Dukes and the KLN90B. Any chance of introducing it to the Bonanza and Barons also?
-
I tried to map the EFIS NAV Source button by incrementing EFIS_NavigationSource, but it did not work.
Is it possible to map this button somehow?
-
EFIS_NavigationSource is read only, I believe. The events for the buttons on the EFIS panel are...
H:EHSI_NavSource
H:EHSI_SystemSource
H:EHSI_TestReference
H:EHSI_SolidBearing
H:EHSI_HollowBearing -
Great, thanks
Backtracking to the TOGA button, I did not manage to get it animated, even after following your instructions and applying the code-change.
-
Does it animate when you click it in the virtual cockpit, or just not when you issue a command like K:AUTO_THROTTLE_TO_GA?
-
I’ll check when back to my FS-computer in a few days… (maybe not, but don’t remember)
-
Not able to press the TOGA button at all with the mouse.
-
BTW: What events would you recommend for adjusting the Barometric pressure and toggle Standard barometric pressure?
And lastly, the CWS-button on the Yoke?
-
I don't know what the issue is with the TOGA button on your end. Like I said, it may not actually be in the model on the publicly available version of the TBM. You can still issue the TOGA command and it will work with whatever GPS software has the capability, but I suggest waiting until the next TBM update for the button animation, if you don't mind terribly.
(>K:KOHLSMAN_INC)
(>K:KOHLSMAN_DEC)
(>K:BAROMETRIC_STD_PRESSURE)(L:var_PilotCws, bool)
-
Thanks, looking forward to the updates of your previous models down the road.
BTW: Have you played with the new ground dynamics?
-
Regarding the UP/DOWN rocker. Is it correct that the altitude can be set to less than 0 feet? It's not showing less than 0, but let's say you press it |Down| once when you have it set at 300 feet. The display then shows as zero, but now let's say you would like to use the VS switch to set it at 2 000 feet. It should be four presses, but at first press, you're at 300, so then not possible to use the VS switch to set 2 000 feet as an example, you would then get closest to 1800 or 2300 feet.
I understand that this is a very minor issue, and also something I could fix with the mapping software (already did), but if this is intended behavior of the instruments, I would ofc like to keep it the way it was. If not, maybe something you could look at for the next updates?
-
Auto Fuel Selector Switch;
when using "L:var_AutoFuelSelectorSwitch, bool", the auto fuel selector on the announcer panel does not turn off, but if moving the switch with the mouse; it turns off. Any idea as to why? -
Ah, I had to check the currently public version, because the next version of the TBM no longer uses L:var_AutoFuelSelectorSwitch.
In the current version, use A:CIRCUIT SWITCH ON:40 AND L:var_AutoFuelSelectorSwitch.
When the next version is released, use only the circuit, not the L:Var.
-
Thanks, btw, the question I asked about in the previous post concerning the rocker, it's a very minor 'issue', but a bit curious as to how it's intended to work; at least I made it so with the hardware mapping that it's not possible to set the data for altitude to less than zero with the rocker.
Also another question about the altitude selector:
https://community.justflight.com/topic/6092/bendix-king-kas-297b-altitude-selector -
I guess this is one of my last questions regarding the TBM and mapping :)
Decision height, is it possible to map the decision height knob, and alt set mode switch?
-
Decision height is (>K:INCREASE_DECISION_HEIGHT) and (>K:DECREASE_DECISION_HEIGHT). By alt set mode switch, do you mean the pull knob on the altitude preselector, or the three position switch to the left of the decision height knob? The former is L:var_VsAdjustMode, the latter is...
L:var_efisDecisionHeightSet = 0 is "NORM"
L:var_efisDecisionHeightSet = 1 is "DH SET"
L:var_efisDecisionHeightTest = 1 is "TEST"I don't have any immediate answers to some of your other questions, but I will get to them and see what I can say soon. Any delay today has been from the one afternoon I've taken off in weeks.
-
Thanks, hope you'll be able to enjoy more spare time soon!
-
@Black-Square said in Binding, H-events and other information:
VsSwitch:
Hi, the VS switch is still giving me headache. How would I implement that with FSUIPC..? Via LUA?
