11bee

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...

Don't be dense. If you want to make a case that FSDT's version is up to current standards, you (and your alter-ego aniiran) are just further embarrassing yourselves. It's not, it's not even close to a current spec large airport in MS2024. Maybe you are at the wrong airport if you think FSDT's state of the art or your machines can't run anything except the most basic aftermarket airports.

You nailed it. Honestly, from a simming standpoint, it's pretty easy to consistently nail landings in the MAX and Airbus. In the CRJ not so much. If you aren't on your game, you'll fall out of the sky, lol. I get a ton of satisfaction completing a full flight in the CRJ. Still wish someone would do a brand new CRJ but the Aerosoft product is solid. Maybe it's me but I really don't find the smaller fonts / displays to be a huge issue. I keep the range dialed down and de-clutter the Nav display to only show basic info.

Flew into KORD from the east, a couple of times this weekend, using the WINDY and WATSN STAR's. Noticed on both, there are no speed / altitude constraints and (if you are using the southern runways), you have to leave the STAR well before the final waypoint or else you will be out of position for lining up on those runways. Looking at traffic flows from Flight Aware confirms this. So from a simming perspective, I assume I just need to wing it and fly whatever vectors / altitudes / speeds I feel are acceptable to get me to the ILS approach fix? Not as easy as it sounds, my first time I descended way too soon and spent the last 40 miles of the flight leveled off at FL100. Any tricks to this? Would BATC be able to handle this kind of a STAR?

I hear you, I gave up on the CRJ years back because Aerosoft pretty much ignored the dozens of issues with the initial release. To their credit, they finally got around to fixing those problems and then added a ton of additional enhancements. I'd love to see someone else do a completely updated CRJ because it's such a challenging, fun aircraft to fly (and it looks pretty nice too). Much more satisfaction taxying in to the gate at KLIT than if I had flown the Bus or a MAX.

It's so strange. PVD has three versions available and there is only a single, very outdated CLT (don't get me wrong, PVD's my home airport so I love that part of it). Anyone who flies a lot in the eastern US has been through CLT, you would think it would be on multiple developer's lists, especaially since, by hub standards, it's really not that big of an airport.

You do know that for 99% of the questions posted here, "simple search of Google" would have answer the question. But then this forum would be dead and just filled with DB's like you. I post here because typically, I get a bit more insight into my questions and often learn more than what Google would spit out. Thanks for taking the time sweetie.

Title says it all. I've got the FSDT version which is a port from FS2020 and is very, very basic.

Just fired up Aerosofts CRJ V2 for a flight I've done many times in RL, KCLT to KLIT. I've pretty much had this on the backburner for years but I finally just needed a break from endless Fenix / iFly MAX flights. For those who don't have this one installed, I really suggest you grab it. It was the first commercial jet released for FS2020 but after that, Aerosoft pretty much just ignored it. That changed a year ago when they released V2. It's a game changer. An EFB that IMO is the equal of Fenix, systems updates, GSX integration, etc. It's a brand-new jet. It really is a satisfying challenge flying this. In some ways, it's just as modern as the A320 series (and way beyond the 737), in other ways, it's old school (no autothrottle and only "predictive" VNAV). Never realized how spoiled I was flying the A320 / 737 until I was on the approach to KLIT and had to manually manage my speed. It's a very satisfying experience to pull off a flight with no issues. If anyone's looking for a break from flying Airbuses or Boeing's, this will do nicely (at least until we get the A220). Check it out!

Without having to watch the full video, anyone know what the "Cabin Voice" button is all about?

OMG...

So yes or no - do you plan on correcting this issue?

No, I was on speed and there was no deceleration required for that segment. 1000' FPM descent to 10,000' and then 8 miles to fly to the waypoint, where it then started a decent to the next altitude constraint.

I've noticed some circumstances where if I'm on a STAR and I have a waypoint with a upper and lower altitude limit (like 12,000 / 10,000), the VNAV will descend a a pretty high rate to the lower limit and then level off and fly at 10,000' to the waypoint. This doesn't seem to be correct (or is it?), I figured the VNAV would compute a descent rate to avoid leveling off. Is this accurate in RL?

That's tough regarding BATC. When I land, my destination airport is typically very active with plenty of planes at the gate and arriving / departing (all my traffic sliders are set to 10). When I reboot BATC, the airport turns into a ghost town. Today KCLT had 7 planes at the gates and 2 arrivals in the 35 min I was on the ground.

Any reason why I can't do layovers and multileg flights using the Fenix Bus or the iFly MAX? I use GSX and BATC. Or do I have to go back to the main menu and load the next flight?

Yeah, that's what I figured. I found a few keyboard binds that I deleted. No change. The weird part is that I had 4-5 initial flights with no issues at all.

I tried to make the most of it after I lost one engine 5 min after takeoff. Instead of just shutting down the sim, I turned back to KCLT. I was halfway there and the 2nd engine died. I was able to restart it a couple of times, both times it failed again after a few seconds. Tried to glide back to KCLT, wasn't going to make it. Found a straight stretch of highway a bit off my nose, was going to replicate that Southern DC-9 mishap from back in the 70's. While trying to align with the road at 500', airspeed at 130 and dropping, I stalled and went in. RIP 11bee.

Any ideas on why I would be getting uncommanded engine shutdowns on the CRJ (Latest Aerosoft version, on MS2024). Just got back to this after a long hiatus, first few flight went fine but ever since, one or the other or both engines die on me. Typically all is well for the taxi-out but once I'm off the ground, the fun starts. I haven't made any control changes and have checked to make sure no existing bindings are the culprit. Any ideas are appreciated.