Jump to content

victoroos

Members
  • Posts

    18
  • Joined

  • Last visited

Posts posted by victoroos

  1. 1 hour ago, aivlasoft said:

    Hi Victor,

    thanks for the good words on EFB.

    121.970 is an invalid frequency. Only .975 is valid (for 25 kHz and 8.33 kHz). But anyway, it depends on the radio stack whether it is capable of displaying a frequency like 121.975.

    You can check the Server's logfile to see which frequency has been set to the simulator.

     

    Okay, I looked at the log. It worked fine. It was 975 indeed. sorry.

     

    Aka, I kept troubleshooting, (I always want to do it self ;)).

    I updated FSUIPC to v6 (I was still running 5), and that worked like a charm. Apparently was that FSUIPC specifically an error.

     

    Thanks for the fast reply. Sorry for bothering :)

  2. HI all,

     

    I love the v2 app. And it's udpates.

    However, I have one question. I wanted to tune EHAM delivery 121.970.

    However, when I do that, my radio stack shows 980 and when I try to switch it to 970 it jumps to 950 (skipping the 970 it should show).

     

    This can only be fixed when I tune a frequency that is a "round" frequency (eham has enough luckily) and then tune it by hand.

     

    is anyone else experiencing these problems. it is..really weird.

     

    I tested it in the NGXU with the latest EFB update.

     

    cheers

    victor

  3. Yeah, I also contacted the dutch ATC. and they gave me about the same info.

    It depends on th cockpit, and would be between 0 and 600 RVR for CAT III. there.

    Except for RWY 36R and 22/04 they are all CAT III.

    What would be the best values to put in then? because it is very dependent on cockpit.

    For cat II they indicated 2200 M (based on DH)

  4. Quote

    The most important bugs are:

    A;1;A128;NA -> a Visibility MUST be indicated and cannot be replaced by "NA". "NA" is only allowed to mark an approach category as unavailable, such as: E;;NA
    *;;A690;NA -> the Asterisk (*) cannot be used as a wildcard for all approach categories, each line must start with the respective approach category.

     

    Minimum approach visibility is in most coutries' AIPs no longer listed on the respective approach chart, but listed in the AD2 part of the airport or even in the common AD1 part. This is unfortunately not handled consistently within the AIP publishers. As a simplification method at AivlaSoft we use standardized min. visibility, such as R75 for ILS CAT III, R200 for ILS CAT II or R550 for ILS CAT I plus some higher visibility for non-precision approaches. As there are no legal requirements for approach minima in Flight Simulation, we freely decided to do so on our own ?.

    There are more? i used yours as a basic

    but thanks, I'll look into them

     

    edit: Fixed: @lonewulf47

     

    EHEH.txt

  5. HI all

    SO, my first a(it is harder then I thought ;).. but if anyone wants, I can look into it because it is fun somehow) the EHAM minimums file.

    it is basic, CIrcling is basically not allowed at EHAM so I disabled that, but both cats (cat 3 has the same as cat 2) and LOC's are done for all the active landing RWY!

    Hope I did it right, if not tell me!

    cheers

    vic

    EHAM.txt

  6. Hello

     

    I have a question. I'm trying to step up my fs style, and with that, belongs minimums and better chart awareness..

    The last part succeeds, with radios etc, thanks to efb..however, in the manual it says I should be able to see the decision height/minimus.. However, I can't find..

    Any advice on that?

     

    Vkr

    Victor

×
×
  • Create New...