Jump to content

tnorton776

Frozen-Inactivity
  • Content Count

    65
  • Donations

    $0.00 
  • Joined

  • Last visited

Everything posted by tnorton776

  1. My 737NGX FMC indicates Nav Data is out of date. How do I fix this?Thanks
  2. I reset my fsx.cfg upon the many recommendations to do so on these forums, however I am now noticing that on all my planes both stock and addon the ILS cuts out and disappears every time I attempt a standard Cat III auto-land. It has nothing to do with the way im doing it, it is a technical issue. Anyone know why resetting my fsx.cfg would cause this issue and autopilot issues in general? I'm also having issues with auto throttle behaving strangely.
  3. Hi guys, I just followed a great post to http://www.venetubo.com/fsx.html and it made huge positive FPS performance impacts. I've noticed between a 50 and 100% increase in FPS. It seems that resetting the FSX.cfg file every once in a while is probably necessary?
  4. I have noticed the autopilot is extremely temperamental and jerky since the patch and even cuts out violently at times. I almost did a 360 degree barrel roll in 1 second last night it cut out so violently. It was really odd. Non of my joystick or other settings are set remotely close to sensitive, and I have set sizable null zones as well to prevent this sort of thing. I have also noticed the plane bounces quite a bit at addon airports when changing views (namely FSDT's) post 737NGX800-900 patch 1b. but less so at stock FSX airports, although still noticeable. Maybe the contact points got altered a bit or something? Idk. I was thinking it may have been an issue with FSDT's stuff, but I wasn't experiencing the bouncing however till post 1b.Anyone else noticing this? Hope this helps. Thanks
  5. Anyone know of a fix for the jitteriness/shakiness that happens (most noticeable at the wingtips) when FSX Jet aircraft are not at full idle F1? PMDG support stated it may have something to do with the way FSX models jet/turboprop aircraft or contact points etc. Its not game breaking by a long shot nor is It much of an issue, until you notice it, but once you notice it, it looks kinda bad and is like one of those pesky annoyances (EX. a car rattle) that get amplified and never go away once you're aware of it. lol.ThanksTom Norton
  6. I am also having this issue. Highly annoying. Cant land/taxi/take off in any planes at night time except for the NGX due to this issue, borderline game breaking.
  7. Thanks for the info guys, yeap put it in C:FSX and been running way better than (x86) folder.
  8. I mean, PMDG's 737NGX cockpit makes X Plane look like some 5th graders weekend graphics experiment. Aside from their bogus costly download service, I love PMDG and I would have been honored to pay PMDG $200.00 bucks for its 737NGX. Xplane though for a 2012 release is truly quite pathetic.. Flight dynamics are from a different planet, looney tunes, or a combination of both, Runway slopes look like the downtown san francisco road network.. and then they have the gall and audacity to demand 80 friggen bucks? Its beyond laughable, i mean ##### do they seriously take us for? Ultra chumps? I borderline feel like calling up the federal trade commission and having them investigate the X plane scam.
  9. Is awful... Fsx looks and feels so much better and more realistic... Whatever you do, do not waste 80 bucks on xplane 10. It's a piece of garbage. just my humble opinion...
  10. Will it cause any problems not installing FSX to the C:program files(x86) 32bit folder on a 64 bit win 7 machine? I'd like to just do C:FSX so I can avoid all the UAC annoyances and bugs I last experienced when installing the game under the x86 32bit directory.
  11. I am wondering if there is any way to change the tilt angle of the landing / wheel well lights on the PMDG737NGX?Thanks
  12. No i appreciate the help, and I will definetly take your word for it. Just a bit skeptical at first cause i've tried fourm fixes before for various things and it usually in general, breaks something when fixing a problem. I do trust PMDG and I will use this fix. thanks a bunch!
  13. yes it is the take off alarm, and it happens after about 23 - 25,000 + Feet. I wonder why I wasnt pressurized... I guess i must not be setting it correctly, although I have it set to auto?
  14. I greatly appreciate the help, but at the same time I really dont like risky community or 3rd party fixes. The last time I tried that fix youre linking me too it gave me really weird and rapidly fluctuating FPS readings in FSX. All of these 3rd party fixes usually break something at the cost of fixing something else. Has microsofts incompetence regarding this issue gotten the best of them? No patch yet in 2 years? I call their tech support and the person from india that answers the phone doesnt even understand english, its really quite pathetic. I could hardly understand whta she was saying as well, I think she said, with a heavy indian accent, "What is be FSX mean?? Mac wins customer support hands down.....
  15. Anyone know what alarm is randomly going off midflight? I dont see any amber or red warning lights anywhere, and suddenly I just get the overthrottle alarm as if i was on the ground and put N1 at 100% with flaps up. If I press Y and enter slew mode and then press Y again and exit slew mode the alarm goes off. anyone know?
  16. Does anyone know if there is some fix yet for this widespread problem? Its been going on since win 7 release. Fix for uiautomationcore.dll crash to desktop??? Its driving me nuts... I was on a 5 hour flight from OAK to OGG last night and turning from base to final approach i crashed to desktop and just about punched my monitor. ><
  17. appreciated thank you, I read that already however. It doesnt seem to be helping me out. I always have a low pressure light for HYD pump B and the engine 2 N2% never spools up.
  18. Could someone direct me to the engine start procedure in the manual. I always seem to be able to start engine 1 with no problems, but never engine 2. obviously im missing something. Please help! thanks
  19. Reduced wingflex is anything but normal or realistic, for the record. I much perfered it before the hotfixes. I hope they change it back. Wings are not stiff, they flex, a lot.
  20. So you are all saying it should take 30 minutes to climb from FL300 to FL390, when in real life as a passenger we got to FL360 at full load flying from oakland to Chicago midway in about 30 minutes? I timed it, and the pilot came on after about 30 minutes from take off saying we have leveled off at FL360. hmmm lets do some math here. 0 - 36000 feet in 30ish minutes in real life at near full load.... and PMDG NGX 30,000 to 39,000 at 50% load in 30 minutes.... Something doesnt add up.
  21. If that is the case, then why are hundreds of people, including myself, having climb performance issues? Why does the FMC have a selectable 27k take off rating? All my other planes are at their true and proper values and perform correctly. I dont get where you are saying FS numerical inputs are somehow way different than real engine performance numbers. I had this same issue with the Captain sim 727 which was set nearly 6k less per engine than their actual real world value, and when I adjusted the numbers to their proper value, it solved the problem 100%. before I adjusted, I barely could get off the runway with 100% load and a 11,000 feet runway. The 727 is designed specifically for short field take offs even at full load it only needs around 5000* feet. so you tell me. The thrust scalar is set to 1.0 for the NGX. perhaps you had issues with your gulf stream because you did not have your thrust scalar set correctly. Chaning its value will drastically affect the static thrust value. Whatever people, do whatever you want. This fixed the problem for me. It might for you to. whatever.
  22. Basing this on the fact that it took me nearly a half hour to climb 9000 feet from FL300 to FL390 with 30% fuel and 50% passenger load (extremely light plane) before the adjustment, and after the adjustment it only took about 5 minutes, which is far more realistic for that light of a load. Also basing this on the fact of this - http://www.boeing.co...pf_800tech.html That information is directly off of boeings website, and it reads 27300.
  23. no, no reason. It was just a typo. There are thousands of lines of information that the PMDG dev crew has to work on to get this thing flying. I guarantee you that you me, them or anyone is going to input inproper data from time to time when working on so much data and information. They put the info correctly into the FMC and it reads - 27k max thrust take off. If 27k is selectable, then why would the engines only have 24k max? obviously there is a discrepancy.
×
×
  • Create New...