Jump to content


  • Content Count

  • Donations

  • Joined

  • Last visited

Community Reputation

37 Neutral

About dcgator29

  • Rank
  • Birthday 01/28/1983

Profile Information

  • Gender
  • Location
    Tampa, FL

Flight Sim Profile

  • Commercial Member
  • Online Flight Organization Membership
  • Virtual Airlines
  1. Whatever was done in April to the mouse detection or mouse movement really messed things up. FSX always had the FPS drop when using mouse look, but P3D seems to have fixed it. It was fine months ago when I first got Chaseplane. But now the dreaded 10-15 fps drop is back with P3D and recent builds of Chaseplane. This is really bad for me because I use a Gsync monitor. Gsync only works above 30fps. When using mouse look with Chaseplane, the fps drops below 30fps, making screen tearing absolutely horrendous.
  2. Rudder trim is mapped to an axis or some other key
  3. Alaska flying is a little more risky than elsewhere; mountains, weather, etc. Alaska Airlines ha a submitted and gotten approval for its own approach and departure procedures. I guess they've proven that their pilots are proficient in flying the tighter procedures. They're property of the airline and not published. Someone managed to get some of them from the airline and they're on avsim in the library. Juneau in particular is surrounded by terrain. The procedures probably fly closer to terrain than normally allowed and save thre airline a lot of money, but Alaska has adequately proven they have and maintain the equipment to safely fly them.
  4. Any ideas? Perhaps track down the FBO owner and get him to add repair facilities? Or is my only hope to sell the aircraft back to FSE?
  5. One of my aircraft has been at a small airport for 2 months, unflown. It now needs a repair but there are no repair facilities at the airport. What are my options for getting it flying again?
  6. FSX is heavily CPU dependent. Most people who are running FSX, and P3D as well, are running their processors over 4.0 GHZ at least. The current gen i-5's and i-7's get more power from equivalent hz, so they don't have to overclock as much, but even then they're running over 4 ghz. You have an older processor. 3.3 stock just isn't going to cut it. I'd suggest a few things. Get rid of lens flare. Disable aircraft shadows on itself definitely. Maybe even aircraft shadows period. Do you see those shadows on final? You may need to drop a notch of autogen to sparse. Do you see trees at the flight levels in PMDG? Ground scenery shadows, nope can't have those. Shadows and autogen are all wasted cpu cycles. Do you want eye candy or fluidity with PMDG? You can't have both, at least to extremes. With a less demanding aircraft you may be able to increase this stuff. You have to compromise though with PMDG. Your config looks good with one exception. It's been awhile since I read up on buffer pools, so please someone correct me if I'm wrong. But i think with buffer pools off; ie Usepools=0, there is no reject threshhold. Remove that. And poolsize=0 is obselete as well. Usepools=0 is all you need to turn it off.
  7. The only one that matters to me is physical gate in the sim. Load the airport in ADE and pick a gate. The gate number in ADE will be the gate number you choose when loading FSX. I get gate numbers from flightaware. Also it's not difficult to find out what gates different airlines use. I don't think anyone really uses the gate when setting up the FMC. It doesn't really matter and it may not match what you see at the addon airport in the sim. AIRAC data doesn't matter, PMDG's sid/star data doesn't matter. What matters is the airport addon and BGL, which doesn't get updated when airac does because the addon is static unless they update it. Where does the EFB get its data from? It doesn't matter if it doesn't match what you see in the sim. If ADE doesn't match what you loaded in FSX then you didn't open the correct BGL. You may have an updated BGL somewhere that FSX is loading. Gate numbers probably aren't updated at all in the AIRAC. You could always add the gates in PMDG's file. Bring up KMCO in google maps. Gate 12 is an AAL gate in the NW terminal, which matches T2G's addon if you use that. The EFB is probably using the same BGL FSX is. FSX's default gates for KMCO don't match at all. I bet you could find an updated BGL on avsim for KMCO if you don't have T2G.
  8. I'm far from an expert but I'll provide what info I know. ILS are the standard approaches because most aircraft have them and they follow the standard 3 degree guideslope. In good weather atc will often vector you onto final and it's your choice if you follow the ILS or fly a visual approach. The cat II and III ILS's have lower minimums used for bad weather and autolandings and as such the radios on the aircraft are under stricter rules and inspections. There must also be failure redundancies on board. On a cat 3 approach in zero visibility, your ILS radios can NOT fail. Here is a good video on cat approaches; long and dry but good if you're interested. http://forum.avsim.net/topic/440291-cat-iii-instructional-video/#entry2972723 Sometimes the vertical glideslope component of an ILS is out at the airport. You would only be able to follow the localizer then. You'll notice for LOC only the mimimum is higher. RNAV is simply a GPS approach. Some commercial aircraft have an FMS/CDU/GPS, some don't. Some may have that equipment but not the approach in the database. RNAV approaches are gaining in popularity but the status quo is to still offer an ILS as the least common denominator. You also notice the RNAV approaches don't generally provide alternate approach fixes. This is where you start the approach, no exceptions. The RNAV approaches have different letter designators X, Y, Z for different initial approach fixes (IAF), missed approach procedures, and decision heights/altitudes. RNP is required navigation performance. It's simply a measure of how precise your GPS can calculate your position. On your PFD you should see RNP/ANP; required and actual navigation performance. You'll see on RNAV Y a RNP .10 and .30 DA; ANP must be within 1 tenth and 3 tenths of a nautical mile. On that Y approach, you see how the descent path are GPS fixes with altitudes. There's no ils signal or glidepath the aircraft is following. The FMS is calculating a descent based on those fixes. Again your FMS must be updated with the approach and fixes to follow it; again why an ILS approach is the least common denominator. The X approach I guess is simply less precise; no RNP requirements so the DA is much higher. It also has a missed approach that turns to the right, which is likely only possible if you've gone missed sooner at a higher altitude. X would likely be used in better weather. This brings us into LPV. LPV is localizer perfomance with vertical guidance. It's like a virtual ILS glideslope. Your aircraft and gps must be able to utilize it. LPV should designate on the PFD. If not, you must follow the decision altitude for your approach; LNAV/VNAV, or LNAV. On the LDA approaches. It stands for localizer type directional aid. It is used when the localizer signal does NOT line up directly with the runway. If you look closely on the LDA 28 approach, it is offset to the right of the runway. It is likely a backup if the main ILS fails. The LDA can get you close enough to the runway that you can land visually. Often terrain is the reason for an offset localizer; you simply can't fly straight in because of a hill. Juneau is an example of this. Hope this helped some. If anything is wrong or not completely correct I'm sorry and hopefully someone can correct or elaborate. The RNAV GPS approaches are designated that way to provide for commercial aircraft FMS's as well as panel mounted GA GPS receivers.
  9. American needs to scrap the aging MD-80,83 fleet. They're working on it with more 737 purchases but it's not going fast enough. I hate flying on them and will choose another flight for that specific reason.
  10. Airport Design Editor. Open the airport BGL and you'll see all the info about the airport; parking spaces, names, airline codes assigned, taxiways, runways.
  11. UTX is not mesh. It is vector and landclass just like Orbx Vector/LC. Like others have mentioned, Fsgenesis and FSGlobal Ultimate are mesh products. Pilot's natually recommends and guarantess compatibility with their FSglobal mesh when using Orbx Vector.
  12. I believe during cold and dark you hold the menu button down a few seconds so you can get the setup menu for external power.
  13. You're 16 so a little naive in the ways of the world. You can absolutely trust the security of online transactions, unless it's from a shady site, which PMDG or any of the several addon sites certainly are not. There are quite literally millions of safe online debit/credit card transactions every day around the world. Online transactions are the status quo in the modern world. No barter system online, no cod, none of that. If you want PMDG you're going to have to figure it out. Maybe get someone else to purchase for you with a debit/credit card or prepaid.
  14. Carenado likely doesn't care about risk in P3D because laws may be different in Chile. Developers in the US or Europe; another story.
  • Create New...