vadriver

Team Problem solved ...... if installing voxatc gauges in the 777, one needs to rebuild a cold&dark panel state to your preferred.

Team Firstly, let me explain ...... not stuttering, not broken but for example, when FO asks for taxi, one hears the FO say callsign & then immediately the controller say the callsign etc, no instructions, no readback and all in a lot less time than had the instructions/readback been sounded. The log shows/writes the complete transmission by both & without any apparent errors. It seems like a Priority/CPU issue and /or clash with other TTS addons such as MCE, FS2C perhaps. And it is not happening in the PMDG NGX (works 100%) for example, but curiously happens in their 777. It has me tossed ..... i could pretend I use CPDLC, but that's a bit untidy during vectors. Any similar experiences / notes would be appreciated ...... the above is with P3D45, Vox742 on W764. Thanks

but only at FSDT & stock airports automatically (gives an abandoned look) but not to other 3rd party SODE equipped airports such FBS's KSFO etc (unless you choose ??) where you will continue to see AI docking.

I may have "cracked" that reputation ....... Seriously though, I ask if anyone who flies the 64bit P3D4 vers of PMDG's 777 & using VocAtc is doing so with success or otherwise. For me, the VoxATC audio is somehow "broken / disjointed / incomplete" though my logs are complete & clean so to speak. My other app MCE is okay, don't know about P2A though. With PMDG's NGX, it is working almost without flaw. So would appreciate any notes for users of that combo. Thanks

love the shorts .......... must get you some pics of similar at YPLB.

i am sure that most developers do spend time testing ..... but against stock / default scenarios in the sim. there's a lot of incompatability hidden under the surface that's not checked, particularly with aircraft & the options for atc / control functions / hardware etc. few ever publish what they have "tested" ... & most can't publish an SDK to review / consider.

so that in the first instance, available runway assignment reflects real world flows ...... downwinds, noise abatment, low visibility.

I actually stopped flying before I started simming ................

nope ....... as long as you have numlock mute enabled, scrolllock can be used in lieu (thus avoiding if you prefer interference with numpad available keys). certainly & preferably to the trigger (easier to hold down for the time needed). i'm sure it will work for you .... for any combination of mce & other speech input apps such as vatsim / vox / p2a.

i use <scrolllock> as above in lieu of either <end> or <numlock> successfully with voxatc for example (scrolllock is a recently added alternative to numlock, thanks to gerald)

if your preference is vfr (mostly) piston aircraft from regional airports (Class C & D) , you should use AIG's general aviation schedules rather than airline type schedules from UTL etc.using Class A & B airspace. I believe Vox could be your answer catering to both vfr & ifr, light to heavy and with TTS voices matching local .... it has its own traffic engine which coordinates well with AIG type bgl traffic files.

love the classic cockpit .......

i was expecting others more familiar with fs2crew would mention using textaloud (& one's preferred TTS voice) to record the equivalent FO sound files fs2crew uses ?

several ........

have a look at the options in fsuipc for setting separate "directly assigned" pedal and tiller axis for nosewheel / rudder control (as per mark's above)......

interesting ..... i have been having "hangs" on scenario load many times recently & traced (?) to a "sode fault" subsequently fixed by a sode uninstall / install. i now realise it has been after using LAO that the above happens.(v139b06). hope to hear more soon ?

robs me neither with 7.42 (no connection) ...... whereas as below i had a connection with a transfer of the indexer (?) but no subsequent joy with 7.41 indeed ....... i noted that voices were the 32bit, not 64bit as used by 7.4x (with P3D4) standalone. i also had problems with "suitable runway not available" which suggests netserver can't read airport (xml) addons in P3D4. Jay wrote recently in a paralell thread "You cannot run VOXATC over a network other than having the AI aircraft server executable on a remote PC" ...... I'm not sure what he means & how but his suggest is it's of limited use anyway & given the standalone is of little comparative impact (AI processing) on the sim pc. The other aside to all this is that the default install of netserver is to Program Files (x86), nt the 64bit folder where 7.42 is on the sim ...... is that not a tad quirky ?

so true ...... that aside, i've found vox atis / ai control / aircraft direction to respect the "geometry" of runway use of addons much better than the default's though at KDEN where i have both 16L/34R and 17L/35R set for landing only, the paralells for departure, i have had approach clear to 34R but subsequently tower clear to 35R. but that's different to Al's experience. the only note i can offer is vox often in light winds will list all runways as options to the correctly cleared irrespective of the afcad's geometry.

i'll wait till i hear how it also affects ATC options ........ one could conjure up an airac update which would reference the "pseudo" ILS's. or just close appropriate runways.

alex ..... can we wait for 2 years as per KORD Runway Development

i too was seriously excited when i saw the topic !!

sode conditional visibilty lighting (taxiway/runway/approach), not triggerable (aka PAL) as with seattle ..........great news, another step to "integrity".

stan / all can i assume sode windsocks, variable seasons, conditional (not pilot activated) low visibility taxiway / runway / approach lighting,not exactly like seattle but almost is among the feature not listed.

check out the afcads sub-forum at AIG for the many "reworks / updates" of airport parking .... they correct many / most of the discrepancies you are seeing. bottom line ...... airport scenery designers are notorious for paying little attention to the AI functionality.

Tomas Correct .....leaving the AIG plans' activity level at 1% for all flights, (as you wrote above) you will see all nearby traffic with any sim traffic slider setting > 0. The use of "randomise" limits the spawning of traffic to those with activity levels < the sim's traffic slider setting (ie a plan of an individual flight with say 20% activity won't show if the sim's slider is set at 15%) In effect, randomise is reducing the reals being shown, so not what you want i suspect. I leave it to Ray to comment on reducing sliders as his rig is similar, mine's a tad humbler ..... but I believe he is talking about autogen & scenery density reductions to compensate for the load introduced by AI (5 fps for me at KSFO).