dnunes

Dear Alex and Stamatis,As I cannot attach a file of the bgl type, I am sending the corrected bgl file, for both Nice and Genoa, to your email address.Alex, as you asked for a brief tutorial, I will try to provide one.First of all you should obtain the correct co-ordinates from AFCAD. With this programme you can also create new navaids for airports that do not have them (as I have mentioned before I created an ILSDME for a small airstrip near Lisbon, but I erased it from the file I am now sending).I think you are used to AFCAD, so there should be no problem with this.In the EasyNavs diretory you will find four utilities, one for each of the Navaids: ILS, VOR, NDB and Markers. In this case you will start the EN2KILS utility.Then on the menu ILS Tools, you will choose Extract ILS Navaids. This prompts you to the FS2002 directory and, in the case of Genoa, you will select Scenedb>Easthem>eursw>scenery>eurswils.bgl.Then, in Easynavs you will select Make database. This will create the eurswils.ils file in the Easynavs directory. This is the file you will be editting.I think the form that is presented to you is self explanatory. In the case of Genoa, to edit the ILS, you will look for the GSE facility. Then you edit it, as required. In the end you choose Save to save the editted file.After quitting this editting form you will choose, in the main menu, Make BGL file. This uses the *.ils file to create the *.bgl file.You will then copy this file to replace the original *.bgl file in the FS2K2 directory. A backup of the original file is of course recommended. If you intend to keep it in the original directory I would advise you to change the extension (e.g. bgl to bglold) and not the file name, as this seems to have been in the origin of the problems I had to obtain a corrected file.Please contact me again if you need further assistance.Best Regards,

Dear Alex and Stamatis,I have been able to get a file that is corrected, although I do not fully understand why it took me so much time to arrive at it. I think I had in the course of my trials some problems due to renamed files.Even now a mystery persists: to obtain the correct DME and GS location I had to define their co-ordinates separately. It should be noted that EasyNavs has a facility "DME at GS" that (should) avoid to input two times the same set of co-ordinates. When I do this I get a wrong location.Anyhow the file is now producing a correct result, as you can see from the attached screen shot. I will be glad to either give you the procedure to follow in case you have EasyNavs. Otherwise I can send the eurswils.bgl file, which also has the Nice correction.Best Regards,

I forgot to add the second screen shot. Here it is.

