Mickey4673

Managed Speed lost during flight

Recommended Posts

For those reporting this issue... when you post, would you please indicate which version of the Airbus you are using?  We need that info along with any report.  We really can't look at any reports without this information given that so many people are not using the latest Experimental Update and still reporting the issue.

 

Many thanks!

 

Share this post


Link to post
Share on other sites
2 hours ago, DaveCT2003 said:

So that you guys are aware... I just completed 7, two hour-ish flights without any managed speed issues.

 

 

 

 

Dave, suggest you try this flight plan KCLTTAPA01.  It was created at www.SimBrief.com.  This is the plan I was flying yesterday in v1.2.2.0 when the managed speed dropped out in CLB and CRZ.  All of my failed flights have been with SimBrief created flight plans.  I also load the A319 in TAKE-OFF state in P3Dv4.4.

 

I'm planning another long flight tomorrow, KCLT-TNCA but I'm going to input the flight plan manually and see what happens re managed speed.

 

Harold

 

KCLTTAPA01.flp

Aerosoft configurator v1220 181214.JPG

Share this post


Link to post
Share on other sites
3 hours ago, DaveCT2003 said:

So that you guys are aware... I just completed 7, two hour-ish flights without any managed speed issues.

 

 

 

 

Try SAN-PHX (HYDRR arrival). I always load the route manually.

Share this post


Link to post
Share on other sites
1 hour ago, haroldeh said:

Dave, suggest you try this flight plan KCLTTAPA01.  It was created at www.SimBrief.com.  This is the plan I was flying yesterday in v1.2.2.0 when the managed speed dropped out in CLB and CRZ.  All of my failed flights have been with SimBrief created flight plans.  I also load the A319 in TAKE-OFF state in P3Dv4.4.

 

I'm planning another long flight tomorrow, KCLT-TNCA but I'm going to input the flight plan manually and see what happens re managed speed.

 

Harold

 

Hey Harold!

 

Sorry you're struggling with this issue.  I've tested most every route reported and I just don't experience this issue.  Just one of our guys has, so this has proven to be somewhat elusive for us all.

 

If I get a chance to schedule it in, I'll try to fly the route you suggested, but I honestly don't think this is a route issue.

 

Best wishes!

 

Share this post


Link to post
Share on other sites

Hi All,

 

The managed speed problem cleared after I reinstalled Windows, P3D and Airbus Pro, but i came back after I updated to version: 1.2.2.0 using the Aerosoft updater.

 

CRZ phase, managed speed in PFD dropped back to 206kt.  Could it be related to a high tailwind factor?

206knots.thumb.jpg.01f68837ab8e7fc5131bd25765cf8539.jpg

Had to go back to selected speed to avoid stall.

Pushed speed knob to see what would happen and managed speed dropped back to 117kt.

FMC perf page:

perf.thumb.jpg.0c6363a9643150193e73e79cce50a17a.jpg

AC status:

status.thumb.jpg.8da5e6169469f33b9a2a463799a8bfbe.jpg

PROG:

prog.thumb.jpg.45616ea839aab4c2aa66a10008b0c4f4.jpg

PFD in selected speed:

1854176372_speedselected.thumb.jpg.f9e5eaae6e42da46d3cc438c9a865de9.jpg

PFD in managed speed:

speedmanaged.thumb.jpg.afea8ad97568ac21050916c5c4abc599.jpg

DES:

des.thumb.jpg.239e6541f8bd3894272af1c1fdb23a69.jpg

Seems like the updater is introducing this issue and a reinstall is needed to clear it.

 

Thanks.

 

 

 

 

 

 

 

Share this post


Link to post
Share on other sites
2 hours ago, djspatrick said:

Hi All,

 

The managed speed problem cleared after I reinstalled Windows, P3D and Airbus Pro, but i came back after I updated to version: 1.2.2.0 using the Aerosoft updater.

 

CRZ phase, managed speed in PFD dropped back to 206kt.  Could it be related to a high tailwind factor?

 

Seems like the updater is introducing this issue and a reinstall is needed to clear it.

 

Thanks.

 

 

 

 

 

 

 

 

I agree with djspatrick .  I can re-install the release version 1.2.1.0 and I do not have the managed speed problem.  At one time I was flying experimental version 1.2.1.3 and did not have the problem.  I missed the v1.2.1.4 release but caught that when I updated to v1.2.1.5, so I'm not sure which release introduced the problem 1.2.1.4 or 1.2.1.5.  As I discuss above, I have uninstalled, re-installed 1,2,0.0 and applied the experimental 1.2.2.0 via the updater.  I still have the problem.

 

