hey Benjamin,I run it over WideFS on a 2nd box. Keep in mind one thing though, your ATC voices will now come from that second device so you can eitherA. Run a male-male cable from the audio out on the widefs client to the line in on the wideFfs server so ATC plays through the same speakersorB. Run your voices through the 2nd machine which is exactly what I do... i have a cheap $15 set of speakers dedicated to PFE (and FDC) and they recreate the real world multi hundred dollar headsets perfectly LOL!!! ;)

John, I stand corrected. Pfe's Atc doesn't hand ai planes to next controllers. I got mixed up with them contacting atc. My mistake.

hey Benjamin,I run it over WideFS on a 2nd box. Keep in mind one thing though, your ATC voices will now come from that second device so you can eitherA. Run a male-male cable from the audio out on the widefs client to the line in on the wideFfs server so ATC plays through the same speakersorB. Run your voices through the 2nd machine which is exactly what I do... i have a cheap $15 set of speakers dedicated to PFE (and FDC) and they recreate the real world multi hundred dollar headsets perfectly LOL!!! ;)

Good to hear that that works. I'll probably keep them through the laptop, then I can set the volume of that machine seperately. Thanks for commenting, I think I'm gonna try PFE soon!

I'm currently doing my first flight LPFR-EGKK. One hitch:My flightlpan calls for the EVUR6V SID out of Faro, which involves heading straight for a few nm to FR612 before turning north to EVURA. I went into the airport's SID/STAR page, typed in the name of the SID and set the altitude for 4000, the sid's initial cleared altitude. Then, in the altitude constraint page, the one where you can enter altitudes for each waypoint, I selected EVURA to be the end of the sid. Clearance and take-off went well, with ATC telling me to use the correct SID with the 4000 ft initial clearance. The problem was that after that, I was never cleared to a higher altitude. After turning north to EVURA, I waited for a few minutes at 4000 feet before asking to climb higher due to clouds, and I was cleared to 17000 feet. I was then told to resume own navigation, and continue climbing to 17000. On reaching 17000, I was not cleared any higher, and after waiting for five minutes or so, hit 4 again, and was cleared to 19000. By this time I was on Lisbon center. I hit "position report" by mistake, and then ATC told me I was XX distance from FR612- which I had already passed. I thought PF automatically dropped waypoints that were close the airport? I then asked direct to the proper waypoint, which was acknowledged, but I still wasn't cleared any higher, and I eventually figured out that the "H" key is a better way of changing altitude than the "4" option, and used that to get cleared up to 33000, my cruise altitude, where I am now over the Bay of Biscay. So- I probably did something wrong- any ideas as to what? Starting from a flight plan that includes the SID, after that has been converted by PF2000, what options do I need to enter to get my initial clearance to be 4000, with the ATC continuing to clear me up higher when (before, preferably) I reach 4000? Was this problem mostly due to PFE missing which waypoint I was headed for, or was it my mistake when I set the SID altitude to 4000? thanks

Well that didn't work. I didn't get any descent instructions at all, which means in this whole flight I got no altitude change instructions. I certainly hope I did something wrong. I was using the WILO4C STAR into EGKK, with the following altitude constraints set in PFE: 18000 feet at KATHY and 13000 by GWC. Nothing happened. What's more, while the H+number key worked to increase altitude, the L+number combination refused to ask for a lower altitude, and it was just as if I had pressed the number without hitting L at all. Here's what I did before the flight:1. Made this FS Flightplan

