• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

NDB doesn't appear to be working

DragonflightDesign

Resource contributor
Messages
892
Country
northernireland
Code:
<?xml version="1.0"?>
<FSData
    version="9.0"
    xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance'
    xsi:noNamespaceSchemaLocation="bglcomp.xsd">
    <Ndb
        lat="52.4493"
        lon="8.4947"
        alt="1.77"
        type="H"
        frequency="338.00"
        range="200N"
        magvar="0.0"
        region="NA"
        ident="WSALP"
        name="Weather Ship Alpha">
    </Ndb>
</FSData>
It compiles fine but when I tune it in the sim (FSX, P3Dv4 & 5) it doesn't come up. Can anyone spot the error? The position is just north of Shannon where another NDB (OL) exists on freq 339.0. I picked the lat/lon/alt as being a known parameter for testing.
 

DragonflightDesign

Resource contributor
Messages
892
Country
northernireland
No, still doesn't work, even after adding the negative signs for north and west. This is a completely clean installation of P3Dv5.0, so here should be no interference from add-on areas and the scenery is set to be priority 2 (priority 1 is the internal Visual FX tool). Base on what Paul said in the other hthread, the current xml test code is
Code:
<?xml version="1.0"?>
<FSData
    version="9.0"
    xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance'
    xsi:noNamespaceSchemaLocation="bglcomp.xsd">
    <Ndb
        lat="-52.4493"
        lon="-8.4947"
        alt="1.77"
        type="H"
        frequency="338.0"
        range="150N"
        magvar="0.0"
        region="EI"
        ident="WSALP"
        name="Weather Ship Alpha">
    </Ndb>
</FSData>
 
Messages
1,360
Country
scotland
Hi Folks

Dai -
Your two examples both show up in FSX.

RANGE - Were you testing from within a close enough distance ?
v1 == Oppendorf, Germany
v2 == Bouvet Island, Antarctica
BTDTGTTS :)

IRL & Sim
North == Positive
East == Positive

In-Game MAP
? Depends on 'Intl Settings', or legacy USAnian code ?
Whatever,
if in doubt, prefix NSEW, (without SIGNAGE)

IDENT -
5 char IDENT == 5 char MORSE == PITAssEar


Here's a working example for JULIET at IRL location -
XML:
<?xml version="1.0"?>
<FSData
    version="9.0"
    xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance'
    xsi:noNamespaceSchemaLocation="bglcomp.xsd">

<Ndb
    name="4YJ - Weather Ship Juliet"
    ident="4YJ"

    region="EG"
   
    frequency="510.0"
    range="150N"
    type="HH"

    lat="52.50"
    lon="-20.00"
    alt="1.77"
    magvar="0.0"
    >
</Ndb>

</FSData>
PS
Did my other thread's NDB file work OK in P3D ?

HTH
ATB
Paul
 

DragonflightDesign

Resource contributor
Messages
892
Country
northernireland
Stoopidity rulz KO. Still had my lat/lon signage reversed.... :banghead: :banghead: The code I posted in the other thread is the code provided in the SDK, so I'd expect it to work, which what confused me. The only slightly glimmering candle was my choice of any old ident code - NA (North Atlantic)- which was actually the correct one. 'NAT' is the full version.

Anyway, all working now. Thank you very much for your help :D
 
Top