Robert Howe

Been trying things for the past couple of hours including removing & reinstalling liveries, also the 300 expansion pack itself. As far as I can see the issue is caused by switching from a default 744 to the 777-300. I'd been loading a default plane first because FSInn sometimes crashes FSX if loaded while the T7 is running.

Has anyone experienced this? Just noticed my N1s are missing.

Will do.

Oops I spoke too soon and assumed too much, it seems. The two flights I referred to in my 2nd post were in the 77L. Just landed at VTUD in the 77F. I was a little nose-high on main gear touchdown. The RA appeared to be showing 0 with the nose still well off the pavement, and the nose gear touchdown sound played while the nose gear was definitely still off the ground. Seems to be an issue with the 77F only.

Thanks, Kyle, I think that explains it. Done two more flights today and watched the radio altimeter carefully, nose gear touchdown sound plays at exactly RA0 then she settles to RA-2 which is the further drop I've noticed. The more I fly and taxi this aircraft the more I like it.

I wonder if anyone else has experienced this. When landing the 77F, after main gear touchdown, the sound of the nose gear hitting the runway seems to play too soon. Everything else is fine with the landing, gross weight about 230 tonnes including fuel, approach at Vref+5. It's just that after I hear the sound of the nose gear making contact, the nose continues to drop significantly then stops abruptly, as though it hadn't reached the pavement when the sound played.

Tried my hand at painting the 77L in the livery of Altair, the VA I fly with, www.altairva.com It's my first go at painting planes. I'm having trouble with the underbelly colour, at the front and rear of the fuselage. Here's a screenshot of my paint job: What I want to do is extend the blue area and yellow border at the front and rear, so it looks more like this paint job my friend did on the NGX: I can't work out where to put the coloured areas on the main fuselage map to make them look right on the finished product. I'd be grateful for help from you experts. Thanks in anticipation.

Thanks, Arne

Thanks, gentlemen. I will get the update on completion of my current flight. Edit... is it necessary to uninstall the 300 and reinstall using new installer, or just run the installer and let it repair/update? I guess the latter...

I've installed SP1b but the PMDG Ops Center program keeps giving me a notification that there is also an update to the 300ER. Is there a separate update, or has Ops Center got its files in a twist?

PMDG support directed me to do a clean reinstall of the T7 (772, then SP1, then 773). That has cleared the sound problem. Still no idea what caused it though.

I'm using the stereo sound. Tried start switch first then fuel switch. As predicted, the strange sound is still there. Here's a quick and dirty recording I made starting engine 1. Start switch first, then fuel switch when oil pressure rises. The background sounds are very faint but the weird intermittent buzz is there, from 36 seconds. Edit: just tested in the 772 and the strange sounds are not there. I only get the strange sounds in the 773.

Tried a search but I can't find this specific issue amid other engine sound posts. I usually start no. 2 then no. 1, autostart procedure with both fuel switches in RUN detent, then start the engines in turn. No. 2 starts fine with no peculiar sounds. When starting 1 I hear an intermittent buzzer, sounds like flaps out-of-position or could be ignition cracker sound, not sure. Hardware throttle at idle during start. Buzzer stops when fuel flow starts and engine runs up. Anyone experienced similiar? It's the 773 BTW.

Yes I'm running SP1 but no, the flights were saved post-SP1

Loaded a saved flight today, 25nm from TOD. At TOD the AP pushed the nose hard down and the aircraft descended at 11000fpm. A shedload of yellow failure warnings came up on the EICAS. Tried reloading the same saved flight, disengaged AP and started descent manually then engaged AP when descent stable. No further AP issues but no. 2 oil temp rose to 260° and oil pressure dropped. Cleared failures in FMC PMDG options and all was OK for rest of flight. No idea what I did wrong. Anyone experienced similar?

Got a reply saying the team would look at the error log I sent them and hopefully fix the issue in an upcoming hotfix. Meantime, I see from another thread that there's no CTD if you reject the PERF data and enter it manually instead. Haven't tried that myself yet.

Thanks gentlemen. Yes it was the BAW livery.

I've noticed that VREF and flap setting is not displayed on the PFD during approach and landing although I did select FLAP30 on the FMC during descent. Is this a customer option? I can't find it in the display pages on the FMC.

I have exactly the same problem. I made my FP using EFASS, exported to my PMDG flightplans folder, then loaded the FP via the FMC. Route loaded fine but on clicking ACCEPT on PERF INIT page I got CTD. Repeatable. I have put in a ticket to PMDG support.

Which version of UIAutomationCore do you have?

What, you mean I don't need to walk 3 times clockwise around my PC either? :smile: Thanks for looking into the doors issue. Not using a panel state at startup seems to be working, touch wood.

I do not have and have never had GSX installed. I started to have the doors problem a few days ago. Other posters helped me to notice that the problem began soon after I set a default panel state. I have now cleared the default panel state so she starts with engines running, then I load a panel state manually. Also I'd like to know if anyone has had the doors problem after loading the T7 in the FSX free flight window. (Following advice from other posters I tried this, no doors problem, but FSX CTD'd on initial climb. I went back to my old way - load the default A321 first, then switch to the T7, no CTD and no doors problem. I didn't use a panel startup, I manually loaded 777 LONG) Rob

Problem recurred today. Startup state was 777SHORT. Tried changing panel state, no joy. Everything went dead. Screenshots showing the doors open and strange configuration of FMC pages:

I had the same problem as Aidan yesterday. The doors were open (3 cargo doors and the L2 entry door) but would not respond to button pushes on the FMC. Moreover, the FMC seemed to think the cargo doors were closed already (the word OPEN appeared next to the LSKs). I tried restarting FSX, turning electrics and hydraulics on and off but no joy. I had started with the 777 SHORT panel state. The problem cleared itself about an hour later without any apparent cause, and it has not recurred today. As a precaution I've saved a panel state with all doors closed, in case it happens again. Rob (edited as I'd forgotten to put my name)