pccitgo

I have made good progress by completely reinstalling VOX Atc. I may have missed hitting setup.exe and hit the msi file by mistake. Anyway it initialises well now. I even have the Vox Pop voices working. Only problem is no other traffic around as I have turned off the Traffic in UT2. If I dont here from the developers I might try experimenting to see what happens if I let UT2 generate some company for me. :-)

I managed to do the VFR tutorial flight. It all went OK until I got to the destination. In real life I would have changed to the Eppley airport ATIS about 10 minutes out to get the QNH and runway in use but that option was not suggested by the Vox ATC until quite late in the flight. Not sure how to do that earlier - is there a way?I think I missed the OVR VOR by a about a mile and therefore got no landing instructions until I reset VOX Atc. Then it went OK.I read a post that you made to another user regarding Ultimate Traffic 2 and some sort of utility. I have sent a message via the webpage requesting that but I havent heard from them after the first post I sent them about 3 days ago. Thanks for your help so far. I did as you suggested re the exe files. I still cannot get the program to initialise unless I right click the VOXATCServer shortcut and run that. When I do that the VoxATC box changes from "Initialising" to " 6.05 initialising" and then it works. Very strange.

Problem solved, I think. I went through all the VOX type exe files until I ran VOXATCServer.exe and it initialised at last.I think the problem stems from the fact that when VOX ATC installed the only items in the All Programs Start Menu are:ATC Aircraft Type Name EditorRegister VOX (it is registered)Runway Number UpdateSID STAR WizardVoice ConfigNothing to click on to actually start VOX AtcCheers and thanks for helpPeter

No. I just load the VOXVFRKansas City Eppley flight and accept the default aircraft. I tried writing and saving a new flight plan but the problem remains. I also disabled UT2 just in case that was the problem. Same problem there.

I am trying to run VOX ATC just using the VFR Kansas City to Eppley flight which of course loads with the appropriate flight plan. I have configured the microphone and speech engine (English - US). I have done the speech training successfully using that flight plan in training mode and no problems there.When I select the VOX ATX box from view and then hit ENABLE all I get is the initialising message which does not change at all. There is no indication of a problem so I am at a loss as to what to do next.My system is an i7 3.4 ghz machine with 8 gig ram running windows 7 64 bit. I have Ultimate Traffic 2 installed but have turned down the aircraft traffic sliders in FSX to zero.Any help to make this work would be much appreciated as I cant do much with VOX ATC as it stands. I have followed all the steps in the manual right up to click Enable in the VOX ATC pop up screen.Peter

Excellent response. That sounds like the way forwardsPeter

Any chance of a reply on this. RC 4 is last part to finish setting up new computer

Many thanks for the info. I did not realise that ATC instructions would be included. From memory I have been able to make up flight plans using web based sites that will take a real life flight plan and turn out a FSX usuable .pln file. Not sure about converting that to a .rte file yet but I sure there will a post on this site that explains how.I am just getting back into flight simming after a longer than expected break from it.Cheers,Peter

I have placed the included files in their correct places and set about doing the tutorial. I see it mentions radar vectoring and, as I have RC ver 4.3, I set about loading the required info into that. However where Radar Contact asks for the .PLN file I come unstuck. I only have a .RTE file. Is there some way to obtain a .PLN file for the tutorial?Many Thanks,Peter

Hi Bill,So during the Approach brief the PF would make a statement like:" On going missed we will divert to the Alternate" (LSFB in this case) or "we will make a second attempt and then divert". I would imagine the company operations manual would have something about the number of attempts due to the fuel on board.The missed approach at LSZH stops at AMIKI. With normal Comms I would expect tp be given vectors and altitudes to re intercept the ILS. What would the crew do from there if they did not have Comms and a second attempt looked promising for RWY 14? Looking at the chart I suspect it is to proceed to TRA. Maybe it is compulsory to go direct to the Alternate if one loses Comms? Maybe the pilot could use his cellphone - it happened where I fly from (al beit in VFR conditions)!Peter

Yes, I noticed that but it just gets you to a waypoint, not all the way back round to have another go at the runway. Perhaps because you have a choice whether to divert to your alternative or recircuit to the same runway or even a different one if the runway was blocked by perhaps another aircraft that cant be moved. I just wndered what a real life crew would do in an MD-11 or similar aircraft. I am guessing they would just start putting waypoints into the FMS to get back onto the appropriate approach. Obviously in a place like Switzerland you would need to be careful.Peter

Having flown the RWY14 approach in Zurich a few times now in the PMDG MD-11 I decided to fly a missed approach. The approach plate for the ILS DME Rwy14 CAT II/III shows a requirement to climb on track of 137 deg (ie the rwy heading) to 4000' and then a LH turn at 5.1 miles DME from the IKL beacon to 360 deg track and intercept the the 234 radial ZUE. At 7.8 DME ZUE then continue the climb to 7000'. Cross ZUE and track the 097 radial ZUE to the AMIKI waypoint. Assuming a second attempt at an approach is allowed which I guess it would be if the reason for going missed was something like an obstructed runway for example, what actions do the crew take to perform a second approach? Would we normally set up something in advance to quickly program the FMS or would we just use the autopilot to follow the missed approach route and then make a "Direct To" a suitable waypoint like TRA in this case. I know that in real life such manoevers would be under ATC directions but I presume one has to be prepared in case of Loss of Comms.So my question is what do the real aircrew do to address the MAP before the initial approach? Peter Coveney

Thanks Rob,I sort of guessed it would be something like that but wondered if the program could be "persuaded" to accept the higher altitude somewhere. Seems like it is written in stone to prevent a situation like you say.CheersPeter

You are right about complex. There are over one thousand pages of text that come with this simulation. Plus the documentation that comes with Flight Operations Center, FS2Crew that is a heap of reading. I have flown the PMDG tutorial a couple of times and the FS2Crew for MD-11 twice and am managing to get from departure to destination but it will take a while before I can start flying with failures on or try a VATSIM trip. The FMS is a course in itself. I was unaware it has climb and descent mode indication on the ND so more study on that required. As for the OUT OF RANGE and FORMAT ERRORs I suppose it will all make more sense once I have read and understood the manual for FMS (I hope).To answer the query about the FMS being in descent mode - in the second picture I had actually made it up to my top altitude and was experimenting with coming down to a lower height.ie from FL340 to FL320 (from memory.)Thanks for the help so far. I am sure I will have more to ask soon.Peter

I always thought that when you load a SID or a STAR into the FMS the height for each waypoint in the procedure was automatically followed by the VNAV function of the autopilot if the aircraft was in Profile mode. Do we enter the heights in the altitude window as standby in case of failure perhaps?Peter Coveney