Piston & Turbine Dukes

That's exactly correct. The yellow band would allow you to fly the aircraft faster in smooth air, but in a turboprop aircraft, there is no such band, meaning that VNO and VNE are the same speed. Unfortunately, I have been unable to locate the logic behind this regulatory decision, but there are several accident reports of structural failure in turboprop conversions flown beyond VNO in turbulent conditions.

Again, I'm not an expert, and I might be wrong about this, but I think you are approaching this in an overly difficult way. That's not a criticism (I seem to approach everything in my life from a difficult angle too), but there are numerous applications that should allow for very easy L:Var manipulation. I'm sure FSUIPC can do it too, but I'm not sure that it requires register manipulation. The B:Var is the new MSFS interaction system, which can be very useful, but it's also incredible abstract and convoluted for developers to set up, so it tends to be underutilized. Not all 3rd part applications have access to B:Vars, so I would try to avoid them wherever possible.

That's correct. Here's a snipped from my manual with an interesting tidbit: Unlike the reciprocating engine version of this aircraft, the combustion heater does not provide any heating to the aircraft, and will never be activated by the temperature controller. The heater has been disabled, because it is not certified for use with jet aircraft fuels, as opposed to aviation fuels. All heating in the aircraft is accomplished via the P3 engine bleed air.

You just need to: Create directory "Microsoft Flight Simulator" inside directory "C:\Users\%USERNAME%\AppData\Roaming" Copy file "UserCfg.opt" from "C:\Users\%USERNAME%\AppData\Local\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalCache" into newly created directory above (1.) That's it - then you can run installer and after install you can remove directory from 1.

I neglected to check the failures tab. The left magneto had failed on and the right magneto failed off.

Yup found it. Thanks. I was actually looking at the A2A Comanche Tablet for it lol

Just resurrecting this old post. As far as I can see there's still no paintkit - is that correct? Any chance Black Square could release one please? I can make do with the plain white aircraft but a paintkit would be easier, to separate out dirt layers and other details (if one exists!)

That’s great, thanks very much.

I was recharging it from the tablet.

I like Elizabethton and Roanoak, cheers

@Black-Square Thank you!

Just experienced this myself. I was definitely not parked on a parking spot. I agree with @seipp that the restriction should only be chocks or brakes, to accommodate airports with crap parking design.

@Noob21 My father purchased the second Piper Navajo Chieftain off the production line (saved from the Lock Haven flood by being in the paint shop). In its first year had de ice boots, radar, and King KN74 RNAV installed. This was 1973. I remember watching the numbers roll up or down when he would change waypoints.

Thanks! @Black-Square

I suspected it was one of your personal touches, I appreciate it. So in this case I should ignore the ETM and keep the engines syncronised based on the engine instruments directly, correct?

@John-S Thanks for the kind words, I'm glad to hear that you are having fun. Logs are a bit difficult, since I cannot write to the file system with JS avionics. Best would be if you could find a reproducible case. Like a sequence of actions and a specific approach that always results in the problems you see. If I can then reproduce the issue on my machine, I can use the debugging tools to see what is going and then it is usually easy to find and fix the issue. The most difficult part is usually to reproduce the issue. A video also helps a lot to see what steps you are taking.

Both engines were at 100%. I've only had the Duke package about a week. I can't thing of any other cause, nothing in my Com Folder but scenery and other aircraft. No performance stuff. It's probably not noticeable in most cases, I only noticed in long cruises when in economy mode. It's by no means a "show stopper" just something I noticed and wanted to see if it was a bug or something I'm doing wrong.

That would be a fun feature (and one that would be both fascinating and horrifying in the real world). Unfortunately, Asobo has not made it possible to save any kind of file from the Javascript context, presumably for security reasons. This means that I am limited in the size and formats that I can choose for stored data within the simulator's own state saving, which I have found not to be terribly reliable. I have brainstormed many amazing features that I would add with better or more stable state saving, but that would either require me to build my own internal networking protocol between JS and WASM (I've done that once already for JS to/from RPN), or for something to change on Asobo's side of things. Trust me, I have lots of ideas, and I will add yours to the list! I would enjoy asymmetric flap extension in aircraft where that is possible. For the Starship in particular, it's theoretically possible for the flaps to become asymmetric, as well as out of sync with the forward wing, which could produce some interesting results. Almost anything is possible in MSFS if you want it badly enough, but the native aerodynamics simulation does not provide any way of achieving this without the kind of creative solutions that I have created for most features in my aircraft.