PA-28R Turbo Arrow III/IV

Thanks @Mark for clarifying this.
Hopefully someday you will find the solution. Make a typealias so the WT GNS430 things you have initialised the GPS100 LOL. just kidding.
As as side note, Im really enjoying this plane, and im doing VOR navigation and VOR approaches.. is great plane.. I have to be focus on the flight since there is little AP involved, specially since Im not using the ALT hold virtual feature.

Feel proud.
IMG_E9845.JPG

Yes, it's a tricky balancing act between how much we "chase" workarounds for behaviours such as this when there are likely going to be changes in future MSFS Sim Updates that natively affect this behaviour. We could spend time trying to find a workaround for it, only for an MSFS Sim Update to release, rendering the workaround absolute, and then requiring even more time for us to go back and "undo" that workaround.

I believe there are improvements to lighting/emissive textures listed in the Sim Update 3 Beta changelogs, so at the moment, we are not planning on making any further changes to the night lighting until we see the results of these changes in the full Sim Update 3 release.

Mark - Just Flight

We are currently focused on converting all of MSFS 2020 products into MSFS 2024 native packages and predominantly bringing them across in an "as is" state. Therefore, MSFS 2024 specific features, such as career mode, aren't supported with our product's initial MSFS 2024 updates.

The status of our MSFS 2024 product updates can be found at the following link: https://www.justflight.com/articles/just-flight-addons-msfs-2024-compatibility-status

We haven't yet investigated career mode compatibility in any of our products, so we wouldn't be able to confidently answer if/when a certain product will receive that compatibility, or what that update/upgrade would look like. However, there is no facility that allows us to transfer products between different stores.

Mark - Just Flight

Thanks for the explanation Mark. Please don't update the F28 too soon then lol ;)

@davenicoll I would recommend following the steps outlined in my reply here to see if that gets you up and running: https://community.justflight.com/post/36544

If the issue persists, could I kindly ask you to contact Just Flight Support via the following link, and our support team will be able to assist with further troubleshooting: https://www.justflight.com/support

Mark - Just Flight

Thanks for the feedback. We have logged the flaps indication on the HUD on our internal bugs tracker to investigate further ahead of a future update to our PA28s.

With regards to aircraft lights not being visible during the day, this is sadly 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.

Mark - Just Flight

Thanks for confirming. We had another user reporting similar behaviour with the Warrior in SU3 Beta so we'll pass on the info.

Hopefully, this is just part of the standard Beta process and will be fixed ahead of the full public release.

Mark - Just Flight

This is not behaviour we are able to replicate on our side, so we would recommend double-checking that the controller sensitivities are set as per our recommended settings here: https://support.justflight.com/en/support/solutions/articles/17000116865-optimal-controller-sensitivity-settings

We would also recommend that the MSFS flight model option is set to 'Modern'.

If the behaviour persists with the above settings, we kindly ask you to raise a ticket with Just Flight support, and one of our support team will be able to assist with troubleshooting: https://www.justflight.com/support

Mark - Just Flight

Thanks for reporting this, and apologies for the delay in getting back to you. I've been in touch with our flight model developer, and it appears that the core behaviour here is a long-standing bug in the simulator's flight model dating back to pre-MSFS days. It's as if the sim links the bubble in the gauge to bank rather than yaw. If you were to look outside of the aircraft at the time of this behaviour occurring, then the aircraft would likely not be slipping, and no rudder input would be required. It's just the indication that would be incorrect.

There are methods in the flight model that can "fix" this, but it is possible that some of the recent improvements to other areas of the flight model have reintroduced this behaviour a little bit.

The flight model is all a bit of a balancing act, making sure one improvement doesn't negatively impact something else, but we have logged this on our internal trackers as something to investigate again in a future update.

Mark - Just Flight

Aaaah - wonderfull news. This make life much more easier.
Thank You!

Ticket submitted !

@flyingpaul1980 The flickering map is a known issue with MSFS 2024, and we are actively investigating a workaround. Based on our recent findings, we are hopeful that we will be able to provide a fix for that in a future update to our PA-28s.

To fix blurry cockpit textures would recommend going to MSFS > Settings > General > Graphics and setting "Texture Resolution" as high as your PC will allow.

The screenshots taken on the product page show the intended quality of the textures in MSFS 2024: https://www.justflight.com/product/pa-28r-turbo-arrow-iii-iv-microsoft-flight-simulator

Mark - Just Flight

Thanks for the feedback. We'll post a reply to each of your points below:

The flaps in the PA28s are purely mechanical, so there is nothing to prevent them from moving in a cold and dark state.

The autopilot behaviour is largely dictated by the GPS unit fitted. With the "GPS 100" fitted, there are no external GPS units fitted, and the autopilot behaves as per our code. With an external GPS unit fitted (WT GNS 430/530, PMS50 GTN750, TDS GTNXi), these GPSs feature their own custom autopilot code, so slightly different autopilot behaviour is expected.

Thanks for the feedback. We'll log this on our internal feature request tracker as something to consider for a future update.

Yes, the KX170B is set up to reflect the real-world configuration where it doesn't support 8.33 kHz spacing. We do have a feature request logged for this to see if we can add support for it within the current model, but we aren't able to guarantee if anything will be possible with that. In the meantime, 8.33 kHz spacing is supported on the other GPS units.

Mark - Just Flight

Looking through the code, the way the HSI has been set up in a way that it shouldn't exhibit any drift, but that's not to say there hasn't been something changed in a recent sim update, or perhaps a GPS may be interfering with the code.

Could you please let us know which simulator you were using when you observed this behaviour, and what (if any) GPS was selected?

Mark - Just Flight