PA-28 Warrior II

Oh wow - I totally missed the fuel auto-switch option in the EFB Thanks for following up - will wait an see if the lights come good with the next few MSFS updates.

The missing copilot model is a known issue in the Warrrior II in MSFS 2024. We have developed a workaround for some of our other aircraft that will be implemented in the PA28s in the next update(s). The main instrument panel lighting can be increased using the two rehostat switches on the main switch panel. All aircraft lighting may not be visible during to day due to a limitation of how MSFS 2024 handles aircraft lighting. The lighting in all of our MSFS 2024 aircraft has been fine-tuned to have a realistic brightness level at night, which does mean that certain lights can look dim or not lit during the day. If we were to increase the brightness of the lights to make them visible during the day, then that would have the side effect of making the lights extremely bright at night. We remain hopeful that this may be something that will be improved in future MSFS Sim Updates. The EFB map flickering in MSFS 2024 was fixed in the v0.4.3 update to the Warrior II. Please ensure you have v0.4.3 of the Warrior II installed (version number can be seen at the top left corner of the EFB Aircraft page). If you are still experiencing this behaviour with v0.4.3, we kindly ask you to create a ticket with Just Flight Support via the following link, and one of our support team will be able to assist with further troubleshooting: https://www.justflight.com/support Mark - Just Flight

The Warrior II has an Avionics Power switch on the right side of the main instrument panel that must be switched on in order for the GPSs to receive electrical power. I've attached a screenshot below showing the switch, as it is an easy one to miss. [image: 883f49fd-ce23-405d-920c-e4fe4749d562.png] Hope that helps. Mark - Just Flight

I can confirm that forward pressure is required with additional nose down trim on approach. I flew a Warrior for the first time last week and noticed this was quite the opposite of what the JF warrior is doing in the sim. Previously I flew the Archer II quite a bit.

Hi! I bought this plane a few days ago and I must say that the internal and external quality of the textures is surprisingly low. This is very apparent in the cockpit when you just zoom in a little bit. Can we expect a resolution update to the 8K standards? P.S.: Otherwise the product is great, keep up the good work!

Thanks Mark, I can use the joystick on the index controllers so I've got a work around in the mean time. Appreciate the response!

I don't have 2024 but have a look at your weight and balance. Do you have 2 pilots or 1? If 1, could just be the offset weight of a single pilot.

Good news! Everything I've been experiencing has been resolved with this latest update, not sure what was causing it but we are all good now! You may close this thread!

There was an old bug, opinions differed on whether or not it was in the WT GNS unit or the JustFlight planes, where engaging the AP seemed to turn on some sort of alt or pitch hold mode by default. The solution was to toggle the Alt Hold clickspot twice, which then released vertical control of the aircraft. I've not extensively tried the plane since it was recently updated; could that be what you're experiencing?

Thank you for your answer. Nevertheless, I made a flight today and the display was normal. Strange isnt'it ?! Edit : my mistake, it was in MSFS 2020. In MSFS 2024, the Navigraph En Route charts are still flickering...

There is a useful tool that can help you creating ktx2 files for MSFS 2024. You also have to create new js files for each texture. If you are working with dds texture format, you have to convert them to png before starting the prosess. The tool is a script that work with the MSFS 2024 SDK (you will have to have the latest SDK installed) The tool is available here (follow the instructions from the author):image-to-ktx2

Thank you. I did some digging and found my issue was double key bindings that were not present in SU2 that are present in SU3 Beta with the Honeycomb Bravo. Once I deleted the keybinding, the issue resolved and I am able to use the physical handle in the sim. Thank you!

Oops... thanks @Derek. Somehow I missed that on the Support page!

Got it, thank you.