Re his comment on high tailwind, I have flown my flights with Active Sky wx for P3Dv4 and almost (if not every) flight I encounter winds at altitude (generally FL350-360) in excess of 100kts.

 

I'm preparing to start another flight.  This flight, in addition to manually entering flight plan, I will also use the "Clear Skies" wx theme from P3Dv4.  Will report results.

 

UPDATE on flight with P3Dv4 Clear Skies wx theme and manually loaded flight plan.  Didn't even make it to 10,000 ft in CLB before managed speed tanked!

 

Obviously as has been acknowledged, there is an issue still affecting some users.  I suspect we are all willing to test whatever to try and resolve this aggravating issue.

 

One thing that works for me to re-establish managed speed is to change the destination runway.  This often recalculates and established the correct managed speed.  If I was just to look at my FMC Perf pages to see when managed speed drops, the best page in DES.  Sometimes when the drop occurs in CRS, the CRZ page managed speed looks correct, but the DES page shows the drop to say, 204 kts.

Share this post


Link to post
Share on other sites

Thought I'd throw my hat in the ring on this as well. I'm running the latest version of everything and I've lost managed speed on all flights.

 

This is all done in the A320 IAE for me. Sometimes it happens in the climb, other times in cruise. Right now doing a trip from KBOS-KRDU (KBOS SSOXS5 SSOXS DCT BUZRD DCT SEY DCT HTO J174 SWL KAROO2 KRDU).

 

Flight plan is manually entered. Right now I have a headwind in excess of 100 knots, yesterday I had a tailwind in excess of 100 knots. That doesn't seem to matter - managed speed tanks regardless. 

 

When it drops during the climb, it looks like it's trying to achieve a speed constraint in the STAR for whatever airport I'm flying to (something around 206-220 knots), but when it drops during cruise it's usually some insane number like 105 knots. I see no correlation to any other speed listed in the FMC. At least if I could follow the logic of the speed it's trying to fly, maybe that would point to the problem. But the drop in cruise to something like 105 knots really throws me off that trail.  

Share this post


Link to post
Share on other sites

Same issue here. Just updated to 1.2.2.0 yesterday and did a short flight KLAX-KSFO as a test. In cruise at FL320 the throttles went to idle and the speed dropped to where the airplane would have stalled without manual intervention.

 

I never had this particular issue before 1.2.2.0.

 

I'm using P3D 4.3.

 

Descent VNAV is still a joke, leaving the airplane in full managed mode still results in blowing almost every speed/alt restriction and ending up way too high and fast at the IAF.

 

Maybe a real-life Airbus pilot can confirm this, but it seems to me that the autothrottle does not reduce power enough in the descent. Even with spoilers deployed the vertical profile is impossible in managed mode.

Share this post


Link to post
Share on other sites

Further to the above: During managed descent from cruise, the system descends at 1000fpm whereas 2000 would be more realistic. Maybe this is an underlying cause of the VNAV issues? Is there a way to configure the default descent rate, either in the sim or buried deep in some config file?

Share this post


Link to post
Share on other sites
4 hours ago, aviator64 said:

Further to the above: During managed descent from cruise, the system descends at 1000fpm whereas 2000 would be more realistic. Maybe this is an underlying cause of the VNAV issues? Is there a way to configure the default descent rate, either in the sim or buried deep in some config file?

 

I've re-read this thread completely several times and I just don't suffer for any of the problems (not a one) mentioned here, and I likely have 10 times or better the number of flights in numerous versions than our customers do.  Very frustrating for everyone concerned!

 

I hope it isn't true, and I'm moving forward as if it isn't, but somewhere in the dark recesses of my mind a thought it forming that this my boil down to what is taking place on individual systems - which is about 400 times more difficult for us to help figure out than anyone might imagine.

 

 

Share this post


Link to post
Share on other sites
2 hours ago, DaveCT2003 said:

 

I've re-read this thread completely several times and I just don't suffer for any of the problems (not a one) mentioned here, and I likely have 10 times or better the number of flights in numerous versions than our customers do.  Very frustrating for everyone concerned!

 

I hope it isn't true, and I'm moving forward as if it isn't, but somewhere in the dark recesses of my mind a thought it forming that this my boil down to what is taking place on individual systems - which is about 400 times more difficult for us to help figure out than anyone might imagine.

 

 

To clarify it a bit more - on initial descent from cruise, I'm getting that 1000fpm descent. When the airplane is a few miles from the next waypoint, it's like the system has an "oh crap" moment, realizes it won't make the speed/alt restriction, and suddenly starts descending around 2400fpm. Of course it's too little too late. I always end up having to use spoilers, which in normal real-life operations would not be necessary unless ATC caused a delay in descending.

 

