Starship

Well, I was able to complete a 2024 flight where I started cold and dark, loaded a SimBrief flight, tweaked the flight plan in the EFB, and loaded to avionics. I was able to do an RNAV approach with vertical guidance in bad weather. Although full disclosure, the first time I tried this flight, somewhere around the time the aircraft was due to catch the GS, the autopilot went crazy and crashed the plane by pointing at the sky all of a sudden. Not sure if I can reproduce that, needs more testing. Really appreciate this update, being able to follow full flight plans is a game-changer.

Thanks, I'll pass this along. I think it's mainly the AP he's interested in.

What part of setting it up are you having trouble with? Do you understand how to use profiles, and how to assign events to buttons? Everything SPAD is mostly documented with Youtube videos. Which is nice if you can find a video that matches what you are trying to do, but it can also mean spending hours wading through content on topics that is not exactly what you are looking for, and wasting time on videos that are no longer relevant because of later changes to SPAD.

I find my pop culture knowledge rather good for a 53 year old US citizen, but Laugh-In was before my time. Anyhow, to aid a little better, a certain password in the Starship is "BurtRutan"

I think I had this once when I was running up with an ambient temperature above 40ºC (104ºF). After the avionics bay overheated, the message was shown. After shutting the avionics down for some minutes, it cooled enough to resume operations and get airborne.

@HansRoaming said in checklist item: pitch/roll/rudder trim set to 0 (neutral): I thought it meant numeric 0. Maybe putting pitch trim all the way down to 0 helps with taxiing in some fashion? Part of my confusion stems from this video: https://youtu.be/lGYOBP8VFVA?si=rry5RAripGu-FQrs&t=192 At 3:12, Nick calls for checking the trims, and Emanuel looks at them and responds "trims are neutral" with pitch trim in the default middle position, and Nick continues the checklist without commenting on that. But I'm not sure how much this means, because even if it's really supposed to be moved down to 0, Nick might've just decided to avoid slowing down the pace of the video for something that was unlikely to matter.

Awesome, made the change, hopefully now the MSFS updates have come out then 1.12 will be released soon.

This was helpful! Thank you!

fixed in SU3

I primarily tune in frequencies through the CDU. I notice that it is impossible to input a comms frequency in the recall field. Not sure if there is perhaps a logic in that, so the RTU and CDU don't "fight" over that field, but if that is the case, I wonder why the yellow arrow still appears - seemingly indicating that the LSK can be used to input the frequency in that field.

@MarkS said in If you're doing a world tour.....: I'm on leg 25 of this massive world tour, available on flightsim.to. It did not include a stop on Reunion, but flew right past it so I added it, as well as a stop in Antarctica. [image: fa09f856-73ae-43a3-bdac-9d3c37af2e14.png] https://flightsim.to/file/93601/around-the-world-flight-plan All these places and still skipped Hawaii...

Oohh...system.cfg... voltage curves... so that's how that works. I was looking all over .xml files trying to find some reference to 26 So maybe when the simvar gets the voltage number, it's starting from the left of the curve and finding the 0:26 entry first and setting capacity to 0? And there's some (undocumented?) behavior in MSFS that says "0 remaining capacity is automatically 0 volts," even if the voltage curve says 0 should be 26? But if that's the case... Yep, tested it and Recharge Batteries disables external power too! (I should note I've only been trying it in FS2024)

I checked again and ran the trig for different altitudes and was completely unable to paint the ground in MAP or WX mode regardless of the tilt. This seems like a shortcoming, I have on occasion at night with heavy rain tilted the radar down so the bottom of the beam catches ground at the edge of the display range. This helps identify a lower detection plane for the radar. For instance is I set the radar to paint the ground at 100 nm and the aircraft is ~30000ft AGL then at 50nm the bottom of the beam is 15000ft etc. Every tilt from -1 to -12 resulted in a dark screen for trying to get any sort of ground return

Grinning and rubbing hands together in the corner

Although you can't do this in real life, I find that creating a flight plan with Simbrief will import the SID into the FMS as a series of waypoints, Vnav can then be used to put in the altitudes so you can see what they are meant to be at. With STARs you have to put them in as waypoints in the FMS one by one and again can use VNav to put in the altitudes. The AP won't automatically fly VNav but you can use them as guides to control your vertical profile. What this means is I don't have to use the 430 and have disabled it, yet can still easily use the AP to fly SIDs and STARs.

I don't think so.

Did this happen?

@DrZGard I thought you were joking but it really stands for North America Not as per the manual.