Error loading profile

[Ryan Miltenberger]

Hello,

I'm working on a profile for my home FIR, and after slapping together a real fast airspace.xml file to make sure I was doing it right, on attempt to load the profile I get the error "Object reference could not be set to an instance of an object", and this is what gets putout in the error log:

"vatSys
Object reference not set to an instance of an object.
   at vatsys.Coordinate.ParseIsoString(String isoStr)
   at vatsys.Coordinate..ctor(String isoString)
   at vatsys.Airspace2.LoadNavData()
   at vatsys.MainForm..ctor()
   at vatsys.Program.Main()"

Any help would be appreciated, thank you.

[Ryan Miltenberger]

Update

After downloading a navdata dump from GNG AeroNav, properly formatting it, it now says airspace.xml is missing or invalid, and provides with this in the error log:

vatSys
Airspace.xml invalid or missing. Cannot proceed without valid file
   at vatsys.Airspace2.LoadNavData()
   at vatsys.MainForm..ctor()
   at vatsys.Program.Main()

[Ryan Miltenberger]

An even further update

Turns out I messed up the airspace.xml, got that file working. Now it's throwing an error in system.xml, but only on the profile I'm attempting to load. Every other profile has loaded with no errors. Below is the error log.

System.Xml
There is an error in XML document (0, 0).
   at System.Xml.Serialization.XmlSerializer.Deserialize(XmlReader xmlReader, String encodingStyle, XmlDeserializationEvents events)
   at System.Xml.Serialization.XmlSerializer.Deserialize(Stream stream)
   at vatsys.DefaultJurisdiction.Load()
   at vatsys.MainForm..ctor()
   at vatsys.Program.Main()

 

[Ryan Miltenberger]

Further update.

After adding the controller positions, a new error has come about.

mscorlib
An item with the same key has already been added.
   at System.ThrowHelper.ThrowArgumentException(ExceptionResource resource)
   at System.Collections.Generic.Dictionary`2.Insert(TKey key, TValue value, Boolean add)
   at vatsys.SectorsVolumes.LoadSectorGroupings()
   at vatsys.SectorsVolumes.LoadSectorsAndVolumes()
   at vatsys.MainForm..ctor()
   at vatsys.Program.Main()

[Jake Saw]

1 hour ago, Ryan Miltenberger said:

Further update.

After adding the controller positions, a new error has come about.

mscorlib
An item with the same key has already been added.
   at System.ThrowHelper.ThrowArgumentException(ExceptionResource resource)
   at System.Collections.Generic.Dictionary`2.Insert(TKey key, TValue value, Boolean add)
   at vatsys.SectorsVolumes.LoadSectorGroupings()
   at vatsys.SectorsVolumes.LoadSectorsAndVolumes()
   at vatsys.MainForm..ctor()
   at vatsys.Program.Main()

Sector names must be unique (you may have defined one twice)

[Ryan Miltenberger]

4 minutes ago, Jake Saw said:

Sector names must be unique (you may have defined one twice)

Just so I'm clear before I make too many replies, each sector must have it's own name, so TOR_CTR with the identifier of SL should be TOR_SL_CTR, if that's what is accurate to name it?

[Jake Saw]

Yes

As an example, if you have 1 parent sector (say the whole FIR) that consists of smaller subsectors used for events etc:

<Sector FullName="ZZZZ Combined Sector" Frequency="131.800" Callsign="ZZZZ_CTR" Name="ZZZ">
    <ResponsibleSectors>ZZA,ZZB,ZZC</ResponsibleSectors>
</Sector>
<Sector FullName="ZZA Sector" Frequency="132.000" Callsign="ZZZZ-A_CTR" Name="ZZA">
    <Volumes>A</Volumes>
  </Sector>
<Sector FullName="ZZB Sector" Frequency="132.100" Callsign="ZZZZ-B_CTR" Name="ZZB">
    <Volumes>B</Volumes>
  </Sector>
<Sector FullName="ZZC Sector" Frequency="132.200" Callsign="ZZZZ-C_CTR" Name="ZZC">
    <Volumes>C</Volumes>
  </Sector>

Each has a unique Name and Callsign

[Ryan Miltenberger]

 

1 hour ago, Jake Saw said:

Yes

As an example, if you have 1 parent sector (say the whole FIR) that consists of smaller subsectors used for events etc:

<Sector FullName="ZZZZ Combined Sector" Frequency="131.800" Callsign="ZZZZ_CTR" Name="ZZZ">
    <ResponsibleSectors>ZZA,ZZB,ZZC</ResponsibleSectors>
</Sector>
<Sector FullName="ZZA Sector" Frequency="132.000" Callsign="ZZZZ-A_CTR" Name="ZZA">
    <Volumes>A</Volumes>
  </Sector>
<Sector FullName="ZZB Sector" Frequency="132.100" Callsign="ZZZZ-B_CTR" Name="ZZB">
    <Volumes>B</Volumes>
  </Sector>
<Sector FullName="ZZC Sector" Frequency="132.200" Callsign="ZZZZ-C_CTR" Name="ZZC">
    <Volumes>C</Volumes>
  </Sector>

Each has a unique Name and Callsign

Awesome thanks. I got all that and it's basically working now. One more question I have, and if you want to take this to the messages I'm more than happy, is when I'm adding radar sites, how would I get data blocks for aircraft to show up? As I've added one that's an SSR_ModeC type and it'll just show the vector lines, history, and the aircraft's return. 

[Jake Saw]

To get a coupled label you must first activate the flight data record

https://virtualairtrafficsystem.com/docs/flightthread/

https://virtualairtrafficsystem.com/docs/fdr/

Defining a ModeS or ADSB type radar will show callsign instead of SSR code in limited labels (without a flight plan).