They are.

 

What panel state were you using for the flights?

Dark and Cold

Just flew ORD-LAX.  Everything was fine except I had a random Caution message that wasn't tied to anything.  Ran through all the systems, everything indicated normal; so it just sat there on the entire time.  Other people have said it is a bug that can happen when starting from Cold and Dark (which I had).

 

The airplane is slippery as hell.  I'm used to the NGX, which people say is also slippery, but I have no problems in it.  I can pretty much throw that thing all over the place and still maneuver it into the profile I want just fine - not so much on the 777.  I had to do a go-around arriving into LAX because ATC dropped me in too fast and I couldn't get it to slow down for the life of me, including putting the gear down.  Being used to landing the NGX, landing was also an experience.  The landing was at night, because I apparently like to make things harder on myself on my first flight, and side-loaded the landing and slammed her down.  EZDok let me know and was jumping all over the place.  I'm pretty sure the 777 was laughing at me as she was limping back to the cargo ramp.

 

FLCH is definitely bugged, though.  I use it all the time and sometimes it would start a descent, or climb, and change altitudes a fraction of what I tell it to and then just level off.  This is what primarily forced my go-around on the 1st attempt into LAX, as I was running checklists and paying attention to other things when I noticed that FLCH had leveled off way above my altitude.  I just started using V/S from that point on.

Those glowing brake rotors look so cool! B)

I came in way too fast at KCOD last night. Thought - "this is going to be tight"! Couldn't figure out why speed was so high. Slammed on the brakes and just managed to stop before I exceed runway limitations! Realised I hadn't disabled the A/T. What a numpty! 

Popped out to have a look at the brake gear - red hot!! I agree, very cool.

Dark and Cold

 

That's what I thought - take a look here:

http://forum.avsim.net/topic/418750-pmdg-777-issue-tracking-thread/

 

(up in the acknowledged part - for now, don't use the C/D panel state and you should be fine)

i thumped it in at DNMM...the video is below at the end...

 

http://www.twitch.tv/tebbsie/b/456767787

So - remember how I told you Lufthansa Technics had my plane in for a heavy landing check yesterday?

 

Well... now there is a FedEx 77F in Nice that might just need that check as well. I really need to read up the FCTM flare technique. Other than that, very nice. I flew the Nice 4R RNAV with visual part, and it handled extremely nice, up until landing. Took the 77L of KAL later to take from Nice to Prague, I opted to try autoland, but I can attend to sliperiness. There are ways to slow her down though... a bit different from the 737 I am used to fly decelerated approaches with. But I got her stable by 500AAL.

I only have two flights, but I have to really try to actually break it.  It is very responsive and easy to handfly.  I've been flying the NGX probably 95% of the time in my last year, and was expecting some difficulties with the 777, but fortunately that's not the case.

During testing, I was hand flying local pattern at KIAH Houston and first time I lost track of the runway turning base to final and got fast, landed long and overran runway. Took out a fence and a shack but I got it stopped before the Hardy Toll Road. Later, I flew a looong trip, KIAH-VTBS only to find FSX doesn't have this airport when couldn't get localizer... dang.

That's what I thought - take a look here:

http://forum.avsim.net/topic/418750-pmdg-777-issue-tracking-thread/

 

(up in the acknowledged part - for now, don't use the C/D panel state and you should be fine)

This isn't 100% reproducible isn't, cause I did a flight yesterday using the C/D panel and everything worked perfectly.

 

Maybe is the fact that I set the C/D panel to be the default one?

 

 

Maybe is the fact that I set the C/D panel to be the default one?

 

No clue.  We've just found that there's a problem inherent in the panel state.  All kinds of errors are present when that panel state is loaded that don't occur when it's not loaded.  That's really all I can say about it.  It's...troubling...