Every aircraft has its own file where it was installed to, so it will only effect that one. Make a copy first though. But have you thought to just make a seperate controller curve in the msfs native controllers GUI for that aircraft? There are plenty of YouTube videos that can take you through that process, it's easy and you would have far more control over the outcome. I have several aircraft with custom curves for rudder or elevators, especially some choppers and their pesky torque pedals.

Cockpit doors. Keep the riff raff away from that beautiful cockpit. It’s a realm for wizards, not passengers with no appreciation for the style, nay the elan that is the Starship

@MikeyFlyz Sorry, I have no experience with any of this, so it's hard for me to make suggestions. As far as I'm aware, what gets displayed in the pop-out is exactly what gets rendered in the simulator, so it's hard to believe that could be the source of the desynchronization. Do you just want to describe the problem a little more and maybe share some screenshots? You never know what might give me the right ideas to share.

I think I have a script that will work... as soon as I can get FSUIPC to work with the HVars. I have my HVar file in my community folder, I can activate the HVar via FSUIPC's "Execute Calculator Code," but the ipc.activateHvar function in the lua script is not working. I will reach out to John for help.

also i have the baron with the same alt selector and it works perfeclty on the baron

@MatzeH84 said in TIT gauge?: One this that is puzzling me, maybe you could clarify how it's coded: Let's say I lean ROP. Max EGT is found. Then in the first coloumn the deviation from the max EGT should be shown, correct? As you will be on the lean side, you would have to enrichen to get a zero reading, and from then on to let's say 50° ROP. Does the sign change from negative to positive at some point? Thanks for your other comments and the videos (you made it look way too easy to find those!), but really quickly on this one: I know the slight sign weirdness you're talking about. I believe that results from MSFS's strange mixture behavior (fuel flow increasing as you reduce the mixture when running too rich), but I should be able to eliminate it in my future aircraft with the new fuel flow behavior available in a late sim update for MSFS 2020. I've just implemented this for the first time in my Commander 114, and then if it works well there (looks good so far, and I don't really expect any issues), I will port this back to all my other aircraft.

Thanks for sharing these kinds of moments unsolicited. They really are the reason I work so hard on these aircraft. I've always been a fan of "simulations" of all types, even theatrical performances! I think it's remarkable when the manmade can simulate the emotions of mother nature and our own senses. Thanks again

I understand the massive amount of work you put in and yes it would be a smaller Duke but not massively different in size. Looking forward to your upcoming releases as well.

Circuit #48 should do the trick as long as the avionics switch is on. Circuit #38 is some panel lighting circuit. You could try circuit #2 if you wanted to bypass the switch and just use battery power. Your files look like a pretty good start! I'll send you a quick message on your contact form so you can get in touch with me directly, in case it makes anything easier.

Hi Michael, Quickly, are you on SU4 Beta? I have been told this might be an issue, and all aircraft lighting has been under constant assault on SU4. I literally see something different or broken every time I download a new beta version. If not, then make sure you download the most up to date version of the Bonanza Professional, as there was a tiny mistake that I let sneak through for maybe an hour of downloads after v1.1 involving specifically the Turbine Bonanza's lights.

I just checked the SDK, and it appears that state 2 is "on". The configuration files call for state 3 on loading, which is altitude reporting mode. You can read about some of the previous requests I have received regarding this (there are four states, and it appears that everyone wants something different), and how to change the default to your own liking here, if you so choose. Let me know if you have any more questions!

@KosmicRavioli Thanks for getting in touch (that's a great username). Here is briefly how I was going to answer your first message, but then your second message raises some questions: The Analog Caravan was my first PT6 simulation, and each successive aircraft has received significant improvements as I've learned what's possible in MSFS. While I would have to look at exactly what's simulated in the Caravan (I wrote the code almost four years ago), I am not surprised to hear some of these limitations. For instance, I know I wasn't simulating residual heat at the time (that debuted with the TBM), and I know my starting simulation was also not as refined, and produced the temperature spikes you're seeing (debuted with the Dukes and back-ported, if memory serves). Now, your second post is more interesting, because all these features are included in the Turbine Duke. You should be well over the ITT limit with the power levers firewalled at 24,000ft. In fact, if we look at the performance tables in the manual, we can see by the shading that we become ITT limited somewhere in the neighborhood of 20,000ft. I have one possible thought, although it might sound a little silly. Have you checked the condition of the engines? As they begin to decline below 25%, their power output will decrease, which would probably also decrease ITT, and lead to a loss of airspeed. If you're still having problems with the Turbine Duke, please feel free to send me videos or screenshots, and I can help you troubleshoot from there.

You're speaking of the beta range? That's by design. It is disabled in flight by default (the "Unrestricted Beta Range" tablet option. If you really want to have an additional lock-out/virtual-gate on the ground, you could create a simple script in something like FSUIPC or SPAD, or I could even provide some custom if you need it to achieve exactly what you're looking for.

Looking at the code, I think L:var_RadioMasterSwitch is all you should need!

This has been a long standing issue with Just Flight's installer since MSFS, and we are experimenting with a solution now. If you want to get the most current recommended solution, contact Just Flight Support, and they will send you step-by-step instructions. You can also look at the Official MSFS forums for thoughts and recommendations from other users. Let me know if there is ever anything else I can do for you!

And you know I'm a sucker for my Starship aficionados! She might not be the most popular of airplanes, but she has always been my favorite. I'm so glad that I am able to share her uniqueness with all of you!

@804737 thanks, I figured that is what you were doing because it looks very realistic. And it's funny (in VR) i tried to shade it with my hand.. Unfortunately it didn’t work, lol. I’ll fool around with the contrast as well. Again, great job!

Hopefully coming this week I hear? #superexcited

Ah, didn't know that. Thanks! Also understand the decision not to go for WASM.

Similarly, while programming SPAD as well, I've been trying to understand the CWS/ATT mode further myself and have confused myself with the manual. Should pushing ATT sync the pitch knob/FD to the current pitch of the aircraft? Or should I be pushing CWS first to achieve that? (I suppose that's really an "order of operations" type question perhaps) Thanks!