Jump to content

Jiblet

Members
  • Posts

    5
  • Joined

  • Last visited

Jiblet's Achievements

  1. Just wanted to take the opportunity to send you good thoughts, kudos and love for doing this. Best of luck and stay awesome Simon
  2. Thanks for the steer Oskar. I've deleted all the AIRAC data I can find on this machine, then reinstalled/updated the data from Navigraph, then finally rebuilt the EFB DB and though I still see some warnings like: 2020-06-02 11:15:25.655 Debug : F:\X-Plane 11\Custom Scenery\arviatcyek\earth nav data\apt.dat 2020-06-02 11:15:25.659 Warning : Spec version '850#' is not implemented. Cannot read file. I see no errors and ILS/Loc approaches are working again! Should I be worried about the warnings, or are those normal for older custom sceneries? Still no idea what I did to cause it in the first place but we're airborne once again! Here's to another year of trouble free use Thanks again, Simon
  3. Hi, Using: EFB 2.1 (build #118) - local machine - default path - licenced. XPlane 11.50b9 AIRAC cycle 2006 (Navigraph) which matches what I have in XPlane (I also tried with the AIRAC cycle that comes with EFB and see the same thing) I think I've done something stupid, though I'm not sure what! Having had no problems with EFB2 in the year I've been using it, last night it started showing "!No LOC available" for all airports, or at least for the 10-12 I've looked at so far. To reproduce I simply make a new flight plan, eg "EHAM LERT", then click the ARR button to see: Note I'm using LERT as an example as it has lots of ILS approaches and I don't have any custom scenery for it, but I see the same issue for all airports including those with/without custom scenery. To fix this I've tried: Rebuilding the database Adding modified sceneries (the "Start Scanning" button) Reinstalling EFB from scratch with its included Navigraph AIRAC cycle Updating that back to AIRAC 2006 Checked the manuals for any mention of "No LOC available" Checked the forums for the same error - I found this FAQ but it doesn't seem relevant as I'm seeing this in XPlane and across all airports) None of which has any effect. Given that it was working just fine at the weekend, I don't think this is a bug, I think its a user issue - I'm just not sure what I've done or how to fix it. I've included the support package files in case those help shed some light on what I've done. Thanks, Simon Server_202006020937.txt.zip Client_202006020937.txt.zip
  4. Ah perfect then, thank you! I'll look forward to the next update
  5. I'm using XPlane and have a few addon airports in my custom scenery, but not every single airport in the world I was hoping that EFB2 would let me determine which airports I have custom scenery and which done. Now on first look at the client manual it talks about the differences between the red, green and blue airport icons - which all appear fine - but it also mentions that addon airports appear as an asterisk with a circle, whereas normal airports (base game airports if you like) just have a bare asterisk. This is what I see for a random area in the USA where I have no addons. On further examination of a random airport it seems that EFB counts "Custom Scenery\Global Airports" as addon airports, but they're not! Those come from the XPlane scenery gateway and come with the base XPlane install, and contain every 3D airport in the game world. is there anything that can be done to ignore the "Global Airports" folder when determining if an airport is an addon? Thanks! And while I'm here, can I say how much I love EFB2? Congratulations on a brilliant product.
×
×
  • Create New...