Starship

The original manuals are a great place to start for anything you might want more detail on than I supplied. Just do so knowing that you might be surprised once you get in the cockpit. I am always here, and even more happy than usual to answer your questions, given that they concern my favorite aircraft ever built

@Helix said in Simbrief profile for Starship: @Derek ok thanks i understand and am signed up just trying to figure out if i need to take a sick day tomorrow 🫣 I feel something coming on too... definitely some kind of virus going on here, better isolate.

I had to think about the best answer to your question for a couple days, because, truth be told, I actually don't do much testing specifically for performance, but I am constantly thinking about it. I think the simplest answer is "that's the only way I know how to be". From optimizing the 3D model, to packing UV sheets, to programming, I work like I'm still living in the 2000's, when every line of code and every polygon counted. It actually makes me rather upset when I see the default MSFS 2024 aircraft, which waste polygons like graphics cards grow on trees. In some aircraft, over half the recommended polygon budget is wasted on literally inaccessible engine geometry. (In case you've ever wondered why MSFS 2024 runs so poorly) Even in MSFS 2020, there would be knobs in the cockpit with 10x more polygons than they needed. The same goes for textures and code. I am constantly looking for algorithms and shortcuts that I can use to speed up code execution. If I've done my job right, you shouldn't be able to notice. I saw some people who were shocked that my Starship avionics suite was "only" 30,000 lines of code, and my tablet interface is "only" 5,000". All I can say is that this wasn't by accident. I'm quite proud of my optimizations, but that's probably where I should leave it, in case anyone begs to differ. There is always more that can be done, but I try to strike a healthy balance. Excellent question!

From the training manual: "There is no published airspeed limit on the use of the windshield wipers. However, it is recommended that the windshield wipers not be operated above 130 KIAS. Attempting to use the windshield wipers above this speed usually proves ineffective."

I don't know anything about that particular addon (although I've always thought that something similar would be a great idea), but I suspect it would work perfectly with Starship. If the download contains BGL's, which are read into the simulator and usable with the default radios, then they should appear in Starship's database and maps. I'll look forward to finding out!

Well - I say it just insane to simulate something that even real pro multi million dollar simulators does bother to create, or even come to their mind. Absolutely no need to give priority to make it as realistic as possible, without ruin a real engine. Thank you for Omega nav system. I really missed it in flight sim. I hoped it was in Vulcan, but no cigar. I attended a short intro course back then when beauties used hot pants. Fun to finally learn how it works. 48 hours to go. I know the price will be right. The manual is worth it alone, and you get the Starship for free.

You are correct! In SYNC mode, the radar acts as a single transducer, controlled by either the left or the right CDU, and displayed on the pilot's ND, copilots ND, and MFD with all the same parameters and modes. In SPLIT mode, the radar acts as if it were two separate transducers, controlled separately by the left and right CDU's. This would allow the pilot and copilot to each control the radar as they see fit for the situation, but also to display a different radar depiction on the MFD from the pilot's ND. As you said, this might be most useful for keeping an eye on long range weather on the MFD while looking at nearby terrain on the ND, or a similar combination.

That's great to hear! It's one of those areas where Asobo had a good idea but didn't fully think it through during implementation. Like adding removable Pitot-Static and engine covers, but not providing a way to reapply them after a flight...I'm glad to see that you've implemented it in a way that solves this issue.

I'm delighted so many people are taking interest in this old system. I do not simulate any "bad" signals, but I do simulate signal strength around the world for each station. If the signal is poor, the system will automatically disregard it. I gather that the disabling feature was predominantly used under the guidance of some publication that identified when stations were out of service. The same goes for GPS satellites, which can also be deselected by number in Starship's avionics. I had no idea someone had written a genuine Omega emulator! I am familiar with the lane system due to LORAN units, but luckily, Starship does all the Omega adjustments automatically, and there is no interface to view them. I have been wanting to create a LORAN navigator for my aircraft for a while, but it's the complexity of the lane and chain adjustments that are keeping me away.

@Sunake said in Preflight question: I realised you can't leave all the avionics on for engine start because I saw a steamer do it and the generator couldn't handle the load and tripped off. I just love the fact that this can happen!

@Black-Square Fair enough Nick, thanks for the insights Cheers James

And I appreciate your understanding of the compromises that must be made when working within the limitations of someone else's software! Since this is atop my list, I will be starting my investigation in just a minute, and will let you know what I find.

Yeah, but probably a lot of work to implement and I am not sure that's worth the trouble. Slew Mode is a great idea.

I doubt I will find the time for this myself, unfortunately, but I can only imagine the fun of getting the audiobook too and listening to the stories while flying the route. What an experience, especially with the atmospherics of MSFS 2024.

That's exactly what I've done. I'm happy to do it, but I thought I would also share that it was two hour endeavor to... Experiment, export, make the changes, export, find out they weren't enough, export, find more small objects, export, test in MSFS 2020, copy all changes to the release builds, test in MSFS 2024, test in MSFS 2020... That's how these tiny changes can add up to days of work very quickly. It's really the exporting that takes the most time. It's worth it to satisfy my OCD, but I also share just so those most interested in my products might understand why I can't implement every change requested of me, no matter how much I want to. Thanks again! It feels great to eliminate even one more MSFS 2024 issue.

@Guenseli Nice to read that you are seeking to make one of your awesome profiles for the Starship!

@jmarkows "Jet Flap Pre-Swirl", IFYKYK.

@Marionettework I saw! Maybe I can get advanced access to help find other issues

I certainly thought about doing that, but I couldn't think of an easy and meaningful way to implement the drift that would result from that. If I come up with something, I will certainly add it. Sometimes it just takes one good walk outside to come up with the right solution.