VERY irritating Fatal Error

[BigRick]

Anyone know what would trigger this error:

 

ATSO exception Target position not valid    at com.intworkings.voxatc.ProcedureSegmentBase.TargetPositionValid(Position posIn, Double heading)
   at com.intworkings.voxatc.IntcSegment.GetNextPosition(Position posIn)
   at com.intworkings.voxatc.Procedure.GetNextSetAltitude(ProcedureSegment psIn, Position posIn, String& altMode)
   at com.intworkings.voxatc.ProcedureAirspaceRoute.RationalizeAltitude(ProcedureSegment ps, Position startPos, Position posIn)
   at com.intworkings.voxatc.ProcedureAirspaceRoute.GetFirstPPosition()
   at com.intworkings.voxatc.ProcedureAirspaceRoute..ctor(Position posIn, Procedure proc1In, Procedure proc2In, Aerodrome adIn, Double cruiseAlt)
   at com.intworkings.voxatc.AirspaceRouter.GetArrival(Procedure transition, Procedure proc, Position posIn)
   at com.intworkings.voxatc.ASSEnroute.GetArrivalProcedure()
   at com.intworkings.voxatc.ASSEnroute..ctor(AircraftStrip asp)
   at com.intworkings.voxatc.ASSEnrouteHandover.MessageEnd()
   at com.intworkings.voxatc.RadioMessageImpl.Dispatch(RTOperator op)
   at com.intworkings.voxatc.ATSO.HandleIncoming()
   at com.intworkings.voxatc.ATSO.Run()
   at com.intworkings.voxatc.ATSOARTCC.Run()
   at com.intworkings.voxatc.ATSOWorker.ActiveRun()

 

P3dV4 and PMDG 737.  Seems to be in the Tokyo Ctr area.  Thanx

 

-Rick

[jabloomf1230]

Rick,

The FATAL ERROR message in VOXATC can be quite annoying, mostly because the error message description gives very little clue as to what caused the error. But generally speaking, the error tends to be caused by either a malformed airport with orphaned taxiways, missing hold short nodes, etc. or a flightplan that has something wrong with it. The latter can be hard to trace as the Navigraph AIRAC files tend have a very small number of errors in them. But one never knows. There's another thread in this subforum where VOXATC uncovered some misnamed waypoints, so it wouldn't shock me that it's nothing that you did on your end.

I guess the questions that I have are the following. What flight plan did you use to generate the error?  If you could post it, I could try to duplicate the error.  If you use a different flight plan but take more or less the same route, does the error occur at roughly the same location? Which AIRAC are you using with both the NGX and VOXATC? Are you also using fsaerodata and did you update the FIR/ARTCC file? I can't remember anyone posting a question about VOXATC and the Tokyo Center airspace sectors, so it's very possible that there is something wrong with the nav data and not VOXATC.

You should send an email to the developer with a copy of the detailed error message. Whether you get a response is hit or miss, unfortunately.

Jay

[dutchkip]

11 hours ago, jabloomf1230 said:

Rick,

The FATAL ERROR message in VOXATC can be quite annoying, mostly because the error message description gives very little clue as to what caused the error. But generally speaking, the error tends to be caused by either a malformed airport with orphaned taxiways, missing hold short nodes, etc. or a flightplan that has something wrong with it. The latter can be hard to trace as the Navigraph AIRAC files tend have a very small number of errors in them. But one never knows. There's another thread in this subforum where VOXATC uncovered some misnamed waypoints, so it wouldn't shock me that it's nothing that you did on your end.

I guess the questions that I have are the following. What flight plan did you use to generate the error?  If you could post it, I could try to duplicate the error.  If you use a different flight plan but take more or less the same route, does the error occur at roughly the same location? Which AIRAC are you using with both the NGX and VOXATC? Are you also using fsaerodata and did you update the FIR/ARTCC file? I can't remember anyone posting a question about VOXATC and the Tokyo Center airspace sectors, so it's very possible that there is something wrong with the nav data and not VOXATC.

You should send an email to the developer with a copy of the detailed error message. Whether you get a response is hit or miss, unfortunately.

Jay

Hi Jay,

You seem to be very knowledgeable about VOX Atc.

I too have some airports that crashing voxatc.

Indexer works, runway number update does not.

I read somewhere that it might have to do with the scenery folder.

C drive SSD 500GB for OS

D drive SSD 1TB for storage

F drive SSD 500 GB for flightsim

I have over a hundred airport sceneries installed and they are in my F:\P3Dv4\ Addon folder (well most of them) Aerosoft ones are in F:\P3D4\ecosystem folder.

Am I right in thinking that they are all in the wrong drive and that I should have installed them all on my 1TB D drive?

Could this be why my runway updater isn't working?

Got ALL ORBX Europ sceneries, Global Vector and OpenLC Europe.

Looking forward to hear from you.

 

Leo de Haan

Scotland

 

[jabloomf1230]

Leo,

It shouldn't matter where the airports are stored, as long as the Indexer is correctly finding all of them and not the stock versions. Other people have reported problems with the runway updater utility when there are a lot of add-on airports installed. I assume that it must be a bug in VOXATC. A subscription to fsaerodata will change how VOXATC refers to airport runway numbers, but it won't change either the geometry of the runway or how the numbers show up in the sim.

Jay

[dutchkip]

Thanks Jay.

Will have to start moving my sceneries off my Flightsim drive anyway as it;s getting a bit crowded.

 

Thanks again for your help.

Regards

Leo