Jump to content

Sign in to follow this  
Arthur42417

Ultimate 787 Update - Version 1.1.3 Released

Recommended Posts

After watching Matt Davies' video seems there's only 1 real vnav/flch issue on descent where the engines randomly spool up to full power. Take a look at 51:50.

 

Share this post


Link to post
8 hours ago, itsjase said:

After watching Matt Davies' video seems there's only 1 real vnav/flch issue on descent where the engines randomly spool up to full power. Take a look at 51:50.

Hello. What distance did He need to descent from FL410 and did the engine was on idlle when descending ?

Edited by musiol1

Boeing777_Banner_Pilot.jpg

Share this post


Link to post

That is so odd, in my humble opinion... judging by the fact the command sector on the EICAS well exceeded the max N1 ref position it's entirely possible that there may have been a stuck joystick axis input or interference of some kind with the USB axis' which can get easily bungled in Windows when you have lots of peripherals connected. When the A/T is in control on ours and on the real thing it will not, and should not command a throttle position beyond that of the N1 ref. Based on passed experience, it leads me to believe it was likely noise from the joystick axis due to a configuration conflict. Because when he switched to FLCH the FMA commanded HOLD during which should have idled the engines and pitched for the MCP window speed.  We never ever encountered that type of FLCH anomaly in our very thorough testing of this update. In my judgment it looks like a controller conflict, which admittingly the gauge and FSUIPC should have ignored the axis when the A/T is on, but since the A/T was in a passive mode like FLCH idle it may have left it more vulnerable to a conflicting full throttle joystick axis position and it's likely what caused the issue.

We'll certainty take a look things going in that area to tidy up any possible controller induced interference of the A/Ts function. Thanks for posting that.

But it remains to be said he was far too fast for the stage of the approach he was on, I noted 260kts. Not only 10kts over the limit for an arrival but 20kts over the SOP default VNAV speed in the descent under 10K. At such a late stage in the approach it was well beyond the point of bleeding off speed with pitch given how close the airplane was to intersecting the extended centerline and IAF. The airplane does need speedbrake intervention under 10K when clean in certain weight configs and can be quite a slippery airplane. If you transition properly at 10K VNAV A/T will have you at 238-246ish at idle or just above it with the target speed being 240 until the constraints of the STAR further specify speed step downs or the approach fix speeds themselves and eventually the manual IAS is controlled when in a vertical approach mode like G/S or G/P. Approach planning, judgement and speed management is key. And since we don't yet model the very complex dotted speed/flap step down point marker algorithm, which dynamically displays and adjusts along the magenta track roughly between a few NM prior to the IAF and the FAF at the present time, pre configuring 10kts IAS step downs in the CDU between the IAF and the last fix of the STAR for VNAV is recommended or to do so manually via VNAV SPD intervene mode as appropriate on approach.

Besides the real thing needs intervention from the crew all the time to keep the automation honest and be one or two steps ahead of it. It's never 100% bang on perfect in the real world either. And while our A/P is still being enhanced, the A/P and airplane is only as good as the knowledge of the person operating it on which modes to be in when and how to use them correctly.

Edited by American 833 Heavy
  • Like 2
  • Upvote 1

qwsig_Emil02-1.gif

Share this post


Link to post

Thanks for your detailed response!

I've also made a post in the support forum about it. I noticed the issue was usually after the first speed restraint on a STAR. It would be descending on vnav at 240 approaching a 190 restriction, the magenta line would move down to 190 and it would ask for more drag, so I'd extend the speedbrakes, but then the throttles would increase to like 50-60 N1, even though it's above profile and the drag required FMC message is still there.

I'm assuming there's no reason throttles should be above idle if the plane is above the profile on speed/height, especially if the drag message is showing. I can provide more details on the exact approach if that would help?

For now I've started using speed intervention and lowering it manually to 190 on the MCP, but it seems to have the same problem. I think it might be related to turns? If I'm at 240 slowing to 200 the throttles will be idle, but if i start a turn while still at 230, throttles will increase and it won't slow down to 200. They only reduce again after the turn has finished. Not sure if this is intended.

Edited by itsjase
  • Like 1

Share this post


Link to post

It's as slippery as butter! Even taxiing requres using brakes often to not shoot dat 30 GS limit. Just finished ANA218 a few minutes ago, vid coming soon. No problems, just forgot to activate the "5" callout, but will be set for next time. Everything went fine as expected, just like the bad fps that come out of my potato... I needed to use V/S mode in the end, but that was a minor issue. Also under bad fps if you try to autoland it still swings from side to side quite dangerously. Other than that aesthetics look beefier now.


signature-dark.png

My system specs: Core 2 quad Q9650 @ 3.51ghz, GTX1060 6gb, 8gb ddr3 1333, 1Tb seagate barracuda, 500gb wd blue

Share this post


Link to post

nvm

Edited by Nyxx

David Murden.  P3D v5  FSL A321 / A320 / A319 : PMDG NGu / 748iF PMDG NG / 747-/ 777 : QW 787 :  Maddog MD-80 :Q400 :

DCS: A10C Warthog : AV-8B Harrier :  F-14B Tomcat  : F-16C Viper F/A-18C Hornet 

My FSL Walkthrough PDF From GPU to Parked.      My PMDG NGXu Light Mod      My PMDG NG SpotLight Profile/Mod.  

PC 4790k@4.6 : 1070 : 16GB DDR3 RAM : Thrustmaster Warthog HOTAS: Thrustmaster TPR.

Share this post


Link to post

I got low fps and its like fluctuating from 30 to 20 . is it normal? im only use chaseplane. btw my cpu is i7-4750hq 3.0ghz with GTX980m 4gb.


