@Barabba Same here, I have the Warrior II since 2021 and textures looked way crispier in FS20. On the other hand, it hand flies really well, like it.

I can confirm that the hot-fix works for me, and yes, I have the bundle. Thanks for resolving this quickly over the weekend!

Unfortunately maps not working in the newly updated Warrior and Turbo Arrows either... at least for me...

Screenshot 2025-05-10 013500.jpg

@aceridgey for the GNS - AUX - SETUP 2 - COM Configuration.

Assuming you're on MSFS 2020, and everything is installed correctly, I think all of your remarks can be attributed to the complexity of the aircraft. Are you familiar with the triple-fed bus system, and turboprop engine limitations?

There are many configuration issues that could cause what you're seeing. For instance, many of the aircraft lights will not work unless the left and right generator buses are online. You will also have to disengage the starters manually for the starter-generators to produce power (usually what closes those bus ties). If it's just the electronics that shut down after several minutes, that comports with the generators not being online too, since the battery will eventually give out, or overheat. If it's the engines that shut down after a few minutes, you are probably exceeding the engine's torque or ITT limits.

Long story short: The current version of the Analog King Air has been in the hands of thousands of happy users for a couple years now, so these are almost certainly not bugs. There could be an installation issue, or an incompatible freeware addon, but most likely it's just the learning curve required for one of the most complex general aviation aircraft in service.

If you continue to have questions, I am always here to help! Feel free to share any videos or screenshots of your situation too. Helping people learn complex systems is my favorite part of creating these aircraft, so I'm always to take a look.

It doesn’t work when started on the runway with engines running either. Also, the autopilot on my RJ doesn’t work either now. I’ll check my F28 and 146 also, but I am seeing a pattern here. the autopilot and 530 do work in non-JF planes. This is happening in both 2020 and 2024

I like Elizabethton and Roanoak, cheers

Then why was F28 V1 coded to level off at the selected altitude if it is just an alert system...

ok work, thx :)

Yes, but I think I found the problem, thanks to Axis and Ohs.

When I spawn into a flight at a parking spot, as I am for this one, Axis and Ohs doesn't load the aircraft profile, it loads a profile for "Avatar" -- and as indicated by someone on the MSFS forum, as soon as I enter the plane using shift-C, it stops rolling - presumably because at this point it loads the aircraft profile with the parking brake set.

I did set a binding in the MSFS control settings as well and made sure the brake was set, but I suspect MSFS doesn't load the native profile until you enter the plane either, because it didn't help. So it looks like it's an issue particular to walk-around mode.

Shortly after the release of the recent PA28 updates, we were made aware of a WASM conflict with the Interactive Paper Charts that was affecting users that had a custom tail number set in the aircraft menu (identification tab). This would cause symptoms in the aircraft similar to what is described above.

We have since released updated installers, which can be downloaded via your account (the updated installer filenames end in 'a').

For the time being, we have disabled Interactive Paper Charts until we've implemented a permanent fix. That should happen on Monday.

Apologies for the inconvenience.

Mark - Just Flight

@Black-Square Thank you!

Sorry that's happening to you. Nothing is more infuriating than a CTD at the end of a flight. Luckily, I can't recall a single reported case of CTD's with the Dukes that wasn't a one-time thing, or wasn't eventually attributed to something else. The method that I have chosen for programming my aircraft makes them delightfully resistant to CTD's, unlike aircraft that use a lot of WASM instruments.

From what I've seen in my own coding, I always suspect the GPS unit in the case of CTD's, because the simulator's native flight planning system seems to be one of its least stable aspects. For the sake of testing, I would recommend using another GPS unit on a couple flights to see if the CTD can be attributed to the GTN 750/650.

Feel free to report back here, but I might also recommend contacting Just Flight support. They have a knowledgebase for general simulator issues, while I specialize in the aircraft specific knowledge. They will also have access to an XBOX for testing, if that's needed. Please let me know what you discover!

Please see: https://community.justflight.com/post/36185

In v0.1.3 of the Vulcan, we upgraded the GPS from the Aera GPS to the G3X Touch for better MSFS 2024 compatibility. Therefore, the functionality of the GPS has changed slightly as the G3X Touch is a more advanced GPS. To cover each of your points:

If a flight plan is created in the MSFS 2024 EFB, the "Send Route To Avionics" button must be pressed in order to import the route into the GPS. If a flight plan is created manually within the GPS, the flight plan must have a departure airport and a destination airport set in order for the autopilot to couple with the GPS (if a flight plan is created in the GPS with only a departure airport and waypoints, the route will be displayed, but the autopilot coupling will not function with an incomplete flight plan). In order for the autopilot to track the GPS flight plan, the ENGAGE knob must be pulled (with IN indicator showing white), the TRACK knob must be pulled, and REMOTE must be selected on the navigational selector.

This is a known side effect of a workaround we have put in place to improve touchscreen display interactions in our aircraft in MSFS 2024. If the workaround is no longer required after future MSFS 2024 Sim Updates, we will update the logic so that control cannot be clicked through touchscreen displays. The GPS can also be moved on top of the glareshield by clicking the upper bezel.

As the G3X Touch is a default GPS unit in MSFS 2024 (developed by Working Title), we sadly don't have any control over the scaling of the GPS. To circumvent this, we have added custom cameras for each GPS position which moves the camera closer to the GPS display. These cameras can be toggled either via the MSFS Camera menu, or via a clickspot on the right bezel of the GPS.

Mark - Just Flight

Your best bet when trying to resolve any issues or ask specific questions is always to contact Just Flight support directly:

https://community.justflight.com/topic/2/product-support