Hi, according to @Mav-jp this is already fixed in next version 4.36.
Regarding time frame, I will give MY personal opinion on this, which is not necessarily the team official position.
I don’t like the 3-4 weeks joke. Nor do I like the sentence: “ask for your money back”. I hope you will never hear it from me, nor from other team member (but that is out of my control). I’ve been to the other side (player) and I know what it is to spend a lot of time on the sim and have absolutely no idea when a loved new feature is coming in, or a long standing bug gets squashed. On the other hand, speaking too much spoils the fun a bit as well. Finding the balance is an art.
Now, it is true that we don’t get any money out of this and we work on our free time. So yes, sometimes things get out of hand and less professional. But that does not mean we should act like that. We should aim high, even if we cannot get there.
BMS is not the first time I work for free, in fact, I regularly work on other free projects and I’ve done my share of contributions to the open source community. IMHO, working for free does not mean we can deliver low quality stuff, treat our users badly or play with people’s time. But yes, it is a good reminder that we, devs, deserve respect and sometimes we will not be able to fulfill all expectations.
I would try to be even more precise with our time frame. I’d say February 2022, but that is a bet. Q1 is safer and reasonable, don’t expect anything in January. Still, if things go wrong, we can get past that mark. But we will try.
As for the code state, we just stabilized most of the critical bugs (races, memory corruptions), now we are paying more attention to small details. Little by little, with the help of our testers, we fix those small things. Sometimes, a regression shows up, but it is becoming less common. As for the data side, I think it is mostly stable, with some additions still being made. But that is not my area, so I will leave this open for data folks IF they want to talk about it.