On 3/30/2019 at 6:50 AM, dray007 said:

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.

yes normal for your pc specs

The first time I bought it, I asked for a refund and returned it.

With the update, I've decided to re-purchase it and give it another shot. And I have zero regrets, I am absolutely loving it.

I feel like I can now really trust FMC and autopilot to do what it's supposed to be doing. The VNAV is more reliable, the speedbrakes work as expected, FPS performance is improved on my system, stability not an issue anymore. There are still a few issues (why do engines not always go to idle when i'm above the vnav path? My engines once shut down mid-flight due to some super-bizarre bug that apparently happens when a Carenado model is loaded on vatsim?), but all things considered it's become a rather fantastic product. The attention to detail is lovely and the developers appear to be making an effort to keep improving it while engaging with the customers.

Edited April 3, 20197 yr by flycln

In testing the new version, I agree. I did have one problem of the plane not properly descending on VNAV. It throttled back but maintained altitude while reducing speed.

Happened late in the descent when I was cleared from above 10,000 to below it. I idly wondered if maybe the plane was trying to slow below 250kts, not realizing that it was already below 250kts.

 

Also on the engine shutdown thing, I had that happen once too, in the previous version, on landing. Deployed reversers and both engines shut off. I don't use VATSIM, so it definitely wasn't that. I even posted a half-joking question to their forums asking if they really simulated that, since it happened shortly after a real 787 experienced a dual engine shutdown immediately upon deploying reversers.

 

Ive done several flights since the update and my biggest quirk is the VNAV descent at 70% N1. The descent profile is to shallow. Panel state is only partial. PFD/MFD brightness has to be adjusted in QW config, master brightness knob does nothing, at least during the day. Autopilot is smooth though.

Regarding a lot of people talking about VNAV descent.

Pretty sure the 787 vnav descent is an off-idle descent by design. They found that keeping the engines above idle during the descent meant you could adjust throttle to maintain the descent profile without having to use speedbrakes, which ends up being more efficient overall.

In saying that, it's still not perfect, and sometimes doesn't want to slow down for speed restrictions.

Edited April 3, 20197 yr by itsjase

My experience with the plane so far has revealed that the following items are not saved....

• panel definition lighting
• TCAS
• Flaps
• Terrain on ND
• Airports/Data etc. on ND

 

Edited April 3, 20197 yr by Christopher Low

11 minutes ago, Christopher Low said:

My experience with the plane so far has revealed that the following items are not saved....

• panel definition lighting
• TCAS
• Flaps
• Terrain on ND
• Airports/Data etc. on ND

 

What do you mean by "not saved"? Not saved after you reloaded the flight?

I always set up my next short flight after I have completed the last one, and then save it for my next flight session. When I load that saved scenario, those items mentioned above have not been saved.

EDIT: On a side note.....either the thrust reversers are not working properly on my PC, or they are not very effective (when compared to my PMDG aircraft)

Edited April 3, 20197 yr by Christopher Low

What are the panel states you can set as the startup state?

Not sure. I have based my comments on the default panel state function.

9 hours ago, Nyxx said:

What are the panel states you can set as the startup state?

Any panel you save can be set as default in the cfg file I believe.

9 hours ago, Nyxx said:

What are the panel states you can set as the startup state?

For some reason I have lost my confidence in creating custom default panel state since update 1.1. It made my aircraft buggy in subsequent updates. Now I just switch to predefined cold and dark setup just like in pmdg 777. And it's very easy to power and configure from cold and dark.

Having bought this tonight and set up chaseplane not done a flight I was disappointed in the FPS compared to PMDG its even lower that FSL. I did set up hi res for displays but .....

Edited April 4, 20197 yr by Nyxx

1 hour ago, Nyxx said:

Having bought this tonight and set up chaseplane not done a flight I was disappointed in the FPS compared to PMDG its even lower that FSL. I did set up hi res for displays but .....

Turn off the hires displays, they literally halve your fps.

 

8 hours ago, Nyxx said:

Having bought this tonight and set up chaseplane not done a flight I was disappointed in the FPS compared to PMDG its even lower that FSL. I did set up hi res for displays but .....

Its hard on the GPU, I run 4k and Hires with weather radar on no ctd.

disabled SLI the fps dropped , tested with one single 1070 QW787 sim was unflyable with my settings.

Then on the cpu/mem side its very hard in some conditions on the mems, figuerd that when helping a friend to get his pc stable.

he get sudden CTD or that P3D closing, swap his mems to one of my kits no problems then i tested his mems with xmp on my stable pc same type of ctd.

get his mems stable 200mz lower frq then xmp with same timings, the strange ting is that his mems had no errors in memtest with xmp and no ctd in P3d with PMDG and other airplanes.

Like this bird, but it can be harder on the system in some rare conditions both gpu and cpu/mem then for example FSL A320 and PMDG.