Jump to content

Wind Request - 2nd Time


Sabretooth78

Recommended Posts

Following up on a previous topic; lately I seem to be having a lot of trouble with this again:

 

 

It seems regardless the state of the "default" flight plan, I'm seeing this.  There was one instance where, prior to descent, I repeatedly requested and updated the descent forecast and exactly one time it actually gave me the correct match of wind speed/direction and altitude.  Am I still the only one experiencing this, or is there perhaps an Active Sky setting which may be causing this?  I've tried toggling the MCDU3 options away from and back to "Sim (Default)" (or whatever the exact syntax is; I'm away from my sim PC) but to no avail.

Link to comment
Share on other sites

Here's a copy of my most recent ActiveSky activeflightplanwx.txt, captured during preflight, which I'm assuming is the source of the FMGS wind upload.  Please correct me if I'm mistaken.

 

Flight Plan:  KBZN/30 N0432F370 BOBKT4 BOY DCT OPPEE TSHNR3 KDEN/16L

 

****

 

DepartureMETAR=KBZN 150156Z 35012KT 10SM OVC055 06/M03 A2965 RMK AO2 SLP045 T00611033
DestinationMETAR=KDEN 150153Z 31011KT 10SM FEW100 BKN200 14/M04 A2973 RMK AO2 SLP034 T01441039
AlternateMETAR=
AverageWinds=291@65
AverageHeadwind=-57.2
AverageTemperature=-45.2
CruiseAltitude=37000
CruiseSpeed=300
KBZN        350@12(6)    267@14(7)    268@19(3)    251@28(-10)    265@45(-22)    269@58(-32)
        268@84(-46)    273@102(-55)    277@87(-58)    278@47(-56)    264@27(-54)    283@8(-54)
BOBKT        290@14(7)    267@14(7)    271@21(3)    250@33(-10)    270@46(-22)    271@58(-32)
        271@85(-46)    275@102(-55)    279@83(-58)    281@44(-55)    269@29(-54)    278@8(-54)
ZORKE        290@14(7)    267@14(7)    271@21(3)    250@33(-10)    270@46(-22)    271@58(-32)
        271@85(-46)    275@102(-55)    279@83(-58)    281@44(-55)    269@29(-54)    278@8(-54)
TOOLS        251@14(13)    251@14(7)    255@18(3)    247@29(-9)    269@49(-21)    271@62(-31)
        273@85(-45)    279@101(-54)    281@87(-59)    280@45(-56)    266@31(-55)    275@7(-55)
TOC        249@11(13)    249@12(7)    253@13(3)    249@28(-8)    271@49(-21)    272@64(-31)
        276@86(-45)    282@101(-54)    284@87(-59)    280@44(-57)    266@33(-56)    269@7(-55)
BOY        250@8(10)    250@8(10)    273@4(6)    262@27(-7)    273@47(-19)    277@59(-29)
        280@78(-44)    288@93(-54)    291@86(-61)    284@50(-57)    264@33(-57)    251@8(-55)
OPPEE        240@15(6)    240@15(6)    273@24(9)    273@40(-6)    280@47(-19)    290@55(-29)
        299@76(-45)    306@89(-54)    304@71(-60)    285@44(-58)    271@39(-58)    242@13(-56)
HNMAN        240@15(6)    240@15(6)    273@24(9)    273@40(-6)    280@47(-19)    290@55(-29)
        299@76(-45)    306@89(-54)    304@71(-60)    285@44(-58)    271@39(-58)    242@13(-56)
SOYAR        240@15(6)    240@15(6)    273@24(9)    273@40(-6)    280@47(-19)    290@55(-29)
        299@76(-45)    306@89(-54)    304@71(-60)    285@44(-58)    271@39(-58)    242@13(-56)
TOD        240@15(6)    240@15(6)    273@24(9)    273@40(-6)    280@47(-19)    290@55(-29)
        299@76(-45)    306@89(-54)    304@71(-60)    285@44(-58)    271@39(-58)    242@13(-56)
MOLTN        270@16(19)    271@16(13)    272@17(10)    268@34(-5)    282@49(-19)    290@59(-29)
        301@75(-45)    310@86(-54)    307@65(-59)    285@43(-59)    273@38(-59)    239@14(-57)
WOOKY        272@15(19)    272@15(13)    274@17(10)    268@33(-5)    283@48(-19)    290@59(-29)
        302@75(-45)    311@85(-54)    307@64(-59)    285@44(-59)    273@38(-59)    238@14(-57)
KDEN        310@11(14)    310@11(14)    304@15(13)    284@25(-3)    288@44(-19)    292@56(-29)
        306@74(-46)    313@83(-55)    304@66(-59)    287@47(-57)    272@33(-60)    236@15(-57)

 

****

 

Is it just me, or are the cruise waypoints (BOY through SOYAR and TOD) showing duplicate first entries?  An "extra" first entry might explain why what the Bus expects to be the 18000 entry is actually in the 24000 position?  Or am I completely off base?


 

Link to comment
Share on other sites

  • 1 month later...

Alas, I have recently the same issue after updating P3D to 4.5 as well as the Beta update from Activesky. Activesky generates a wx. file but somehow, when i ask for a wind update during the initials I get no response. I had no time do "dive" into the problem only but to realise it happened after the updates....

Link to comment
Share on other sites

This now happens for me constantly, whether or not I have a PLN flight plan loaded, after the latest ActiveSky update, etc.  I've been inclined to ignore it since there doesn't seem to be a will to address it - and the conditions being one FL off are generally still fairly close and as such for sure more accurate for FMGS calculations than having no wind input at all.

 

Still, I would like to hear some official input from Aerosoft on the matter.  It may well be an ActiveSky issue, but it's also in Aerosoft's interest if their product is directly intending to pull data from a buggy feature.

Link to comment
Share on other sites

  • Deputy Sheriffs

Coud it be that you are mixing something up? The Airbus takes the wind data from a file being generated the moment you load the flightplan into ActiveSky.

This file is located in the folder ...P3D/PMDG/WX and is named in the followig way:

ICAOdepICAOarr.wx; example for a flight from Nurnberg to Hamburg, the filename would be EDDNEDDH.wx.

But TBH I never checked whether this file is being updated  by ActiveSky during a flight.

Link to comment
Share on other sites

I'll check for that file next flight, which will be tomorrow evening - I was previously looking at the activeflightplanwx.txt as mentioned above.

 

Are you sure the "EDDNEDDH.wx" file would be in the PMDG folder?  That seems a little odd for instance if you didn't have any PMDG installed.

Link to comment
Share on other sites

  • Deputy Sheriffs
7 minutes ago, Sabretooth78 said:

Are you sure the "EDDNEDDH.wx" file would be in the PMDG folder?  That seems a little odd for instance if you didn't have any PMDG installed.

Yes, I was partly wrong. the P3D path is needed, when you use another tool then AS. In case of AS, the data are read from the file you mentioned.

Although I still have the feeling that even the activeflightplanwx.txt is not being updated by AS, when AS downloads new weather. Which would be quite odd. But to make sure I've asked this in the AS forum.

Link to comment
Share on other sites

On 6/13/2019 at 10:05 AM, mopperle said:

Yes, I was partly wrong. the P3D path is needed, when you use another tool then AS. In case of AS, the data are read from the file you mentioned.

Although I still have the feeling that even the activeflightplanwx.txt is not being updated by AS, when AS downloads new weather. Which would be quite odd. But to make sure I've asked this in the AS forum.

 

Just to document another instance (as I said it happens consistently).  This time with the A321 IAE; 1.2.4.1.  Attached is the activeflightplanwx file and my AS settings if that helps.  Everything posted was captured while paused, during preflight so it should all be consistent with the wx picture at that moment.

 

Flight plan:  KJFK DCT COATE Q436 RAAKK Q440 SLLAP DCT GRB DCT KINGZ DCT FAR DCT DIK DCT MLP GLASR1 KSEA

 

Note GRB:

 

Please login to display this image.

 

Please login to display this image.

 

 

Please login to display this image.

 

Note based on the activeflightplanwx file, the entry 160@7(12) leading off the GRB line.  If you include that as 6k altitude (when it should in fact be surface?), then it might seem as though the Bus is reading an incorrectly delimited file, or the Bus doesn't skip an entry it should be skipping.  It's over my head regardless, so curious to see what you hear back from Hifi.

activeflightplanwx.txtCMS_PTA_EF.CFG

 

Link to comment
Share on other sites

  • 5 months later...

Apparently my old friend (which still occurs with the A320 despite a full system rebuild/reinstall) has appeared on the A330:

 

(The viewpoint is towards the back of the cockpit because I didn't pause my TrackIR :))

 

Please login to display this image.

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. Privacy Policy & Terms of Use