Jump to content

alpha117

Members
  • Posts

    171
  • Joined

  • Last visited

Posts posted by alpha117

  1. Urs,

     

    Everything get back to normal when you shutdown the Data Provider and restart it. So it not a 'show stopper'.

    I've only just seen this today, as this is the first time I've had two PC's.

     

    Has anyone tried running EFB on the second network PC, to see if that stops the AI disappearing?

    It was just that PlanG still was showing AI traffic via simconnect on the second PC, when it disappeared from EFB, which is on the same PC as FSX, but on the second screen.

     

    Yes I now have 2 PCs and 3 screens :shock:

    The wife thinks I'm mad.

     

    I even might be going for a third PC tomorrow. :lol:

     

    Apart from my main PC(FSX), which is new the other 2 are second hand ones from my Dad(thanks Dad) :D

     

    Just a thought

     

    just thought of a Question. How does EFB connect to FSX? Simconnect F SUIPC or another way?

     

     

    Clive

  2. I can tell you the file EFB reads its the 22Z file which is the incorrect file. I know because I've just loaded EFB to test it.

     

    EGNJ 081050Z 36010KT 8000 3000S RA SCT004 BKN011 BKN015 15/15 Q1006

    EGNJ

    2012-07-08T10:50:00Z

    53.57

    -0.35

    15.0

    15.0

    360

    10

    4.97

    29.704725

    RA

    MVFR

    METAR

    31.0

     

     

    It Should have read the 04Z file as this file has the latest data:

     

    EGNJ 081350Z 35009KT 9999 SCT016 SCT029 17/14 Q1006

    EGNJ

    2012-07-08T13:50:00Z

    53.57

    -0.35

    17.0

    14.0

    350

    9

    6.21

    29.704725

    VFR

    METAR

    31.0

     

     

    So, what do you think the issue is? IS it EFB reading the incorrect file OR is REXe over writing files OR something else?

     

    If EFB could sort the files by 'created date and time' and then look at the latest; regardless of the file name then the issue would be solved

  3. Just to confirm again that each Z file holds two sets of data

     

    20Z time stamped at 1135hrs AND 2345hrs the same day :shock:

     

     

    That's me now on this subject.

     

    The only 'easy' way is to purge the metarXML folder manually of the correct Z files at the correct time, then EFB will give the correct weather data every time.

     

    that's what I will do, the manual way I think. Saves the grief

     

     

    good night all

  4. Thanks for that info Andy,

     

    Here's the time stamps on the files from REXe

     

    10Z 1820hrs

    12Z 1959hrs

    14Z 2057hrs

    16Z 2157hrs

    18Z 2257hrs

     

    I think the 20Z file will be about 2357hrs ;)

     

    Remember this is the rewrite of these files in the same day. SO as an example the 14Z file has held data for 1057hrs and 2057hrs (approx ;) ) today

     

    So for EFB to give the correct weather it would have to 'read' each file twice in 24hrs at the right time.

     

    Again, that's just my humble opinion. I'm sure others here will know much more about this than me.

  5. Just got the NEW _14Z data file downloaded time stamp of 2057hrs

     

    Therefore I think you get 10 files in 24hrs, each one being overwritten once.

     

    If you don't 'fly' more than 10hrs in 24 I think you would not notice that there is a problem either and if the 10hrs+ of flying (long Haul) goes into another day you would also not notice the issue.

    Then again if you didn't use EFB or perhaps FSCaptain(nudges Travis :D ), then you would never find out these 'small issues :roll:

     

    @Travis......would this be the same issue in FSC perhaps?

     

    Then again; all that I've written here maybe totally wrong :cry:

  6. Yep, it sure does overwrite the files. It's just over written the _12Z file. 'Refreshed' in EFB and it updated OK.

    So, within the next 20 minutes REXe should download the _14z file with new data and the problems will start IF you already had downloaded the _14Z earlier in the day, as the current data will be written to this file and not the _20Z file and EFB will still be looking at the _20Z file, which has out of date weather data.

     

     

    Just to prove that I shut down EFB totally and replace the _20Z file back into the metarXML folder. Remember that the _14Z file has later data than the _20Z file.

     

    Restarted EFB and it read the _20Z file so now if I was flying the weather that EFB is reporting is now 10 hours old and hence the yellow warning triangle.

    Also be aware that the weather depicted in FSX will ALWAYS be current.

     

    The time stamp of the _20Z file is 1135hrs

    The time stamp of the NEW _12Z file is 1959hrs

     

    Is the way forward to get EFB to 'read' the date and time of the each file in the MetarXML folder and use the latest one regardless of the 'file name'?

     

    How I would love to be a program Tester ;)

     

     

    Over to you URS

  7. I've left REXe running

     

    I now have the _12Z file downloaded. SO my theory is slight out :lol: Only in I think you get 12 files per 24hrs and these are over written.

     

    Also if you use 'historical weather' in REXe it is from what you have in your MetarXML folder only. SO you can't get weather from two month ago if you haven't downloaded it. Like you can do in other weather programs.

     

    Now there are two files, EFB is not updating.

     

    EFB data from _10Z

    EGNJ 301750Z 25012KT 9999 SCT030 18/09 Q1005

     

    REXe Data from the _12Z

    EGNJ 301650Z 21017KT 9999 SCT040 19/11 Q1004

     

    EFB is not reading the _12Z data even if I restart the DP

     

     

    Changed EFB to 'Online from NOAA

    EGNJ 301820Z 25011KT 9999 SCT030 17/10 Q1005

×
×
  • Create New...