4 hours ago, jon b said:

Yes, you obviously have speed pitch and yaw info presented onto your view of the runway, it’s not being used for guidance. Although it can be used in LVO for a “HUD take off” which uses the localiser to give centreline tracking guidance.

After rotation you initially pitch the aircraft symbol up to the “TOGA reference line” (around 12 degrees) that I mentioned in the HUD while waiting for the guidance cue symbol to become active and usable.
It’s basically the same technique as you’d employ with a proper aircraft like the 747 where you aim for an initial pitch attitude (15 degrees) and hold until the flight director becomes usable at around 100-200ft (later software upgrades allowed the FD to be used almost straight after lift off on the 747))

So, without the takeoff reference line on the QW 787 HUD the proper takeoff technique isn’t available, of course you can still fly the real 787 with an unserviceable HUD and use the PFD for rotation so I’m not saying the QW is unusable but the TOGA reference line in the HUD really should be included.

Would you say it is good enough to accurately simulate a long-haul flight (obviously without non-normals), Jon?  Actually, now I remember your reply a while back referring to Curate's egg when I asked a similar question as I type this!

I know you're a 787 driver - same as another guy around here.  I've always held off on the basis the PMDG 747 was probably more enjoyable to use, and I already have that.  Plus the 747 is probably cooler being a bit more old-school and having four donks and all that.

Edited July 6, 20223 yr by VHOJT

41 minutes ago, VHOJT said:

I remember your reply a while back referring to Curate's egg

Yes, that phrase amuses me for some reason.

41 minutes ago, VHOJT said:

Plus the 747 is probably cooler being a bit more old-school and having four donks and all that.

That’s certainly as true for the real aircraft as it is for their simulation counterparts. The QW version seems ok for normal operations , and I quite like it, I can’t say I’m a fan of the real world 787 though.

 

Edited July 6, 20223 yr by jon b

I have it and like it . Its just below PMDG in terms of depth. Its 2 month since i had a flight but will pick a trip or two again this month 

issues from top of my head is the dark cockpit,  stutter when using terrain radar and low FPS displays. 

Stability is very good.

Stable 12 hour+ flights.

 

Michael Moe

Edited July 6, 20223 yr by Michael Moe

On 7/6/2022 at 6:02 PM, Michael Moe said:

Stability is very good.

Stable 12 hour+ flights.

 

Michael Moe

same here regularly fly it on qantas ultra long haul flights.  no issues.

It is a nice addon but I always have the same problem and that is that the autopilot disconnects on its own. Two nights ago I wanted to do QFA8 KDFW-YSSY and after assigning a keyboard command to disconnect the joystick I left it at cruise for the night. Waking up the next morning I found that the LNAV command had disengaged itself and the aircraft was somewhere east of South America. It is a little frustrating.

1 hour ago, Samaritano said:

It is a nice addon but I always have the same problem and that is that the autopilot disconnects on its own. Two nights ago I wanted to do QFA8 KDFW-YSSY and after assigning a keyboard command to disconnect the joystick I left it at cruise for the night. Waking up the next morning I found that the LNAV command had disengaged itself and the aircraft was somewhere east of South America. It is a little frustrating.

Hmmm, I regularly do 10-12 hour hauls and have never seen that happen.  You've disconnected joysticks so it can't be an errant button press and if you're leaving it overnight I'm guessing no time acceleration.  

This happens on every flight?  What do you use for flight planning and loading the plan into the CDU?  No disco's in the flight plan in the CDU?  Do you have any keyboard assignments related to LNAV in P3D control settings?   

 

 

I have been plagued by this problem for a while now. I don't use time acceleration and it does happen in every flight (Autopilot disconnect part).

I use simbrief to create a flight plan and it is imported into the sim via the simbrief downloader in which I select via the Route request option in the FMC. I don't have a disco's when checking my FP. As for LNAV button assigment the problem happened for the first time on my last flight and it could be related to the Honeycomb QW787 throttle profile that I imported.

1 hour ago, Samaritano said:

I have been plagued by this problem for a while now. I don't use time acceleration and it does happen in every flight (Autopilot disconnect part).

