How manage conflicts

erasam
New Member

Posts: 3

How manage conflicts Dec 8, 2020 10:31:24 GMT

Post by erasam on Dec 8, 2020 10:31:24 GMT

I have executed the conflict search of FSXP3D_WorldNavaids and several items have been collected (as following grouped by add-on scenery folder)

BEG (VORDME) Freq: 114,95 [Path: H:\Games\Microsoft Flight Simulator X\Addon Scenery\LIME\Scenery\LIME_MAIN_FSX.bgl]
ORI (NDB) Freq: 376,5 [Path: H:\Games\Microsoft Flight Simulator X\Addon Scenery\LIME\Scenery\LIME_MAIN_FSX.bgl]
ORI (VORDME) Freq: -0,01 [Path: H:\Games\Microsoft Flight Simulator X\Addon Scenery\LIME\Scenery\LIME_MAIN_FSX.bgl]

BLA (VORDME) Freq: 116,10 [Path: H:\Games\Microsoft Flight Simulator X\Addon Scenery\LILE\Scenery\APE-LILE-v1_0.BGL]

CAS (LOC) Freq: 117,95 [Path: H:\Games\Microsoft Flight Simulator X\Addon Scenery\LIMF\Scenery\AFX_LIMF-V1_0a.BGL]
CSL (VORDME) Freq: 116,75 [Path: H:\Games\Microsoft Flight Simulator X\Addon Scenery\LIMF\Scenery\AFX_LIMF-V1_0a.BGL]
ITOC (ILSDME) Freq: 108,70 [Path: H:\Games\Microsoft Flight Simulator X\Addon Scenery\LIMF\Scenery\AFX_LIMF-V1_0a.BGL]

CIA (ILS) Freq: 109,90 [Path: H:\Games\Microsoft Flight Simulator X\Addon Scenery\LIRA\Scenery\LIRA_Project.BGL]

GSE (ILSDME) Freq: 109,30 [Path: H:\Games\Microsoft Flight Simulator X\Addon Scenery\LIMJ\Scenery\LIMJ Airport.bgl]

IAOS (ILSDME) Freq: 109,75 [Path: H:\Games\Microsoft Flight Simulator X\Addon Scenery\LIMW\Scenery\APE_VVTo-LIMW.BGL]
SCS (VORDME) Freq: 109,25 [Path: H:\Games\Microsoft Flight Simulator X\Addon Scenery\LIMW\Scenery\NVE_VVTo-LIMW.BGL]
SVC (NDB) Freq: 418,0 [Path: H:\Games\Microsoft Flight Simulator X\Addon Scenery\LIMW\Scenery\NVE_VVTo-LIMW.BGL]

ITO (ILSDME) Freq: 110,55 [Path: H:\Games\Microsoft Flight Simulator X\Addon Scenery\LICJ\scenery\LICJ_ADEX_ON.BGL]
ITO (ILSDME) Freq: 110,55 [Path: H:\Games\Microsoft Flight Simulator X\Addon Scenery\LICJ\scenery\LICJ_ADEX_AI.BGL]
PAL (VORDME) Freq: 112,30 [Path: H:\Games\Microsoft Flight Simulator X\Addon Scenery\LICJ\scenery\LICJ_ADEX_ON.BGL]
PAL (VORDME) Freq: 112,30 [Path: H:\Games\Microsoft Flight Simulator X\Addon Scenery\LICJ\scenery\LICJ_ADEX_AI.BGL]
PRS (VORDME) Freq: 113,00 [Path: H:\Games\Microsoft Flight Simulator X\Addon Scenery\LICJ\scenery\LICJ_ADEX_AI.BGL]
PRS (VORDME) Freq: 113,00 [Path: H:\Games\Microsoft Flight Simulator X\Addon Scenery\LICJ\scenery\LICJ_ADEX_ON.BGL]
RAI (ILSDME) Freq: 109,50 [Path: H:\Games\Microsoft Flight Simulator X\Addon Scenery\LICJ\scenery\LICJ_ADEX_AI.BGL]
RAI (ILSDME) Freq: 109,50 [Path: H:\Games\Microsoft Flight Simulator X\Addon Scenery\LICJ\scenery\LICJ_ADEX_ON.BGL]

