@django1489 Everything is all ready to go, I just don't like to rush things. I'm sure this goes without saying, but when I'm planning on releasing a news update with screenshots, the complete store pages, and the manual all at once, there is a lot that needs to be checked over. Much like releasing anything to the public, that last 5% of work at the end is often more like 30-40% of the drudgery. Thanks for your continued excitement. It always makes the slow part at the end a little more enjoyable.

@django1489 I'll reiterate: we could really use a good one in the sim.

@Black-Square said in Century IV autopilot, altitude capture questions: AP_PITCH_REF_INC_UP Aha, I misssed it, thanks. That text is in the Change Log, which I did not assume was something I needed to read. The behaviour which I found non-intuitive regarding the tablet's "Control AP Pitch with Hardware events" setting, is as follows: With this option enabled, I am unable to make changes to L:var_AP_PitchKnob (page 143 of the Duke Turbine manual) With this option disabled, I am able to make changes to the this variable and see it change in the cockpit Well, at least after a few hours of trying stuff, this seemed to be the fix to make my spad.next configuration able to set the desired pitch for ATT mode. Should I instead use these: AP_PITCH_REF_INC_DN”, “AP_PITCH_REF_INC_UP”, and “AP_PITCH_REF_SET”? Thanks and have a great weekend.

@Voice-of-Reason Thank you for the reply Looking forward to it

Unfortunately, it is not possible to jettison payloads on the PC or Xbox Marketplace versions of the Vulcan. This is due to a marketplace policy that prohibits animated weapons from being included in products sold on the marketplace. The visibility of the weapons can be toggled via the Aircraft page on the EFB/Tablet. Mark - Just Flight

License Failure errors on the EFB/tablet are typically activation/installation related. We would recommend contacting Just Flight Support for further assistance with this: https://www.justflight.com/support Mark - Just Flight

@jasmits almost done from what it seems. I hope beta testers dont take forever

@Rich thank you so much for following up with MP team. I am also eagerly looking forward to flying the Duke in MSFS 2024 but it is really frustrating the issue is still not yet resolved by MP team after such a long time... I know this is a common question that comes up from time to time and Just Flight does not normally consider this - but is there any chance Just Flight would exceptionally allow purchase transfer for Duke if the MP issue still persists for a prolonged time? This should at least mitigates the inconvenience to PC customers. No pressure if there are other barring considerations

Thank you so much

Normally, I would offer you a custom code solution to extract that state from my software as an L:Var, but the GTX 327 is the only piece of default avionics still in use in my aircraft. I've been meaning to create my own version for ages now, but I know it's also low on the priority list for most of my users. You can still make an edit to the default simulator's files to get what you want, but be prepared for it to reset every time the simulator updates. You can also make a package with an improved GTX 327 to keep in your community folder. I would be happy to give you some pointers on that, if you need any.

OK Mark, I will post a ticket. Further examination shows that the only weights that are now correct in the aircraft tablet AIRCRAFT page are the empty weight and the fuel weight. Unfortunately the flipchart which provides the V speeds also shows the incorrect weights and therefore V speed. Even putting the correct weights into the MCDU PERF INIT page does not change the flipchart weight. As a further example with the RJ100 with 100 pax the Simbrief TOW is 43803 KG yet the aircraft flipchart and tablet are showing the TOW as 35568 / 36000 in the flipchart, so the Vspeeds are all wrong. Sadly the MS system for aircraft weight and balance is complete garbage and only showing 2 passengers with no way of changing the weights to the correct figures. So the aircraft is not really fit for purpose.

Just checked on both the Turbine Duke and the Grand Duke - in both aircraft if you pull either the Cabin Temp breaker or the Vent Blwr Breaker the blower fan shuts off regardless of what Cabin Temp Mode you are in.

Any possible update on this? Am I wrong for having my hopes up that we will have G3X in the Bonanza and Baron at some point?

The v4.4 update for our PA-28-161 Warrior II is already available on the MSFS 2024 marketplace on all platforms. Note, the v4.4 update was an MSFS 2024-only update and the latest version of the product on the MSFS 2020 marketplace is v4.3. The changelogs for these updates can be found here: https://support.justflight.com/en/support/solutions/articles/17000118189-pa-28-161-warrior-ii-msfs-changelog Mark - Just Flight

This isn't something I recall seeing reported before; however, if it is hydraulic-related, the HYD.1 or HYD.2 caption would be illuminated on the CWP. HYD.1 system pressure will vary depending on usage, but should automatically increase pressure once the load on the system is reduced. HYD.2 system requires resetting after engine start via the "HYD 2 RESET" button on the left console. In any case, could I kindly ask you to raise a ticket with Just Flight support at the following link: https://www.justflight.com/support In the ticket, if you would be able to provide any screenshots/videos of the behaviour, as well as steps on how we can replicate the behaviour, then that will put our support team in the best position to offer assistance. Mark - Just Flight

The front and rear countermeasure equipment for the 146 RAF variants is located on the EXT_01 texture sheet. For the equipment to appear on a livery, the word "RAF" needs to be included in the Title= entry of the livery's aircraft.cfg. Hope that helps. Mark - Just Flight

@jmarkows said in Repeated NAV mode disconnects while VFR hopping: are you reverting to roll mode when you're still receiving the tuned VOR? Yes. In the most recent case, the FMS / VOR Status page showed the VOR in all three slots plus the DME. It was listed with a 130 nm range, the dropouts occurred on inbound and outbound legs beyond 50 nm. Inside 50 nm it's generally been fine. @DrZGard said in Repeated NAV mode disconnects while VFR hopping: we would much more often utilize the OMNI needle for verification of being on course and heading mode Thanks for the tip, I will give that a shot.

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.