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!

Thanks / Dave!

Thanks for sharing your experience. This is not the first time that I have heard of the native weather radar causing performance issues after a long flight. It seems this only affects a small number of users, and we haven't been able to determine the cause, except that it has something to do with the native weather radar display. Troubleshooting has been slow going, since I've never been able to reproduce this on a computer that I have access to. We found some BIOS settings or graphics driver changes that may have made a difference in the past, but nothing was definitive. Unfortunately, without anything definitive, it's difficult for me to approach Asobo with something for them to look into. If you feel like you're seeing this very consistently, and you're willing to help, I might be able to devise some tests for you to run (editing the weather radar code), but I will warn you that a lot of good men have lost a lot of hours trying to track this one down. Thanks again, and I hope you are otherwise enjoying the aircraft! Let me know if there is ever anything I can do for 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

@djw4250 I do not run 2020 anymore. But I assume the scripts should be the same no matter what sim you are using. I do use the following scripts for 2024 and they seem to work well: Right for Cross feed 19·(>K:FUEL_SELECTOR_2_SET) Right for Off 0·(>K:FUEL_SELECTOR_2_SET) Right for ON 20·(>K:FUEL_SELECTOR_2_SET) For the left you have to replace the 2 with 1 Using these scripts with my hardware does move the switch in game.

@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.

@jmarkows Thanks so much, wasn't 100% sure that's what was meant... so I tried it last night, but didn't reload a flight to check. Appreciate your help.

@Mark Are you still in discussions with Asobo on this issue? I see it's still not resolved in SU5