I purchased the 777 base pack yesterday (beta 0.3), and after a couple of aborted flights, I want to share my feedback on this aircraft. I'm always honest with developers, because it's my experience after 30+ years of dealing with software that that's the only way to do it. I also want to use my vast sim experience to push CS to new heights, having thousands of hours in FSX, FSW, X-Plane and P3D in all major dev's aircraft.

The first thing I noticed with this 777 is a performance issue especially noticeable in the cockpit. When FPS drops below 25, the human eye start to notice it, and this aircraft is at 15 to 19 FPS on ground on my computer (i7-6700K/GTX 1070 8 GB/32 GB RAM, P3D v4.4). So obviously there's some (excessive) processing going on in some systems or the gauges/panels. Outside the 777 I get about 30 FPS. As I've understood I'm not the only one having this experience, so this is something that must be looked at.

The real show-stopper for me is the fact that the (auto)throttle gets stuck at cruise. Follow the link below to watch a YT-video. No matter what I do, the throttle is stuck and keeps accelerating the aircraft. The video also shows the low FPS (Fraps in upper left corner).

Meters should disappear completely after pressing MTRS, the 777 still show it above the purple feet indication top right of the PFD.

VNAV logic is where devs show their skills. The CS 777 is pitching at maximum angle given speed or thrust available. This is not how Boeing (or Airbus for that matter) does it in real life. The nose will bob up and down as the aircraft searches for optimum climb angle while maintaining the speed set in the FMC. This is beautifully and realistically done by a competing dev, but I'm sure CS is capable of recreating this logic for their 777.

If CS can put fuel and pax/cargo load in the EFB or FMC/CDU, that would be lovely.

The outside 3D model looks stunning, just like the 757 which is the most beautiful re-creation in any sim. The cockpit is okay, but the panels could have had a more Boeing-like typeface or at least a more clear text appearance.

Link to video (unlisted YT video, only available if you have the link):

youtu.be/5uc75jgD5No

(As I've not posted 3 times in this forum, I'm not allowed to make the link click-able. Sorry for that...)

I too am having a similar problem.  I had done a couple of successful flights, but then the autothrottle started to act just like described.  My flight plan called for a cruise of .833 mach at fl340.  As soon as i reached that cruise, the speed continued to climb.  I tried as you told to click on the speed button and adjust the mach reading to .85 and then click on it again, my speed continued to increase.  i click on the speed button again and now I am up to mach.891, so I adjust it back to .833 and click on the speed button again and it continues to increase speed again.  Click on the speed button again and now it is up to .893.  Nothing seems to keep it under control, unless i am misunderstanding what you are instructing.  Not sure what you are saying by pressing the ias/mac button.  It does nothing to let me change it.  Only the speed button does.  Thanks.

Ouch! I just had this happen to me for the first time in v0.3, but I was flying the 777-300ER GE115B (it's the first time I have flown the 777-300 in v0.3).

Pressing the IAS/MACH Selector Switch did not fix the problem, but as I was pressing the switch, I somehow wound up clicking on the IAS/MACH Reference Switch (MACH Speed showed .9xx in the speed display (I can't see exactly what it was, as Nvidia Shadowplay was recording at *medium quality in P3Dv4, and the video looks so crappy I can't read anything on the panels)), and when I clicked on it a second time, the throttle levers retarded, and the speed started dropping, and now the 777-300 is happily cruising along at .833, like it should be.

*Nvidia Shadowplay set at medium quality creates great videos in all my other games, but not in P3Dv4.

parsec71 wrote on Apr 28^th, 2019 at 3:00pm:

Try to turn off the pax cabin.

We'll check the AT and if it's an easy fix will do it.

The fuel and payload manager will appear in the 1.0.

parsec71 wrote on Apr 28^th, 2019 at 3:00pm:

Pls save the flight right at the issue and attach the files to your post. 

It has happened twice today in the 777-300ER. I have saved the flight and attached it to this post.

I really do hope that Captain Sim will come up with a fix for the autothrottle problem that many are experiencing.  Today, I am flying and it took me over half an hour to get the cruise speed settled to what the flight plan called for.  This involved disconnecting the autopilot, turning off the autothrottle switches and numerous times, adjusting the mach speed with no resolution   Once it settled, I noticed that the altitude went up to a thousand feet above the planned altitude even though the altitude screen was set for 39000 feet which matched the cdu altitude.
   
Not sure what the problem is.  I thought this was a plane that was brought over from a 32 bit program and made into a 64 bit program to work with P3D.  Does changing the bit rate also affect a lot of the parameters which is what it is doing to the autothrottle?  I'm not a techy so I don't know.  All I know is that it is making it very difficult and frustrating to try to fly this wonderful plane.

DV006 wrote on May 8^th, 2019 at 10:04pm:

We are working on it.