I have flown exactly the same flight, in FS9 with ASE, using the PMDG 747-400, BA livery, on two successive days, with the same results each time.First, yesterday, 1 March 2010 (as previously posted, but the Moderator has asked for separate posts from individual users). ++ QUOTE++Today I flew YSSY (Sydney) VTBS (Bangkok) in FS9, using the PMDG 747 with BA livery, and ASE. Online with VATSIM.Specs:Dell DXP051 X86-based PC x86 Family 15 Model 6 Stepping 4 GenuineIntel 2793 MhzTotal Physical Memory: 3.00 GBTotal Virtual Memory: 2.00 GBPage File Space: 5.84 GBMicrosoft Windows XP Home Edition Service Pack 3 Build 2600NVidia GeForce 7900 GXT, driver 6.14.11.7824Creative SB X-Fi sound card, driver 6.0.1.1361FS9, SP 1ASEAt first, all went well. Then, when Iwas about 150 nm north-west of Darwin, all hell broke loose. Basically, I was showing an AS 0f about 300 kts and was in an irreversible descent. I disconnected AP and AT and wrestled back control, though not without flying a few miles upside down. I leveled at Fl 240 indicated at a speed of 160 kts indicated.I then closed ASE, went to World -> weather-> Clear all. Problem solved.I rearmed VNAV and gently climbed back to cruise at FL 380 without mishap.I flew another 100 nm or so.I then reengaged ASE, with AT and AP engaged, LNAV and VNAV.Before the brown stuff hit the fan, I just had time to register: OVERSPEED! and an indicated alt of ... wait for this... 58000 feet. (As in: Fifty-Eight Thousand feet). And I wasn't even flying the Virgin space trip livery! Once again: Overspeed, irreversible descent, cut ASE, restore Weather -> Clear all.Now this is all good fun, and I must confess I haven't tried it out in FSX, but I don't think the developers can actually claim a result just quite yet tongue.gifI hope this will help somebody, somewhere. I'm off to nail the Shiraz.John ++ENDQUOTE++Today, 2 March 2010Same result. About 200 nm south-east of Bali, end of the world. Speed goes from .84 to all red bars, overspeed alerts, plane uncontrollable.Solution: close ASE, reset Weather in FS9 to Clear Skies; problem solved ... but I'd lost 3000 ft in the couple of seconds it took me to take remedial action.This time, I noticed a couple of things.First, it happened in almost exactly the same geographical location.Second, I was passing from a long period of 'Advanced Interpolation' across northwest Australia, and had entered a weather station id'd as WADD (Bali).I used Report -> WX Config on the ASE screen to check. This is what WADD was reporting:WADD 021700Z 34004KT 10SM FEW018 27/25 A2983Not exactly tsunami weather! Winds aloft were showing 52/9, -51 degrees C, at FL 390; I was at 380 but I feel that's near enough.Could it be that *leaving* an area of Advanced Interpolation (rather than entering it) can cause mayhem?Finally, I'm afraid I can't replicate this on FSX (which I have) because I don't own the PMDG Queen of the Skies for X.Hope this adds to the general stock of knowledge!John

Thanks John for the informative post!When you get a chance, can you fly the route in a default plane and see what happens and report here?

Thanks John for the informative post!When you get a chance, can you fly the route in a default plane and see what happens and report here?

Wilco ... and glad to do so.John

Wilco ... and glad to do so.John

Having the same thing right now right over the waypoint EBONY in between Boston and St. John Newfoundland. In the CS757 in FS9 en-route from KEWR-EGCC at FL350. Got overspeed warning and immediately checked TAT. It was at -26 then immediately dropped to -16, I went into an Overspeed at M.93. Within a few seconds TAT had gone back to -26 and everything stabilized followed by the same thing repeating 3 times before TAT has now stabilized at -28 again...The only thing the log reflect at the time was up/downdraft started...Jim, did you do a full install or the upgrade most of us have done. Trying to figure out if that can be a factor...Thanks,-Paul

Hi,Full install.

