Are all the F15 commands in "BMS - Auto-F15ABCD.key"?
-
Hi,
While the F16 has more then 1200 callbacks(“BMS - Auto.key”), the F15 has around 780(“BMS - Auto-F15ABCD.key”).
Is this right or does it also use callbacks from “BMS - Auto”?Thanks
-
@janjan Some are still duplicated/same in both… like AFGearToggle for example
As the work continues to evolve, I’d expect further specialization of F-15 callbacks, fewer duplicates / less overlap.
But some core basics like “pause” and “recenter trackir” will undoubtedly remain the same.
-
@airtex2019 compare the BMS-Full*.key files for the normative lists.
we don’t know what you have or don’t have in your Auto*.key files … that’s up to you
-
-
@airtex2019
I understand that at this time it contains all the necessary command.BTW, my “BMS - Auto” contains ALL teh F16 commands.
-
@janjan oh, was your question, does BMS fallback to bindings in the regular keyfile – ie. is the ‘MyKeyfile-F15ABCD.key’ an “override” layer for ‘MyKeyfile.key’ … similar to how ‘falcon bms user.cfg’ is an override layer applied to ‘falcon bms.cfg’?
in my limited testing - the anser is no. BMS will probe for the existence of ‘MyKeyfile-F15ABCD.key’ and, if not found, it will try to use ‘MyKeyfile.key’
but once in flight … there is only ever 1 of those two keyfiles loaded in memory
-
@airtex2019 yes, that was the question.
I’m in the process of creating another plugin for the F15 and I noticed that there are less commands in the F15.
e.g. the F16 has specific position commands while the F15 does not. (yet)
E.g. f16 has a command to “set air source to norm” while the f15 has a command to toggle it.
From a plugin perspective, toggling is not reliable unless you can now the current switch position.I guess they will keep adding commands in the future.