Awesome explanation!!

@Black-Square That worked perfectly. Thanks a lot for taking the time to explain it!

@kityatyi said in The Black Square fleet-wide ILS tracking issue continues: Working Title Cirrus SR22T and the Grumman Albatross Just in case it saves you some time, if both of those aircraft use the WT G1000, then I would expect them not to exhibit the issue, as they have the same WT autopilot as the GNS 530. To obtain useful information from the default aircraft, it would have to be from one without any avionics besides nav/com radios.

@miller39687 Excellent! Glad my guess was at least somewhat accurate. If it's anything less than obvious, please let us know in case someone googles the same question in the future. One of the reasons I like this forum so much is that it appears very high in the Google search results, which hopefully makes solving problems easy for my users.

That was it. It never occurred to me to look in that section of the tablet. And there it was COVERED. Had to start the aircraft up many times to check it out after removing the covers. Thanks to whoever posted that.

Usually in BlackSquare products the GA button functionality depends on what GNS unit you have installed (and thus which autopilot is working under the hood), but in the case of the Caravan, there's no flight director, so GA mode doesn't do anything.

Ok figured it out. In my specific view the selector was hidden. I see the valve now

@Bigmarty Thank you so much for replying with your solution! I was unaware of this mapping, so I might be able to help users in the future who encounter this issue. Thank you!

@joncoughlin Just curious, did you ever figure this out? I'm currently working on the same issue, using Axis and Ohs. I tried to use chatgpt to write an RPN script for the purpose, but probably because I'm not experienced with LLM prompts, I gave up after about a dozen non-working scripts. EDIT: Just to clarify, I'm able to control them with button presses, but I dropped some money on the ProDeskSim F28 levers, which includes the fuel valve levers, so I'd prefer to find a way to bind them to axes. So I can set the LVar to 2/off with the button at the bottom of the axis, and I can set it to 1 when that button is released, but I have no elegant way to then set it to 0. Too bad the Bravo doesn't have detents you can set as buttons, like the Thurstmaster Airbus quadrant.

@djw4250 I'm glad it worked. I've probably spent hours in these sections of the BS manuals. I still feel lost half the time lol

I Used The Pro series of Bonanza, Baron and Caravan and the Analog King Air for the tests. In those tests I used The GTN750 with the KX-155 as well. I also used the GNS430 with the Bonanza. I did not use the GNS430 for the Starship earlier BUT after your post here i just tried to switch over to having the FMS1 by the 430. The flights with the 430 were all OK. So to be clear: There is nothing wrong with how the STARSHIP works, It was me expecting a function it probably should not even have. And it flies so nice & really can keep one busy if one wants! Thanks for taking time Nick. Dave.

@Black-Square Ya know Nick, that unreleased update with the interactable control surfaces sounds like a perfect time to add the cockpit window sun shields and "brakes off" sign in the window we chatted about ages ago Also, taking delivery of our IRL Commander in the next 4-6 weeks. I sent a justflight message with my email ages ago, but haven't heard from you. If you want to connect on Commander stuff, feel free to reach out!

@djw4250 That space usage is kind of a reality check for me lol... but what a cool base to build a simpit around.

Hey, just wanted to bring this up- as you said it looks good so far on the Commander.. have you already worked on a solution?

@Chotter Thanks for this but I am not a mobi expert and am rather lost on what to put where. I have used Mobi, but only with things from the HUB. Your code makes sense to me with what you are doing though. With that said: I think that first I create a new project: Create a new "Add Input Config": Choose Input: In the module, be lazy and scan for input, move a blue prop lever: After that I am at a loss where to go to input the actions you have mentioned. Hope you can drop a little more help.