jsmcwilliam

The plot thickens! I have installed Little NavMap but it will take me a little time to acquaint myself with how it works. I have flown a Lang1C departure EKCH/EHAM and EKCH/ESSA departure without problem so the problem seems to be limited to EKCH/EGCC and specifically ODN departures. My setup is without third party scenery at present. A while ago I did a flight to EGCC and like you I restarted VoxATC at intervals along the route. My experience was similar, however, I was able to fly into Manchester but the descent profile given by VoxATC was way to late resulting too high altitude on approach followed by a missed approach senario which VoxATC handled satisfactorily. I have since done the following: 1. Moved my installation of Level-D Simulations navdata from my E:\ drive to the recommended sim root directory (p58 in VoxATC manual). 2. Removed the SID/STAR waypoints according to your suggestion above. 3. Ran the indexer and runway numbers utilities. 4. Flew the EKCH/EGCC departure (ODN1C) departure without any hitches. My conclusion is that somewhere along the ODN1C departure there is something (? waypoint) which generates a FATAL ERROR in VoxATC. I would not seem to be a frequency since they were all used during the LANG1C departure and did not cause any problem. I future I will program the my flightplans direct to the transition. I will try the approach to Manchester ASAP to see how that goes. John https://www.dropbox.com/s/002ryqglpuwk7a0/EKCHEGCC01.pln?dl=0 https://www.dropbox.com/s/vfbdn3xcddzbhsk/error.log?dl=0

Hi again. I followed your recomendation and invested in fsaerodata. Unfortunatedly the old error reappeared and I enclose the error.log to see if you can make anything of it. https://www.dropbox.com/s/002ryqglpuwk7a0/EKCHEGCC01.pln?dl=0 https://www.dropbox.com/s/vfbdn3xcddzbhsk/error.log?dl=0 John

Here comes the matching flightplan generated by PFPX. https://www.dropbox.com/s/002ryqglpuwk7a0/EKCHEGCC01.pln?dl=0 and a new error log using the above. https://www.dropbox.com/s/vfbdn3xcddzbhsk/error.log?dl=0 I will look into your suggestions on Monday as I am busy tomorrow. John

My setup has been simplified and now consists of P3DV4 with Voxatc, default scenery, EZCA and my PMDG 737 ngx. I made a fresh install of Voxatc after running repairs on the P3DV4 Content, Client and Scenery. I repeated the ODN2A departure from runway 04R starting at the gate. The FATAL ERROR appeared as expected at the handover from tower to departure just as I was preparing for a left turnout. I enclose the error log here: https://www.dropbox.com/s/vfbdn3xcddzbhsk/error.log?dl=0 As I said before I'm grateful if you can shed light on this problem and find a solution. John

Thankyou for the detail in your reply - I am most grateful for your help. The situation at present is the following. I opted to eliminate your first two suggestions by reinstalling P3DV4.4 with the default scenery + Orbx Global. I did not installed my FlyTampa Copenhagen. After that I installed my PMDG 737 ng along with FS2Crew, EZCA 3.0 and VoxATC. Active Sky is on a remote and my Navgraph data came from AIRAC 1218. I checked to see that everything was working and tried a test flight EKCH-EGCC using the ODN1C departure from runway 22R ( FS2Crew was not used). I noted the following: 1. VoxATC seemed to work on the ground, however, the taxilights did not appears after taxi clearance. 2. After takeoff I was asked to switch to the departure frequency and after responding the old FATAL ERROR appeared. I continued flying the departure and did not disable VoxATC. 3. I could hear other aircraft communicating with ATC but could not hear its response. I restarted Vox and was asked to contact Center. Again, my response after fequency change caused the FATAL ERROR. 4. The flight was terminated. I tried a new scenario, EKCH-ESSA from runway 04R. This worked without any problem. (On the other hand, I have previously tried an ODN1C departure from 04R with a similar result to the above.) I then tried a flight EKCH-EHAM from runway 22R using a Lang1C departure. Again, no problem. So the runway does not seem to be the problem, rather the departure chosen. I enclose an old error log: https://www.dropbox.com/s/vfbdn3xcddzbhsk/error.log?dl=0 If you want I can do a rerun of the EKCH-EGCC ODN1C departure and sent you an updated error log. John