On my last flight I tried starting my descent ~15 miles before the FMS's computed TOD point. It came a lot closer to hitting the altitude at the next waypoint, but then lost it again on the next segment.

 

This suggests to me a glitch in the VNAV program logic.

 

My test flight was KLAX DARRK2.STOKD SERFR3 KSFO, ILS RWY 28R with EDDYY IAF.

 

I was using the "Clear Skies" setting (all weather turned off).

 

I have a very clean Win 10 install; I use that system only for games with no windows security or user account control enabled. All apps are run as admin, even though that shouldn't matter with UAC disabled.

 

I'm happy to help diagnose; I'm a computer geek and programmer as well as real-life pilot.

Share this post


Link to post
Share on other sites
1 minute ago, aviator64 said:

To clarify it a bit more - on initial descent from cruise, I'm getting that 1000fpm descent. When the airplane is a few miles from the next waypoint, it's like the system has an "oh crap" moment, realizes it won't make the speed/alt restriction, and suddenly starts descending around 2400fpm. Of course it's too little too late. I always end up having to use spoilers, which in normal real-life operations would not be necessary unless ATC caused a delay in descending.

 

On my last flight I tried starting my descent ~15 miles before the FMS's computed TOD point. It came a lot closer to hitting the altitude at the next waypoint, but then lost it again on the next segment.

 

This suggests to me a glitch in the VNAV program logic.

 

My test flight was KLAX DARRK2.STOKD SERFR3 KSFO, ILS RWY 28R with EDDYY IAF.

 

I was using the "Clear Skies" setting (all weather turned off).

 

I have a very clean Win 10 install; I use that system only for games with no windows security or user account control enabled. All apps are run as admin, even though that shouldn't matter with UAC disabled.

 

I'm happy to help diagnose; I'm a computer geek and programmer as well as real-life pilot.

 

I've flown most every route that someone had a engine problem with, and I've never encounterd an issue.  At this point I just can't believe it's a route issue.

 

The updater theory has some merit, I will discuss this with the dev for that.

 

What I'm wondering is this....

 

For everyone who is having this issue, please report if you're using AI Traffic (whether generated by P3D, VATSIM, IVAO or by other means.  Also, please report if you have or don't have any Carenado aircraft installed.  Their is a DRM problem with Carenado software that will kill the engines of non-Carendo aircraft if the model is called by an AI aircraft.

 

For those interested in helping rule this out.... please do the same flights without any AI/Online traffic and see if you still see the problem.

 

 

.

 

 

 

 

Share this post


Link to post
Share on other sites

My test flights are always done with all AI traffic turned off. I do have Carenado aircraft installed but whenever I complete a flight with ANY third-party airplane I always exit completely out of P3D and restart with a clean default startup flight (in my case, the P3D stock Baron in a cold and dark state), position at the departure airport and then load the third-party airplane.

 

On my test flights today I did not get the sudden power chop and slowdown issue, just the managed descent problem mentioned above.

 

Still seeing excessive bank angles during small course changes, but that is another topic. The managed descent is the really critical issue, for me anyway.

 

 

Share this post


Link to post
Share on other sites
57 minutes ago, DaveCT2003 said:

 

I've flown most every route that someone had a engine problem with, and I've never encounterd an issue.  At this point I just can't believe it's a route issue.

 

The updater theory has some merit, I will discuss this with the dev for that.

 

What I'm wondering is this....

 

For everyone who is having this issue, please report if you're using AI Traffic (whether generated by P3D, VATSIM, IVAO or by other means.  Also, please report if you have or don't have any Carenado aircraft installed.  Their is a DRM problem with Carenado software that will kill the engines of non-Carendo aircraft if the model is called by an AI aircraft.

 

For those interested in helping rule this out.... please do the same flights without any AI/Online traffic and see if you still see the problem.

 

 

.

 

 

 

 

RE the Carenado DRM problem.  I do have Carenado a/c and I encountered this very issue when I first got the MadDog.  Would be flying along dumb and happy and WHAM!  Both engines shut completely off.  Finally tracked it down to using vPilot to fly online in Vatsim.  vPilot had done some mapping of my Carendo models. 

 

Once I understood the problem, the resolution was simple - exclude the Carenado/Alabeo models from mapping.  No problem ever since.  The problem lies with Carenado DRM and not vPilot software.

 

The A319 does not exhibit the same problem - i.e. the engines completely shutting down.  The managed speed just gets reset. 

 

Since the managed speed issue is happening to me every flight, I will fly an offline flight tomorrow without vPilot.  I do not have any "traffic" programs running.

 

