Baron Professional

@lilycrose Same here, also on SU4 Beta. I really hope this can get resolved soon. I've been putting quite a few hours on the Bonanza and the Baron, it's a shame not to see the Hobbs meter go up...

Thanks for the reply, appreciate your efforts.

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

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.

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.

I meant that the code from my first post doesn't work reliably outside of XML, not even with SPLIT or WAIT commands, as you suspected. Of course, I can use the new L:Vars via Axis and Ohs after I've edited the XML file - great!

dont worry too much, focus on important things my wish would be to make the planes more alive. with alive i mean: i was onboard a few GA planes and the noises i heard are far from what i hear in most MSFS planes, also the noises in Airliners are far form what you hear, the cracking of materials etc. a copilot could say something at certain situations, JustFlight 146 has such a copilot and makes the cockpit alive, heatblure also creating an atmosphere in the cockpit not adjusting cabine temp. or not adjusting the cabine altitude should result in consequenzes the plane "speaks" to the passengers depending on what you do. thats why i like the term a plane is alive - is a breathing machine. you might be terrible biased but from my POV there is nothing matching the starship. happy weekend Nick

Interesting! I suspect that wasn't the intended behavior, but I'm not surprised that it persists. Glad you solved it!

See this post https://community.justflight.com/topic/9569/taxi-speed-at-800-1000-rpm-too-fast

See answer in your other post.

Thank you! I agree it's not horrible but the tiny screws disappearing on the panel in VR would be a welcome fix.

Thanks a lot for the quick reply. Problem solved !!

I bet your moving your mouse up and down - try moving it left and right while holding the left mouse button. I'm able to scroll quickly both directions. Same thing for the cowl flaps - took me a while to figure that out.

Dang! Thanks, working now! I just overlooked this option and only saw the checkbox above this one. I made an update of the TDS between flying the Bonanaza and the Baron, maybe this reset it.

Thank you, I’ll dive into the Spad community

Hmmm... no one else is interested in this?