[flightplan]title=LPFR to EGKKdescription=LPFR, EGKKtype=IFRroutetype=3cruising_altitude=33000departure_id=LPFR, N37* 00.51', W007* 57.57',+000024.00departure_position=28destination_id=EGKK, N51* 08.53', W000* 11.25',+000203.00departure_name=FAROdestination_name=LONDON_GATWICKwaypoint.0=LPFR, A, N37* 00.51', W007* 57.57', +000000.00,waypoint.1=FR612, I, N37* 01.45', W008* 04.03', +000000.00,waypoint.2=EVURA, I, N38* 39.53', W007* 55.06', +000000.00, UN873waypoint.3=BIRBA, I, N39* 06.20', W007* 30.43', +000000.00, UN873waypoint.4=PORTA, I, N39* 19.48', W007* 18.09', +000000.00, UN873waypoint.5=RODAP, I, N39* 37.56', W007* 03.54', +000000.00, UN873waypoint.6=BABOV, I, N39* 52.35', W006* 52.24', +000000.00, UN873waypoint.7=BARDI, I, N40* 35.00', W006* 18.08', +000000.00, UN873waypoint.8=ZMR, V, N41* 31.48', W005* 38.22', +000000.00, UN873waypoint.9=NUBLO, I, N42* 39.57', W004* 59.19', +000000.00, UN873waypoint.10=GOKAN, I, N43* 26.44', W004* 31.36', +000000.00, UN873waypoint.11=DELOG, I, N44* 19.44', W003* 59.14', +000000.00, UN873waypoint.12=DESAB, I, N45* 49.49', W002* 57.33', +000000.00, UT176waypoint.13=TERPO, I, N47* 20.56', W001* 55.44', +000000.00, UP87waypoint.14=GODAN, I, N47* 38.31', W001* 57.35', +000000.00, UP87waypoint.15=DIN, V, N48* 35.09', W002* 04.56', +000000.00, UP87waypoint.16=REVTU, I, N49* 35.49', W001* 43.32', +000000.00, UP87waypoint.17=BOLRO, I, N50* 00.00', W001* 41.29', +000000.00, P87waypoint.18=DOM08, I, N50* 07.18', W001* 40.51', +000000.00, P87waypoint.19=DOMUT, I, N50* 15.42', W001* 40.09', +000000.00,waypoint.20=KATHY, I, N50* 31.14', W001* 19.59', +000000.00,waypoint.21=AVANT, I, N50* 49.12', W000* 56.18', +000000.00,waypoint.22=GWC, V, N50* 51.18', W000* 45.24', +000000.00,waypoint.23=HOLLY, I, N50* 53.12', W000* 05.42', +000000.00,waypoint.24=WILLO, I, N50* 59.05', W000* 11.30', +000000.00,waypoint.25=EGKK, A, N51* 08.53', W000* 11.25', +000000.00,

2. Opened PF2000, selected 33000 as the cruise altitude, and opened that flight plan. Then I hit compile, and exited when it was done. 3. Opened PFE, selected the ADV. In the waypoint adjustment altitude window, I set KATHY for 18000, GWC for 13000, and HOLLY for 8000. I set the end of the DP for EVURA, and the beginning of the STAR for DOMUT. 4. In the SID/STAR airport page, for LPFR, I named EVUR6 as the SID for rwy 28, with a completion altitude of 6000 and a transition altitude of 4000. For EGKK, I named WILO4 as the STAR for Rwy 26L, with a minimum altitude of 2000 and a transition level of 6000. As far as I've been able to read up, that should do it. However, this led to PFE not detecting that I had passed the first waypoint, FR612, and then not providing me with any altitude guidance at all for the duration of the flight. What did I do wrong?

HelloDon't touch anything in PF2000 adjust your altitudes from the main screen. Here is the sequence I use

I didn't touch anything in PF2000 besides the select flightplan, the cruise altitude, and the compile flight plan buttons. When I hit compile I did get the connection with PFE so I assume it worked. I don't think starting PF2000 from PFE would make a difference.

I'm currently doing my first flight LPFR-EGKK. One hitch:My flightlpan calls for the EVUR6V SID out of Faro, which involves heading straight for a few nm to FR612 before turning north to EVURA. I went into the airport's SID/STAR page, typed in the name of the SID and set the altitude for 4000, the sid's initial cleared altitude. Then, in the altitude constraint page, the one where you can enter altitudes for each waypoint, I selected EVURA to be the end of the sid. Clearance and take-off went well, with ATC telling me to use the correct SID with the 4000 ft initial clearance. The problem was that after that, I was never cleared to a higher altitude. After turning north to EVURA, I waited for a few minutes at 4000 feet before asking to climb higher due to clouds, and I was cleared to 17000 feet. I was then told to resume own navigation, and continue climbing to 17000. On reaching 17000, I was not cleared any higher, and after waiting for five minutes or so, hit 4 again, and was cleared to 19000. By this time I was on Lisbon center. I hit "position report" by mistake, and then ATC told me I was XX distance from FR612- which I had already passed. I thought PF automatically dropped waypoints that were close the airport? I then asked direct to the proper waypoint, which was acknowledged, but I still wasn't cleared any higher, and I eventually figured out that the "H" key is a better way of changing altitude than the "4" option, and used that to get cleared up to 33000, my cruise altitude, where I am now over the Bay of Biscay. So- I probably did something wrong- any ideas as to what? Starting from a flight plan that includes the SID, after that has been converted by PF2000, what options do I need to enter to get my initial clearance to be 4000, with the ATC continuing to clear me up higher when (before, preferably) I reach 4000? Was this problem mostly due to PFE missing which waypoint I was headed for, or was it my mistake when I set the SID altitude to 4000? thanks