Jim, I have just completed this flight (YSSY-VTBS) using FS9's stock Boeing 747.Routing: YSSY KAT A576 BLI G464 PNK N875 ENREP N891 BKK VTBS.PLN waypoints as used by the GPS:[flightplan]AppVersion=9.1.40901title=YSSY to VTBSdescription=YSSY, VTBStype=IFRroutetype=3cruising_altitude=36000departure_id=YSSY, S33* 56.46', E151* 10.38', +000021.00departure_position=16Ldestination_id=VTBS, N13* 41.09', E100* 44.56', +000005.00departure_name=KINGSFORD_SMITH_INTLdestination_name=SUVARNABHUMI_INTLwaypoint.0=, YSSY, , YSSY, A, S33* 56.46', E151* 10.38', +000000.00, waypoint.1=, , , KAT, N, S33* 42.38', E150* 17.58', +022999.98, A576waypoint.2=, , , PKS, V, S33* 7.51', E148* 14.13', +035999.98, A576waypoint.3=, , , VIMAB, I, S31* 30.54', E145* 21.29', +037999.97, A576waypoint.4=, , , APOMA, I, S29* 53.52', E142* 40.53', +037999.97, A576waypoint.5=, , , POLEV, I, S26* 55.12', E138* 10.11', +037999.97, A576waypoint.6=, , , KALUG, I, S25* 53.59', E136* 43.29', +037999.97, A576waypoint.7=, , , AS, V, S23* 47.34', E133* 52.41', +037999.97, A576waypoint.8=, , , TIMMI, I, S21* 55.18', E130* 39.35', +037999.97, A576waypoint.9=, , , TATUK, I, S19* 25.45', E126* 38.46', +037999.97, A576waypoint.10=, , , CIN, V, S17* 35.18', E123* 51.06', +037999.97, A576waypoint.11=, , , ATMAP, I, S12* 0.00', E118* 15.17', +039999.97, A576waypoint.12=, , , ILDAM, I, S10* 35.31', E116* 53.04', +039999.97, A576waypoint.13=, , , BLI, V, S8* 45.02', E115* 9.47', +039999.97, G464waypoint.14=, , , TIRAS, I, S7* 28.00', E114* 29.42', +039999.97, G464waypoint.15=, , , KOLTA, I, S6* 27.53', E113* 49.40', +039999.97, G464waypoint.16=, , , PKN, V, S2* 43.35', E111* 41.45', +039999.97, G464waypoint.17=, , , OSUKA, I, S1* 17.30', E110* 24.42', +039999.97, G464waypoint.18=, , , PNK, V, S0* 4.44', E109* 22.30', +039999.97, N875waypoint.19=, , , ARUPA, I, N0* 31.40', E108* 48.46', +039999.97, N875waypoint.20=, , , NIMIX, I, N1* 24.51', E107* 59.26', +039999.97, N875waypoint.21=, , , ESPIT, I, N2* 0.11', E107* 26.23', +039999.97, N875waypoint.22=, , , BOBOB, I, N2* 22.05', E107* 5.57', +039999.97, N875waypoint.23=, , , LEBIN, I, N3* 14.38', E106* 6.03', +039999.97, N875waypoint.24=, , , ELGOR, I, N3* 30.14', E105* 48.18', +039999.97, N875waypoint.25=, , , MUMSO, I, N3* 44.20', E105* 32.12', +039999.97, N875waypoint.26=, , , SUSAR, I, N3* 58.47', E105* 15.47', +039999.97, N875waypoint.27=, , , DAMOG, I, N4* 12.24', E105* 0.14', +039999.97, N875waypoint.28=, , , NOPAT, I, N4* 23.12', E104* 47.56', +039999.97, N875waypoint.29=, , , ENREP, I, N4* 52.23', E104* 14.42', +039999.97, N891waypoint.30=, , , IKUMI, I, N5* 53.35', E103* 55.12', +039999.97, N891waypoint.31=, , , IGARI, I, N6* 56.09', E103* 35.05', +039999.97, N891waypoint.32=, , , SAMOG, I, N8* 0.00', E103* 14.23', +039999.97, N891waypoint.33=, , , XONAN, I, N9* 14.41', E102* 50.20', +039999.97, N891waypoint.34=, , , BENSA, I, N10* 26.23', E102* 26.41', +037999.97, N891waypoint.35=, , , ANOBO, I, N11* 3.23', E102* 14.41', +031999.98, N891waypoint.36=, , , RYN, V, N12* 46.48', E101* 40.41', +026999.98, N891waypoint.37=, , , BKK, V, N13* 53.36', E100* 35.46', +005999.99, waypoint.38=, VTBS, , VTBS, A, N13* 41.09', E100* 44.56', +000000.00, All went well until I was some way past Bali, way beyond the point where problems occurred before.The only mishap in this first sector of the flight occurred when I was coming up on W/P ATMAP, which was associated in my mind with the previous debacles. I opened up ASE main screen and checked on the weather station -- no problem -- but as soon as I clicked on WX Config I got a message: ASE has encountered a problem and has to close, you may lose etc etc..I reloaded ASE, reloaded the flight plan within ASE and went on my way.Then...a picture is worth a thousand words.Despite closing ASE and resetting Clear Skies, the aircraft was unfortunately lost with all souls :( Let me know if there is anything else I can do.John