VEN (ILS) Freq: 109,95 [Path: H:\Games\Microsoft Flight Simulator X\Addon Scenery\LIPZ\scenery\LIPZ_ADEX_Vic171025.bgl]
VEN (NDB) Freq: 379,0 [Path: H:\Games\Microsoft Flight Simulator X\Addon Scenery\LIPZ\scenery\LIPZ_ADEX_Vic171025.bgl]

ZR (ILSDME) Freq: 109,35 [Path: H:\Games\Microsoft Flight Simulator X\ORBX\FTX_GLOBAL\FTX_FTXG_AIRPORTS\Scenery\ADE_FTX_FTXG_LFMU.BGL]
AS (ILSDME) Freq: 108,90 [Path: H:\Games\Microsoft Flight Simulator X\ORBX\FTX_GLOBAL\FTX_FTXG_AIRPORTS\Scenery\ADE_FTX_FTXG_LFJR.BGL]
AUB (NDB) Freq: 427,0 [Path: H:\Games\Microsoft Flight Simulator X\ORBX\FTX_GLOBAL\FTX_FTXG_AIRPORTS\Scenery\ADE_FTX_FTXG_LFHO.BGL]
CS (NDB) Freq: 345,0 [Path: H:\Games\Microsoft Flight Simulator X\ORBX\FTX_GLOBAL\FTX_FTXG_AIRPORTS\Scenery\ADE_FTX_FTXG_LFMK.BGL]
CS (ILSDME) Freq: 111,10 [Path: H:\Games\Microsoft Flight Simulator X\ORBX\FTX_GLOBAL\FTX_FTXG_AIRPORTS\Scenery\ADE_FTX_FTXG_LFMK.BGL]
DV (ILSDME) Freq: 111,55 [Path: H:\Games\Microsoft Flight Simulator X\ORBX\FTX_GLOBAL\FTX_FTXG_AIRPORTS\Scenery\ADE_FTX_FTXG_LFRG.BGL]
RDE (ILSDME) Freq: 110,75 [Path: H:\Games\Microsoft Flight Simulator X\ORBX\FTX_GLOBAL\FTX_FTXG_AIRPORTS\Scenery\ADE_FTX_FTXG_LFCR.BGL]

IBZ (LOCDME) Freq: 109,10 [Path: H:\Games\Microsoft Flight Simulator X\ORBX\FTX_GLOBAL\FTX_FTXG_AIRPORTS\Scenery\ADE_FTX_FTXG_LIPB.BGL]
IPE (ILSDME) Freq: 110,95 [Path: H:\Games\Microsoft Flight Simulator X\ORBX\FTX_GLOBAL\FTX_FTXG_AIRPORTS\Scenery\ADE_FTX_FTXG_LIRZ.BGL]
IPR (ILS) Freq: 110,50 [Path: H:\Games\Microsoft Flight Simulator X\ORBX\FTX_GLOBAL\FTX_FTXG_AIRPORTS\Scenery\ADE_FTX_FTXG_LIMP.BGL]

IHH (ILSDME) Freq: 108,75 [Path: H:\Games\Microsoft Flight Simulator X\ORBX\FTX_GLOBAL\FTX_FTXG_AIRPORTS\Scenery\ADE_FTX_FTXG_EBLG.BGL]
IKT (LOCDME) Freq: 110,70 [Path: H:\Games\Microsoft Flight Simulator X\ORBX\FTX_GLOBAL\FTX_FTXG_AIRPORTS\Scenery\ADE_FTX_FTXG_EBKT.BGL]
ILG (ILS) Freq: 109,35 [Path: H:\Games\Microsoft Flight Simulator X\ORBX\FTX_GLOBAL\FTX_FTXG_AIRPORTS\Scenery\ADE_FTX_FTXG_EBLG.BGL]
ILGP (ILSDME) Freq: 109,35 [Path: H:\Games\Microsoft Flight Simulator X\ORBX\FTX_GLOBAL\FTX_FTXG_AIRPORTS\Scenery\ADE_FTX_FTXG_EBLG.BGL]
LG (NDB) Freq: 348,5 [Path: H:\Games\Microsoft Flight Simulator X\ORBX\FTX_GLOBAL\FTX_FTXG_AIRPORTS\Scenery\ADE_FTX_FTXG_EBLG.BGL]

