146 Professional

after nearly 2 years: the problem is still not fixed (UNS-1)...

Thanks! I'd no idea it was that easy to get rid of him. I'd never noticed the option before

Thanks for reporting this. The UNS-1 should definitely have button sounds, but it looks like something has happened to prevent them from playing. We've logged that, and it'll be investigated ahead of the next update. The forward galley lights are intentionally linked to the cockpit door position, so if the cockpit door is closed, the galley light will be off to prevent light bleeding into the cockpit when the door is closed. If the cockpit door is open, the forward galley lights can be controlled via the switches above the FWD SERV door. Mark - Just Flight

This is a known issue with our aircraft post-SU4 due to changes in the SimConnect logic in MSFS 2024. At the time of writing, updates for all of our MSFS 2024 products are either in testing, or released. Please see: https://community.justflight.com/post/45963 Mark - Just Flight

@Mark Thanks! Wish for the best.

Thanks a lot for the further elaboration and link. Hadn't considered that the flipchart option was there as an option for non-normal procedures - setup makes sense with that in mind. Hadn't realised, that 24/33 were the landing options, but I see that reflected in real life material as well, and it makes sense.

@Martyn said in About v2.4: Hi. As per our conversation on Reddit, we've improved the engine and oil temperature simulation logic and those changes will be included in the next update. Yep. Thanks for taking the time out and replying.

The main altimeter is currently using the logic described in the link forum thread (that was updated in v2.4). We'll take a further look at the Standby Altimeter logic in a future update. Mark - Just Flight

@Mark Does this also apply to the X version, or is it only for the PC marketplace? Thx

Thanks Mark.

https://www.justflight.com/support

SU4 lighting fixes: https://support.justflight.com/support/solutions/articles/17000124987-146-professional-msfs-changelog

We have no plans to change the package names of any of our products. It is an SDK requirement to have the package names identical across MSFS 2020 and MSFS 2024 products, and it is particularly important for in-game marketplace products to ensure that we can offer a free-of-charge upgrade path between 2020 and 2024 versions. If the package names were to differ between the simulators, then the marketplace would consider them as two separate, unrelated products and require a full price purchase in both simulators. Mark - Just Flight

That's also been my experience and solution, but I hadn't looked at the file(s) to see what was funky about them. I wonder if the failed save file is related to backing out of the initial load.

Excellent, thanks Mark