Jump to content

You're browsing the 2004-2023 VATSIM Forums archive. All content is preserved in a read-only fashion.
For the latest forum posts, please visit https://forum.vatsim.net.

Need to find something? Use the Google search below.

error log


Koen Meier
 Share

Recommended Posts

Koen Meier
Posted
Posted

curios to know what this means.

vatSys
Object reference not set to an instance of an object.
   at vatsys.Profile.Load()
   at vatsys.MainForm..ctor()
   at vatsys.Program.Main()

Link to comment
Share on other sites

Jake Saw
Posted
Posted

Profile.xml is either missing or invalid

  • Like 1

Jake

Developer - vatSys

image.png.3cc3dde479bc419c580ca959161ce25e.png

Link to comment
Share on other sites

Koen Meier
Posted
Posted

got another one. after i found out the system doesn't like the 8.33 stuff.

mscorlib
Input string was not in a correct format.
   at System.Number.StringToNumber(String str, NumberStyles options, NumberBuffer& number, NumberFormatInfo info, Boolean parseDecimal)
   at System.Number.ParseInt32(String s, NumberStyles style, NumberFormatInfo info)
   at System.Int32.Parse(String s)
   at vatsys.LogicalPositions.Load()
   at vatsys.MainForm..ctor()
   at vatsys.Program.Main()

Link to comment
Share on other sites

Jake Saw
Posted
Posted

LogicalPositions refers to Positions.xml, it's failing to parse a number somewhere - eg. DefaultRange or the CFL levels

  • Like 1

Jake

Developer - vatSys

image.png.3cc3dde479bc419c580ca959161ce25e.png

Link to comment
Share on other sites

Koen Meier
Posted
Posted

getting an iso string error
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()

however i am not entirely sure what the error could be.

Link to comment
Share on other sites

Jake Saw
Posted
Posted

ParseIsoString is it failing to parse a Coordinate, and given it's Airspace2 it'll be in Airspace.xml somewhere

Jake

Developer - vatSys

image.png.3cc3dde479bc419c580ca959161ce25e.png

Link to comment
Share on other sites

Koen Meier
Posted
Posted
On 9/11/2020 at 4:25 AM, Jake Saw said:

ParseIsoString is it failing to parse a Coordinate, and given it's Airspace2 it'll be in Airspace.xml somewhere

i looked at the file but cannot see any error.  only thing is there are some repeated iso values but i caannot imagine that causing the a fore mentioned issue.

Link to comment
Share on other sites

Jake Saw
Posted
Posted

Koen,

If you attach the Airspace.xml file in question here I can take a quick look for you.

Jake

Developer - vatSys

image.png.3cc3dde479bc419c580ca959161ce25e.png

Link to comment
Share on other sites

Koen Meier
Posted
Posted

seems only png, jpeg,jpg and pdf are attachable.

Link to comment
Share on other sites

Anthony Power
Posted
Posted

If you change the Airspace.xml file extension from .xml to .pdf or one of the other accepted file types, Jake can then change it back when he gets it.

  • Like 1
Link to comment
Share on other sites

Koen Meier
Posted
Posted
8 minutes ago, Anthony Power said:

If you change the Airspace.xml file extension from .xml to .pdf or one of the other accepted file types, Jake can then change it back when he gets it.

doesnt work. as it gives an error.

Link to comment
Share on other sites

Anthony Power
Posted
Posted

Ah ok, it worked for me with a .txt file I changed to .pdf

Link to comment
Share on other sites

Koen Meier
Posted
Posted

this works via word 

Airspace.pdf

Link to comment
Share on other sites

Jake Saw
Posted
Posted

Koen,

The majority of your longitudes are not in the correct format

+483505.431+133018.809

Should be:

+483505.431+0133018.809

(longitude must be 3 digit degrees)

Jake

Developer - vatSys

image.png.3cc3dde479bc419c580ca959161ce25e.png

Link to comment
Share on other sites

Koen Meier
Posted
Posted (edited)
1 hour ago, Jake Saw said:

Koen,

The majority of your longitudes are not in the correct format


+483505.431+133018.809

Should be:


+483505.431+0133018.809

(longitude must be 3 digit degrees)

These data came from your program to convert sct to xml. That output is what I used in an excel sheet to get my dataset.

online i found, https://www.w3.org/2005/Incubator/geo/Wiki/LatitudeLongitudeAltitude . which matches up with all coordinates.

   Latitude and Longitude in Degrees:
      ±DD.DDDD±DDD.DDDD/         (eg +12.345-098.765/)
   Latitude and Longitude in Degrees and Minutes:
      ±DDMM.MMMM±DDDMM.MMMM/     (eg +1234.56-09854.321/)
   Latitude and Longitude in Degrees, Minutes and Seconds:
      ±DDMMSS.SSSS±DDDMMSS.SSSS/ (eg +123456.7-0985432.1/
Edited by Koen Meier
Link to comment
Share on other sites

Koen Meier
Posted
Posted

and even after adding a 0 in front of the longitude it still gives an iso warning.

Link to comment
Share on other sites

Jake Saw
Posted
Posted

The xmltools are example programs (with source code), not complete solutions.

Attach your updated file.

Jake

Developer - vatSys

image.png.3cc3dde479bc419c580ca959161ce25e.png

Link to comment
Share on other sites

Jake Saw
Posted
Posted
	<Point Name="MISRI" Type="Fix">+515635.9980+072853.000</Point>

 

  • Like 1

Jake

Developer - vatSys

image.png.3cc3dde479bc419c580ca959161ce25e.png

Link to comment
Share on other sites

Koen Meier
Posted
Posted

many thanks for your help

GsTA5.png

have to do some more work like setting the default center point and setting certain routes as CDR. but at least it is starting to look like something.

Link to comment
Share on other sites

 Share