ONL (NDB) Freq: 290,0 [Path: H:\Games\Microsoft Flight Simulator X\ORBX\FTX_GLOBAL\FTX_FTXG_AIRPORTS\Scenery\ADE_FTX_FTXG_EBLG.BGL]

IPRV (ILSDME) Freq: 110,90 [Path: H:\Games\Microsoft Flight Simulator X\ORBX\FTX_GLOBAL\FTX_FTXG_AIRPORTS\Scenery\ADE_FTX_FTXG_LGPZ.BGL]

IST (ILS) Freq: 110,50 [Path: H:\Games\Microsoft Flight Simulator X\ORBX\FTX_GLOBAL\FTX_FTXG_AIRPORTS\Scenery\ADE_FTX_FTXG_LDSP.BGL]
TRI (NDB) Freq: 378,0 [Path: H:\Games\Microsoft Flight Simulator X\ORBX\FTX_GLOBAL\FTX_FTXG_AIRPORTS\Scenery\ADE_FTX_FTXG_LDSP.BGL]

MAR (ILSDME) Freq: 109,70 [Path: H:\Games\Microsoft Flight Simulator X\ORBX\FTX_GLOBAL\FTX_FTXG_AIRPORTS\Scenery\ADE_FTX_FTXG_GMMX.bgl]

NNN (ILS) Freq: 108,70 [Path: H:\Games\Microsoft Flight Simulator X\ORBX\FTX_GLOBAL\FTX_FTXG_AIRPORTS\Scenery\ADE_FTX_FTXG_ESNN.BGL]
OS (NDB) Freq: 378,0 [Path: H:\Games\Microsoft Flight Simulator X\ORBX\FTX_GLOBAL\FTX_FTXG_AIRPORTS\Scenery\ADE_FTX_FTXG_ESNN.BGL]
SNN (ILS) Freq: 110,30 [Path: H:\Games\Microsoft Flight Simulator X\ORBX\FTX_GLOBAL\FTX_FTXG_AIRPORTS\Scenery\ADE_FTX_FTXG_ESNN.BGL]
SU (ILSDME) Freq: 110,90 [Path: H:\Games\Microsoft Flight Simulator X\ORBX\FTX_GLOBAL\FTX_FTXG_AIRPORTS\Scenery\ADE_FTX_FTXG_ESSU.BGL]

Actually I don't know how to sort them out...

Herve Sors
Administrator

Posts: 727

How manage conflicts Dec 8, 2020 11:21:37 GMT

Post by Herve Sors on Dec 8, 2020 11:21:37 GMT

There's nothing to sort. It is just for your information. Several addon sceneries you installed define navaid data on their own that probably supersede default stock data contained in my updates. Now it's up to you to check that what they provide is OK. If not, you will have 4 options
- uninstall the addon scenery so as default stock data are restored
- ask the addon scenery designer to correct scenery navaid data (preferred but rarely carried out)
- correct them by yourself (or let me know if you are not familiar with available tools for doing that)
- continue living with current anomalies if it does not disturb your sim pleasure too much..

-H

Last Edit: Dec 8, 2020 11:28:20 GMT by Herve Sors

