Ok have raised on ms bug section too. Feel free to vote affected. JF/BS mods apology if link not allowed just makes sense t get moving if issue there end https://forums.flightsimulator.com/t/marketplace-library-aircraft-not-staying-enabled/754442/2

@Black-Square Apologies for hijacking the thread, but I have a question: If I have the GNS430 enabled in the Starship, is it possible to have the Flight Plan showing on the main FMS? I know I can have the built in the 430 and acting as the main navigation system, but I'd like to know if it's possible to "follow along" without having to break my neck.

Does the above code also work for the Dukes and/or the new Baron Professional, please? I am considering buying one of the two, provided the copilot can be squeezed in to them using the code. It worked fine for the TBM, but I am unsure if it works for the Dukes/Baron Professiona, so I ask before purchase.

Thank you. I’ll be looking out for it. The RJ cockpit doesn’t do anything. No lights, no gauges etc. No EFB. It starts when I quick start it but nothing works in the inside and ohhhh, the graphics. Can’t wait for the update. Hope all is well. ️

Thanks

@Mark Thank you! These conditions, plus the conditions for boarding logic, would be awesome to add to the manual in a future update! (I just realized I probably haven't combed the EFB manual exhaustively, so please excuse me if they're already in there)

@Mark Thank you! I'm going to try and map them to raw buttons first, then I'll see if I can go through FSUIPC or something to get them onto my axis. If I get this working well, I will see if I can make a blog post or video for other users

In addition to the @GroverJ41's fantasitc reply above, we also have a tutorial flight from Page 153 of the F28 Professional Operations Manual that will walk you through an entire flight in the aircraft: https://downloads.justflight.com/products/JFF003039/F28_Professional_MSFS_Manual_v2.2.pdf We also have a 4-part video series on our YouTube channel that covers that tutorial flight: https://youtu.be/zZQf0yjYHtw Mark - Just Flight

The weight changes are a known limitation of how the MSFS 2024 walkaround mode interacts with the custom fuel/payload managers in third-party aircraft. However, we do have a workaround currently in testing, and if our testing team approves that workaround, we will include it in the next update to our products. Mark - Just Flight

I would be lying if I said I have ever left the simulator paused for that long! Leaving the simulator paused for many hours is not something we usually test for, so I couldn't say for certain if this is just a one-off, an issue caused by the 146, or an issue caused by the simulator. Could you please let us know if you experienced this with MSFS 2020 and MSFS 2024? Once we know that, we can get this logged on our internal trackers and investigate it further to see if there's anything we can do to improve that on our side. Mark - Just Flight

Thank you for taking the time to provide some detailed feedback. I have logged all of this feedback on our internal trackers for our flight model developer to take a look at ahead of the next flight model update to our PA28s. Mark - Just Flight

That's not a behaviour I recall seeing reported before, and it shouldn't be possible to deploy the lift spoilers in flight, so it sounds like something that could be caused by a controller conflict. The first thing I would recommend checking is if you have any "SPOILERS" control assignments being inadvertently triggered by your external hardware (TOGGLE SPOILERS, SPOILERS AXIS, EXTEND SPOILERS, etc.). For reference, the conditions for automatic lift spoiler deployment are listed on pages 79-80 of the RJ Professional Operations Manual: https://downloads.justflight.com/products/JFF003765/RJ_Professional_MSFS_Operations_Manual_MSFS2024.pdf Mark - Just Flight

Unfortunately, as you say, I believe this will be a limitation of using Chaseplane with some of our products. The Vulcan, and a few of our other products, rely on the core MSFS camera system to move the user to certain locations in and around the aircraft. As Chaseplane overrides the default camera system, the cameras that we trigger in the code no longer exist, so the camera will not change. It's something we have logged on our internal trackers for further investigation, and to see if there is any form of a workaround we can find for Chaseplane users. In the meantime with the Vulcan, it should be possible to create custom Chaseplane cameras inside the AEO/Navigrator compartment and then trigger those via the Chaseplane interface. Mark - Just Flight

This isn't something I recall seeing reported previously, but if this happens again, could I kindly ask you to raise a ticket with Just Flight Support via the following link: https://www.justflight.com/support In the ticket, if you could provide further details on when this behaviour is observed, then we can begin to log any further instances of this to see if a trend starts to emerge. Mark - Just Flight

@greene19xx Nope not heard anything back, I thought it might be the fact I was using msfs addon manager, so I uninstalled it, then installed it straight in the community folder but still getting the same thing.

I will do. Thank you, Derek.

For a 1985 p baron?

@Voice-of-Reason i contacted Microsoft and i have the 2020 version now.

I tried that via the system.cfg but there's absolutely no effect in the sim. Testwise I set hideGPS and forceRegistration to 1 and entered 75% fuel to right aux tank but starting up the sim everything is with the original settings and values.

OK solved it.