Edmoore

Ah - might have fixed this... anyone reading in future try checking your GPS source is set to GPS1 in the RXP settings:

Hey there, I could well be doing something wrong here but with the GTN750 in the SF260, the behaviour of the CDI needle on the HSI is not what I expect. In most cases, the CDI shows no deviation from the GPS track even when the 750 is clearly showing one. Toggling the autopilot into NAV mode will usually 'refresh' the HSI and the CDI will jump to the expected position. SF260 version 4.4.6 Not quite sure exact version of RXP GTN 750 but downloaded it only a couple of days ago X-Plane 11.50b12. Example image of CDI not reflecting course deviation: Example of CDI needle showing correct course deviation once AP NAV mode engaged: My GTN settings:

Hi all, Hoping for some real-world expertise here. So I'm departing from an airport that has relatively low altitude restrictions in the SID for some time after departure. VNAV kicks in soon after takeoff and gets me up to 5000' or thereabouts at a fairly steep pitch angle which is to be expected on takeoff. Having leveled off at 5000 and sat there at 250 knots or so for a while, we're at some point going to get clearance for a further climb. I can do this with LVL CHG or I can stick in VNAV, and hit that little "continue climb" button (forget the name now). But seeing as we're still below 10000 and the aircraft knows it needs to stay under 250, this results in a massively steep pitch angle as the engines go to N1 - I've seen 12, 15 degrees of pitch a couple of times. My question is - in real life, is this how it would be done? I only ask because it seems like it would be a quite dramatic "leveled off, then suddenly really steep climb" sensation for the passengers. I guess the faster you get to your assigned altitude the better for ATC and your fuel flow, but I can't remember experiencing this sort of departure as a real life passenger. I could well be misremembering though... Appreciate any thoughts!

Thanks Michael. This link may work / be quicker for some: http://library.avsim.net/sendfile.php?Location=AVSIM&Proto=ftp&DLID=161004

LOL! Yeah the first time I used VNAV for some reason I forget I would have to LOWER the MCP altitude as well as increase it on the climb... resulted in a pretty precipitous descent once I'd realised..

Sanity prevails. Thanks Rónán.

Patrick - exactly! Actually all joking aside, it's genuinely helped me with my landings. The FCTM recommends flaring at 10' which always seemed super low to me, but watching the autoland do it you realise it's just about perfect.

Thanks all.

Fred - it still sometimes happens even when the minimums have been preset. And in all honesty, under what logic would you say it made sense for it to default to 9000 if setting in flight?There's way too much hair-trigger "read the manual" stuff around here at the moment. Tedious.

Yep, me too. Annoying.

I've had weird performance with them in Preview on OS X as well. Possibly just because they're very complex?

Ah yes, I momentarily forgot that when you make a joke on the internet you have to telegraph it with a flashing beacon... Sense of humour failure, Nigel?

Yep that's it. Hasn't come up again since though. Definitely remember not being able to clear the scratchpad.

This not being the first time I've used a forum, I did try that. No results came up (even now only this thread appears). Maybe an issue with the search function?

Try pressing LVL CHG, that seemed to wake up the VNAV in my case.

It's making my hand flown landings look completely rubbish. Frankly I think something ought to be done about this. This aircraft is going to destroy the self esteem of sim pilots everywhere. EDIT: Apparently I need to spell out that *I am using hyperbole to make a point about how good the autoland performance is*. Blimey.

I've had the same problem a couple of times; in my case switching to LVL CHG (even when on the ground) seemed to "wake up" VNAV which was then able to be switched in.

Ah yes. I am an idiot.Thanks all.

Tried doing a pushback via the FS ACTIONS menu. Nothing happened. Did the shift-P FSX one instead. Now I'm pushed but something keeps reapplying the parking brake the second I release it. The physical brake lever in the virtual cockpit is correctly releasing and re-applying, but the red FSX "PARKING BRAKES" message in the lower left won't go away whatever I press. Quite annoying as just spent 40 minutes preflighting! Any ideas?

I agree to reading the introduction and going through the tutorial carefully. But I think it's acceptable to ask questions that may be answered somewhere in the FCOM - we're all friends here, and it's okay to ask some fellow simmers about some behaviour or feature that might otherwise require searching through thousands of pages of documentation that is written with professional pilots in mind.

On the fuel and payload pages, although the descriptions were all there (i.e. the text that says FWD CARGO, PASSENGERS or the quick options like RANDOM etc etc), no values appeared at all, even though the aircraft was acting as though any changes were taking place (e.g. the fuel quantity on the upper DU would reflect what I pressed). It seems to have been a bug as I've reset the flight and done what I think was the same procedure again with no issues.

Hiya, Going through a startup from cold and dark. Got the APU up and running and entered flightplan, but the CDU isn't showing any figures for payload or fuel (it shows all the other text and I can press 2/3 full or whatever and there's a slight bump as the load changes). Fuel quantity changes on the upper DU. And now when I go back to the menu page of the CDU there's no longer an FMC option.Where am I going wrong?

I've never really used the Instant Replay feature so this may be a well known limitation, but I've noticed that the flaps never show as any other position than fully up even when playing back a final approach with flaps 30 etc. Is this is a bug or is FSX Instant Replay a bit crap?

Ah so you're saying it's an operational thing?I did try engaging VNAV after takeoff the first time and it still didn't engage. Plus although I'm very new to this I was basing the "arm VNAV on the ground" procedure from this bit of Ryan's tutorial:

Huh - appears to have suddenly come on now. I think all I did was (whilst still on ground), press LVL CHG and that seemed to wake up the VNAV mode which will now toggle on and off quite happily. Be grateful if any of the VNAV wizards from PMDG could let me know whether this is expected behaviour?