Hi, I run voxATC ver 7.42 under Windows 10 and P3DV4.4. I have Orbx Global Scenery, Base, Vector and Landclass with REX Airports HD and Orbx ESSA. I also have FlyTampa Copenhagen (EKCH). My navdata is version Airac 1812. I just did a second flight EKCH-EGCC with my PMDG 737 ng and had the same problem in both cases. I was on a Odin 2A departure from runway 04R (Flytampa scenery). VoxATC was up and running and everything seemed to be normal. When I got to CH368, 6000ft. I changed frequency to 119.90 (Kastrup departure) as requested. At CH 371 I was asked to contact Center on 119.42 and got a Fatal Error as a result. I have the error log for that phase if anyone is interested but right now I haven´t figured out how to include this as an attachment. I tried again at the end of the departure procedure (ODN) and the same error asked me to disable VoxATC. I continued my flight without VoxATC, however, at LIBSO (beginning of approach to Manchester) I was able to restore contact with ATC again and fly the approach ROSUN1G to runway 24R. My instructed descent was way to late, however, and I had to declare a missed approach. This worked and I was able to land using VoxATC. I would be grateful for your comments on this – is it scenery related and how do I fix it. On the second flight I added the line: <DescentRatio Value="3.5 /> to the VASettings file but it did not seem to have the desired effect. I have since noted that my FlyTampa Copenhagen scenery had only one runway available in the P3DV4 scenario planner so I deleted the scenery.cfg file and allowed it to regenerate. This had the desired effect as far as available runways are concerned but did not eliminate the FATAL ERROR in VoxATC. If anyone has suggestions I would be most grateful. John McWilliam

Hi, I just did a second flight EKCH-EGCC and had the same problem in both cases. I run the latest VoxATC on P3Dv4 under Windows 10. I was on a Odin 2A departure from runway 04R (Flytampa scenery). When I got to CH368, 6000ft. I changed frequency to 119.90 (Kastrup departure) as requested. At CH 371 I was asked to contact Center on 119.42 and got a Fatal Error as a result. I have the error log for that phase if anyone is interested. I tried again at the end of the departure procedure (ODN) and the same error asked me to disable VoxATC. I continued my flight without VoxATC, however, at LIBSO (beginning of approach to Manchester) I was able to restore contact again and fly the approach ROSUN1G to runway 24R. My instructed descent was way to slow, however, and I had to declare a missed approach. This worked and I was able to land using VoxATC. I would be grateful for your comments on this – is it scenery related and how do I fix it. On the second flight I added the line: <DescentRatio Value="3.5 /> to the VASettings file but it did not have the desired effect. I have since noted that my FlyTampa Copenhagen scenery has only one runway available in the P3DV4 scenario planner so I deleted the scenery.cfg file and allowed it to regenerate. This had the desired effect as far as available runways is concerned but did not eliminate the FATAL ERROR in VoxATC. If anyone has suggestions I would be most grateful. John McWilliam

Thanks for that. I corrected the sound source in the sim settings and turned off "voice". Now it works and I can hear everything. John

Followed the above suggestion but the VoxATC voices still cannot be heard unless the sim sound is turned off. Moving the sliders to the right in Voice Configuration did not, therefore, solve the problem. When I listen to ATIS it is the sim voice I hear. If I turn the sim sound off I hear the VoxATC voice!! I can turn the sim voice off in the sim settings, however, it is not then possible the hear ATIS at all. There seems to be a conflict regarding the sound output to my earphones and whereas the sim sounds work even together with FS2Crew this is not the case with VoxATC. To date turning the sim sound off seems to be the only solution, however, this is not very realistic. Any further comments will be gratefully received. John

Thanks, should have seen that option. John

I’m new to this program and have difficulty in hearing ATC - I have to turn sim sound off (Q) in order to understand ATC. I have minimised voice and engine sounds in P3Dv4 but this has not helped. I use FS2Crew and can adjust it’s volume to be heard over other background noises and would like to be able to do the same in VoxATC. Any suggestions? I run under Windows 10 with headphones, no speakers. John

Could you explain that in more detail John McWilliam

I have been struggling to get VoxAtc 7.42 up and running. The concept is good but there are too many problems with it - bugs, poor support, conflicts with other programs etc. The manual didn’t explain how to create a flight plan very well but in the end I managed to solve the conundrum by creating a .pln file in pfpx and importing it into the flight planner in P3Dv4 and from there loading it into my scenario. The end result was a reasonably successful IFR flight with my Q400 in P3Dv4 with Active Sky, Ultimate Traffic 2, EFB 2, EZCA and FS2Crew. It started at a standard airport (esmq). I found I had to start FS2Crew first otherwise I lost the voices of the copilot, cabin crew etc. It ended at an Orbx airport (essa). As soon as I left the runway VoxATC went silent so I never got taxi instructions or a gate - was this a conflict with the scenery file? I then tried a flight from my FlyTampa Copenhagen Airport. I followed the above flight planning procedure but as soon as I enabled VoxATC I lost contact with FS2Crew - scenery problem? So now I am on the verge of abandonning VoxATC and returning to live VATSIM. The alternatives Pilot2ATC, VoxPro X etc try to do much and not as well as the addons listed above. Reliable and consistent ATC is all that is missing in my cocktail of addons and VoxATC seemed to be the answer. Maybe further developement will make this an attractive option. John McWilliam

