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

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

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

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.

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.

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.

After more testing with the F15 v1.9.1 all looks good just like the F16 mentioned above. The flight model is vastly improved over the previous version. Now in comparing these birds to other fighters released for MSFS (warbirds included) the Airshow Assistant wingman weapons problem is a non issue. From the Heatblur F14, Indiafoxtecho F35, and EF2000, I can find no offering where there's this kind of incompatibility with Airshow Assistant. Wingmen show fully loaded with weapons as presented from the main aircraft the user is flying. Again, whatever was done on DC's end a few versions back it would be nice to see that method return.

I'm not using 3rd party avionics but the GNS530/430 combo and the autopilot here doesn't react on it's own baro settings, too.

Thx a lot!

Increase the failure rate is functionally the same.

+1 for the invisible pushback tug causing this. Have experienced this myself in multiple aircraft and determined by pulling my hair out that it was a tug that had somehow remained connected.

Looks like Nick discovered the problem and has a fix for it

Hi, I'm really enjoying the plane so far. Minor bugs here and there won't take that away! Maybe still someday you'll bring more detailed bus views to electrical view Yes I was talking about the red rectangles. I understand your reasoning about keeping products inline with each other, or maybe you'll change the view on all to more telling. Perhaps black rectangle when not enabled and red to alert raised lid. Clearing the avinics2 situation. You need to be on standby power. Then I have 100% reproduction rate: [image: d3fa7750-c815-4755-9e19-7c9c938aa0f1.jpg] Those conversion numbers might help out too so I don't have to open browser but just could use calculator that's on the desk.

What chart are you looking at? According to the manual, at your altitude and settings, the fuel flow should be 29. [image: 9e5b85be-0003-4a79-8e7d-fece8966a589.png]

If it's an underlying issue with the sim that is causing this excessive thrust at low torque at least it makes sense... I've flown a bit more and the 3rd notch of flaps make a huge difference (who would have thought!). I am now able to control my airspeed in final even on a steep approach. I did a few flights in PNG last night and had a blast!

H:ALT_AltitudeSelectKnob_Dec_1 and H:ALT_AltitudeSelectKnob_Inc_1 are the events for the reference altitude.

@Black-Square is it really only with Starship? I thought it would have been being rolled out to the rest of the fleet by now. Not having the workaround is less of an issue for most starting spots, but drastically limits your options for doing multi leg flights without going back to the menu.