Could someone try this with either fsaerodata installed or stock scenery? I get the dreaded FATAL ERROR when I try to contact Provo Approach. It's one of the few instances of an error with VOXATC that I have seen in the last year with P3d4 and VOXATC 7.42. I tried methodically disabling specific FSAD approaches, but it made no difference.

On 10/4/2019 at 7:36 AM, jabloomf1230 said:

I tried methodically disabling specific FSAD approaches

Jay

Your post "seems" similar to my experience recently (since investing in fsad) ..... though at other airports (in Asia). Previously I had used Herve Sors' navaid / fix updates (which don't include gps approach updates) seemingly okay.

In that, the recurring "coincidence" is that the approach options available are ils or visual only & that rnav's are no longer listed (& further more often than not stars are not assigned).

One has to say though that the above is further confused by Vox's preference for vectoring irrespective.

So my growing suspicion, which could lead to FE's, is that Vox is having "conflicts" with FSAD's data to adequately compile tracks/routes for stars & approaches using that updated sim navdata as asked by the Vox airac.

Make sense ?

 

 

Thanks John.

But wouldn't that be easy to check by disabling the approach data in FSAD (located in ..\Documents\fsAerodata Files\Navigation Data\P3D) and enabling the Navigraph LevelD 767 dataset that VOXATC can use? Or vice versa? Jose Rubio from FSAD was not sure whether the two Navigraph approach datasets conflict or not.

Jay

23 hours ago, jabloomf1230 said:

the Navigraph LevelD 767 dataset that VOXATC can use

Jay

Correct me, but i understood that Vox only uses that airac to search for the required waypoints (fixes / navaids) along a procedure (sid / star / approach) in the sim's database of waypoints to compile "possible" instructions by atc such as rnav as well as ils approaches.

That database needs to be updated to include current waypoints that match what an updated Vox airac looks for.

That said, it seems (after a cursory search) that not all the "current" waypoints are included in fsad's navaids folder whereas they are in Herve's.

I also don't see the "approach" files in the fsad P3D folder as being of any use to Vox as the waypoints along the included procedures are not the same as the Vox airac.

So for now I am reverting to Herve's fixes update in lieu of Jose's Navaids & P3D folders .... as was my way initially with Vox.

Will report whichever ...

Edited October 6, 20196 yr by vadriver

1 hour ago, vadriver said:

That said, it seems (after a cursory search) that not all the "current" waypoints are included in fsad's navaids folder whereas they are in Herve's.

The waypoints are appended to the end of the FSAD approach file MBPV.xml (after all the approach XML) , but it's possible that for some reason VOXATC doesn't read them correctly. Little NavMap (in sim scenery mode) sees those waypoints and displays the approaches correctly, so there's that. I used ADE to create an updated airport file that includes all the information in MBPV.xml and disabled MBPV.xml. I'll let you know how that goes. 

You may be right, but the VOXATC manual states that the LevelD 767 AIRAC data is used to create approaches. However, I've never seen any difference in the behavior of VOXATC (with FSAD) with the LevelD 767 AIRAC either active or inactive.

Here's what I've discovered which is confusing. If I create a version of MBPV with ADE and correctly add in all the approaches and waypoints from the FSAD XML file and then disable the FSAD XML file, the same error occurs on any flight from MTCH to MBPV. But if I start at a different airport, for example, North Caicos (MBNC), the flight proceeds without the FATAL ERROR after I am told to contact Provo Approach. I also tried all the various VOR approaches from the menu and they all work too, so I have no idea what the error is caused by. But in any case, VOXATC can recognize all the various approaches such as as VOR-X, VOR-Y, VOR-Z, NBD, etc., so it having no trouble finding the embedded terminal waypoints.

I should add that even a VFR flight from MTCH to MBPV  won't work. There's no error message, but the ATC just doesn't answer.

Just one of the many mysteries of VOXATC.

2 hours ago, jabloomf1230 said:

But in any case, VOXATC can recognize all the various approaches such as as VOR-X, VOR-Y, VOR-Z, NBD, etc., so it having no trouble finding the embedded terminal waypoints.

can i ask if you had these before the "tweak" ?

I'm not sure what you mean. I've never had any trouble previously with VOXATC using Navaid approaches having qualifiers like X, Y and Z. My test of including the FSAD approach information directly in the MBPV ADE file shows that VOXATC is having a problem with either the direction of the flight plan to MBPV or the altitude at which the Provo airspace is entered. Neither of those explanations makes any sense.

It does show that the approach waypoints are included in FSAD and used by VOXATC just like they are with the Herve Sors freeware add-on.

On 10/5/2019 at 11:31 AM, vadriver said:

Your post "seems" similar to my experience recently (since investing in fsad) ..... though at other airports

Jay

Your mysteries" in hindsight seem different to mine ....... a lack of approach options apart from ils / visual ones.

I'll push on to understand more if one can, but then as with yours, it may be isolated to few airports.

8 minutes ago, vadriver said:

a lack of approach options apart from ils / visual ones.

Yeah, that's some other kind of issue that you shouldn't be seeing with VOXATC and FSAD. I always put FSAD at the top of the scenery library using the XML add-on method. That assures that no other add-ons will impose out of date AIRAC information. 

On 10/8/2019 at 2:47 AM, jabloomf1230 said:

My test of including the FSAD approach information directly in the MBPV ADE file shows that VOXATC is having a problem

jay 

thanks for your clues above.

On 10/8/2019 at 9:22 AM, vadriver said:

I'll push on to understand more if one can,

so far my thinking (after some trials) is that:

• the airac is only used to route sids & stars, not approaches
• approaches are sourced from all possible afcads, both stock & addons, whether duplicated or not.
• if you delete all approaches, you will be assigned a visual approach only to open landing runway/s (not to all runways that have an approach in a "normal" afcad)
• if you selectively add approaches you "want" (using fsad's airac support) to one's preferred (addon) afcad, then you will be initially assigned an instrument procedure to that open runway along with a visual as an option .... & that's all.

so, my trials will continue but essentially i now have several afcads each with only an appropriate rnav to just one runway which i swap beforehand to suit the "likely" tailwinds on arrival.

and to add, AI being controlled by the "classy" Vox traffic engine will also sequence correctly to that runway & not others.

On 10/8/2019 at 9:32 AM, jabloomf1230 said:

Yeah, that's some other kind of issue

yes, but thought the above may help.

😃

Edited November 22, 20196 yr by vadriver