• 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.

Next Sde Build.............

I lean toward SDE being picky. I use both types of lat/lon formats in one single large XML and have never had a problem.

There could be a space missing.

I am going to try and find what BGLComp does not see as an error in respect to SDE.
 
Found it

<TaxiwayParking index="8"
type="GATE_SMALL"
name="GATE_F"
number="13"
lat="N33 37.5315'" <------------- apostrophe that should not be there
lon="W084 26.5557"
heading="259.60"
radius="14.1M"
airlineCodes="COAX, USAX, DALX"
teeOffset1="7.92"
teeOffset2="12.19"
pushBack="BOTH"/>

Reminds me of a splinter in my hand that hurts but I can't see it to remove it.
 
Last edited:
Hi Bert

The right window XML does not change. SDE uses the decimal format all the time in the XML.

As for the property grid changing Units works here for me. I change from one to the other then click a new object in the grid to get the change to come into effect. It does not automatically update the object properties that you are looking at - you need to change to another one then back again.
 
Yes

BglComp does not error the apostrophe as long as it is inside the qoutes. I compiled a test xml with additional apostrophes and the compiler did not complain.
 
OK I will have SDE handle them - basically strip them off the incoming XML since they don't really do anything.
 
Wishing functions

Hi, Jon

scruffyduck said:
The function to allow that to happen is not implemented yet but it will be

The Move button which is not activated will provide that function in a later build.
Click to expand...

It would be useful if the "GoTo" (or "Fly Aircraft To") new function opens a little window showing the point coordinates (14 decimals after period) and user's aircraft heading, as TCalcX_002.exe does, and a bit more, identify the QMID and landclass guid or name.

I think you have done this before, in others applications.

Thanks,

José
 
Jon,
As for the property grid changing Units works here for me. I change from one to the other then click a new object in the grid to get the change to come into effect. It does not automatically update the object properties that you are looking at - you need to change to another one then back again.
Click to expand...

Yep, it works for me too. Sorry for the confusion.

Bert
 
I was wondering what the best way to get the Lat and Long format that SDE presents me with, but as I've read in this thread I assume everyone is just entering it as it's displayed in FS and SDE converts it stripping the space, etc. Am I correct?
 
You are correct. Depending on the setting you have to display Lat/Lon in SDE (Degrees, Decimal Minutes DDM for the string representation or Decimal) you can enter that. SDE will display your preference in the Property grid but always use decimal in the XML. Be aware that you can connect to FSX with SDE and copy the lat/lon values directly into an object.
 
Vor/ils/ndb

Hi, Jon

I didn't find navigation aids, as ILS/VOR/NDB, neither the frequencies nor the objects, in the decompiled files, although they are present in the scenery.

Could you please tell me which bgl's types contain those elements, in FSX?

Regards,

José
 
ILS are associated with Runways so as Graham says, you need to check under the runway element. There can be multiple ILS per runway.

For Ndbs again check the Airport Record. SDE will move any Terminal NDBs to the relevant airport record and they are listed by name in the list of elements associated with an airport. The same is true of terminal waypoints. So far I have not found an APX file which contains anything other than ILS, Terminal NDB and Terminal Waypoints. Non airport naviads are listed in the NVX files.
 
Could'nt find a VOR....

Hi, Grahams and Jon

Please, dont take me as a lazy people, but I didn't find my VOR

GrahamS said:
Have a look in the Airport section under Runway, usually at the bottom of that section.
Click to expand...

I'm attaching my xml code. Please, could you point out where there's a VOR in that code?

Code: 
<?xml version="1.0"?>
<FSData version="9.0"
xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance'
xsi:noNamespaceSchemaLocation="bglcomp.xsd">