I use simbrief to create a flight plan and it is imported into the sim via the simbrief downloader in which I select via the Route request option in the FMC. I don't have a disco's when checking my FP. As for LNAV button assigment the problem happened for the first time on my last flight and it could be related to the Honeycomb QW787 throttle profile that I imported.

OK, so putting LNAV aside for a second and back to the AP disco's.  So yesterday on the flight you set a keystroke to disable the joysticks the A/P stayed on but LNAV disconnected?  

If you go to your game controller settings within windows and go to each controller do any of the Axis/switches have any noise associated with them? Is there any movement without you touching them?  I'm wondering if there is a noise instance from the joystick which QW is interpreting as a commanded action and disco's the AP... Isn't there a setting for QW to ignore joysticks with A/P connected?  In my instance I had so much rudder noise I had to increase the deadzone until I could offset it.  

Not saying this is your issue but it's someplace to start.

Sorry if this is considered as a highjacking of the thread, but I have a question. I don't want to sound ungratefu to the producer but, is anybody aware of proper working Honeycombe profiles for the QW 787 yoke & throttles. The ones downloaded from the Aerosoft website don't seem to fuction hardly at all.

Best regards to all

After doing a clean install of windows 10 and fresh installation of the latest V5 of P3D I am still having the same autopilot disconnect problem. Honestly I did not check to see if it was the LNAV that had disconnected because I was frustrated and shut down the sim. I only have a few addons installed at this point and have no idea what can be causing this. FSLabs and PMDG don’t manifest this behavior.

For anyone having "disconnect" or strange flight characteristics (nose dives), I'd recommend you manually go thru every controller profile and delete all the button and axis mappings (for EVERY controller, no exceptions) and then manually re-assign axis/buttons to your devices.  Now go thru each USB device control calibration and set the Sensitivity to max 127 and the null zone to 1 for all assigned axis.   

Be sure to save the profile after completing the task (note the profile is saved for ALL connected devices).

Once nice aspect of P3D is that if a USB controller/device disconnects the sim just pauses for a second or two and does NOT CTD ... unlike MSFS that will CTD if you have any momentary disconnect from a USB device (a known bug that was fixed then returned in MSFS).

One other suggestion is to make sure all your USB devices are set to never go into power saving mode (sleep) mode, this can be handled via Device Manager.

I've not had any issues with the QW787 other than when it was using an older TrueGlass DLL (provides the weather effects on windshield area) ... an update solved that issue.

 

3 hours ago, Samaritano said:

After doing a clean install of windows 10 and fresh installation of the latest V5 of P3D I am still having the same autopilot disconnect problem. Honestly I did not check to see if it was the LNAV that had disconnected because I was frustrated and shut down the sim. I only have a few addons installed at this point and have no idea what can be causing this. FSLabs and PMDG don’t manifest this behavior.

As has been said. It is not the QW787 that is the problem. Somehow you have inadvertently set up control conflicts that is disconnecting the AP and LNAV. Maybe you have other add ons that have the same key/axis  assignment that is causing the issue. Try running just P3D and the QW787 on it's own to test.

@Samaritano It could also be a loose connection of the stick or throttle. I sometimes move them on the desk thus the connection slackens which leads to sudden outage of the controls. I needed some time to get aware of this.

Unfortunately nothing works. I went ahead and deleted every single axis assigment from each controller and then reaasign them. I went and start assinging my axis thru FSUIPC. That din't help either. There is no noise from any of the controllers. I did one flight from KLAS to KPHX and everything worked great. When I tried yesterday a flight from YSSY-KSFO the autopilot disconnected while LNAV and VNAV were still engaged.

While the autopilot was flying the airplane I deliberately moved the controllers and the autopilot stayed connected.

At this point I have no idea what else can I try. I even left the WX radar off just to ruled out that possiblility. Now I am going to try flying without Active Sky and see what happens.

 

https://gamepad-tester.com/

 

On 12/12/2022 at 7:35 PM, Samaritano said:

Unfortunately nothing works. I went ahead and deleted every single axis assigment from each controller and then reaasign them.

You need to including removing unused button assignments also, not just axis.

Here is a free and very handy tool (online) for checking control buttons/axis: https://gamepad-tester.com/

Suggest you leave the website active and monitor values while you fly and see if you notice any odd controller activity that my trigger a AP disconnect.

Good idea to check turbulence settings in ActiveSky.