The problem is that people are getting too comfortable, now it seems that if you don't hit the magic button to port everything and get almost everything done the addon is no good.

I did most of my flight-training and flying in the 70's.  To be honest, I thought VOR navigation (and VOR approaches for non-ILS fields) were modern miracles (though the first time I went under the hood and made a flight attempting to keep my needles centered and the aircraft on altitude I was all over the place).

I am certainly enjoying the modern flight management systems that are even installed in many basic GA aircraft, but when something like the Starship comes along and I get to go back to more of the flight management practices of my flying years it's a blast.  It's actually quite advanced in comparison to what I flew, in that I can enter all of my navaid frequencies for the entire flight, have a displayed flight path and it will even auto-tune - pretty nifty really.  And, playing around with the VLF/Omega system is going to be interesting too!

I have been flying it waaaay too much... waaaaaaaaaaaay too much.

8 hours ago, Aglos77 said:

The problem is that people are getting too comfortable, now it seems that if you don't hit the magic button to port everything and get almost everything done the addon is no good.

It's the children of magenta effect that is so pervasive in aviation now.  People want as much automation as possible.  They don't want to put in the work for flight planning, hand-flying, older navigation methods, or accepting the realism they claim they desire.  Folks are asking for metric units, but it seems the Starship was never fully made with metric units.  They can't be bothered to convert from pounds to kilograms.  They want flight plan importing, which is not realistic in a GA plane.  They want GPS units that were never installed in the real aircraft.  I'm surprised I haven't seen anyone ask for a HUD, lol.  

At the end of the day, the Starship is not hard to preflight or program for a flight.  It is not hard to fly.  It uses GPS to navigate from point to point.  You are not obligated to use VOR, NDB, VLF, or any other method to get around.  You can even create temporary waypoints with the joystick on the panel below the MFD while editing your flight plan.  It is just a unique aircraft that attempted to break many barriers in a time when the aviation community was still stuck between old and newer technologies of navigating.  

I absolutely LOVE this plane! Old school/first gen glass, the need to understand and manage systems, and that sexy design make this flight sim bliss. I don't know how he does it, but Black Square is an artist.

17 hours ago, Orlaam said:

They want flight plan importing, which is not realistic in a GA plane.  They want GPS units that were never installed in the real aircraft.

While I get where you're coming from with most of your post, I have to quibble a bit on these comments.

Addressing the GPS issue first, it's pretty doggone common these days to have fully modern GPS units in some pretty old and humble GA aircraft as well as many warbirds, older jets etc. - many much older and lesser than Starship.  And, in fact, a GPS unit is modeled and available as a nav source in Black Square's implementation, so... 

And second, relative to flight plan imports - it is completely realistic in GA aircraft of all sorts and all ages.  See above re: modern GPS units in older GA plans.  And anything newer and/or higher end these days is most likely sold with fully glass cockpits with all the modern amenities including flightplan importing.  There's nothing about "GA" that makes flight plan imports unrealistic.  It just wouldn't be realistic for THIS GA plane.

That said, I agree what I believe you're generally trying to say.  If you're buying Starship, you need to understand and accept that its soul is deeply rooted in its time and technology.  What you get is a state-of-the art, for its day, glass cockpit implementation that is beautifully and faithfully modeled with all its wonders and warts.  If you wish it to be something it isn't and never was, you're probably missing the point of this implementation.

 

Scott

Edited July 12, 2025Jul 12 by tttocs