<Airport ident="SBES"
  region=""
  country="Brazil"
  state=""
  city="Sao Pedro Da Aldeia"
  name="Sao Pedro Da Aldeia"
  lat="S22 48.96666"
  lon="W042 5.51667"
  alt="18.59M"
  trafficScalar="0.70"
  airportTestRadius="4000M"
  magvar="22.00">

  <Tower
    lat="S22 48.98769"
    lon="W042 5.54494"
    alt="0.00M">
    <SceneryObject
      lat="S22 48.98769"
      lon="W042 5.54494"
      alt="0.0000M"
      altitudeIsAgl="TRUE"
      pitch="0.00"
      bank="0.00"
      heading="50.00"
      imageComplexity="VERY_SPARSE">
      <LibraryObject
        name="{DC6A2ADA-3104-4FBC-9030-5B58906C3834}"
        scale="1.00"/>
    </SceneryObject>
  </Tower>

  <DeleteAirport
    deleteAllRunways="TRUE"
    deleteAllStarts="TRUE"
    deleteAllTaxiways="TRUE"
    deleteAllBoundaryFences="TRUE"
    >
  </DeleteAirport>

  <Runway number="7" designator="NONE"
    lat="S22 48.77075"
    lon="W042 5.56991"
    alt="18.59M"
    length="2400.00M"
    width="28.04M"
    heading="43.90"
    surface="CONCRETE"
    primaryTakeoff="YES"
    primaryLanding="YES"
    primaryPattern="LEFT"
    secondaryTakeoff="YES"
    secondaryLanding="YES"
    secondaryPattern="LEFT"
    patternAltitude="1000.0F">

    <Markings
      edges="TRUE"
      threshold="TRUE"
      fixedDistance="TRUE"
      touchdown="TRUE"
      dashes="TRUE"
      ident="TRUE"
      precision="TRUE"
      edgePavement="FALSE"
      alternateTouchdown="TRUE"
      alternatePrecision="TRUE"
      leadingZeroIdent="TRUE"
      noThresholdEndArrows="TRUE"
      />

    <Lights
      edge="HIGH"
      center="HIGH"
      centerRed="TRUE"/>

    <BlastPad end="PRIMARY"
      length="100.05M"
      width="48.11M"
      surface="ASPHALT"/>
    <BlastPad end="SECONDARY"
      length="100.05M"
      width="48.11M"
      surface="ASPHALT"/>

    <ApproachLights end="PRIMARY"
      system="ALSF2"
      strobes="12"
      endLights="TRUE"
      reil="FALSE"
      touchdown="TRUE"/>
    <ApproachLights end="SECONDARY"
      system="ALSF1"
      strobes="12"
      endLights="TRUE"
      reil="FALSE"
      touchdown="TRUE"/>

    <Vasi end="PRIMARY" side="LEFT"
      type="PAPI4"
      biasX="28.65M"
      biasZ="950.0M"
      spacing="91.44M"
      pitch="3.00"/>
    <Vasi end="SECONDARY" side="LEFT"
      type="PAPI4"
      biasX="28.65M"
      biasZ="950.0M"
      spacing="91.44M"
      pitch="2.95"/>

  </Runway>

  <Helipad type="H"
    lat="S22 49.01378"
    lon="W042 5.60846"
    alt="18.59M"
    heading="133.39"
    length="34.14M"
    width="34.14M"
    surface="CONCRETE"
    transparent="TRUE"/>

  <Start type="RUNWAY"
    number="7" designator="NONE"
    lat="S22 49.22601"
    lon="W042 6.04472"
    alt="18.59M"
    heading="43.90"/>

  <Start type="RUNWAY"
    number="25" designator="NONE"
    lat="S22 48.31581"
    lon="W042 5.09567"
    alt="18.59M"
    heading="223.90"/>

  <Start type="HELIPAD"
    number="1" designator="NONE"
    lat="S22 49.01333"
    lon="W042 5.62565"
    alt="14.63M"
    heading="133.39"/>

  <Com type="APPROACH"
    frequency="119.450"
    name="ALDEIA"/>

  <Com type="GROUND"
    frequency="121.900"
    name="ALDEIA"/>

  <Com type="TOWER"
    frequency="119.450"
    name="ALDEIA"/>

  <Com type="TOWER"
    frequency="122.800"
    name="ALDEIA"/>

</FSData>

Thanks in advance

Regards,

José
 
Hi Jose

Well, I don't know where or how you obtained your XML code, but I just decompiled the file AP936400.bgl and there are entries for R07:VORDME, R25:VORDME, R07:NDB and R25:NDB under the entry for SBES.
 
Hi Graham

Those are approaches. I think Jose is looking for an ILS at that airport. I have checked this aiport and there is no ILS shown for that airport in the FSX. So you are correct Jose in that there are no VOR/NDB records in the XML you have there.

Jose

Are you saying that there should be an ILS or Terminal NDB or are you looking for nearby Naviads. FS marks terminal naviads and ILS with the airport ICAO that they belong to. These are found in the APX file and a tool such as BGLAnalyzeX or SDE will move any found to the relevant airport and/or runway.

If the naviads are not assigned to an airport then they are not in the APX file but are in the NVX. In this case NVX04050.

There is an NDB - ADA Freq 345.00 and a VOR ADA Freq 112.1 located nearby the airport - these are both in NVX04050 when this is opened in SDE.
 
Last edited:
You found, Jon

Hi, Jon and Grahams

GrahamS said:
That'll teach me to look a bit more closely, Jon...LOL
Click to expand...

Now I can see my VOR and NDB, that aren't in the APX's files (NVX04050.bgl).

Thank you both.

Regards,

José
 
Last edited:
You must log in or register to reply here.
Back
Top