I'm having a simular problem with FS9 and ASE update. Flying wilco 737 or Feelthere Airbus. Route from LFMN to EHAM. LFMN IRMAR UN853 GIVOR UL47 GTQ UN852 DIK UM624 BUB PESER EHAM.I keep getting servere wind shifts and temp changes. So far when I fly in the USA with ASE everything operates smoothly. Bill M

Not sure if it's related, but on my first flight with ASE and the Overland A320, the airspeed indicator suddenly showed 000 several minutes after take-off (from KLGA to KIAD), autothrottle went to full and when the indicator returned to normal, I was doing like 400/500 knots at 6000ft... I can only associate that with ASE.:(

Mike, you had your PITOT tubes freeze up. You need to use Shift/h to turn on heat. Default FS weather can cause the same thing.John, was that a plan generated by FS itself?

Jim:1. Route found using Vroute (freeware edition).2. Route built using FSBuild ver. 2.3.7.5 build 236. Aircraft payload weight and alternate (VTBU) input by me; winds aloft taken automatically from ASE (accurately).3. Plan exported by FSBuild to FS9 GPS (and others, not relevant here).4. Plan (.pln) loaded into FS9 (SP1) via Load A Flight page.5. Route flown using GPS/NAV switch set to GPS; AP on; AT on.John

Mike, you had your PITOT tubes freeze up. You need to use Shift/h to turn on heat. Default FS weather can cause the same thing.

Pitot and anti-ice were all on. I also checked if maybe I had failures enabled, but all of them are off.:(

Hi,I'm also having some problems with the overspeed and loss of altitude in ASE. What's basically happening is that all of a sudden the red bars on the PFD indicating an overspeed are overlapping the red bars of "underspeed". The plane (PMDG B737 and B747) starts to descend with a vertical speed of -8.000ft p/m. In other words: out of control.This has happened to me on a flight from OMDB to WSSS, and on a flight from VTBU to WARR.What I would like to know, is how can I quickly fix this "weather problem"? Will hitting the button "Refresh" solve it, or do I have to restart ASE all over again?Jon

Hi Jon:On my first flight, detailed in the OP, I mentioned that after the initial 'crash' I regained control by closing ASE. Then, some time later, I relaunched ASE only to have the same thing happen immediately, even though I'd flown about 100 nm miles from the original scene.Hope this helps. (But I'm not optimistic :( )John

Then, some time later, I relaunched ASE only to have the same thing happen immediately...

That's what happened to me too. Because of the problems with ASE I switched to Real Environment Extreme for FS2004, but somehow this didn't work either. I was flying with REX, but I wasn't getting any weather (i.e. no wind, no clouds, TAS same as GS). So I closed REX, and switched back to ASE. As soon as I connected ASE the already mentioned problem was back again.So it seems that whenever you have an abrupt change in the weather update, things start to go wrong. From what I've read on this forum, it seems that these problems are due to advanced interpolation. Maybe it would be a good idea to implement a feature so that advanced interpolation can be turned off.Jon

That's what happened to me too. Because of the problems with ASE I switched to Real Environment Extreme for FS2004, but somehow this didn't work either. I was flying with REX, but I wasn't getting any weather (i.e. no wind, no clouds, TAS same as GS). So I closed REX, and switched back to ASE. As soon as I connected ASE the already mentioned problem was back again.So it seems that whenever you have an abrupt change in the weather update, things start to go wrong. From what I've read on this forum, it seems that these problems are due to advanced interpolation. Maybe it would be a good idea to implement a feature so that advanced interpolation can be turned off.Jon

I agree.ASE problems arise especially with FS9. It is too different from FSX.ASE developers should build two different programs, one for FS9 and another for FSX, with different options.PS: REX 2004 is nothing compared to AS :(