Dear All,I think we are now mixing up LFMN (Nice C

Dear Alex,Stamatis is right. With AFCAD you will not change the Navaids co-ordinates. You will use AFCAD to locate your navaids and get the co-ordinates. Then, with EasyNavs you can correct or install new navaids. This is done (in the case of SW Europe) editting the file eurswils.Regards,

Dear Alex and Stamatis,The DME can be located anywhere, as you can define its co-ordinates independently of the localizer and GS. When you have an ILSDME you usualy locate it at the GS.What I can tell you is that something strange is happening with this particular ILS. As I said before, when I first looked at the problem I found a wrong location for the GS and DME: both were at the localizer co-ordinates. Then I corrected the co-ordinates for the GS and DME, and amazingly nothing changed!As you can have the aircraft position shown in AFCAD, I even checked that that the co-ordinates provided by AFCAD were consistent with F2K2. I will work on it a little more next weekend.Best Regards,

Alex,That is true, according to the GS you should be much higher, but the VASI shows that you within limits.Next weekend I will try again to make some tests, trying to understand what is happening. There seems to be something strange with this airport. As I have told in my first post, the Nice airport had a similar problem. I corrected it and now it is OK.As a further test I installed an ILS in an airfield, near the Lisbon airport, which of course has no ILS in real life. I followed the common procedure, i.e., I located the navaids with the help of AFCAD and used the coordinated provided by AFCAD to locate the localizer, GS and DME using EasyNavs. Everything worked nicely: the DME shows zero when I am at the threshold and the GS brings me to the numbers in the runway. This assured me that I can locate correctly the navaids. Surprisingly that seems not to work in Genoa!I will let you know if I make some progress on this subject.Best Regards,

Dear Alex,You are in the same situation I have found: on the second shot you are almost at the threshold and the DME reads 1.6 miles (this is the far end of the runway, where the localizer is installed). On the other hand the GS shows you are very high: although the Jeppesen chart says the GS is erroneous below a certain point, I do not believe FS can simulate this, as there is no special configuration for the ILS.In case you manage to obtain the correction, please send me the eurswils file so that I can compare it with mine.What puzzles me is that I found the original file was wrong, with the localizer, GS and DME at the same co-ordinates. I changed the GS and DME to the location indicated by AFCAD, which seems to be correct, and the result was exactly the same!Best Regards,

Thanks Alex for your reply. I still feel there is something wrong. The DME is at the same location as the GS, i.e. at the displaced threshold. My Jeppesen chart says that the ILSDME reads zero at this point, what would be normal. However if I taxi my aircraft to that position the DME reads 1.6 miles. This is the location of the localizer at the far end of the runway! The distances to GSE, in the Jeppesen chart show correctly the distances to the displaced threshold, what is correct, as the DME is at that location, but that is not what I get when flying an approach.If you have EasyNavs, could you please send me the configuration you have for GSE? I think that could help.Thanks for your help.

You can get AFCAD here at Avsim. Look for the file name or for the author's name : Lee Swoordy.Regards,

I have found an error in the Genoa ILS (ID=GSE) similar to that in Nice: the GS is at the same location as the localizer, resulting in a wrong glidpath. The DME also shows the distance to the localizer and not to the runway threshold, as it should.While I had no problem in correcting the error in Nice, I am not able to make the correction in Genoa. I get the correct coordinates for the localizer and GS using AFCAD, which shows the correct location, and use them in EasyNavs to modify the bgl file.The problem is that the correction is not effective, as I always get the same glideslope and DME error.Has someone an explanation for this? I would be grateful for any help.Best Regards,

Certainly Bill Grabowski's ERJ-145 Panel is one of the best, what seems to be a common opinion. But what about Yannick's Falcon 50? For me, although not as realistic as Bill's panel, is a great one, combining to the possible extent the reality with the constraints of a PC simulator.

I have made several flights from M

I have a much less powerful machine then you have (AMD's K6 at 450MHz,128MB memory). Under FS2000 I had the same problem you report: very frequent hangups, with the sound still running. I tried many suggestions, it sometimes seemed to get better, but I would always have the same problem.Then I installed FS2002 and hangups WERE OVER! I think that FS2002 is much more balanced in the use of system resources. I manage to get a reasonable compromise between graphics resolution and frame rates, which are normally better then they were with FS2000.Regards,

Thanks a lot. I could not find the link in your site, but I managed to get it from Avsim, after searching for the author's name. I already had done that but I think I misspelled the name.Next I will get some of your repaints!Regards,

After reading your comments, and as I have other ATR airplanes, I tried to download the one you have praised so much. The problem is that I cannot find it in Avsim. Will you please inform where it is?Thanks in advance.Best Regards,

Thanks a lot. As I already had downloaded the file sometime ago and ran into problems, I think the best will be to uninstall everything and start with a recent file!Best Regards,

It seems there is now an installer for the Project Airbus's A320. Will someone please tell me where I can find it?Thanks in advance.

I have performed the installation according to your procedure. I must have something wrong because:a) The panel is that of a default 737:( All the plane is black: both the outside and the inside when in VCI see in the configuration file that a 737 panel is used, but there are lots of A320 specific gauges. When do you see them?Any idea of what might be wrong with the texture? I realize I have a poor graphic system, but it never happened with any other plane.Can you provide some help?Regards,

Thanks Eric for your message. I have understood your comment.As Brynjames has asked, here is what I have done:I used AFCAD to check the location of the navaids at Nice Cote d'Azur. They seemed OK, and in line with the information in the Jeppesen charts.Then I used the EasyNavs tool to extract the eurswils.bgl file. I noticed it had the error I reported: the GS had the same coordinates as the localizer. I changed the location of the GS, as per the information provided by the AFCAD tool. I replaced the original file with the one generated by the EasyNavs tool and everything was then correct.You can download the EasyNavs utility from Avsim.Regards,

I am glad someone was able to read English and not quickly jump into "nice" comments...The problem is not of course with the offset localizer, but with the glide slope. It happens that last Sunday I was able to see where the bug was and correct it. The problem with the glide slope was that it had the same coordinates as the localizer, i.e., at the far end of the runway!As I had the correct coordinates for the GS, which I got using AFCAD, I corrected the bgl file and now everything is correct.Thanks to all those that gave attention to my problem.Best Regards,

Since FS2K I have found a problem with the glide slope of runway 4R at the Nice Airport (LFMN): when using the ILS approach the A/C will run beyond the runway without coming to the ground.The same problem happens in FS2K2.Today I saw a file, to be installed using AFCAD, that would result in slight changes in the location of the localizer and glidepath. I installed it but the problem persists: following the glidepath the A/C passes over the threshold of the runway some 300 feet above. The VASI lights show that I am too high.For the runway 4L everything is OK, and I come to the runway normally.Has anyone experienced this problem? Is there any correction for it?I hope someone can help!Regards,

I have been following your discussion with interest. Where can I find GPSout.zip?Thanks in advance,I have already found it, so please ignore this message!

Thanks a lot for your information. I suppose I can find them in the Avsim Library, right?Regards,

This is only(?) a panel. What aircraft would you recommend?Thanks in advance.Domingos