Just to complement last answer, from a technical perspective for those who are curious:
we moved to git (much better version control management, allows multiple changes to be easily managed at the same time). Downside: some coder had a hard time adapting to it.
Gitea infrastructure: much better reviews (which are still optional, but we do anyway). More pairs of eyes looking at the code means knowledge being spread and more people to catch bugs.
A few coders write some units test, which is good to avoid future regressions. But this is still a small effort.
Flag: almost every change is flagged, so we can revert and test in case of problems. This is very close to 100%.
Quicker test iterations: we try to generate internal installers for testing much quicker than we used to be, to get constant feedback.
Comms: we are trying to improve, having a common comms center. This is still not adopted by all but Max made some magic integrating Discord with Rocket channel. And we also a internal wiki which we are trying to feed with useful information. And we are also trying to be more open/closer to the community: we are all on the same team. We are one.
Bug philosophy: one CTD is one CTD more than what we want. We really chase bugs as they show up. Stable code allows us to do more magic in the future.
Getting rid of legacy/old stuff: we are slowly killing old stuff, which was just a pain to maintain.
Plaaning: as soon as we release a version, we try to create a roadmap to the next one. This kinda guides us in terms of features. It is not set to stone: this release for example, has a totally new feature related to… well, chevrons, which wasn’t planned. But the main feature was the top priority all the time.
illetve egy adalék a VR mellett megjelenik egy nem F16 os gép is ami repülhető és külön simbolikával, ami early WIP ,de ez megnyitja az utat, hogy később más gépek is repülhetőek legyenek saját avioval.