Thanks for the reply, appreciate your efforts.

Many thanks! I really appreciate your efforts. I will test it later when I get home.

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. Here is one for eg, right at the end he talks about saving the profile for the C172. You'll figure it out. https://www.youtube.com/watch?v=Zxi73gZhXDE

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

This should fix the problem that MS just won't do. After doing this I've never had a problem with long path names. https://www.autodesk.com/support/technical/article/caas/sfdcarticles/sfdcarticles/The-Windows-10-default-path-length-limitation-MAX-PATH-is-256-characters.html

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

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.

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!

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!

Just to give this a bump: Same problem here. Did Asobo mess it up again?

Hi Mark, thanks for your reply. I should have explained a bit more. The issue is that once I select the aircraft livery and other options they save and apply for the current session. However, when I restart Microsoft Flight Simulator 2024 they disappear and I have to select them all again. [image: e6cca261-8c45-4be7-aac7-03dbd607f3e8.png] Not using a beta I have also noticed the MSFS24 marketplace has version 0.4.2 not 0.4.3.

I've just disabled the GSX config for the Avro passengers and unlinked GSX again... SAS livery works fine now... I'll continue to monitor... Rob

Awesome! I'll give that a try!

trying to figure out how too... everything exceeds file size limit.

Hi, still back to the original question. An option to disable the "VLF Update" message at least would be nice.