PilotBobUK

Hi Guys, thanks to the various replies I've had to this post I now understand how this works to a far better degree than before. I hadn't realised the nav aid data was contained in the scenery files, that accounts for the original installation using a nav aid database dated around 2004. At that time Lydd did have a DME and NDB but no ILS. I came across a program (World FSXP3D package https://www.aero.sors.fr/navaids3.html) which updates the nav aid database to the latest airac cycle. After running this, FSX now has up to date nav aids including Lydd and Southend. I've been able to successfully fly a full instrument approach into both airports without a hitch. (Nil wind you understand ) So I'm back up and running, now I just need to tune the controls a litle bit to make things more realistic but delighted to have finally got somewhere at last. Thanks again to everyone for your input. I wonder if my instructor would accept a printout of the flight analysis in order to sign off the approach?

Hmmm, that's kinda what I was afraid of

Well guys, thank you for your willingness to assist but I think I'm just gonna give up on FSX. I've tried everything I can think of including looking at the various .cfg files and altering one or two settings there all to no avail. So I tried uninstalling "Acceleration" and my VFR scenery files then FSX, then deleting the FSX folder. Then I re-installed FSX on it's own. Now I can get the ILS/Loc and DME to work at Lydd but attempting to fly the approach via the 14DME arc was fine until it came to intercepting the localiser. The aircraft flew straight through it with not so much as a flicker of the Localiser needle. It's all just so frustrating getting one thing to work then another seems to fall over. Maybe I'll try MSFS2020 when I can raise a few more beer vouchers to buy it, or should I wait for 2024 to be released?

Thanks guys, to answer a couple of questions, Lydd does have a co-located DME coupled to the ILS frequency. I have a print of an approach I did some while ago using FSX before the HD failure which clearly shows the 14DME arc was flown, so I'm sure it was working before. I have tried setting another VOR (DET) on Nav 1 and distance is then shown properly. I also tried an approach to Southend, unfortunately it wouldn't lock on to the localizer there either. I am using the Carenado PA28 but have also tried the stock 172 with the same results. I will have a look at the aircraft.cfg file to see if anything is obvious but I think I'll probably be out of my depth there.

Thanks guys, to answer a couple of questions, Lydd does have a co-located DME coupled to the ILS frequency. I have a print of an approach I did some while ago using FSX before the HD failure which clearly shows the 14DME arc was flown, so I'm sure it was working before. I have tried setting another VOR (DET) on Nav 1 and distance is then shown properly. I also tried an approach to Southend, unfortunately it wouldn't lock on to the localizer there either. I am using the Carenado PA28 but have also tried the stock 172 with the same results. I will have a look at the aircraft.cfg file to see if anything is obvious but I think I'll probably be out of my depth there.

Hi all, having re-installed my FSX due to a HD failure, into a clean Win 7 system using i7 3770 and GTX970 I'm delighted with how the aircraft fly. However I want to be able to use it for instrument training and have tried to fly the ILS into LYDD (EGMD) This requires ADF and DME as the initial approach is a 14m DME arc at 3200ft until intercepting the Localizer. I set the ILS frequency on Nav 1 to LYDD ILS (108.15) and DME to R1. The DME shows no didtance to the beacon. If I set DET (117.30) on Nav 2 then select R2 on the DME it works perfectly. It just stubbornly refuses to pickup the ILS distance, which makes flying the proceedure impossible. Any ideas what's happening?

Well it sure looks like we've found the problem, until I find a way to alter the VC a workaround is to fly using the 2D cockpit view which gives me the new instruments I put in using FSPS. At least I can now practice my instrument approaches again. If anyone has any further ideas they would be much appreciated. Thanks for the help so far.

This all sounds more likely, the thing is I'm sure I did have some years ago, at least a DME in the panel as I used it to fly the ILS approach at LYDD which requires a DME. SInce having to re-install everything due to a hard drive failure I've lost everything I prevoiusly had.

Thanks for the input, I sort of thought something like that was happening, however on looking into it I have no "panel" files in the "Virtual store", back to the drawing board.

Hi everyone, I'm using FS Panel Studio and am really struggling with modifying the panel in My FSX Carenado Cherokee. I've opened Panel.cfg by aircraft and picked the Main Panel. Here I have deleted the radio stack and replaced it with 2 x GNC255's, Bendix DME and ADF. I then saved the file and ran FSX, but the panel is the same as the original one. I also noticed that the basic bitmap for the panel in Panel Studio is not the same one as the model I'm flying in FSX. I've also tried to modify the stock MS C172 in the same way but still no changes. What is going on here? am I doing something wrong? any ideas? FSX running in Win 10 with a complete new install.