Have you found out something about the issue?

Digging up an old thread because I got back into the Starship after a few months. I was busy going over the equipment requirements again, to update my SimBrief profile. In short, if you're not using the GNS 430, but you accept the fact that your Starship has ONE GPS receiver: You are not capable of RNAV10 or RNP4 remote or oceanic as this requires two independent Long Range Navigation Systems. The Starship has 2 FMC's, but they are linked to only ONE receiver. Hence, they are not independent. (There is a designated area where only one LRNS is sufficient) Even though you meet all requirements for Terminal RNAV 1 SID's and STAR's, you can't accept one because it is not line-selectable from your FMS (FAA AC 90-100A 10. b. (3) "General Operating Procedures" pg. 13 You can fly an RNAV GPS approach down to LNAV minima, because you have a GPS receiver and the approach IS line-selectable from the database. Due to having only one GPS receiver, NAT HLA is also not approved. (Except for the fact that you're not RNP4/RNAV10 qualified anyways). Cheers,

@Black-Square did you ever have any luck with this? I dusted off Starship tonight to help someone learn how to program the FMS and very quickly rediscovered the joy. I had the same issue reported above though. I tried dialing in a speed on the ASI and then activating IAS PROF, and it didn't do anything. I cleared the setting on the ASI and tried IAS PROF again and it immediately picked up my current airspeed and started climbing.

I love this attention to detail! I just started flying the B36T after spending a lot of time in the Baron and noticed the fuel discrepancy and thought it was a bug too LOL.

SimBrief has performance built-in. Even takeoff performance. Which I have checked is spot on!

@Black-Square When do you expect to implement these changes in your Add-On? I love both Bonanza and Baron and would like the small objects culling problem to be sorted out.

This would be an awesome feature, I would definitely use it on the whole range of JF aircraft, I assume the a300 will have the UNS1 as well so that would be perfect. I think the code would carry over to the Boeing FMC as well, as far as the Pyhton script goes.

This bug is confirmed. Sometime after engine start, anti skid becomes INOP and nothing can fix it. Hydraulic pressure is adequate. All systems are in normal position.