FATAL ERROR with certain scenery?

[pegruder]

 

So I've been using Vox for awhile now but can't seem to figure out why at JFK I get a fatal error just after contacting clearance.  If I takeoff and call mid flight I have no issues.  I also have no issues flying IN to JFK, only starting a flight there.  Anything I should check for in particular related to the scenery?  Its the DrwDrzewiecki Design JFK pack.

[jabloomf1230]

I have DD KJFK. Let me check the ADE file for faults and I'll get back to you. In the interim, make sure that you don't have another 3rd party version of KJFK installed.

[jabloomf1230]

Here's what I've discovered with ADE. DD has correctly closed several KJFK runways (4R, 13L, 22L, 31R) for use as departure runways, but the developer also left the runway starts enabled. This can cause endless confusion for even the stock AI and ATC, so it possible that it is making VOXATC break down and cry. There are several duplicated parking space numbers which also can be an issue.

But my guess is that the elaborate taxiway network combined with the large number of gates and AI aircraft is just exposing some kind of bookkeeping bug in VOXATC. One thing that you can try is to turn the VOXATC AI activity level down a few notches and see if the error still occurs. Or use the FSUIPC traffic limiter to see if that helps.

I haven't seen the VOXATC FATAL ERROR on clearance at DD JFK (which means nothing as individual sim setups are what often dictate what types of errors occur), but I will try some flight plans and see if I can duplicate it.

 

[pegruder]

6 hours ago, jabloomf1230 said:

Here's what I've discovered with ADE. DD has correctly closed several KJFK runways (4R, 13L, 22L, 31R) for use as departure runways, but the developer also left the runway starts enabled. This can cause endless confusion for even the stock AI and ATC, so it possible that it is making VOXATC break down and cry. There are several duplicated parking space numbers which also can be an issue.

But my guess is that the elaborate taxiway network combined with the large number of gates and AI aircraft is just exposing some kind of bookkeeping bug in VOXATC. One thing that you can try is to turn the VOXATC AI activity level down a few notches and see if the error still occurs. Or use the FSUIPC traffic limiter to see if that helps.

I haven't seen the VOXATC FATAL ERROR on clearance at DD JFK (which means nothing as individual sim setups are what often dictate what types of errors occur), but I will try some flight plans and see if I can duplicate it.

 

Thanks for the tips.  I did have the FSDT version installed but I thought I removed it.  I've tried several different flight plans as well.  Ill also try lowering the AI amounts if all else fails.

[jabloomf1230]

I'm also looking at the taxiway network which has a large number of double letter designators. 

So far no error at KJFK, but one flight plan resulted in ATC saying "Taxi to Runway 31L." with no taxiways. I can't say that I've ever seen that at any airport.

[pegruder]

9 hours ago, jabloomf1230 said:

I'm also looking at the taxiway network which has a large number of double letter designators. 

So far no error at KJFK, but one flight plan resulted in ATC saying "Taxi to Runway 31L." with no taxiways. I can't say that I've ever seen that at any airport.

Is it possible something OrbX related could interfere?  It looks like the FSDT version is removed.  I can't find it anywhere.  If you can't duplicate it it doesnt seem related to the scenery itself.  Just trying to think of what else I have installed that could cause it.

[jabloomf1230]

1 hour ago, pegruder said:

Is it possible something OrbX related could interfere?  It looks like the FSDT version is removed.  I can't find it anywhere.  If you can't duplicate it it doesnt seem related to the scenery itself.  Just trying to think of what else I have installed that could cause it.

I don't see how. I have the full ORBX suite (Global Base, Vector, etc.) installed. I might PM you later today with some ideas. 

[jabloomf1230]

Chris,

I found one more interesting feature of DD's KJFK. KJFK has two parallel perimeter taxiways A and B that circle all the gates. DD added two distinct gaps in both A and B, probably to prevent aircraft from taking a circuitous route to and from runways. I'm not sure what this design trick does to the logic in VOXATC, though. Here's one of the gaps:

