Jump to content

KiloJuliett

Members
  • Posts

    476
  • Joined

  • Last visited

Posts posted by KiloJuliett

  1. Hi guys

     

    Sorry for not getting back to you earlier. I discussed the topic with Urs in the meantime. The main issue is that different FSD server networks use different formats for their whazzup files. More specifically the data fields are at different positions. As there is no generic network traffic format supported, whazzup files from other networks only work if the relevant data fields are at the same position. So to check this, you need to compare VATSIM and IVAO files with the ones generated from your network. If any of them fits, you can change the url in the EFB server to point to your status file. Be aware that EFB also does a check for a minimum number of data elements and does not read the file if the value is too low.

    The file from the url @PCPiloot sent me works when it is entered instead of the default VATSIM file.

    There are no plans currently to expand the functionality of EFB in this regard, as the number of EFB users also flying online is quite small.

  2. Yep, the traffic monitor is what I meant. This could be helpful if you spot another case. However, E17S seems to be a fantasy designator. Maybe this is part of the problem. I don't know if there is any cross check with the ICAO database. Urs will be able to clarify.

  3. On 8/13/2020 at 9:33 PM, robert_folmer said:

    However when I say save plan it saves it to C:\Users\User\Documents\KFMHKFMH03.pln. Is that correct?

    What application is saying this?

     

    Have you loaded the flight plan in EFB?

    What aircraft (default, specific addon) are you using?

  4. When your route is expected to go from an uncovered sector (UNICOM) into a covered one (ATC FREQ) and then back to an uncovered one (UNICOM), this is the correct behaviour. The stations presented in the ATC Freq Ribbon represent your route (from left to right).

  5. On 5/27/2020 at 11:32 AM, lonewulf47 said:

    Hi Michael,

     

    That's very simple to answer. We do not have the complete worldwide Holding Database available in the dataset provided by Jeppesen or LIDO. Therefore we can only use the Holding information provided for a specific waypoint. In most of all cases there is just a flag set to indicate the presence of a holding, but no information on the layout. Our policy is to use a standard right turn reversal holding if no other information is provided. To draw each holding correctly (possibly even more than one holding procedure may be available on one single waypoint) it would require access to the worldwide Holding Database. Of course Jeppesen and LIDO do have this, we (unfortunately) don't...

  6. I believe CPflight radio panels do not support the native flightsim standby frequency, which is used also by EFB. Some hardware unfortunately does not synchronise this data with the default instruments, but keeps it their own. Hence they cannot be manipulated by EFB. As far as I'm aware, this has been an issue since and didn't change (unless the software interface for your hardware changed).

  7. The Tallin Scenery from Drzewiecki renders two messages during the DB creation.

     

    Quote

    Debug   : Invalid navaid: Ident='ILK', Name='<missing>', Position='59.4133534 24.8004171', Filename=C:\Lockheed Martin\Prepar3D v5\Addon Scenery\EETN Tallinn X v2\scenery\Tallinn EETN.BGL
    Debug   : Invalid navaid: Ident='IIB', Name='<missing>', Position='59.4131609 24.8727635', Filename=C:\Lockheed Martin\Prepar3D v5\Addon Scenery\EETN Tallinn X v2\scenery\Tallinn EETN.BGL

     

    However, when opening the file with ADE, there is a name set. Maybe an issue of specific characters (/)?

    dbBuilderLogfile.txt

  8. 21 hours ago, Tom Slott said:

    it shows always up as 121.380

    In the PMDG radio panel? Then it's purely a pseudo-display of 8.33 kHz frequencies. In fact, FSX/P3D do not support (yet) 8.33 kHz frequencies, hence 121.380 cannot be a frequency actually set. I guess it's only PMDG imitating 8.33 kHz compatibility.

×
×
  • Create New...