Joystick Button Assignments Specific to the 146
-
The TMS sync button doesn't currently have an associated MSFS control assignment. The problem we have is the very limited number of suitable assignments that we can 'hijack' for these non-default systems and controls. If you can use LVars then it's "L:R_TMS_Sync, number" (1 = button pushed).
The most significant and not-obvious (e.g. afterburner) control assignments are listed in the manual but we'll try to put together a document dedicated to all the support assignments.
-
The TMS sync button doesn't currently have an associated MSFS control assignment. The problem we have is the very limited number of suitable assignments that we can 'hijack' for these non-default systems and controls. If you can use LVars then it's "L:R_TMS_Sync, number" (1 = button pushed).
The most significant and not-obvious (e.g. afterburner) control assignments are listed in the manual but we'll try to put together a document dedicated to all the support assignments.
@martyn said in Joystick Button Assignments Specific to the 146:
The most significant and not-obvious (e.g. afterburner) control assignments are listed in the manual but we'll try to put together a document dedicated to all the support assignments.
This would be a massive help to SPAD.next users like me if it's not too much trouble :)
-
Hello!
Quick question on the yoke sync button: is there any way to make it unsticky such that it remains activated only for the time I have it pressed? This would make short corrections much easier.
-
The TMS sync button doesn't currently have an associated MSFS control assignment. The problem we have is the very limited number of suitable assignments that we can 'hijack' for these non-default systems and controls. If you can use LVars then it's "L:R_TMS_Sync, number" (1 = button pushed).
The most significant and not-obvious (e.g. afterburner) control assignments are listed in the manual but we'll try to put together a document dedicated to all the support assignments.
-
The TMS sync button doesn't currently have an associated MSFS control assignment. The problem we have is the very limited number of suitable assignments that we can 'hijack' for these non-default systems and controls. If you can use LVars then it's "L:R_TMS_Sync, number" (1 = button pushed).
The most significant and not-obvious (e.g. afterburner) control assignments are listed in the manual but we'll try to put together a document dedicated to all the support assignments.
@martyn how are the lights defined (Beacon, Strobe, Nav, Landing and Taxilights)?
I just got a Honeycomb Alpha/Bravo and the lights came predefined with the MSFS defaults. None of them work and the Switches are blocked in the panel. Had to remove all assignments to get at least the switches working in the panel.Mike
-
@martyn how are the lights defined (Beacon, Strobe, Nav, Landing and Taxilights)?
I just got a Honeycomb Alpha/Bravo and the lights came predefined with the MSFS defaults. None of them work and the Switches are blocked in the panel. Had to remove all assignments to get at least the switches working in the panel.Mike
-
The TMS sync button doesn't currently have an associated MSFS control assignment. The problem we have is the very limited number of suitable assignments that we can 'hijack' for these non-default systems and controls. If you can use LVars then it's "L:R_TMS_Sync, number" (1 = button pushed).
The most significant and not-obvious (e.g. afterburner) control assignments are listed in the manual but we'll try to put together a document dedicated to all the support assignments.
@martyn said in Joystick Button Assignments Specific to the 146:
L:R_TMS_Sync, number
Hi Martyn, thanks for the reply.
I have the latest (paid) version of FSUIPC7 with the WASM module enabled, which should expose all local variables.
I can't see any LVARs for the 146 e.g. in the 'Control sent when button pressed' dropdown of the Button & Switch Assignments dialog.
Are they prefixed in a different way than your description above?
Cheers,
Sledge -
@martyn said in Joystick Button Assignments Specific to the 146:
L:R_TMS_Sync, number
Hi Martyn, thanks for the reply.
I have the latest (paid) version of FSUIPC7 with the WASM module enabled, which should expose all local variables.
I can't see any LVARs for the 146 e.g. in the 'Control sent when button pressed' dropdown of the Button & Switch Assignments dialog.
Are they prefixed in a different way than your description above?
Cheers,
SledgeUpdate: I restarted and can see it in the LVAR list via the WASM function.
Will presume that I have to use it as a custom control and see how I get on.Sledge
-
Update: I restarted and can see it in the LVAR list via the WASM function.
Will presume that I have to use it as a custom control and see how I get on.Sledge
@the-sledge when you have it working could you please share the assignments for taxi and landing lights?
I tried for an hour today to use dev mode and spad data/even monitor to figure it out and failed.
I could see a lighting status flip between 32, 36 and 40 depending on off/taxi/land but - I could see no change when the second switch was moved. ie I suspect I could frig it to set both on as soon as one moved but it feels like I should be able to make it work as the sim does with individual control over each side.
-
@the-sledge when you have it working could you please share the assignments for taxi and landing lights?
I tried for an hour today to use dev mode and spad data/even monitor to figure it out and failed.
I could see a lighting status flip between 32, 36 and 40 depending on off/taxi/land but - I could see no change when the second switch was moved. ie I suspect I could frig it to set both on as soon as one moved but it feels like I should be able to make it work as the sim does with individual control over each side.
Hey. Yes, I got it working fine as a custom offset via FSUIPC.
I will load up the plane and check out the LVAR list again later tonight. Hopefully it stands out as 'obvious'.Sledge
-
@b3lt3r said in Joystick Button Assignments Specific to the 146:
umbwheel configured to manage VS and that actually works in the BAE
Hi Guys I am also starting to get into the 146 and have the alpha bravo Radio and Mutli Panel Combo. I was wondering if anyone hast a more or less complete Multipanel Setup working?
I am struggling a little with getting everything mapped with SPAD. Does not help if you have a toddler that demands all your patience and time :Dcheers
Oli
-
Don't mess with SPAD...it is a subscription and you will have to re-buy every update. Just buy a licensed version for FSUIPC7 from John Dowson here http://www.fsuipc.com/. He has over 10,000 presets from MobiFlight for a bunch of payware including PNDG 737 and the Bae146. Easy to use. John is a flight sim legend and FSUIPC has been around for many years and he continues to update. And you can request a trial period to check it out, usually gives about 3 weeks...
-
Don't mess with SPAD...it is a subscription and you will have to re-buy every update. Just buy a licensed version for FSUIPC7 from John Dowson here http://www.fsuipc.com/. He has over 10,000 presets from MobiFlight for a bunch of payware including PNDG 737 and the Bae146. Easy to use. John is a flight sim legend and FSUIPC has been around for many years and he continues to update. And you can request a trial period to check it out, usually gives about 3 weeks...
@davecat don't know what you are talking about w.r.t SPAD, but it is most definitely has a buy-once model. And not to mention support for other hardware like stream deck, which for me is a great addition.
That being said, FSUIPC can be an addition to it.
-
Clear as mud!! From SPAD
First of all, it cannot be emphasized this enough, your license to use SPAD.neXt will never expire, and you can always use it, once you purchased a license.
For always being up-to-date and being able to use the latest version of SPAD.neXt, you will need a valid update subscription. Once it expires it's your free decision to renew it or not.
If you do not renew it, you will "just" stay at the major release, that was published when the subscription expired. If you decide to renew the subscription later on you can do so.What will be charged for the update subscription?
The pricing for the update subscription has been determined as follows (Dec. 2018):
All prices +VAT.Normal License (any Standard license)
1-Year: €9,99
2-Years: €16,99
3-Years: €22,99
Lifetime: €31,99Complete License:
1-Year: €14,99
2-Years: €24,99
3-Years: €31,99
Lifetime: €49,99
(Also keep in mind, your first year is always included in the license)Do I need to renew the update subscription even with the Complete licence?
Yes. The complete license is just "the complete package" (everything that's there featurewise and will ever be there in future). Nevertheless coding new stuff costs time (and thus money). The update subscriptions is to upkeep the development. Just like e.g P3D. Just that we openly say why, and not just say "Hey, if I change the major version, go and buy a new license, and I change it every year" -
Clear as mud!! From SPAD
First of all, it cannot be emphasized this enough, your license to use SPAD.neXt will never expire, and you can always use it, once you purchased a license.
For always being up-to-date and being able to use the latest version of SPAD.neXt, you will need a valid update subscription. Once it expires it's your free decision to renew it or not.
If you do not renew it, you will "just" stay at the major release, that was published when the subscription expired. If you decide to renew the subscription later on you can do so.What will be charged for the update subscription?
The pricing for the update subscription has been determined as follows (Dec. 2018):
All prices +VAT.Normal License (any Standard license)
1-Year: €9,99
2-Years: €16,99
3-Years: €22,99
Lifetime: €31,99Complete License:
1-Year: €14,99
2-Years: €24,99
3-Years: €31,99
Lifetime: €49,99
(Also keep in mind, your first year is always included in the license)Do I need to renew the update subscription even with the Complete licence?
Yes. The complete license is just "the complete package" (everything that's there featurewise and will ever be there in future). Nevertheless coding new stuff costs time (and thus money). The update subscriptions is to upkeep the development. Just like e.g P3D. Just that we openly say why, and not just say "Hey, if I change the major version, go and buy a new license, and I change it every year"@davecat I see. I have totally forgot about their time-limited licenses, because went complete lifetime when buying for the 1st time.
Ither way. FSUIPC - 25 EUR, SPAD (Standard license, which IMO is enough for home setup) - 32 EUR. With these prices -- both licenses are "pay once". I have FSUIPC for some of the mod tests, but for "just using it" I've been using SPAD for > 1 year now. If you have stream deck/two sims -- it is IMO totally worth it to get a Complete license as well.
But you do you, anyway this is probably not a place for this discussion.