erasam New Member Posts: 3	How manage conflicts Dec 14, 2020 22:14:09 GMT Select Post Deselect Post Link to Post Member Give Gift Back to Top Post by erasam on Dec 14, 2020 22:14:09 GMT Hi is there an easy way to undertand if they are actually the same data replicated (that means the add-on scenery doesn't affect it) or there are real differences to correct ? Moreover I'm unfrtunately not so able to correct them

Herve Sors
Administrator

Posts: 727

How manage conflicts Dec 14, 2020 22:29:16 GMT

Post by Herve Sors on Dec 14, 2020 22:29:16 GMT

>>is there an easy way to undertand if they are actually the same data replicated (that means the add-on scenery doesn't affect it) or there are real differences to correct ?<<
not absolutely an easy way but at least you could check identifiers, frequencies and positions as well as how it affects or not sim behavior
Also check ORBX forums and discussions on other scenery you installed to identify possible known problems
In case you detect a problem or it is a known one, then solutions are quoted in my previous answer

erasam
New Member

Posts: 3

How manage conflicts Dec 17, 2020 7:42:44 GMT

Post by erasam on Dec 17, 2020 7:42:44 GMT

In the search for conflicts I think it could be useful to see if there are real conflicts and the details of it (for example a NDB frequency has been changed from XXX to YYY, LAT/LON has been mooved from XXXX to YYYY) otherwise it is really common to have conflicts with add-on scenery (any of these can include items that are overcominf standard scenery) and manual corrections would be a nightmare

niksan29
Moderator

Posts: 101

How manage conflicts Dec 17, 2020 8:40:34 GMT

Post by niksan29 on Dec 17, 2020 8:40:34 GMT

HI!

unfortunately, there is no other way but manual comparison

the conflicts button is just a "link" to help with begin manual checking: too many parameters may differ:
for ILS: beam width, glide slope, heading, offset, range, alt, coordinates, name.
for NDB and VOR\DME: range, alt, coordinates, name.

for a start, you can open the sim map and see if there are any duplicate nav aids that are indicated in the list of conflict

NDB, VOR\DME and markers will definitely have a duplicate,because the logic sim engine does not allow to exclude them aids.
but it's not as bad as I remember (but maybe I'm wrong, I need to check), in this case, the stock nav aids will also have priority, that is, when entering the correct frequency in nav instrument on a sim aircraft, it will be used nav aids from the stock files(which are replaced by the update from aerosors, that is, they will be correct) even if there are two identical nav aids on the map with the same frequency.
if we talk about ILS, then duplicates will be only if ILS ID does not match, if ILS ID match then, according to the logic sim engine, the sim will use ILS from a third-party decoration(but in 99 % there will be differences from the real ) and exclude stock ILS.

P/S
also I want to remind: updates are meant to be used without third party decoration addons,if you use third-party decorations, you will have to fix everything manually, the decor designer will hardly help you

Last Edit: Jan 12, 2021 15:54:29 GMT by niksan29

Cheers!

niksan29
Moderator

Posts: 101

How manage conflicts Jan 12, 2021 15:53:42 GMT

Post by niksan29 on Jan 12, 2021 15:53:42 GMT

Dec 17, 2020 8:40:34 GMT niksan29 said:

NDB, VOR\DME and markers will definitely have a duplicate,because the logic sim engine does not allow to exclude them aids.
but it's not as bad as I remember (but maybe I'm wrong, I need to check), in this case, the stock nav aids will also have priority

i had some free time and i some tests regarding this question:

-in case if ID for NDB, VOR\DME will match, then your navigation devices will use third party NDB, VOR\DME(not stock), I also noticed that in this case, duplicates of NDB will be displayed (on the standard sim map), but duplicates VOR\DME will not be displayed(but the arrow points in its direction and distance).
that is, if your scenary has the wrong(inaccurate coordinates\range\name\alt) nav aids but with the correct ID, then they will be used

-in case if ID for NDB, VOR\DME not match,but the frequency matches, then all NDB, VOR\DME will be displayed (on the standard sim map) then your navigation devices will use third party NDB, but attention not third party VOR\DME, it is used by the stock, in one word the sim is full of surprises

regarding ils everything is as I said in the message above

as for markers, there will always be duplicates (if they are in both scenes), they do not overlap, the closest will probably be used...

summarize the conclusion,we have several options:

1)only use stock ports after upgrade from aerosors(it only depends on whether you like the stock landscape
or not and this is also the recommended way if you are using updates)

2)use third-party scenes and fix everything yourself (a lot of work, almost unrealistic)

3)use third-party scenes and ask the developer to fix (almost unrealistic)

3)use third-party scenes and upgrade from aerosors + self manual fixes (my choice, this way we will significantly facilitate our work)

I hope someone will find it useful

Last Edit: Jan 13, 2021 14:46:36 GMT by niksan29