https://www.dropbox.com/s/6h5qjpw9zvhtjvb/DD KJFK Taxiway A and B gap.jpg?dl=1

[jabloomf1230]

The two gaps are the taxiway bridges over the expressways. I was able to cause a Fatal Error after about 5 tries. I'm guessing that because DD KJFK is a performance hog (I can barely achieve 20 fps), something bad happens to VOXATC and it crashes. You could try turning down your P3d  IQ settings to see if that helps.

[pegruder]

Just tried turning down everything - no change.  Might uninstall the DD version and try the FSDT version again.

[pegruder]

So I uninstalled the DD Version, reran indexer, tried stock, same error.  Installed FSDT, re-ran indexer, tried again - same error.  Removed FSDT and reinstalled DD version - reran indexer, still no good.  Not sure what this could be picking up at this point.

[jabloomf1230]

1 hour ago, pegruder said:

Not sure what this could be picking up at this point.

You could turn on detailed logging in the VOXATC Advanced Setting Utility and then take a look at the log to see what the detailed error message might be. It's possible that the error has nothing to do with the airport scenery, but rather has to do with the AI models and flight plans. I can't remember offhand which AI traffic app you are using. One other option is to try using one of the default P3d aircraft and see what that does. 

[pegruder]

Just now, jabloomf1230 said:

You could turn on detailed logging in the VOXATC Advanced Setting Utility and then take a look at the log to see what the detailed error message might be. It's possible that the error has nothing to do with the airport scenery, but rather has to do with the AI models and flight plans. I can't remember offhand which AI traffic app you are using. One other option is to try using one of the default P3d aircraft and see what that does. 

Going to give that a shot next.  I'm running MT6 for traffic.  I'd love to switch to UTL but still waiting on the dev to update the bridge.  I just removed the MT6 file for JFK but that didn't seem to help.  I also just found some additional FSDT files that may or may not be affecting me.  Gonna re-run indexer and try again...

[pegruder]

Still no good - Here's the logs: 

 

2298360 Ins Text set : Standby and wait to be called back
2298360 Prompt disabled
2298360 Prompt Text set :  kennedy clearance  jetblue seventy nine  ready for clearance washington dulles intl  
IN 23:22 From :jetblue three forty one:  kennedy clearance
IN 23:22 From :jetblue three forty one:  
IN 23:22 From :jetblue three forty one:  jetblue three forty one
IN 23:22 From :jetblue three forty one:  
IN 23:22 From :jetblue three forty one:  ready for clearance
IN 23:22 From :jetblue three forty one:  long beach
IN 23:22 From :jetblue three forty one:  
IN 23:22 From :jetblue three forty one:   Terminator

IN 23:22 From :kennedy clearance:  jetblue three forty one
IN 23:22 From :kennedy clearance:  
IN 23:22 From :kennedy clearance:  standby
IN 23:22 From :kennedy clearance:  
IN 23:22 From :kennedy clearance:   Terminator

ATSO exception Object reference not set to an instance of an object.    at com.intworkings.voxatc.AirspaceRoute.GetPosAtDist(Double distIn, Position posIn)
   at com.intworkings.voxatc.ClearanceImpl.SendClearance()
   at com.intworkings.voxatc.ASSGettingDepartureClearance.ControllerAvailable()
   at com.intworkings.voxatc.ATSO.CheckWaitingStrips()
   at com.intworkings.voxatc.ATSO.Run()
   at com.intworkings.voxatc.TerminalATSO.Run()
   at com.intworkings.voxatc.ATSOWorker.ActiveRun()
2306828 Ins Text set : FATAL ERROR! disable VoxATC
VADI key pressed event : 211
RSC Key pressed
VADI key released event : 211

[jabloomf1230]

Not being the developer I can only guess but it looks like the error is related to your flight plan. If that doesn't work, zip up the logs, load the zip file  to the cloud and send the link of the zip file via the official VOXATC contact web page.