Marcfourneau

You would fly as directed by atc. Enter via th dme arc from north or south as directed and then follow the loc to the rwy per the descent profile. If not using the direct entry fly to the iaf, CAM, at 3000 then outbound via the track indicated depending on your aircraft type. Make the turn at dme 8 to intercept the inbound course back to CAM (1700 at dme 8) and fly the descent profile. In real world you would rarely fly the full procedure with the outbound turn rather you would be vectored to the loc by atc.

This is what worked for me with this problem: I had just loaded the weather before closing the doors. When I reset the weather I could open the doors. I think there is some sort of pressure logic that keeps them from closing.

Works and flies fine for me after the sim connect fix. I completely uninstalled fsx on my system.

BTW I didn't notice whether vnav had disengaged or not since I switched to vs mode.

I had a similar but not exact thing happen last night. I was flying LGA DCA on the Clipper1 arrival. I changed the BAL xcross to 10000 per the published STAR but the CDU failed to update the subsequent waypoints (and yes I hit exec), and I got the "unable next altitude" message even though I was well able to descend to the correct altitude. I was able to fly the arrival fine but only with vs and fl chng. This is disconcerting esp flying vatsim since alt constraints can vary and reminds me of the difficulties with the Wilco airbus. I wonder if the CDU logic needs to be looked at more closely.Marc Fourneau

Try inputting winds aloft in rte data pages. It makes a big difference in the use of drag, even with a small tailwind. I was on ua flight to sfo last month and we did a 360 on the golden gate 4 arrival because we were too fast and high.Marc

Simply, yes, buy it, it's the only solution.

Obviously a highly personal choice, but as far as airliners, the best are those that have well modeled fmc's. To fly a decent heavy realistically it must have vnav modeled correctly. In my hangar, pmdg, feelthere embraer, and lds are the only ones. Wilco airbus is the most glaring failure in this regard but qwings also comes up short. Even Pmdg's MD 11 FMCG has some quirks but I have learned to work around them. To fly a jet reliably you must make crossing restrictions realistically and without programmable vnav, it's a challenge. If you have any thoughts of vatsim, get an addon with a fully (not "lite") FMS.

There is a -700 editor. But I have the same question for -900 and -600.

Watch the outside temp. FsInn wax is notorious plus I have rarely noticed this with AES. If it happens again, clear the weather and see what happens to climb rates.

I was using ASE but was seeing the same severe windshifts. I figured this was because I needed fsuipc as stated in some other posts. Do you use fsuipc with ASE?

I am flying the737 with REX weather engine. The winds are constantly changing and at times making approaches impossible. Today I was landing at LAX, 24R, when I was facing a 50 kph headwind at low altitude. The winds then shifted and died at 2000 ft which resulted in a stall and crash. I have had this happen at various times at other airports but this was the most severe. I have read about the need for fsuipc with ASE but not with REX. My question is, is this a universal problem, and if so, is the only fix, fsuipc, which I don't own? Is this an issue being patched? Thanks in advance. Marc Fourneau

That happened to me too. I uninstalled the the whole addon and then reinstalled and haven't had any problems since.