Hi,

I'm running LNM beta 3.0.1, but the same problem is also in 2.8.12. I am not fully understanding the airport rating. According to the instructions you get one start for:

1. Addon

2. Parking

3. Apron

4. Taxiways

5. Tower

Besides it's a bit questionable if Apron and taxiway should be separated (many addon airports don't have aprons by design, as they use ground polygons), i noticed that the "addon" flag only works if the scenery is ONLY present out of the main scenery folder, i.e. it's not existing in the default airport database. If it's an update on an EXISTING default airport, then it does not get the start.... is there something wrong with my installation, it's a bug or a wanted feature? PS: "addon" is correctly listed in the "facilities" list of the airport information tab as expected, and the yellow overlay mark is also present, so LNM recognizes it as an addon airport.

 

The method has to deal with all kind of simulators and add-ons. I see no need to change it and I also checked the code. The addon is applied correctly.

Alex

Thanks for answering. I see. So should be a problem of my installation if there i never get the star for addon sceneries, even if they are recognized as such.

Final question (unrelated): i noticed that if I use ADE to modify some default VOR or navaid (mainly frequency), in LNM it gets duplicated. It finds the original one and the updated one, and keeps displaying both... is this normal? Also it seems like there is no code implemented to VOT-type of VORs.... VOT are useless in general, but it's a trick to make a default VOR disappear withing FS....

 

11 minutes ago, arrex said:

Thanks for answering. I see. So should be a problem of my installation if there i never get the star for addon sceneries, even if they are recognized as such.

I just debugged through the code and it seems than not all attributes from an add-on are considered by LNM when overwriting a stock airport. Will check. This might affect MSFS add-ons too. Does not happen in all cases.

 

12 minutes ago, arrex said:

Final question (unrelated): i noticed that if I use ADE to modify some default VOR or navaid (mainly frequency), in LNM it gets duplicated. It finds the original one and the updated one, and keeps displaying both... is this normal? Also it seems like there is no code implemented to VOT-type of VORs.... VOT are useless in general, but it's a trick to make a default VOR disappear withing FS....

FSX has no update mechanisms for navaids. You can only do this reliably by replacing stock files. LNM simply removes obvious duplicates for navaids with the same name at roughly the same position (did not check the code, this is what I remember).

Alex

6 minutes ago, albar965 said:

I just debugged through the code and it seems than not all attributes from an add-on are considered by LNM when overwriting a stock airport. Will check. This might affect MSFS add-ons too. Does not happen in all cases.

I see. From what i see, most properties are properly taken from addon airports (layout, frequencies).... I actually only found this inconsistency on the rating. Not a big deal anyway.
 

7 minutes ago, albar965 said:

FSX has no update mechanisms for navaids. You can only do this reliably by replacing stock files. LNM simply removes obvious duplicates for navaids with the same name at roughly the same position (did not check the code, this is what I remember).

That's fairly correct. You cannot exclude any type of navaid, but you can override some information. For VOR these are the type (VOR, DME, VOR+DME or VOT), the range and the frequency. If the navaid is moved more than a certain amount, it "gets duplicated". What I noticed is that if I just change the frequency and not the position, LNM duplicates it. So something must have gone wrong in the code. And I also noticed that VOR defined as "VOT" are simply listed as VORDME, like that property is not considered.

 

2 minutes ago, arrex said:

That's fairly correct. You cannot exclude any type of navaid, but you can override some information. For VOR these are the type (VOR, DME, VOR+DME or VOT), the range and the frequency

Changing frequency only should not create duplicates. Not sure about type. Will check.

Edit: VOT is not used in LNM. It appears only in FSX documentation so far. I've never seen it in the wild.

Alex

Edited January 23, 20242 yr by albar965

12 minutes ago, albar965 said:

Changing frequency only should not create duplicates. Not sure about type. Will check.

Edit: VOT is not used in LNM. It appears only in FSX documentation so far. I've never seen it in the wild.

Thanks.

Regarding VOT it is not used because FS (and AFAIK P3D) do not use them. And hence it becomes a trick to hack FS limitations: if you need to "delete" a VOR, you can set it in an addons as VOT, so it effectively disappears from the simulator.... Some sceneries (including mine) are using this trick. Was wondering if this can be somehow implemented in LNM (i.e. avoid showing VOTs, or listing as something else, that you can disable, or having a map option "show VOTs")... just a new feature, low priority, suggestion....

 

Rating is now fixed for MSFS, FSX and P3D.

Adding VOT? Unlikely, sry.

Alex

Duplicate VOR are only deleted if ident, region, frequency, type are the same and if they are close to each other.

Can pass me a BGL to test this?

Alex

I can provide you with the BGL, but:

1. you have to tell me how to pass it to you

2. it's a normal ADE file... nothing particular

3. from what you wrote i already see the problem: for the FSX-P3D world (not sure for Xplane and MSFS), you have only to check for ident, region and the "proximity".... frequency and type (guess by type you mean VOR, DME, VORDME or VOT) can be altered by programs like ADE and it's normal way of working to do it. The criterion for "overwriting" is only ident, type and position. In my file i have indeed changed the frequency and hence i get the duplication.

 

Per email: https://albar965.github.io/contact.html 

Saves me a lot of time building a test case.

Alex

Ok, will send it now....

 

Plenty thanks, got it. 👍
Gimme a day or two.

I changed the de-duplication to check only region (unused in FSX and P3D) and ident. Means that you can change type and frequency for updates of VOR and NDB now. Moving navaids far away will still result in duplicates.
The last inserted navaid (add-on) wins and the other (stock) is deleted. This also applies for P3D.

Thanks for the file again. This makes it easier to check if I add this to my test mockup.

Alex