RayProudfoot

If anyone has LYBE - Nichola Tesla Airport, Belgrade the attached AFD file will correct the ILS for 12/30 not being detected by EFB's scanning process. My discussion with ORBX is here and they have provided an 'official' fix for anyone that wants it. https://orbxsystems.com/forum/topic/178769-lybe-ils-issue/?tab=comments#comment-1587795 LYBE_ADEP4_RAY.bgl

That appears to have fixed it, thanks Oskar. LATER: It hasn't fixed LYBE but that AFD doesn't conform to the SDK with navaids placed at the North Pole. I have raised it on the ORBX forum a few months ago but they haven't fixed it.

There appears to be a general problem with ILSs not showing with the latest builds. I imagine Urs will reply tomorrow.

The problem appears more widespread than I initially thought. Inbound to UK2000 Manchester (EGCC) no ILS is shown for 05L when I know for a fact it is available.

Gents, Running Server v2.1 #113 and Client v2.1 #113 but the following 3rd party AFDs which have ILS do not show in EFB. LatinVFR KMSY, ORBX LYBE and ESSA. I'm attaching the BGLs but please note they are modified versions because I have custom jetways by Cartayna and have edited out some errors but left navaids alone. Is it a problem with how EFB is reading the AFDs? RAY.zip

All deleted, thanks Urs. 👍

In fairness, it was an unusual situation. Urs, feel free to delete the entire contents. Nothing is relevant now.

Affirm Oskar. I cannot see a delete option. I have exceeded my allowance by a factor of around 8. Maybe I’ve broken it! 😁

Just a gentle reminder I have exceeded my allowance for uploaded files from beta testing days and cannot see a way to delete them.

Hi Oskar, Yes, I'm on 1908 but I've just heard back from Stephen Cooke who advises LGRP renamed them to 06/24 in May. So a change to the AFCAD is needed. I shall do that later. CTRL + Alt + A shows 06/24. 👍

Update. I've just remembered EFB will use Navigraph data for runways so I've posted on Navigraph asking them to check the designations.

I am baffled by the EFB Client showing the wrong runways for Just Flight Rodos LGRP addon airport. They show as 06/24 when they should be 07/25. P3D v4.5, EFB Server v2.1 Build #109; Client v2.1 Build #109. I have checked the AFCAD using ADE and the runways are shown as 07/25. In P3D Airport selection they are 07/25. I tried Enhance / Update Runways in the Database but when I enter LGRP the runways are returned as 07/25. So I abandoned that. Here are the entries in the airportFiles_P3D4.txt... LGRP D:\P3Dv4\Scenery\0602\scenery\APX55190.bgl (53) Base D:\P3Dv4\SimMarket\JustSim-LGRP P3Dv4\data\scenery\AFX_LGRP.bgl (259) COM, and more No duplicate AFCAD apart from the default but that's never been a problem with other addon airports. runwayMappings_P3Dv4-NG.txt contains no entries for LGRP. I would attach the BGL but I have run out of space and cannot find a way of clearing all the files I attached when I was a beta tester. Hope you can thrown some light on this problem and free up some space for me.

😁 The P3D version of Catch-22!

Having just substituted Ray Smith's FSX AFCAD I don't think it's worth it. Taxiway B is misaligned and there are taxiway signs in the middle of taxiways. I'll revert to the original but keep the ZSCB one disabled. That's how the others have coped when flying airliners.

I've read through a few topics about this issue and from the replies it's pretty clear that even if I was to complain or ask for an alternative AFCAD that includes both runways the request would fall on deaf ears. I've just taxied to 35 and at least EFB now shows my aircraft at YSCB without the switch to a non-existent airfield. I see there is a modified AFCAD on AvSim and althought it was designed for FSX I imagine there's a reasonable chance it might work with P3D. It's worth a crack. https://library.avsim.net/esearch.php?CatID=fsxafcad&DLID=155044

Hi Oskar, I searched the ORBX forum and found someone with this question. They add this ZSCB AFCAD for light aircraft for Rwy 12/30 as you state. Since I have no interest in seeing GA use a different runway I shall disable that BGL. That will fix my problem but if you wish to find a solution for the wider EFB customer base that would be a good idea. I agree they are a law unto themselves with their imaginative AFCAD designs but their scenery does look very good.

Thanks Oskar. It’s the strangest thing I’ve seen in P3D and EFB. If it displayed ZSCB continuously whilst on the ground it would make more sense than switching based on ground position. The installation has has been handled by ORBX as it places all scenery into its own parent folder. I shall investigate and report back.

EFB Server v2.1 #108 and Client v2.1 #108. I have Orbx Canberra installed. When positioned at a gate the client corrrectly shows the airport layout for YSCB. However, when I taxi towards 35 and pass the half-way point the map changes to ZSCB - Canberra GA (China). I line up on 35 and take-off. Once airborne the map detail returns and I can see my route to Sydney. But in the top of the map it still shows ZSCB but then soon changes to YSCB. All is well thereafter. Any ideas how to fix this?

Good tip, thank you. 👍

Thanks Oskar. I must admit I didn't consider real-world data. To ensure Radar Contact gives me the correct runway designator I should really edit the AFCAD and amend the runway so it matches the real-world one.

I have FS DreamTeam KORD installed for P3Dv4. Looking at the runway designations in ADE, Runway 10/28 is described as that. But after running the database update that runway is shown as 10L / 28R in the Client map. I'm reading AP_KORD.bgl in the OhareX\Scenery folder. When I run MakeRwys it creates a runways.xml file that also identifies them as 10/28. I'm confused. Why the difference and how to correct it?

I should clarify my statement. The server is running on Win 10 build 1809 but the client is running on Win 7 Pro.

Just for info I’ve been running 1809 for a couple of months now and EFB v2 has been fine. I run the client in a networked PC.

Thanks Urs. That feature will be very helpful when deciding on a suitable parking gate.

In EFB v1 the gates that had a working jetway were identified on the display in blue with a black circle. Unless I've missed something obvious I cannot see the same in v2.