You can use one of two methods to enable the SID. 1. In the SIDs/STARs page enter the SID name and altitude and save. Then tick box " SIDs (DPs ) Active. OR 2. In the altitude constraint page select the end of your SID. If you use 1. you will get ATC vectors (or told to continue own navigation) and climb instructions, when you reach the SID "Alt Comp" altitude OR reach the first waypoint in the flight plan, whichever happens first. If you use method 2. you will get ATC vectors (or told to continue own navigation) and climb instructions, when you reach the SID "Alt Comp" altitude or reach the end of the SID waypoint whichever happens first. I dont include SID waypoints in the compiled flightplan, and don't have this issue. Peter

Andqui,Check in the official forums. I think I read a thread regarding missing altitude instructions.OK her it is http://www.ocs-support.co.uk/forums/viewtopic.php?f=4&t=732&sid=11e8daed43507cebe4ac6b2081f2f45bI think it is a bad installation issue. Anyway, there are links in the thread which should help you.

I didn't touch anything in PF2000 besides the select flightplan, the cruise altitude, and the compile flight plan buttons. When I hit compile I did get the connection with PFE so I assume it worked. I don't think starting PF2000 from PFE would make a difference.

HelloFollowing the screenshots:1: highlight your flightplan and click Convert FS FP to PF2000 2: click on click here to start Proflight2000, once in PF2000 click Select Flight and select the plan you have just converted, click Compile just click through the following screens, do not alter anything else. 3: Once the compile is over click exit, then click on Adjust FS FP for PF2000 Back at the main PFE screen select the new ADV then click on Adjust Waypoint altitudes, SID's and STARS for selected ADV Flight file. Adjust your waypoint altitudes here. See how that works out

It went a bit better this time- I did get cleared to my cruise altitude. I set the 6000 foot restriction on my SID, and last time I must have forgotten to reset my altimeter leading to me not reaching that height.The only gripe I have is that departure didn't clear my to a higher altitude after contact, but waited until I had leveled off at 6000 to trigger my higher clearance. Is there any way for PFE to clear you to higher altitude as you're approaching the initial restriction, as opposed to waiting until you reach it, so you don't have to level off at low altitude?

Edited September 27, 201114 yr by andqui

My only real beef with pfe is when there are cross winds or variable winds, it will keep changing runways on me like every 30 seconds up to five times, I wish as soon as you contact approach you could request a runway for landing, as it is now I believe you have to wait until your handed over to tower to request your runway.

I give up- PFE missed me passing a waypoint in Spain, and for some reason the ctrl+shift+w command to go direct-to is unresponsive. I'm going to completely reinstall.

What I'd like to see is a hybrid of PFE and VOXATC. I love PFE for the regional voices, but I like VOXATC for the ease of use and the sids\stars on the fly. I know that the latest versions of VOX are for FSX only. This would be in a perfect world.

It went a bit better this time- I did get cleared to my cruise altitude. I set the 6000 foot restriction on my SID, and last time I must have forgotten to reset my altimeter leading to me not reaching that height. The only gripe I have is that departure didn't clear my to a higher altitude after contact, but waited until I had leveled off at 6000 to trigger my higher clearance. Is there any way for PFE to clear you to higher altitude as you're approaching the initial restriction, as opposed to waiting until you reach it, so you don't have to level off at low altitude?

Your SID will always have an altitude limit. You can find it in any SID plate. Once PFE ATC has acknowledged that you have reached your SID ceiling they will give you an altitude of their choosing.Here is the initial part of a FP from EGLL to LIMZ:-EGLL 80MID DP 4000 26nmHAWKE FL250 75nmXAMAB FL290 87nmVEULE FL390 112nm Quite often if the airspace is busy I'm not cleared above FL60 until MID (which is actaully quite realistic!!). But sometimes I might even be cleared up to FL170 before MID. Also when there is little traffic PFE ATC will give "No Speed Restriction". So each flight varies. Having said that the step downs usually follow the FP exactly.vololiberista