Does anyone know how to run these two programs with one mic? I have a remote setup for Pilot2Atc which demands a mic on that machine wheras Fs2Crew which runs on the sim pc requires the mic to be plugged in there! John

Is there anyone out there who has a remote setup of p2atc and runs FS2Crew. I would be interested to know how this is done. FS2Crew requires the mic to be plugged into the sim pc whereas P2Atc requires the mic to be plugged into the remote. John

I run P3DV4 unders Windows 10 and have just had to repair my P3DV4 Client and Content files. When I tried to start FS2Crew for my PMDG 737 I have background sound but the audio test does not produce any sound and the flight officers voice is absent. I use a headset and have set my audio output to "Speakers (Realtek High Definition Audio) in both FS2Crew cfg and P3DV4 sound but this has not helped. FS2Crew is set for voice and the system check shows no errors. The Windows 10 Realtek HD Audio Manager has speaker config set to Stereo and the test produces sound in both L & R headphones. I have also tried setting these to Realtek Digital Output (Realtek High Definition Audio) -same result. Can some kind soul give me the info necessary to overcome this problem. John McWilliam

Thanks for the response. 1. Checked the manual and the response is under Before Start Checklist: "Free and Zero",however, this does not register as green text and I have to use "Set & Checked" to get past this. Not a major problem. 2. OK 3. OK Thanks again.

1. I run under Windows10 and have recently upgraded to P3DV4 with the assoc. PMDG 737 and FS2Crew. During the before start checklist when asked for Rudder and Aileron Trim there was no response. The response: Set and Checked got me past the problem. 2. Into the Initial Climb I was asked twice if the I was "Happy to release the cabin". After that no problem. 3. After setting STD pressure there was a repeating voice: "Altimeter setting". I managed to stop that by switching to local pressure and back a couple of times. Your comments would be interesting! John McWilliam

I love this aircraft and have flown it for several years on FSX. Now I have aquired Prepar3D and wonder if I must purchase this addon again - it looks so on the webb site - or is there any reduction for FSX owners? John

The FO preflight is completed normally as are the successive checklists. The problem is with the FA who never appears and delivery of the load sheet, closing the cabin and external doors etc. If I do these manually the flight can be completed normally.

I have been running the latest version for about two weeks and note the following in connection with a short turn around: 1. The cabin crew do not appear i.e. they don´t ask if they can start boarding and are absent throughout the the flight 2. Load sheets are not delivered 3. Doors are not closed The FO seems to function fine and the flight can be performed in spite of the missing cabin crew. I note that someone else has a problem with the FO, however, this may be a different problem requiring a different approach.

I run FSX-acceleration on a Windows 7 (64-bit) PC and am learning the Q400 together with FS2Crew. I have an irritating reply on one of the checklists which wants to confirm that the APU is OFF. I do this by pressing the PWR button on the APU which I understand is the correct method, however, FS2Crew always comes back at me with "Are you sure?" Why, what have I omitted.? /JSMcWilliam/

I fly NGX 800/900 WL frequently and I have never had this problem before and have been using it successfully together with FS2Crew and FSiPanel. After Installing the Majestic Q400 and its FS2Crew as well assoc. Navgraph data it has ceased to give guidance information. Should I reinstall or is there another explanation? jsmcwilliam

Copied some data onto the spreadsheet for you to check out before I continue. There did not seem to be a way of saving the changes so I don't know if you will get them. Sent a mail at the same time but uncertain if it goes to the right person and for that reason am write you again here. Questions: 1. In order to get my gross weight down to 15000 lbs I had to remove all passengers and bagage and could not carry enough fuel to get to FL260 (200l). I topped up after reaching FL230 with 60l and had 47l still in the tank at FL260. Is this the right procedure? 2. Unsure whether ASN installed the right ISA profile. The cabin indicated a TAT of -37C at FL260 and according to my manual profile in ASN I should have had -42.5 at FL240 and -54.4 at FL300 i.e. approx --45C. however, this may be a misunderstanding on my part. How can I check this and should FSX weather be set up for "User defined weather"? JSMcWilliam (SAS1629)

Thanks again. I think I can start now and plan to begin with 15000 lbs@98%. It will take me a few runs to finetune the procedure so don't expect any results to be posted for a day or two. JSMcWilliam (SAS1629)