RayProudfoot

Sorry Oskar, I don’t speak German so can’t understand your first sentence. I don’t know what CL means. Difficult to answer that question. You might be better asking on the FlyTampa forum as this is not a specific problem with EFB.

This post answers the question about 12/30 not being active... http://flytampa.org/forum/viewtopic.php?f=28&t=11211

Oskar, Its because FlyTampa have closed both ends of that runway for takeoff and landing. If you’re familiar with ADE by ScruffyDuck (freeware) it’s not difficult to edit the airport and change the runway properties. If you ask on the FlyTampa forum it’s possible someone has made an alternative available. EFB v2 is simply reading the status of scenery files (BGLs) and is doing everything correctly. It is in your interest to have a basic knowledge of how P3D works which includes BGL files. LATER: I’ve just remembered there is a program supplied with FlyTampa EKCH which may switch 12/30 back on. Check your readme.

I agree with Urs’s view on this missing runway problem. The Aerosoft LPPT is another that has a extra 03/21 runway added ( via a 3rd party fix) to make the PAPI lights visible. A bug in P3D causes some PAPI lights to disappear when a few miles out. The fix solves this problem but if EFB were to show all runways including those that have both ends set to closed it would make the map look a mess.

@sprowse, Hi Steve. I'm the Concorde beta tester than Oskar mentioned. I've just tried loading the classic EGLL-KJFK route into EFB from the pln I created in PFPX. This includes waypoint UPGAS - formerly SW of Cardiff and the accel point for supersonic acceleration. On loading it into EFB it now uses the current UPGAS waypoint in the North Sea so clearly it needs modifying. The only way I have found that works in EFB is to enter the lat/lon of the waypoint in the ATCWaypoint id section of the pln. I replace UPGAS with N5124W000350. It then shows the correct location of the waypoint. I saved the plan then edited the efbr file and replaced N5124W00350 with UPGAS hoping it would rename the waypoint. Sadly it doesn't as UPGAS is a current waypoint. The original name of N5124W00350 remains. So we're stuck with the lat/lon name. It's not really a big issue because the correct positioning is more important than the name. Hope that helps. Also, make sure you edit any Concorde pln and change the cruise altitude to FL600. Even though it rarely reaches that altitude it does ensure AS16 processes the weather correctly.

If you have PFPX then that will do fine. No other sources needed I would have thought.

You can import a route from PFPX, enter one manually or use the link to RouteFinder for it to generate one for you.

Bob, there’s a great Taxi feature that makes it a breeze at both departure and destination.

Speaking as a beta tester I’ve not seen any bugs for a while. A small but dedicated team worked hard on finding and reporting them. I was testing many flights with FSL Concorde and EFB v2 coped admirably. The ability to quickly change waypoints in a plan is much better than v1 as is selecting SIDS and STARs.

One possible solution is a 2nd networked PC running the client on a modest display. I run v2 on an i5 PC with resolution of 2560*1440 using around half the screen area. The other half runs LittleNavMap, Radar Contact and a LUA program showing key P3D info.

It took a while to accept the new design and layout but now there’s no way I would want to revert to v1. The design is much better and the workload much reduced from v1. And, it looks brilliant! ?

posted in wrong place.

The entries weren’t needed for that problem. Glad you’re sorted.

UPDATE: Just seen your latest reply. Good, problem solved. You still need to remove those entries from runways.txt. Remove the EHAM entries. They’re not doing anything. When you say “that didn’t work for me” please be specific. What didn’t work? The configuration tool for EHAM gives you the option to enable all runways. I know as I had the same problem and that fixed it. Perhaps you can provide a screenshot of the utility and your chosen option.

After making the change to the runways using the configuration tool provided you need to start FSX/P3D so the indexes can be rebuilt. Then exit FSX/P3D, Start EFB and rebuild the database. It worked for me.

It’s accessible from the Windows Start menu. Find the entry for Aerosoft Schiphol and it will be there.

There’s a executable supplied with the scenery that gives you the option of showing all runways or those suitable based on wind direction. Choose all to fix the problem.

Leo, The information is in a log. Check your log folder.

Glad to have been of help Dane.

Hi Dane, Try selecting the properties option for the runway. There will be clear indicators if either or both ends of the runway are closed for takeoff or landing. Those yellow X marks are suspicious. Its a simple procedure to uncheck the closed options but bear in mind you cannot only have one end open for takeoff or landing. It’s both or nothing. For example if 08 is open for takeoff then 26 must also be open.

Dane, The only thing I can think of is that both ends of the runway could be set to closed for takeoff and landing. Use ADE to check if you have it.

Confirmed fixed. Thanks Urs.

Thanks Urs, great service and much appreciated. I'll report back later once it's installed.

Thanks Urs.

Hi Urs, Do you have a date in mind when you will release an update to cope with closed runways?