11bee

Check out the control tower, nice cold Sam Adams beer sitting on the console. I love this airport, it's one of the best.

Given the continued release of fixes on nearly a daily basis, I do have to ask why, given the very extended development period, none of these issues were noted and addressed during the very long beta? At least the dev is responding to the multiple problems, which is refreshing to see, but I'm just surprised so many problems made it to final release. I'll be waiting quite a while before making a purchase decision for this one.

Pacsim has announced that they are working on CLT. Don't really know much about these guys but it has to be a significant approval over the status quo. Looking forward to seeing some updates from them.

That's disappointing. It's a major immersion killer that's been present since Day 1. You'd think Asobo could devote a bit of time to addressing it. I don't even care if they skip the animation and simply teleport the jetway entrance to the side of the aircraft.

Any idea why Asobo / aftermarket devs have still been unable to fix the issue of jetways not connecting to parked, static airliners at airports? Somewhat of an immersion killer to taxi in at a major airport and see 30 jets sitting at their gates, all with the jetways retracted.

Not to go OT and risk the wrath of others but any feel for how progress is coming along for SP1?

How annoying. That's what I ended up doing. Restarted and all was well. It did seem that some of my control setting were changed after the SU5 update. Is that a known issue?

Just loaded a flight with the new update. I spawn on the ground next to the jet as always. Shift-C doesn't get me into the cockpit. Hit escape to see if a control binding was changed, nothing happens. The keyboard doesn't seem to work at all. Am I missing something here? Using the Fenix A319, if that matters.

Trying to figure out the proper A/P procedure when I'm doing an ILS approach. The ILS typically has at least two waypoints that bring you first onto the localizer then to glideslope capture. Assuming I get vectors to final, should I then put the autopilot back in NAV / VNAV mode or simply arm LOC and after capture, ensure I'm on a good decent profile using V/S to capture glideslope. Any advice from RL pilots (especially airliner crew) is much appreciated.

True but this is certainly much, much better than the status quo.

Still need developers of current aircraft to integrate it into their products, so I'd image that it's going to be a long time before we see it on our flight decks.

To echo others, Fenix really takes their time but it's always worth the wait. TBH, I'm not sure what is "broken" with the VNAV, it seems to do a credible job for me. The update I'm really looking forward to the iFly Max service pack. I'm loving the MAX, it's a blast to fly and it's such a nice change from the level of automation you get in "the Bus". iFly has already done a very nice job but this SP is going to take the MAX to the top of the civilian airliner pyramid (IMO). The other item I'm waiting on is the long delayed A220 (can't recall who the dev is right now). Looking forward to learning a brand new control system. Early screenshots look amazing.

You can't hide behind the "early access" shield forever. It's been two years and I'd argue that IFR vectoring is no better than when it was released on Day 1. I have a feeling that "early access" will still be thrown out there as an excuse two years from now. So again, maybe just hold off on adding all those other features and just get the main aspect of this product fixed. Once that's fixed, go ahead and add a million shiny new features to it. But until then.... As an aside - Just wondering what the reaction would have been if Microsoft decided to release "MSFS 2024 (Early Access)". Then, when everyone complained about it's horrible initial state, they would simply just throw out the "but it's still in early access" language.

This is the crux of the issue. I've had this add on since nearly Day 1. ATC was broken then and I'd argue that it's just as broken today. I'm at a loss for why they don't focus their resources on fixing the major component of BATC - the ATC system. Instead, they are going off on multiple tangents trying to introduce the latest new "feature". Only thing I can come up with for a reason is that it's an attempt to generate sales revenue. At this point, I use BATC for the AI traffic (which in itself is still heavily flawed) and for taxi/takeoff. Once I'm at TOD, it simply ignore BATC instructions (if they even remember that I'm out there).

It's 100% pilot error. I'm so spoiled by autothrottles in the iFly and Fenix, I've forgotten how to manage thrust when you are in the approach phase. This thing bleeds off speed quickly when dirty and it's really hard to get that airspeed back. Not complaining, it's loads of fun trying to nail landings, just requires a bit more work...