@Christopher Low

At 5'...

 

Regards,

Edited May 27, 20188 yr by charliearon
embedded the video

I went ahead and bought it since they gave a timeline for updates. Since most of the issues have been documented by other people, I'll just say this... it feels like an early access product. I've run into so many issues that I'm just going to wait for the hot fixes then decide whether to get a refund. 

The 787 seems to be a big hit with the VATSIM community. Since it's been release I've never seen more 787's on the server than maybe the 737. It's like every third plane is a 787. Even the Twitch streams are dominated by the 787 in the FlightSim section.  Im currently on my 3rd long haul flight in the 787. This flight is 15hrs. I've been flying the doors off this plane since release and besides the minor bugs that have been documented by QW, it's been working great. 

Long Hauls so far have been: KSLC-EHAM, YSSY-KLAX, KLAX-ZSPD

 

Edited May 27, 20188 yr by Wise87

Yeah, it hs potential, but at the moment it is far from a "good" product.

Nevertheless I like it 🙂 The AP problems bug me the most. Just starting my next flight now, only doing a small hop.

 

Are you guys using the feature which takes you to a certain waypoint?

29 minutes ago, swiesma said:

Yeah, it hs potential, but at the moment it is far from a "good" product.

Nevertheless I like it 🙂 The AP problems bug me the most. Just starting my next flight now, only doing a small hop.

 

Are you guys using the feature which takes you to a certain waypoint?

What issues is that? 

So far, I haven't run into any...
Have completed a couple of flights so far, and the plane is behaving as expected.

11 hours ago, SKEWR said:

 I did not like the performance hit you get with HDR on (havent tried the "reduce memory" HDR setting on the QWdispatcher).

First I've heard of this issue. As someone who always uses HDR this, for me, is very concerning. I'm wondering what the performance difference is between having it on vs off? 

4 hours ago, F_riedrich said:

Quote from the manual: "In all cases, the new climb altitude must be selected in the MCP altitude window before VNAV commands the climb". 

Does this mean, that i have to manually change the altitude everytime a step climb is due? If yes, couldn´t i just enter 43000 (AP) before takeoff and the FMC then would automatically climb as high the OPT allowed it to?

 

Edit: the reason i´m asking is that i don´t have to be at the computer all the time when flying long haul (>6h)

OK, I just tested it. Either the manual is wrong or it´s a bug. I didn´t have to change anything - it does everything automatically even on the MCP.

50 minutes ago, Anders Bermann said:

What issues is that? 

So far, I haven't run into any...
Have completed a couple of flights so far, and the plane is behaving as expected.

I explained it some posts before.

On the first flight I Ran into the VNAV bug. On the second one the AP went completely crazy and did not react to any inputs except for speed / lvl change. No heading, no LNAV, no VNAV... everything gone.

4 hours ago, F_riedrich said:

Quote from the manual: "In all cases, the new climb altitude must be selected in the MCP altitude window before VNAV commands the climb". 

Does this mean, that i have to manually change the altitude everytime a step climb is due? If yes, couldn´t i just enter 43000 (AP) before takeoff and the FMC then would automatically climb as high the OPT allowed it to?

If you follow the 2 steps to setup auto step climb, you will not need to manually change the MCP ALT. Start with your initial cruise altitude, and when the time comes to step climb, the aircraft will do it all for you.

-Tony@PVD

53 minutes ago, swiesma said:

I explained it some posts before.

On the first flight I Ran into the VNAV bug. On the second one the AP went completely crazy and did not react to any inputs except for speed / lvl change. No heading, no LNAV, no VNAV... everything gone.

Hmm weird...

So far, I've only found one weird thing - and I'm not sure it's a bug or error...

If I press CTRL + SHIFT + A (which I use in Outside cam to maneuver during walk-around), it re-loads everything and I'm suddenly in the middle of nowhere. I can't find an explanation, but when I go into Go to Airport, every filter is cleared. There's no shortcut keys mapped to that specific combination in Controls and it's only in the QW 787 it happens...

2 hours ago, swiesma said:

On the second one the AP went completely crazy and did not react to any inputs except for speed / lvl change

I found that if you have the FMC set to type in an entry, it is impossible to change the legs or anything.  If you click the bar to remove the ability to type in an entry into the FMC, you can edit everywhere.

Tried to replicate but cannot. 

Tried now a flight without beaming forward to a certain waypoint and now the AP worked good. 🙂

Edited May 27, 20188 yr by swiesma

After crashes, BSOD`s and awful LNAV/VNAV performance, I have asked for a refund. Will go ahead and buy the F-18 for DCS, which is at least honestly labeled as early-access (something that QW should also do).

4 minutes ago, GCBraun said:

After crashes, BSOD`s and awful LNAV/VNAV performance, I have asked for a refund. Will go ahead and buy the F-18 for DCS, which is at least honestly labeled as early-access (something that QW should also do).

Gimme a break - 4 flights so far with no problems, maybe it's your VR usage that creates the problems.

Today, do a flight with 787 from Kbfi - Seatle to Panc Anchorage. 

Departure folowing the steps climbs method, on cruise level...make rapidly a jump... to the descend waypoint with the QW feature (fantastic to have). Was a little suspiciou, but the descend and approach worked perfectly. 

Sure, I like this new style of cockpit, this plane make his official incoming in mine hangar.

Pehaps someone's problems are the editing of a good pln. Or a big part for a good descent and approach is to control the speed or the drags... to help a perfect altitude level in Vnav...