• Content count

  • Joined

  • Last visited

Community Reputation

0 Neutral

Flight Sim Profile

  • Commercial Member
  • Online Flight Organization Membership
  • Virtual Airlines
  1. p2409a

    Flight level 270 - Possible Scam

    Great explanation Chock...makes perfect sense when you explain it, but beforehand seems illogical!
  2. p2409a

    Flight level 270 - Possible Scam

    One UK-based airline was flying into a secondary airport in Nigeria, and had to cancel the route because of the general dishonesty, thieving, violence and scamming going on at every single point in the trip, starting at Heathrow, and then again once inside Nigeria. It began at checkin with the violence, or threats of violence of the Nigerian passengers being asked to pay excess baggage charges for all the crap they'd bought in the UK that they wanted to sell in Nigeria (huge industry: these people are nothing if not 'commercial'!), continued on with the stealing of the VOR beacons and generators close the airport (so the pilots were reluctant to fly for safety reasons), and ended with the cabin crew extremely reluctant to crew the aircraft given the behaviour of the passenger (spitting at them was just one part of it @tooting!) and needing a set of gun-toting security guards to take them from the airport to the crew hotel. The company decided the behaviour of the Nigerians just wasn't worth the risks, even though the fares were astronomical, and on paper, the route was predicted to make millions. Luckily, no-one using FSX has to deal with these problems - the VORs can't be stolen or destroyed, the crew can make their own way to the hotel, and you can avoid weight and balance issues by just setting a few numbers in FSX!
  3. p2409a

    Virtual Pilot 3D - Don't buy it!!

    Interestingly, the site http://www.virtualpilot3d.com/ geo-resolves to Illinois, USA. I initially thought this scam would have come from some 3rd world country with reasonable internet access (Russia, parts of Asia like China, possibly India, but not Pakistan or Iran for example). But it's coming out of the good old USA! I'd love to understand the people who get sucked in and buy it. Obviously they're not serious Flight Simmers, who are usually up on the latest versions of the main Flight Sim software. Maybe it's 'dabblers', or people who indirectly heard about how much fun products like FSX/X-Plane are. The internet can make you quite depressed when you see, for every great 'thing', there's a scammer trying to part you from your cash with dishonesty.
  4. p2409a

    Pmdg Fmc - Writing Sids And Stars Issues

    Old topic I know, but thanks downscc for that tip on using 'NAVAID' instead of 'FIX' in your SIDS/STARS. Saves a lot of hassle associated with getting lat/lons right, and in the right format. Thanks again. Pete
  5. p2409a


    I hope so divingly: unless you set things up using the 'both must match' philosophy, you won't get anywhere at all with Autoland!
  6. p2409a


    There's a lot going on with Autoland on the PMDG 737NGX, and a few forum postings too that go into it in detail. It took me a while to work it all out, but if you're an experienced FSX simmer, and just want the absolute basics in setting up AutoLand (wthout any explanation), here are my steps. First, you will need some data. Note your chosen runway's Length, Altitude, and Direction. You can get Length and Direction from the CDU (Shift 3), via the INIT REF screen. The Altitude is availble from the CDU by looking up the airport (INDEX - NAV DATA - Airport Summary). Then, as you're flying, getting lined up for landing (on a Cat III runway): Set yourself up for an ILS landing. In the radio stack (Shift 4) In the HGS, enter the runway length and altitude and In the NAV radios, enter the ILS frequency into both NAV radios (must match) Change the radial in the Course setting for both Captain and F/O sides (must match) Ensure both your F/O Flight Director (FD) is ON (as well as Capt. side obviously). Keep flying, and when roughly established, click the VOR/LOC button. When closer still, and fully established on the localiser, click the APP (approach) button. Now (critical), switch on both autopilots (A/P Engage section). If you've set things up correctly both A/P Engage buttons will be green/lit, and as you get closer to landing, the primary display will show 'LAND 3', and G/S 'Flare' etc. ready for an autoland. If you are not set up for Autoland, one Autopilot light will extinguish when you switch on the other ie. only one Autopilot active at a atime. The main thing to look out for to know you're set up for Autoland is the 'LAND 3' message. If you had to describe the Autoland setup in just a few ridiculously short words, they would be: Set up your HGS (heads up display) with the correct runway length/altitude AND Set both NAV radios to same ILS frequency. Set up both the Captain and F/O with the same course radials, both flight directors (F/D's) on, and switch both Autopilots on too so they both stay lit. There's of course a lot more technical detail to the Autoland feature, but if you just want to see it in action, follow these instructions. I hope this helps people who just want a fast, no explanation way to set their PMDG 737 up for Autoland - and have fun with this fantastic feature! Pete
  7. p2409a

    Pmdg Fmc - Writing Sids And Stars Issues

    Old topic I know, but was trying to create exactly the same thing: approaches for NZQN. The painful part is inserting all the new fixes (QN775 etc.) - the lat lons needed to be worked out manually. A few 'learnings' from editing the PMDG SID/STAR file for NZQN: 1) You must enter every FIX entered as part of a SID/STAR in the SID STAR file - it's not enough to have them in the waypoints file only. 2) In a STAR, it's invalid to put a TRK xxx degrees between waypoints: the FMC knows what the tracks are anyway (not 100% sure of this, but seemed to remove an error). Also, note the difference between HDG and TRK, and the use of OVERFLY to ensure a waypoint is actually passed over (next procedure eg. turn won't occur till this has happened) 3) For NZQN, the STAR mentions FL ranges eg. above 16000' and below 17000'. The way to code this is 'AT OR BELOW 10000 AT OR ABOVE 16000' 4) The default PMDG SID/STAR files for NZQN have 2 runways (05L and 05R, 23L and 23R). As NZQN has only one 05/23 runway, I took out 05L, 05R, 23L, 23R and replaced them with 05/23 throughout the SID STAR file, and in the airport file too. 5) The FIX lat/lons are in the format 'S 44 23.12345' ie. degrees, and minutes (including seconds) to 5 decimal points. This differs from some other PMDG files where the lat/lons are in the format 'S 44.234098' (degrees with minutes/seconds to 6 decimal points. I made a quick Excel file with macro functions to do this conversions which I found a great help.
  8. p2409a

    Warning Sounds - Why Can't I Hear Them?

    What does this mean? Signing off with your real name?
  9. p2409a

    Warning Sounds - Why Can't I Hear Them?

    If you still can't get your cabin sounds going after updating DirectX, particularly if you have a special sound card or special speakers (eg. subwoofers etc.), here's another thing to check: Go into your soundcard device settings, and make sure you've selected the right speaker configuration for your actual speakers. The soundcard setting application (usually available through control panel) is the place where you tell your soundcard all about your speakers, so it can send the right kinds of sounds, on the right channels, to the right speakers. For my Realtek soundcard (as an example: other soundcard setting apps are similar I believe), and a L/R and Subwoofer speaker set up, I needed to choose '5.1' for speaker configuration. 'Stereo' or 'Quadrophonic' or any other setting (except 'Headphones' - see below) wouldn't cut it. The goal is for your soundcard channels to match your speaker setup. An easy way to test to see if this might be the problem is to set your speaker configuration to 'Headphones' then check whether your FSX cabin sounds come out with this setting (through your headphones). The reason this is worth a go is because you're guaranteed to be able to match your soundcard output to headphone speakers: there are only 2 of them, left and right, no funny business with subwoofers, center speakers or rear speakers etc.! The Speaker Configuration setting often also has a test file to play which runs through sending sound out to each speaker it thinks is there. Play this file, and make sure it repeats the sound on each speaker. Again, if the sound file plays with a 'gap' it's likely your either missing a speaker (so the channel output goes nowhere), or your speaker configuration is wrong. An additional thing to check: make sure you only have 'Optional Speakers' checked for speakers you actually have (and plugged in!). The goal of all this is to make sure your soundcard recognises your speakers (number and type) and can send the sounds from the right channel in your soundcard to the right speaker plugged in to your computer. Like a few other people, I've been sitting on this problem (no cabin sounds in PMDG 737-800 NGX) for a couple of years until today I finally decided to sort it out. I knew it was a setting problem somewhere, because I know they used to work, but re-installing PMDG 737 didn't fix things. Interestingly, I had no problems with my PMDG 747. And yes....this thread is definitely worth a pin!!! Cheers P2409
  10. p2409a


    Yep...the quick fix (without the great explanations in this thread): head to your FMC (Shift-3) click the 'CRZ' button on the FMC reset the cruise altitude to something close to where you actually are. This should then allow you to activate the VNAV button on the autopilot.