I think the post immediately above yours indicates that they have.
Ah … I have AAO. So is this possible then with AAO?
99% sure yes, though I’m not super familiar with A&O. Here are the controls I used:
EventActionChangeValue TargetDataDefinition=“LVAR:bksq_TabletVisible” Value=“0” EventActionChangeValue TargetDataDefinition=“LVAR:XMLVAR_YokeHidden1” Value=“1”
EventActionChangeValue TargetDataDefinition=“LVAR:XMLVAR_YokeHidden2” Value=“1”
EventActionChangeValue TargetDataDefinition=“LVAR:bksq_throttleLocks” Value=“0” EventActionChangeValue TargetDataDefinition=“LVAR:bksq_controlLocks” Value=“0”
I might add chocks and covers eventually.
2 Likes
Yes but the dev of the KLN90 is adding some approaches to the GPS, currently only some of them were included I think in the next version you will see more.
A very very nice feature of the KLN90 is OBS mode, very useful for visual approaches as you can line up with the runway from as far as you like. Just make sure to enter the runway course in the HSI and then press the OBS button in the plane which is in the FO panel above, this makes the GPS switch to OBS and now you will capture that radial towards the airport.
ILS capture works fine with the KLN90 I just switch from GPS to NAV when in range and press the APPR button, both localizer and glideslope were correctly captured.
Make sure to put the pitch control knob in neutral before glideslope is captured.
3 Likes
Hopefully they can work with Navigraph to interface with the AIRAC cycle. I’m looking forward to firing up the KLN90 - I used to use that and the -89B back in the day.
Thank you for the helpful and detailed reply 
1 Like
The KLN is using the sim data, if you update it with Navigraph then it is up to date, the issue is that the dev choose to only load some of the procedures in the KLN to be sure they are the procedures that the GPS can do irl but I think some RNAV approaches were missing, those will be added. Is not a problem with the AIRAC.
The KLN90 is using the latest Working Title functions so it works really very well, as well as the WT GNSs.
1 Like
Love the aircraft, other than I have yet to find a way to assign a button for the AP pitch wheel so I don’t have to use my mouse to scroll it for VS adjustments…
The manual says to use “L:var_AP_PitchKnob”, +/- 15 as value.
That said, I created my Spad.Next StreamDeck+ profile using the BKSQ Baron as the basis of the Duke profiles, and even though the Dukes don’t have a VS mode, VS still works if you have controls mapped that way. It’s kind of cheating for me to do this, but I’ll put that on my backlog to “make it real” someday. (I think even IAS mode works as well as an additional ‘cheat’.)
1 Like
I’m probably misunderstanding something, but my assumption, and correct me if I’m wrong, is that a fully-modeled navigator should simply read an navigation data file (like AIRAC) and interpret the procedures built into the data as such. Where I’m confused is the notion of building each procedure into the navigator individually as if the data aren’t complete enough to do so.
You upload a nav cycle into a real Garmin or even the sim Garmins and it just knows the procedures… right? Or do they have to massage those data first?
Yeah I got that. I was basically just thanking the guys who took care of it.
1 Like
If you post on the JF community forum Nick, the dev, is likely to reply to you. He’s currently engaging with the myriad of posts and questions on there now.
Alternatively submit a ticket to our support team and you’ll get a reply with most the content coming from Nick.
I’m using… LVAR:var_PitchTrimPower … 1=on 0=off … works perfectly…
EDIT: …nevermind… answered the wrong question… 
3 Likes
Just bought this- Soon as I loaded the DUKE Modern, turbine. CTD. Strange 
You are right but you can for example load the procedures labeled as “GPS” only in the Nav device, then you have all available in the sim but not all of them in the GPS.
And just now v1.1 of the KLN90 was released with this:
- All RNAV approaches that are allowed for LNAV only will now be available
2 Likes
Just to update on this one, so people don’t get a wrong impression. Now after just 3 additional flights I’ve got:
- An AC blower malfunction
- The lights for the co-pilot side have gone out
- The fuel filter is clogged.
So the frequency seems to be the same as in the King Air. No idea how people fly with higher multipliers 
2 Likes
Perfect - yeah, exclude the ones that are flagged for WAAS (SBAS) or GBAS, good to go!
1 Like
I have these. Definitely a step up from my previous thrustmaster ones and I don’t regret my purchase. Pretty good although probably best described as upper mid range rather than high end.
Yes, “upper-middle” should be good enough for me for rudder pedals. The Yoke/Stick is much more “limbs-on” than the pedals, and I’m happy with my Boeing TM yoke. Can’t quite justify the ~$600 TM Pendular pedals, though I’m sure they’re amazing.
Pedal delivery tonight via Amazon! Still continuing to see intermittent twitching from my current pedals when taxiing, so not a moment to soon.
1 Like
There seem no ingame bindings to work. At the moment you would have to use Scripts via 3rd Party Software (AxisAndOhs/Spadnext).
Here my two Scripts from AxisAndOhs (dots are spaces):
-
Decrease Pitch:
(L:var_AP_PitchKnob,·number)·0.5·+·20·min·(>L:var_AP_PitchKnob,·number) -
Increase Pitch:
(L:var_AP_PitchKnob,·number)·0.5·-·-20·max·(>L:var_AP_PitchKnob,·number)
0.5 are the same steps the var would take on mousewheel scroll. and the actual range is from -20 to +20 with inverted pitch values. Meaning Var goes negative, but pitch goes Up.
Cheers
2 Likes