@rortaus The post you're replying to is from August 2024, so I'd recommend contacting Just Flight Support: https://community.justflight.com/topic/2/product-support

@Andydigital Yay! Glad I thought of something else for you to try.

Thank you for the advice. I guess I read right past that part in the instruction manual... right after the wingspan options instructions. I see it now and I'm going to set it to 1 minute. Be interesting to see if I notice a real difference.

I haven't tried that yet. I did a flight today that worked OK so I'm going to cross my fingers and hope it was a one-time glitch! Thanks for the reply, you make great aircraft

Thanks, Mark. I was able to find the ini file but no luck there. However, I found the issue was with a binding on my throttle for the autothrottle - a go around mode. Deleted that and the problem is solved. Thanks again.

Bought the Baron last night. After flying from LHBP to LRHR for the inaugural trip, this screenshot is from the return leg, while being vectored for the ILS RWY 13R approach into Budapest by ATC, with the stunning Danube Bend ahead of us. [image: a4596b42-10ba-4e7e-afdb-8e8818d4e1d6.jpg]

JustFlight updated the scenery on their end, and it's now compatible with MSFS 2024.

The Baron is just wow! I own the MSFS 2020 version too, which was my favorite along with the King Air, but this new version is in a league of its own!

We don't have any further estimate to share at the moment, but work is continuing on the update behind the scenes, and we'll share more information once the update is closer to release. Mark - Just Flight

Got it ! This is a never ending treasure hunt

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

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.

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

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