Jump to content

RayProudfoot

Members
  • Posts

    961
  • Joined

  • Last visited

Profile Information

  • Gender
    Male
  • Location
    : Cheadle Hulme, Cheshire, England

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

RayProudfoot's Achievements

  1. Hi Urs, I was wondering if it was possible for you to allow the user to be able to rename user-defined waypoints. I ask because on my Concorde flights I find it useful for the accel and decel points to be included in the plan. If you're unaware these are the points at which the reheats are engaged and supersonic climb commences. Likewise at the other end it's the point at which power is reduced before the descent commences. They're different on every flight depending on weight, altitude and location. When I create them they're named U001 and U002. I would like to rename them to ACCEL and DECEL. Could you consider this please?
  2. Urs, I have PFPX. I should be able to create the waypoints in that planner. Bit of a nuisance but there aren’t that many for Concorde as waypoints were a few hundred miles apart.
  3. Hi Urs, I have bought FS Labs Concorde for P3D v5 and many of the historical routes it used cannot be imported into EFB because many of the waypoints aren't in the current AIRAC database. Trying to enter them by hand is extremely difficult. Is it possible to bypass the AIRAC check please?
  4. I've received an email from Stephen Cooke with the data he extracted from LittleNavMap. 👏 That should be sufficient. Thanks Stephen.
  5. Hi Urs, I see EFB holds the Transition Altitude for each airport. Where does this info come from? Is it a source you have to pay for? I ask because I still use Radar Contact v4 for ATC in P3D v5.3. But its data is now over 15 years old and I do see some differences between the TA in the RC4 files and that shown by EFB. Is there a site you can direct me to so I can try to update my RC4 files please?
  6. Thanks Stephen, I'll have a look on his website. The next time this problem arises at least I'll know what the solution is.
  7. @srcooke, how did you find out this ID had changed? Is there a published list somewhere that lists changes? If so it would be helpful so I can check my installed airports each month for any changes required.
  8. Gents, I'm pleased to report Stephen was correct. The identifier was out of date. I used Herve's utility to correct it. It took a little while to work out which option to use as some were read-only. The BGL attached yesterday now has the correct ID. This is a powerful utility and something I'll use as and when required to correct other issues. Many thanks! 👏
  9. If that’s the reason for the Localiser not being recognised then that makes sense. But having tried Herve’s utility I do prefer AFD. Assuming default ILSs can be edited with it. If not then it’s Herve’s.
  10. Thanks Urs. Attached. I had another thought about this last night. I was wondering if the VOR over the airfield might have changed its frequency. I'm flying at present but perhaps you could check if that might be the reason the ILS couldn't be recognised as it might be associated with the STAR. If that's the case I can understand why it needs to have the current frequency. LIEO_ADEX_ADE_enhanced.bgl
  11. Hi Urs, Thanks for the link. This is a third party airport and the associated BGL containing the ILS frequencies seems up to date. If I attach it would you be able to verify its accuracy? I have used Herve’s updated data before but not currently. I’m not sure how his could help in this situation as it’s not a default AFCAD.
  12. Hi gents, P3D v5.3HF2 running ORBX LIEO. I have a current Navigraph cycle - 2401 - but can't reconcile the issue of EFB showing no localiser available for Rwy 23 ILS. The frequency is 111.30 which appears to be correct from searches. The attached screenshot confirms this as the correct frequency and when I tune it in P3D it comes alive. So why is EFB reporting none available? I'm confortable editing AFCADs with ADE if required.
  13. Hi Urs, This is proving troublesome. The scenery affected is added via add-on.xml rather than an entry in scenery.cfg. So I changed all 9 entries to scenery.cfg using Addon Organizer. I then added \add.scenery\ to the file BglSceneryExclude.txt. But when running the database update the log produces this entry. Same for all bar the airport name... Warning : Path 'C:\p3dv5\Flightbeam\Flightbeam - KDEN\scenery\add.scenery\Flightbeam\Flightbeam - KDEN\scenery' in C:\p3dv5\Flightbeam\Flightbeam - KDEN\scenery\add.scenery\add-on.xml does not exist Debug : -- No scenery category found in: C:\p3dv5\Flightbeam\Flightbeam - KDEN\scenery\add.scenery\add-on.xml Any ideas how to resolve this please?
×
×
  • Create New...