Starship

Ah yes, I forgot the location I gave is specific to Steam installations and it's different for MS Store installations. Glad you found it, let me know if that did it.

Awesome! Is there also a way to bind an axis? When I tried, I only found an axis set which said only for MSFS2024? So I can't really make a profile, which works in MSFS2020 and 2024?

Awesome, will place a ticket with support, happy to help. Glad to be first. And that makes sense.

Ahhh that’s a shame. I’d got used to all the B/IE goodness making that all easy. At least I can just crack on with an SD profile now

Ah I found that searching the forum it is due to performance reason, I report an extracted part: User Question : “ I noticed that for some of the screens when I pop them out both pilot and copilot screens get popped out at the same time and that is a little annoying if you want to put only the pilot screen in some monitor.” BS Answer: “This is one of the ways I was able to ensure that Starship performs better than most default aircraft in MSFS 2024. I am considering a free "cockpit builders edition" if there is enough interest that sacrifices some performance (if you even want both instruments in that context) for this convenience. In the meantime, hopefully an automated window placement tool could be of assistance.”

@sbanks75 said in Here is how you use Starship Throttles with AAO and reverser: I threw in the towel and went and had a beer in the garden instead! Best option, always!

Hm. I just looked at my reference photos from the real thing, and that aircraft had the 1/10ths of an hour. I wouldn't have made that up out of nowhere though, since I'm all too familiar with recording hobbs time too. I'll look into it.

You gave me a good laugh!

Ok thank you Nick! It's a beautiful plane by the way! Wonderful work

That's actually an adorable feature idea!! It would be very easy to implement from the coding side, given how my temperature simulation works. The model side, on the other hand... not so easy after MSFS 2024. I've actually handled the exact window shades in that very aircraft while conducting research for this project. Fun to think about.

I have told Just Flight's lead developer, and hopefully he will make the bug report with Asobo soon. Thanks again!

@Black-Square thanks. It's not that big a deal, I'm sure someone will publish hardcoded registration livery until they fix this. I just thought I was doing something wrong. MSFS 2024 is definitely still a WIP, but we're all in this for the long haul. As far as I'm concerned, this is the end game airplane, there is nothing else I'm nearly as interested in... unless you do a Velocity v2. I mean I don't know what else there is to do, I hope you do some other Rutan one or something weird/fast/quirky. PS. The textures on those cockpit instruments are so good. I'm looking at them in full sun with glare, at 4K HDR. Flawless. The aircraft is living and breathing.

The fuel and passenger payload should already be saved and restored. Originally, I recall payload setting to be broken in MSFS 2020, but I had the code in all of my aircraft to do it anyway. I believe I have seen it working recently, but I wouldn't swear to it.

@MatzeH84 I just wanted to let you know that, while it might seem that I am focusing my attention on the other thread about deleting waypoints, I believe the two issue are related, so I am not ignoring you!

This one took me a minute to look into. I thought I made a mistake, but the problem is that it's impossible to distinguish an entry of 1505 on the CDU between 150.5 kHz, and 1505.0 kHz without a decimal key. The description in the avionics manual is ambiguous, so I might have to ask one of the owners to test it for me. Ah, I suspect the checklist might not actually be your problem. If you are using external hardware, it's possible that it might be setting (or not setting) the "avionics master" event. I've tried overriding this in all my aircraft, but sometimes I still see it present itself due to the number of hardware/binding software combinations that there are in the wild. This old "radio master" binding still affects some of the radio navigation code in MSFS that hasn't changed since the 90's.

ohhhh, yeah! That's it! Thanks

No worries! No misunderstanding at all! I'm sure you understand that I walk a fine line between people who will be upset with me that I didn't add a feature, and others who will be upset because I did when it's not "realistic". Thank you for your kind words, and I hope you continue to enjoy!

I had an excellent tech instructor during a Beech course many years ago who was heavily involved in the systems engineering behind the Starship (basically adapting earlier 1900 systems and the unique conditioning system was his pervue). He later went on to working on the 1900D project which actually utilized a lot of the systems improvements from Starship. Anyways, he didn't have many particularly positive things to discuss in regards to Burt Rutan. Burt is a visionary and elegant designer of aircraft, and big pioneer of composites in aviation - but ultimately he wasn't a talented production engineer who stuck things out through to the actual production phase. It was explained to my that Burt basically abandoned the program after completion of the smaller scale prototype by Scaled Composites. When it came time to develop the tooling, processes, certification basis, and systems of a true - production quality aircraft - he had largely detached himself from Beech. That, and all the financial troubles and fallout from the Starship program that lead to the eventual purchase of Beech by Raytheon - had left Rutan's name a bit sour at Beechcraft. So anyways, I don't know if Rutan would ultimately be much of an interesting guest in regards to seeing what we enjoy as simmers and what Nick has so generously developed. Simply put, beyond the initial prototype, overall aerodynamics and design (which ultimately was still less efficient and more costly than a similar King Air 350) - Rutan himself was long removed from the Starship project at rollout.