Dray Langley

Share this post


Link to post

Hi

I am having a hard time performing full autoland using 787-9 after the update. In less than 6nm with calm head winds using Asp4 weather my plane starts to oscillate by banking left and right. It gets really bad at 500 ft above ground then I have to disable autopilot. 

Is anyone else experiencing this. I have experienced this flying into Heathrow then again into singapore. 

My fps count remains between 20 to 25 and I am using AIG with traffic set to 50%.

I also used activesky to insert wind data

Edited by biloo

Bilal Asif Khan

Share this post


Link to post
11 hours ago, American 833 Heavy said:

But it remains to be said he was far too fast for the stage of the approach he was on, I noted 260kts. Not only 10kts over the limit for an arrival but 20kts over the SOP default VNAV speed in the descent under 10K. At such a late stage in the approach it was well beyond the point of bleeding off speed with pitch given how close the airplane was to intersecting the extended centerline and IAF. The airplane does need speedbrake intervention under 10K when clean in certain weight configs and can be quite a slippery airplane. If you transition properly at 10K VNAV A/T will have you at 238-246ish at idle or just above it with the target speed being 240 until the constraints of the STAR further specify speed step downs or the approach fix speeds themselves and eventually the manual IAS is controlled when in a vertical approach mode like G/S or G/P. Approach planning, judgement and speed management is key

I have to agree with you here.  I not exactly sure why he would choose FLC to slow down and engage the mode just 200ft above the selected altitude. I think speedbrakes would have been a better option.


Jose Albino

AMD Ryzen5 3600 @ 4.2Ghz - G.Skill Ripjaws V 16 GB DDR4 3600  - Gigabyte Aorus Elite X-570 WiFi - Asus ROG Strix GTX1060 6gb - WD Black SN750 NVMe 500gb - AData sx8200 Pro NVMe 1TB

 

WIN10 - P3D v.4.5, X-PLANE 11

 

Share this post


Link to post
On 3/27/2019 at 6:33 PM, Christopher Low said:

... I am rather impressed. It handled the flight just as well as any of my PMDG aircraft (including allowing me to have VNAV and SPD mode active at the same time).

The 3D model, VC and sounds are all excellent. The plane seems to handle just fine when on the ground, and is nice and smooth through turns when following the magenta line.

In short, I felt that I was in control of this aircraft throughout the flight. It did what I expected it to do, and it did it with some style :cool:

 

I very much agree.
This aircraft is a joy to fly now, after the update.
Nice job QW!


Best regards,
David Roch
Intel 9900K@5.1, Asus Maximus XI Formula, 32Gb G.Skill TridentZ 4133 CL17, EVGA RTX 2080 Ti XC ULTRA GAMING, 3x SSD Samsung 970 Pro M.2, Corsair 1600W PSU & 49" Samsung curved 4K TV monitor@30Hz.
MSFS Alpha tester

Share this post


Link to post

I also agree.

In the last few months I have purchased two aircraft which for me represent the best values (best bang for my buck) in the last 2 years. One is the Diamond DA62 the other the QW787.

The QW787 features including 'jump ahead', EFB, facsimile charts for major airports and sufficient fidelity to make it feel realistic enough represents a major undertaking and accomplishment. I have completed 3 long flights that were flawless from departure to auto land.  During two the  arrival changed, which required me to clean up the route and manually re-enter the arrival and approach, which I believe is what pilots do:). 

My P3dv is extremely stable and I attribute that to a few decisions I made when I built this one. I decided NOT to over clock, no second party shaders (read RR opine on that subject) and not screw with the P3d config settings. All my settings are accomplished via the P3d settngs except one (wideview). 

Bob

  • Like 1
  • Upvote 3

Bob Prince

Share this post


Link to post

How do I import the AS16 winds?

I request the Winds and get a message to load them in the RTE DATA page?! Where is this?!


Stefan Wiesmayer

My second hobby: BMW F87 M2 LCI

Core i7 6700K | Asus Z170-A | beQuiet! Power Zone 850w | Arctic Liquid Freezer 240 | Asus PA328Q 4K IPS | Asus Strix1080 ti | 32 GB DDR4 G.SKill 3200 | Samsung SM951 M.2 SSD | Beyerdynamic DT 990 Edition

Share this post


Link to post
7 hours ago, swiesma said:

How do I import the AS16 winds?

I request the Winds and get a message to load them in the RTE DATA page?! Where is this?!

On the Legs page, bottom right.

Share this post


Link to post

You do have to have some perf data input such as flight level for the winds to show up in the legs page.

Share this post


Link to post

Did anyone else have installation issues with this version? Mine is getting stuck at about 14% and moving or doing anything after that. I have disabled anti-virus. Anyone have any suggestions?

 

Edit..after 45 minutes the installer finally finished..all is working now.

Edited by Bigt

Share this post


Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  
  • Tom Allensworth,
    Founder of AVSIM Online


  • Flight Simulation's Premier Resource!

    AVSIM is a free service to the flight simulation community. AVSIM is staffed completely by volunteers and all funds donated to AVSIM go directly back to supporting the community. Your donation here helps to pay our bandwidth costs, emergency funding, and other general costs that crop up from time to time. Thank you for your support!

    Click here for more information and to see all donations year to date.
  • Donation Goals

    AVSIM's 2020 Fundraising Goal

    Donate to our annual general fundraising goal. This donation keeps our doors open and providing you service 24 x 7 x 365. Your donation here helps to pay our bandwidth costs, emergency funding, and other general costs that crop up from time to time. We reset this goal every new year for the following year's goal.


    22%
    $5,540.00 of $25,000.00 Donate Now
×
×
  • Create New...