Sorry I'm a little behind on this thread. @Jiblet said in TQ6+ and the reverse detent: But the caravan goes maybe 20% (a guess) in to its reverse range when you pull the TQ6+ throttle all the way back past the detent to the stop. Pardon me for starting with the basics, but how have you determined this? Are you reading the (A:GENERAL ENG THROTTLE LEVER POSITION:1, percent) variable to see what your hardware is actually setting? If the variable is reading zero when your throttle is against the reverse stop, then the Caravan is not in reverse. Sorry if I sound doubtful. This part of the code should be the same as all my other aircraft, which breaks the throttle input range at exactly 0% and 20% (5% deadband over 15%). Just looking for any hints that might help find you a solution.

There MSFS external view is centered on the model's origin, which we are advised by the SDK to have as close to the center of lift as possible, hence why we see this with high wing aircraft. I agree. Very annoying, but I haven't seen any solutions in the numerous threads I've seen on the subject.

@Black-Square OK great, thank you so much. Always good to know that I'm not doing something wrong. I have managed to avoid this for the most part by turning on the standby generator which kicks in during beta application. This is my first Black Square product as I'm an airliner flier rather than GA and I am so impressed by what a great quality product this is. I hope over time we might see another airliner type product like a B1900, SAAB340 or dare I even dream of a DHC8-100/200/300!

@SadBucket

@hangar_101 It was my error. I had assigned F2 for the Chase Plane Fly-By input, which also happened to be the MSFS 2024 Default Thrust Reverser assignment. So of course I lost power when I did the Fly-By view. I just removed the Default Thrust Reverser assignment from the F2 binding to solve the issue as I don't use it in any case.

the anchor is essentially just the lat and long hold with a visual element. Unfortunately you'll have to imagine it unless it gets added with an update...

I imagine what you cannot see on the gauge is simulated if that's what you're asking.

I believe we are also getting a slight update with the adverse yaw in 1.1 so that you should not see the ball swing left when it should most probably swing right with power application... I don't think moving the indicator is in the cards unfortunately...

@C-FJDH I believe the way the starship is modelled is accurate. I don't believe the Starship NAV mode uses GPSS and thus will roll hunt to center the CDI similar to tracking a VOR. Best option is to center the CDI using HDG hold and then engage it, or place the aircraft near the correct HDG and then use direct to if practicable.

https://community.justflight.com/post/47373

https://community.justflight.com/post/47373

@Zacke I just meant its the same source as the msfs simulated "NEXRAD" not actual NEXRAD**. As of right now there is no way to properly simulate wxr radar in msfs. You may have confused the Starships custom ground radar which would work similarly in logic to the wxr radar if it could be done.

I highly recommend using a linear axis. The PT6 features a flight idle and ground idle position. Flight idle is to be used for eng start and as minimum idle while airborne. Ground idle can be used in lieu of braking at slow speeds to save on brake wear. The further beta detent is the full reverse thrust you would use when landing. It is highly recommended you bind that as a button input to "Throttle 1 Decrease". On the HC Bravo you can use the detent at the bottom end of the axis as it acts as a button depress. I also recommend leaving unrestricted beta range OFF and instant beta on touchdown ON in the tablet so you can leave the throttle at idle into the landing and simply press the reverse thrust button bind to activate reverse thrust after touchdown. You can also bind Throttle 1 Idle to activate on release so the throttle returns to the ground idle position on release of the button. I find this is the best way to use the Black Square aircraft.

Physically correct!

I don't see any way to bind the elevator trim switch natively in the sim, and I also can't find a way to bind it with Axis and Ohs. Watching sim events through AaO, it appears pushing the trim switch with a mouse click activates the same sim events as using the trim wheel. The only thing I can find in the Behaviors inspector that differentiates the trim switch is for animating it. Otherwise all I see is that the switch activates K:ELEVATOR_TRIM_SET, which is also activated by the trim wheel. It's possible there's a way to do it via an RPN script (which you'd also need external software for) but I don't know how. My coding years are far behind me, so maybe (hopefully) someone else can pop into this thread and tell us I'm wrong.

@Tadeus72 When I complete the world tour in a month or so, I developed a “US Western Mountain Loop” tour for the VA I fly with: “We start at Brown Field in San Diego and head north along the Sierra Nevada and Cascade mountain ranges. Upon reaching Mt. Ranier, we travel east and then south along the Rocky Mountain range. The westbound legs include a tour of the Grand Canyon (because it's there, of course) before returning to San Diego. 18 legs, 3088 nm.” It’s here if you’d like to take a look: https://crew.macairvirtual.com/index.php/tour/details/272 This one I intend to fly what I’ll call “scenically low” so I can really appreciate the scenery. I think it will be a wonderful late-spring, early-summer adventure before I start the summer Greek island tour.

Yeah I'd love an actual paintkit with layers but not sure if bksq ever releases those. I don't like doing it all with blender.

I’ll try messing around with it after work and see if I can get the issue replicated and if so come up with some more info that Nick may find helpful.