hi Ray

             Clearly a "glitch" somewhere.......but then computers do that now and then.......don't they ?

 

Regards

 

David

 

Indeed they do. I'm convinced they entertain and frustrate in equal measures. :smile:

This was a very curious problem. Makerwys gets its scenery path from scenery.cfg (your library settings) or whatever .cfg file it uses that you set up in the library function. There must have been some restriction somewhere in the original LIRF scenery folder. There also might have been a deletion somewhere in a conflicting add-on. That is why I encourage examining runways.txt as I detailed in a prior post.

 

Glad your folder change got it working.

Hi Ron

                 At your suggestion I have had a good look at the LIRF entries in Runways text.

                 There were some errors reported in there.........

                  I fixed them all except the ILS ident for 34L in the navaid properties.....should be FSW (as per the runway properties)

                  but shows  as ISW and is reported in Runways.txt as a mismatch  error.

                  It seems ISW is in the default scenery file and I cannot change it.

                  Hopefully MakeRwys can cater for this.

                 

Thanks for your help with what was a frustrating but interesting exercise.........I have certainly learned a bit of how FS/RC works.

 

Best regards

 

David

I don't recall but some localiser properties can not be changed at least in FS9. (I think you know that runways.txt is just a log and you does not affect the properties used.)

 

ADE will not let you edit properties that can not be changed.

 

Here is a list from ISD's 2005 version of LIRF.

 

Type,Ident,Name,Freq,Airport,Dist Nm,Comments
ILS,FLL,ILS 16L,108.100 Mhz,LIRF,1.5,
ILS,FSS,ILS 34R,109.300 Mhz,LIRF,2.6,
ILS,FEE,ILS 07,109.700 Mhz,LIRF,0.6,
ILS,FEE,ILS 07,109.700 Mhz,LIRF,0.6,
ILS,FRR,ILS 16R,110.300 Mhz,LIRF,1.4,
ILS,ISW,ILS 34L,108.900 Mhz,LIRF,1.0,
ILS,FNN,DO NOT USE,108.000 Mhz,LIRF,2.7,Orphaned ILS
ILS,ITA,DO NOT USE,108.000 Mhz,LIRF,2.7,Orphaned ILS
MARKER,,OUTER,,,147.2,
VOR/DME,OST,OSTIA,114.900 Mhz,,0.3,
NDB,OST,OSTIA,321.00 Khz,,0.4,

 

exported from ADE.

Hi again Gents

                           I have had the same problem with MakeRwys not recognising an AFCAD again ........with LIPX this time.

                           It seems that if an airport is installed in FS9\Addon Scenery the AFCAD will not be scanned if it is in the

\airport\scenery directory.

                            Shifting the AFCAD to FS9\addon scenery\scenery cures the problem.

                            Very odd !

 

Regards

 

David 

Download link? Need to examine it and install. FSX or FS9.

 

http://www.scruffyduck.org/simple-airport-scanner/4584282795 is a utility (free) designed for situations like these. If this does not pick it up it is a scenery problem installation, permissions, priority, etc. At first run it will index all installed scenery (except default as I recall). Then search for its results for LIPX and check its path. Last listed has priority.

 

https://www.dropbox.com/s/dlyy4966e5eqglq/Simple%20Airport%20Scanner%20LIPX%20F1%20afcad%20display%20copy.jpg?dl=0

 

This is an afcad file added by Ultimate Traffic (Classic) as shown by the scanner.

Thanks Ron.......I'll look into it......

 

Best Regards

 

David

I found a freeware FSX update for FS9 ISD LIPX:

http://realearthx.it/prodotto/lipx-verona-villafranca/ You'll notice a  zero price for checkout. Use Google trasnslator.

 

AVSIM has the FS9 ISD LIPX 2006 plus a service pack.:

 

http://www.freewarescenery.com/fs2004/italy.html

 

and scroll down to near bottom for italy for both links

 

I can install either and downloade all. Which FS version are you using?