I have a question about the Roll Trim (which I'm guessing is another name for Aileron Trim).  Outside of it being listed in the checklist as having a takeoff setting, I can find no other info on it.  There is a recommended Takeoff setting (see below) but nothing more is mentioned in the POH:

Note that I have set the Roll Trim to the TO mark.  Now what?  In other words,  should I reset to the neutral position after takeoff?  After reaching Cruise?  Don't change at all?

1 hour ago, RandallR said:

Note that I have set the Roll Trim to the TO mark.  Now what?  In other words,  should I reset to the neutral position after takeoff?  After reaching Cruise?  Don't change at all?

I expect it's not in the manual because it is used like any other trim control after takeoff.  You adjust to trim the plane as needed/desired once in flight.  Is the plane wanting to roll left?  Right?  Trim it out as appropriate.

 

Scott

2 hours ago, RandallR said:

 should I reset to the neutral position after takeoff?  After reaching Cruise?  Don't change at all?

Assuming you would use the autopilot: if you prepared the plane for the AP (set desired speed or vertical speed), it wouldn't really matter to change trim after Ap is engaged.

Assuming you don't use AP and fly manually: change the trim gently to achieve the desired attitude during initial climb. Then adjust as the flight progresses. The goal would be that you don't have to pull a lot (or at all) on your yoke to get the performance you aim for.

The aircraft has never shown any out-of-normal roll tendencies.  Though some aircraft I've flown (RW) have had aileron trim I've never needed it, though I've certainly spent a lot of time setting elevator trim and some with rudder, especially on initial takeoff and climb situations with a powerful engine.

Since the procedures call for a specific setting at takeoff, I'll use that setting, then change back to center during cruise climb.

11 minutes ago, RandallR said:

The aircraft has never shown any out-of-normal roll tendencies.  Though some aircraft I've flown (RW) have had aileron trim I've never needed it, though I've certainly spent a lot of time setting elevator trim and some with rudder, especially on initial takeoff and climb situations with a powerful engine.

Since the procedures call for a specific setting at takeoff, I'll use that setting, then change back to center during cruise climb.

The Starship has a tendency to roll quite a bit on takeoff.  Nick didn't find that information in his production of the aircraft, so it isn't represented in the flight characteristics.  He was presented this information by another user on the JF forums and if I had to guess, he might include some yaw changes in the an upcoming update.  I'm not sure how that all works from the programming perspective, so I can't speak to whether or not he will include that yaw effect however.  Normally, yes, you would dial that trim in to counter the yaw.

v1.2

New Features:

Flight Plan Importing in MSFS 2020 & 2024 is now supported.  Flight plans can be imported from the MSFS 2020 World Map (manually created or imported from a file), and they can also be injected from the MSFS 2024 EFB at any time during the flight.  Given the uniqueness of Starship’s avionics, these flight plans must be reinterpreted for Starship; therefore, this feature is still considered “experimental”.  For more information see the new “Importing a Flight Plan” section of this manual.  The best way of importing a flight is via the “Send to Avionics” option on the MSFS 2024 EFB.

NEW Magnetic Compass Effects including physics filtering and erratic behavior from onboard magnetic fields.  See the “Magnetic Compass Effects” section of this manual for more information.

Implemented ground comm functionality to power the left RTU, COM1 transceiver, and the pilot’s audio circuitry when the battery master switch is in the off position by pressing the “GND COM” push button on the electrical panel.

Several push buttons and switches, such as the Battery Amps, Aft Fuel Quantity push buttons, and ground ice detector switch will now animate with their respective L:Vars.  Also added “L:var_PropGovTestSwitch_Override” to animate the propeller governor test switch with external hardware.

Added persistence to tablet payload unit switch between sessions.

Added electrical circuit needed for some hardware to recognize the avionics state.

Added persistent tablet option to disable auto-filling of payload data on CDU.

The MFD cursor can now be used to select user-created waypoints from the map, and the MFD map will only display genuine user-created waypoints, as opposed to temporary ones created by importing flight plans.

Only user-created waypoints will persist between sessions and be displayed on the inspect user waypoints screen, as opposed to temporary ones created by importing flight plans.  This should eliminate the “INVALID USER WPT” message on CDU startup.

The heading bug leading line (dashed magenta) will now appear whenever the selected heading is adjusted for a few seconds, the currently correct behavior in the real aircraft.

Improved avionics fault detection update speed for MFD Avionics Status Screen display, and added “AVIONICS FAULT” message to CDU.

Added headphone jack highlight to better alert users to the headphone isolation feature.

Added L & R LIP HEAT LOW EICAS messages, for when the inertial separators are deployed, but bleed air temperatures are insufficient to heat the induction inlets.

Windshield wipers now flutter when deployed at high indicated airspeeds, and also become jammed when airframe icing is moderate.

When the wipers are deployed at high airspeed, the apparent wind will affect the resistance on the motor, slowing down the downward sweep.  At high enough airspeeds, the wipers will not return to their parked position until airspeed is lowered.

Workaround to fix MSFS 2024 light flare bleed-through.

Added tablet option to enable exterior registration meshes in MSFS 2024.  There is a hard-coded bug in MSFS 2024 that interferes with the ultra-custom dynamic registration system in Black Square aircraft.  Sim Update 3 failed to resolve this issue, but a potential fix may be in the works for Sim Update 4.  Currently, the dynamic registration may work depending on how the aircraft was loaded..

Bug Fixes:

Payload state saving now appears to work in MSFS 2024 after removing a section of the new “navigation_graph.cfg”.  It was previously being overwritten every time you entered/exited the aircraft.

Changed CDU ADF frequency entry interpretation to allow for setting of frequencies with decimal components below 1,000 kHz.

CDU messages that were previously acknowledged (white) would remain acknowledged, even when they were triggered subsequently again.

Circuits on the hot battery bus would not respect battery discharge and failures under some circumstances.

User waypoint delete function would not update the user waypoint CDU screen.

Left and right radar tilt did not synchronize when in radar SYNC mode.

In some circumstances, the localizer and glideslope would not capture when transitioning from autopilot modes other than NAV.  This appears to be due to the native sense of localizer-based approach arming.  A workaround has been implemented for a seamless experience when using the proper HTML events to control the autopilot.

Under some circumstances, a runway waypoint could be replaced with the waypoint representing the opposite end of the runway during software back-end flight plan checks.

Created a more robust check for duplicate waypoints to avoid erroneous WPT IS DUP IN FPLN CDU messages.

PASS OXYGEN ON EICAS message would not trigger when the passenger oxygen system was deployed.

LOC DISAGREE EICAS message now requires a localizer frequency to be tuned, as opposed to just a VOR frequency.

MAIN & STABY DEICE FAIL messages will now extinguish during deicing tests, even if the test button is being held down, as per the procedures handbook.

Windshield and cabin window icing effect restored on interior model.

Restored windshield wiper effects in MSFS 2024.  Caused by 2024’s different interpretation of the specified RPN update frequency.

Fixed tiny hole in condition lever dust cover geometry.

Fixed typo on toilet occupancy placard in aft of cabin.

Restored airspeed indicator trend arc.

Restored airspeed indicator blue rectangle (best single engine climb speed) adjustment with pressure altitude.

Workaround for batteries that disconnect when recharged to exactly their full capacity due to a bug in the simulator.

 

I have performance degradation over time flying Starship in SU2. The issues seems was acknowledged by developer as well and has to do with avionics. However, I don't see anything in description of this patch that related to this issue:(  

This issue was mentioned in  the patch.

19 minutes ago, RandallR said:

This issue was mentioned in  the patch.

OK - maybe a work in progress?

Bug Fixes v1.1 (0.1.1):

Removed waypoint symbol text label hiding from MFD map screens.  This was a potential cause of performance degradation on long flights.