holland786

The AIRAC has been updated on the day of the new cycle every time for quite a bit - the sim updates automatically.

First, thank you for your feedback! We're working on an update to the 4K texture pack which should be available shortly. This may improve your experience. For the sake of our own data, what are your specs? The example you give is a known bug, but this is in an unguided path, meaning it would not be trying to follow the path on the ND anyway. This happens in a number of scenarios, inlucidng course-to-fix legs in procedures, overfly waypoints, some cases where you overshoot a turn, etc. This is accurate to the real FMS behaviour and the result of intentional tweaking. The drawing bug is not intended, but because it does not affect guidance is not a priority at the moment. If you have other examples of LNAV issues, feel free to let me know or open a GitHub issue: https://github.com/flybywiresim/aircraft/issues I've forwarded this feedback to the dev who worked on VNAV. The level off point missing is a known bug due to it not being able to placed on MANUAL legs at the moment. This is a known issue that the engine model is currently overpowered. This will see continuous work going forward. Feel free to open an issue on GitHub if it doesn't already exist: https://github.com/flybywiresim/aircraft/issues There should be some improvements coming in the next release, look out for that.

Curious to hear more about your experience (and what matters most to you), always helpful to near what people are looking forward to the most.

Load/save is far from a basic functionality. It requires ensuring all systems save and load a consistent state that can occur in the real aircraft (made challenging by the fact that many of the IRL plane systems we design around are not made to spawn in flight - this is a problem that has to be designed around even in real full motion sims). At an alpha stage on both aircraft it simply does not make sense to spent so much time designing support for this around systems that are constantly changing and being improved. But it is an alpha release problem. In the past 4 years we have moved systems between different programming languages, rewritten them dozens of times, changed the architecture of the avionics along the way, all while having to take into account extensive future system development, performance considerations and feasability while running entirely in-process. Adding yet another level of complexity that has to span multiple technologies and frameworks while we already have to address bugs and performance concerns early in the release cycle is not a good idea. I'm curious to know on which information you base this claim. If you have identified a basic restructuring we could do to implement load/save, we'd love to hear about it. Furthermore, with all the code being freely available to use and modifiy, contributions to it would be very welcome. To be clear - we would definitely like this functionality to exist. But it's not as simple as it seems, especially during alpha.

Not quite the case - fms-v2 is available to the public in the development version, but it was decided to merge it without FINAL APP so that the rest of the features would be available to users without delay. See my above response regarding FINAL APP itself.

No one has "lost focus", and FYI, the A380 project was started 4 years ago. So certainly not a new distraction to avoid working on FINAL APP. Otherwise, we'd have been distracted for a long time. The reality is just that the person working on FINAL APP is on vacation, and that it was previously waiting for fms-v2 to be merged (which it now is). We thank you for using our aircraft, however. Glad you enjoy it!