Harold

Share this post


Link to post
Share on other sites
2 minutes ago, haroldeh said:

RE the Carenado DRM problem.  I do have Carenado a/c and I encountered this very issue when I first got the MadDog.  Would be flying along dumb and happy and WHAM!  Both engines shut completely off.  Finally tracked it down to using vPilot to fly online in Vatsim.  vPilot had done some mapping of my Carendo models. 

 

Once I understood the problem, the resolution was simple - exclude the Carenado/Alabeo models from mapping.  No problem ever since.  The problem lies with Carenado DRM and not vPilot software.

 

The A319 does not exhibit the same problem - i.e. the engines completely shutting down.  The managed speed just gets reset. 

 

Since the managed speed issue is happening to me every flight, I will fly an offline flight tomorrow without vPilot.  I do not have any "traffic" programs running.

 

Harold

 

 

Okay, thanks Harold, that pretty much confirms that isn't the problem, at least for those not as experienced with this as you are.  I remember you from the Maddog thread!

 

Thanks for the info!

 

 

Share this post


Link to post
Share on other sites
I also have the problem that suddenly the speed decreases during the flight.
Did yesterday 3 flights with the a321 made.
EDDP - LOWS FL 190 - flight without problem
EDDS - LEMD FL 360 - Speed lost
LEMD - GCRR FL 380 - Sped lost

Unfortunately, my english is not so good for the error description.
Unfortunately, you can not leave the cockpit until the TO because otherwise the plane crashes.
Actually only fly boeing but for quite some time also airbus.
I have no idea how to fix this error in flight.
I turn off the autopilot, move the throttle and turn AT on and off. Then I get everything under control again.
But that is not a solution.
That was not before the update to version 1.2.0.0
 
I fly with UT Live, Aktiv Sky, P3DV44,
I have no Corenado AIrplanes
 
Frank
 

Share this post


Link to post
Share on other sites
11 hours ago, haroldeh said:

Once I understood the problem, the resolution was simple - exclude the Carenado/Alabeo models from mapping

 

How does one exclude specific aircraft from being used as AI in P3D?

Share this post


Link to post
Share on other sites
4 hours ago, aviator64 said:

 

How does one exclude specific aircraft from being used as AI in P3D?

 

That is going to be add-on specific.  I was talking about vPilot.  See the attached image on how to do it in vPilot.

vPilot excluding model matching.JPG

Share this post


Link to post
Share on other sites
4 hours ago, djspatrick said:

Just noticed that my rogue CRZ managed speed was the same as the Descent target speed:  206kt.

Relevant?

 

 

Not to beat a dead horse as I know this has been accepted as an issue, but I want to second what djspatrick said.  I was just in CLB managed mode when the managed speed dropped to the same value that was erroneously shown as the speed (.78/207) on the DES page.  Note that the CLB page, however, still thinks the managed speed should be 295/.78 but the a/c is following the DES speed.

 

When I got to cruise, the CRZ page showed .78 as the managed speed, yet engaging the managed mode the target speed dropped to 111.

 

Maybe this info will help someone look in the code to spot the problem.

A319 v1220 TNCA-KCLT 181217 Managed speed drop.JPG

Share this post


Link to post
Share on other sites

But still we have the problem that we can not reproduce it.

I did flight with the A321IAE today again and did not see this issue, nor did I see it with other models in the last days.

Also it it is a bug in the code, IMHO veverybody would see this. So for me the question is, what is different on your systems compared to others:
some possible causes:

- P3D version (most unlikely)

- broken P3D installation?

- leftover fom old files during install/reinstall of the Airbus

- manually editing of aircraft files

- issues due to location of installation folder

....

maybe you can comment on my suggestions

Share this post


Link to post
Share on other sites
10 minutes ago, mopperle said:

- P3D version (most unlikely)

P3Dv4.4.16.27077

 

- broken P3D installation?

How to tell?  No other a/c appears broken but the Aerosoft A319.

 

- leftover fom old files during install/reinstall of the Airbus

I ran the uninstaller and appear to get a clean uninstall.  What else to do?

 

- manually editing of aircraft files

None.

 

- issues due to location of installation folder

P3Dv4 is installed in F:\Program Files\Lockheed Martin\Prepar3D v4

Other folders are C:\Users\Harold\Documents\Aerosoft and C:\Users\Harold\Documents\Prepar3D v4 Files

No indications of problems.  Ensured that last install and updater were run as Admin.

 

Harold

 

 

 

Aerosoft folder 181217.JPG

Share this post


Link to post
Share on other sites
Guest
This topic is now closed to further replies.