vadriver

voxatc user guide ..... a tad out of date & a tad brief but should give one a feel to the "cloners".

i'm guessing you mean TTS generated controller / ai crew / copilot comms, no phonetics etc. & no (missing) sound files. but then they'lll need a much better AI engine to control / use holdings / downwind ops & avoid closed runways. very much a clone of voxatc you might say.

jay are you still of a "mixed opinion" as to whether voxatc reads the fsad approach files adequately if at all. my "best" experience (& the only way to be offered rnav approaches which are rarely included in an afcad, either stock or addon) is to import the fsad approach file into one's "highest priority" afcad, deleting existing out of date & /or duplicates and even culling approaches that may not be used by your aircraft's category. the above followed noticing the only airports i was offered rnav's for were those few (T2G's) which included (though out of date) rnav's in their afcad ...... & with fsad proc folders enabled. consequently, i have disabled the those folders from "direct" use. appreciate your/others thinking on this.

my medical examiner is trolling my posts ..... and as he remarked, 90nm is the answer 😶

david firstly, i have not been assigned a "descend via" star (or "climb via" sid) clearance with V742, just a "cleared via" ..... though regularly after such i will receive initially an altitude restriction to the star's limit, but then shortly after that an altitude restriction to an earlier & higher level (roughly for example, a sequence of "cleared via timbers 2 mark you transition", then after a while "descend to altitude 5000" then after a short while "descend to FL240", this later restriction being the one imposed) it seems somehow that vox does not find a "flag" of some sort in the airac to completely distinguish a legacy star from an rnav one. the bottom line seems to be not to expect a "descend via". the other issue involved with your example is how v742 calculates a TOD to initiate a descent clearance. one understands the default vnav profilev742 uses is 2.5nm per 1000' from one's destination and that it does not recognise any star restrictions such as the vnav gates on the TMBRS2 arrival ..... which for an arrival at KPDX say from FL360 at TOD would be only 80nm to run (over MOXEE) whereas to be at WIDMR at 5000', your preferred TOD (for a 3o fpa) would be near AARON. so, i believe you should expect to request a descent to suit & not rely on vox. one can add to the VASettings.xml file .... <DescentRatio Value="4.0" /> ..... or similar to create earlier vox initiated descent calls (but which may not suit other profiles) the devil is unfortunately in the "tweak".

agree ..... whatever discount as their airports are without low visibility daytime ALS / runway lighting.

john uninstall all panels using panel setup (from start menu), then check the aircraft.cfg's to confirm gauges removed (& only then delete any not removed in the first step) run indexer & if successful, reopen panel setup & install to the listed aircraft (yours). hope that works for you.

good to hear ... surprised it didn't show as "available" in panel install after "indexing".

rich / jay pondering the above ..... it's closer to 40o so need a few more to help. i think we need to consolidate our thinking & promote this "abandoned" masterpiece so more can "appreciate" its worth ie it is not for the "candy" one may want / expect but the reality. hope that makes sense at 0936Z

rich did you not mean the "WPNAVAPT.txt" file ..... similar to the "airports.dat" but with ILS data. ps keeping cool as jay is in the north east ??

indeed ..... but the subtle difference is FPV can graphically show hourly movements of what is available from AIG's core & latest flightplans (some of which you may not have installed) & thus what you might compare to one's local "real" experiences. AIC on the other hand tells you the result of what you have installed. but both programs well help one's thoughts on where to put the "slider".

I find flight plan visualizer more than helpful understanding what can be spawned at an airport https://library.avsim.net/download.php?DLID=212254

john the only need one has (to use any plane) is to install the voxatc gauges in the panel.cfg for that aircraft ....... not sure about the NGXu, but that file is in the -800 for the full suite of NGX aircraft. run the indexer to see a list of aircraft "panel.cfg's" or copy the entries from an existing vox configured file.

you can turn off any one / combination of the 6 DOF's. i recommend trialling one at time to tweak the response curve to suit you, your monitor etc. .... other's profiles are a bit pointless in my opinion because of these & whether you use a hat clip or the pro clip. try a flight with yaw & pitch only first & then introduce other DOF's if you choose. & above all, make sure you have no background light sources (e.g. sun through the window behind) to upset the "flow".

mike an interesting note ........ i set voxatc 50% (& it seems "similar" to default. i might try & compare with AIG's forecasts.

this may sound counter intuitive but ....... setting higher activity means you won't see that flight unless your sim slider is set to more than 75 etc. (but that's without Vox where sim slider is at zero). leaving the activity at 1 allows vox's slider to be the master of AI (not sure if setting 75 affects / restricts the Vox AI as i've always used activity 1)

& if they don't, i won't no matter what else ...... even if i'm still using W764 compatibles and self supporting.

hmmm .... i have no simple answer to your wish. AI is very much about "flightplans with nominated aircraft (models)" & so lends itself more to the "heavies". I can't think of a way (& maybe more so with models for the "lighter end" of GA) plans could be compiled for any local without a fair amount of effort ie & not readily available. i can only suggest you search AIG forums for what may suit.

if your enroute plan begins at a sid (transition) & ends at a star (transition), you should be assigned both as per voxatc's airac .... if they don't, you will receive vectors to/from your enroute's. approaches (after the star) on the other hand are assigned from those included in the destination afcad. you will receive vectors to the approach if no suitable approach transition is included in the afcad (what voxatc calls for example a full ILS).

chris firstly, go for a walk & breathe some fresh air. when you return (for your Cat C & D IFR ) just load your enroute (no sids or stars) in the sim's plan & you're good to go. unfortunately you're on your own then "responding to Vox's assignments" which suits the weather etc as required (not random if you check your TAF's etc, particularly for approach). there's no way you can hop out of your plane to see the "controllers panel as you can in P2A" ... but hey, it's more real that way. extras are about options to that route ... holding / vectors / alternates etc.. but if you want them, run the indexer after input.

i was hoping to hear you had a registration code ..... but your call obviously (or was it ?) voxatc is one "leading" addon in my opinion but i can understand why many shy away because of the lack of support etc. for what are / seem to be "minor and / or explainable nuances". it seems further sales are unlikely given your experience.

18 months ago for my Vox 7 purchase, yes. then a PayPal non-member credit card transaction followed by an email from info@voxatc.com with the registration code (within the day) Paypal details of seller were........ Internal Workings at sales@voxatc.com. all smooth as ... THEN !

https://www.fsdeveloper.com/forum/threads/zbaa-beijing-international-airport-for-fsx.430996/ is worth the read on A_A's development of ZBAA. & the low vis daytime lighting is one of best (yet not often mentioned in a features list)

i guess you can (have) check if your payment has been debited to your card or whichever & who that payee may be ?

& landing ........ downwind.